Yes, it sure looks like this bug. I guess we'll have to wait till 2.4 is out,
do you know when it's coming out?

Thanks a lot


rajdavies wrote:
> 
> Looks like you could have ran into this bug:
> http://issues.apache.org/activemq/browse/AMQ-1308 
>   - you could try a 5.4-SNAPSHOT - which would have the fix in?
> 
> On 11 Feb 2010, at 01:23, packetrider wrote:
> 
>>
>> Hi,
>>
>> We're running ActiveMQ 5.3 in the standalone mode, with HTTPS. We  
>> get an
>> exception indicating that the message is too long: not sure if this  
>> is a
>> bug, or there are some restrictions on the message size.
>>
>> Any help is appreciated
>>
>> Here's the log
>>
>> INFO  - leMessageListenerContainer - Trying to recover from JMS  
>> Connection
>> exception: javax.jms.JMSException: Failed to perform GET on:
>> https://10.111.1.162:61616 as response was: 500
>> DEBUG - content                    - << "<html>[\n]"
>> DEBUG - content                    - << "<head>[\n]"
>> DEBUG - content                    - << "<meta http-equiv="Content- 
>> Type"
>> content="text/html; charset=ISO-8859-1"/>[\n]"
>> DEBUG - content                    - << "<title>Error 500 encoded  
>> string too
>> long: 91169 bytes</title>[\n]"
>> DEBUG - content                    - << "</head>[\n]"
>> DEBUG - content                    - << "<body><h2>HTTP ERROR:
>> 500</h2><pre>encoded string too long: 91169 bytes</pre>[\n]"
>> DEBUG - content                    - << "<p>RequestURI=/</p><h3>Caused
>> by:</h3><pre>java.io.UTFDataFormatException: encoded string too  
>> long: 91169
>> bytes[\n]"
>> DEBUG - content                    - << "[0x9]at
>> java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> org 
>> .apache 
>> .activemq.transport.util.TextWireFormat.marshal(TextWireFormat.java: 
>> 44)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> org 
>> .apache 
>> .activemq 
>> .transport.http.HttpTunnelServlet.doGet(HttpTunnelServlet.java:86) 
>> [\n]"
>> DEBUG - content                    - << "[0x9]at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:693)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 
>> 487)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 
>> 362)[\n]"
>> DEBUG - content                    - << "[0x9]at
>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 
>> 181)[\n]"
>> DEBUG - content                    - << "[0x9]at org.mor"
>> -- 
>> View this message in context:
>> http://old.nabble.com/ActiveMQ-with-HTTPS%3A-message-string-too-long-tp27540958p27540958.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> 
> Rob Davies
> http://twitter.com/rajdavies
> I work here: http://fusesource.com
> My Blog: http://rajdavies.blogspot.com/
> I'm writing this: http://www.manning.com/snyder/
> 
> 
> 
> 
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/ActiveMQ-with-HTTPS%3A-message-string-too-long-tp27540958p27555385.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to