You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by john bush <jb...@rsmart.com> on 2012/08/09 22:46:00 UTC

after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

After upgrading my app to run on tomcat 7/java 7 from tomcat 5.5 /java 6
without any changes to any active mq client code or active mq dependencies. 
I occasionally get these in the logs.  Just endless loop forever.


2012-08-09 13:24:19,198 ERROR
MulticastDiscoveryAgent-advertise:tcp://localhost:61616:Thread-14
org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent -
failed to process packet: java.net.SocketException: Socket closed

Any ideas, totally stuck here.  It went away for a day and now back.  Very
strange. 



--
View this message in context: http://activemq.2283324.n4.nabble.com/after-tomcat-7-java-7-upgrade-failed-to-process-packet-java-net-SocketException-Socket-closed-tp4654984.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

Posted by john bush <jb...@rsmart.com>.
5.4.0.

When stepping through this it comes down to the socket call in java.
I decided to scrap java 7, for the time being and after seeing Oracle
has moved the EOL of java 6 back from nov 2012 to feb 2013, I think
I'm not the only one having issues with java 7.

I have no idea what the cause, but it scares me enough to wait it out
until next year.

On Mon, Aug 13, 2012 at 12:39 AM, Torsten Mielke-2 [via ActiveMQ]
<ml...@n4.nabble.com> wrote:
> Hello John,
>
> What version of ActiveMQ do you use?
> Does any version of ActiveMQ support Java 7 already?
>
> Or do you possibly receive garbage data on this broker? Perhaps coming from
> an non-ActiveMQ client?
>
>
> Torsten Mielke
> [hidden email]
> [hidden email]
>
>
>
> On Aug 9, 2012, at 10:46 PM, john bush wrote:
>
>> After upgrading my app to run on tomcat 7/java 7 from tomcat 5.5 /java 6
>> without any changes to any active mq client code or active mq
>> dependencies.
>> I occasionally get these in the logs.  Just endless loop forever.
>>
>>
>> 2012-08-09 13:24:19,198 ERROR
>> MulticastDiscoveryAgent-advertise:tcp://localhost:61616:Thread-14
>> org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent
>> -
>> failed to process packet: java.net.SocketException: Socket closed
>>
>> Any ideas, totally stuck here.  It went away for a day and now back.  Very
>> strange.
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/after-tomcat-7-java-7-upgrade-failed-to-process-packet-java-net-SocketException-Socket-closed-tp4654984.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/after-tomcat-7-java-7-upgrade-failed-to-process-packet-java-net-SocketException-Socket-closed-tp4654984p4655037.html
> To unsubscribe from after tomcat 7/java 7 upgrade: failed to process packet:
> java.net.SocketException: Socket closed, click here.
> NAML



-- 
John Bush
602-490-0470




--
View this message in context: http://activemq.2283324.n4.nabble.com/after-tomcat-7-java-7-upgrade-failed-to-process-packet-java-net-SocketException-Socket-closed-tp4654984p4655091.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

Posted by Torsten Mielke <to...@fusesource.com>.
Hello John,

What version of ActiveMQ do you use? 
Does any version of ActiveMQ support Java 7 already?

Or do you possibly receive garbage data on this broker? Perhaps coming from an non-ActiveMQ client?
 

Torsten Mielke
torsten@fusesource.com
tmielke@blogspot.com



On Aug 9, 2012, at 10:46 PM, john bush wrote:

> After upgrading my app to run on tomcat 7/java 7 from tomcat 5.5 /java 6
> without any changes to any active mq client code or active mq dependencies. 
> I occasionally get these in the logs.  Just endless loop forever.
> 
> 
> 2012-08-09 13:24:19,198 ERROR
> MulticastDiscoveryAgent-advertise:tcp://localhost:61616:Thread-14
> org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent -
> failed to process packet: java.net.SocketException: Socket closed
> 
> Any ideas, totally stuck here.  It went away for a day and now back.  Very
> strange. 
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/after-tomcat-7-java-7-upgrade-failed-to-process-packet-java-net-SocketException-Socket-closed-tp4654984.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.