You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by yogu13 <yo...@synechron.com> on 2013/03/19 11:09:55 UTC
ActiveMQ 5.8.0 Issue with HTTP Connector
Hi,
We are using ActiveMQ 5.8.0 on JDK 1.6.37 (ubuntu machine). We are getting
the following error... As soon as we get the error the consumer count for
the queue goes to 0 and stops processing of any messages within the queue.
Below is the trace of it
2013-03-19 20:42:00,240 | WARN | /api/message/example |
org.eclipse.jetty.servlet.ServletHandler | qtp1348062170-27
javax.jms.JMSException: java.io.UTFDataFormatException: encoded string too
long: 67966 bytes
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1391)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1319)
at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1798)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
at org.apache.activemq.web.WebClient.send(WebClient.java:251)
at
org.apache.activemq.web.MessageServlet.doPost(MessageServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:447)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:363)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
at
org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:931)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:992)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.concurrent.ExecutionException:
java.io.UTFDataFormatException: encoded string too long: 67966 bytes
at
java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at
org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:799)
at org.apache.activemq.broker.region.Queue.send(Queue.java:721)
at
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:406)
at
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:392)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:282)
at
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:129)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:317)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:135)
at
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:499)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:749)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:241)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
... 1 more
Caused by: java.io.UTFDataFormatException: encoded string too long: 67966
bytes
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:364)
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:323)
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitiveMap(MarshallingSupport.java:62)
at
org.apache.activemq.command.Message.beforeMarshall(Message.java:226)
at
org.apache.activemq.command.ActiveMQTextMessage.beforeMarshall(ActiveMQTextMessage.java:107)
at
org.apache.activemq.openwire.v6.MessageMarshaller.looseMarshal(MessageMarshaller.java:277)
at
org.apache.activemq.openwire.v6.ActiveMQMessageMarshaller.looseMarshal(ActiveMQMessageMarshaller.java:111)
at
org.apache.activemq.openwire.v6.ActiveMQTextMessageMarshaller.looseMarshal(ActiveMQTextMessageMarshaller.java:111)
at
org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:168)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.addMessage(KahaDBStore.java:430)
at
org.apache.activemq.store.kahadb.KahaDBStore$StoreQueueTask.run(KahaDBStore.java:1191)
... 3 more
2013-03-19 20:42:14,480 | WARN | /api/message/example |
org.eclipse.jetty.servlet.ServletHandler | qtp1348062170-30
javax.jms.JMSException: java.io.UTFDataFormatException: encoded string too
long: 185503 bytes
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1391)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1319)
at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1798)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
at org.apache.activemq.web.WebClient.send(WebClient.java:251)
at
org.apache.activemq.web.MessageServlet.doPost(MessageServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:447)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:363)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
at
org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:931)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:992)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.concurrent.ExecutionException:
java.io.UTFDataFormatException: encoded string too long: 185503 bytes
at
java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at
org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:799)
at org.apache.activemq.broker.region.Queue.send(Queue.java:721)
at
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:406)
at
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:392)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:282)
at
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:129)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:317)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:135)
at
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:499)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:749)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:241)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
... 1 more
Caused by: java.io.UTFDataFormatException: encoded string too long: 185503
bytes
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:364)
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:323)
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitiveMap(MarshallingSupport.java:62)
at
org.apache.activemq.command.Message.beforeMarshall(Message.java:226)
at
org.apache.activemq.command.ActiveMQTextMessage.beforeMarshall(ActiveMQTextMessage.java:107)
at
org.apache.activemq.openwire.v6.MessageMarshaller.looseMarshal(MessageMarshaller.java:277)
at
org.apache.activemq.openwire.v6.ActiveMQMessageMarshaller.looseMarshal(ActiveMQMessageMarshaller.java:111)
at
org.apache.activemq.openwire.v6.ActiveMQTextMessageMarshaller.looseMarshal(ActiveMQTextMessageMarshaller.java:111)
at
org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:168)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.addMessage(KahaDBStore.java:430)
at
org.apache.activemq.store.kahadb.KahaDBStore$StoreQueueTask.run(KahaDBStore.java:1191)
... 3 more
Please note that the message comes via the HTTP connector in XML format.
Please do let me know if you need anything else. We experienced the same
error in ActiveMQ 5.5.1 because of which we upgraded to 5.8.0 hoping the
issue would have been fixed.
Thank you!
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
I also see exceptions logged at info level in activemq.log which keep
repeating as if kahadb is continuously trying to persist this message but
unable to write due to the UTF restriction...Below is the log for the same
activemq.broker.TransportConnection.Transport | Async Exception Handler
2013-03-19 21:12:15,863 | WARN | Transport Connection to:
tcp://192.168.100.37:52603 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:20,902 | WARN | Transport Connection to:
tcp://192.168.100.37:52604 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:25,950 | WARN | Transport Connection to:
tcp://192.168.100.37:52605 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:30,994 | WARN | Transport Connection to:
tcp://192.168.100.37:52606 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:36,032 | WARN | Transport Connection to:
tcp://192.168.100.37:52607 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:41,085 | WARN | Transport Connection to:
tcp://192.168.100.37:52608 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
2013-03-19 21:12:46,154 | WARN | Transport Connection to:
tcp://192.168.100.37:52609 failed: java.io.UTFDataFormatException: encoded
string too long: 150073 bytes |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4664877.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP
Connector
Posted by yogu13 <yo...@synechron.com>.
I was able to fix the issue...
The issue was content-type which was being set as part of the HTTP Request.
The HTTP Request had a content type as "application/x-www-form-urlencoded"
we changed it to "text/xml" and the exception doesnt comeup. Perhaps there
is a fork in logic the way data is serialized based on content types.
I accidently discovered it but from what i know there is nothing on this
written in the documentation.
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665359.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP
Connector
Posted by yogu13 <yo...@synechron.com>.
Hi ,
First, Thank you for your time...I do not think directly connecting to MQ
and dropping the message should be a problem as to my understanding it
should still go through the kahadb store via openwire (exception trace)
which in this case is throwing the exception. Unless you marked the message
as a non persistent.
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665127.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re:Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP
Connector
Posted by SuoNayi <su...@163.com>.
I'm Sorry for that I'm using the Java client to send the message.
I never use Servlet to send messages but I can have a try if I have free time.
At 2013-03-25 20:16:25,yogu13 <yo...@synechron.com> wrote:
>Hi SyoNayi,
>
>Can you attach your code?
>
>Regards,
>-Yogesh
>
>
>
>--
>View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665101.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
Hi SyoNayi,
Can you attach your code?
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665101.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
Thats strange!
We use the HTTP Connector of ActiveMQ i.e the producer sends a http request
(RESTful Call) and gets the message converted into JMS Mesage and is dropped
into the queue. Hence the client (producer) doesnt need to have activemq
library with him. The messages sent are persistent in nature as well
I tried reproducing the issue with ActiveMQ 5.5.0 and ActiveMQ 5.8.0 but in
both instances resulted in the above exception.
Can you attach the producer code which you use? i can try and replicate it
for you..
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665045.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by SuoNayi <su...@163.com>.
I have just succeed sending a text message whose payload and a string property are both more than 64K.
Can you ensure your client and broker are using the same version?
At 2013-03-22 15:38:04,yogu13 <yo...@synechron.com> wrote:
>Its the payload which is more than 64K .. the only workaround which i am
>aware of is using BytesMessage instead of sending the information as
>TextMessage.. Is there a way i can send this info as TextMessage ?
>
>Thanks for your time..
>
>Regards,
>-Yogesh
>
>
>
>--
>View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665042.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
Its the payload which is more than 64K .. the only workaround which i am
aware of is using BytesMessage instead of sending the information as
TextMessage.. Is there a way i can send this info as TextMessage ?
Thanks for your time..
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665042.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by SuoNayi <su...@163.com>.
Seems one string property of your message is larger than 64KB.
It's unusual that one message has a property whose size is larger than 64KB.
I guess If it is the payload of the text message rather than a property
it will work as there are some workarounds.
At 2013-03-22 14:49:46,yogu13 <yo...@synechron.com> wrote:
>I understand that there is a limit on the writeUTF8 method provided by
>DataOutputStream class but as i understand that there are workarounds for
>this as well.
>
>My question is why isn't ActiveMQ removing this restriction on 64K limit
>using the workarounds.. To my understanding neither does ActiveMQ call out
>that the max size for the text message is 64K..
>
>
>Regards,
>-Yogesh
>
>
>
>--
>View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665040.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
I understand that there is a limit on the writeUTF8 method provided by
DataOutputStream class but as i understand that there are workarounds for
this as well.
My question is why isn't ActiveMQ removing this restriction on 64K limit
using the workarounds.. To my understanding neither does ActiveMQ call out
that the max size for the text message is 64K..
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4665040.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by SuoNayi <su...@163.com>.
Simply, your message is larger than 64KB.
Take a look at:
http://www.drillio.com/en/software-development/java/encoded-string-too-long-64kb-limit/
At 2013-03-20 20:33:58,yogu13 <yo...@synechron.com> wrote:
>What can be done to get some answers here :)
>
>LEt me know if i am missing out on details.. i searched through various
>forums to only find that people who ended up with this issue never got any
>resolution.
>
>Regards,
>-Yogesh
>
>
>
>--
>View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4664944.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ 5.8.0 Issue with HTTP Connector
Posted by yogu13 <yo...@synechron.com>.
What can be done to get some answers here :)
LEt me know if i am missing out on details.. i searched through various
forums to only find that people who ended up with this issue never got any
resolution.
Regards,
-Yogesh
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4664944.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.