Re: Problems with UTF-8 encoding.

Hi Raul, Mayank is not the only one with the problem. For example I use JMS native client to send a message and then consume it via the REST API. I post object messages like so: /ObjectMessage message = session.createObjectMessage(new String(mystring.getBytes("UTF-8")));/ /producer.send(messag

Activemq via REST - consumer cannot read JMS options

When consuming from a queue using the built-in REST API. Is there a way to see the properties of the message such as: JMSType, JMSActiveMQBrokerInTime,... Note that the API used looks like: http://:8161/api/message?destination=queue:// Is there anything that can be included in the request to get

Archiving messages for after use while using JDBC on master/slave

Hello, I am using JDBC with master/slave so I am not using the high performance journal. Is there a way to have the messages logged or saved automatically on the file system (so they can be consulted anytime afterwards)? It looks like there is no documentation about that. Thanks. -- View this