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 serial
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
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 wrote:
>Hi SyoNayi,
>
>Can you attach your code?
>
>Regards,
>-Yogesh
>
>
>
>--
>View this message in context:
>http://
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.
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 na
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 wrote:
>Its the payload which is more than 64K .. the only workaround which i am
>aware of is us
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://acti
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 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
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 wrote:
>What can be done to get some answers here :)
>
>LEt me know if i am missing out on details.. i searched throug
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/A
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
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/messa
13 matches
Mail list logo
