[jira] [Closed] (AMQ-5924) AMQ hangs at socket write in 3.2.2 version under solaris os

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-5924.
-----------------------------
    Resolution: Invalid

Version 3.2.2 is ancient and no fixes would be provided here.  Recommend taking your questions to the users mailing list for help. 

> AMQ hangs at socket write in 3.2.2 version under solaris os
> -----------------------------------------------------------
>
>                 Key: AMQ-5924
>                 URL: https://issues.apache.org/jira/browse/AMQ-5924
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool, AMQP, JMS client
>    Affects Versions: 3.2.2
>         Environment: Operating system : Solaris
> Application Server : JBOSS
> Active MQ version : 3.2.2
>            Reporter: Rama Krishna
>            Priority: Critical
>
> This is a weird issue that has been bugging for us for a long time. 
> To implement Messaging framework, we are using Active MQ 3.2.2 version in our production. During sending of some messages, socket write hangs at a certain point. Part of stack trace pasting here which can be helpful in investigation. 
> Thread-46
>   at java.net.SocketOutputStream.socketWrite0(Ljava/io/FileDescriptor;[BII)V (Native Method)
>   at java.net.SocketOutputStream.socketWrite([BII)V (SocketOutputStream.java:92)
>   at java.net.SocketOutputStream.write([BII)V (SocketOutputStream.java:136)
>   at org.activemq.transport.tcp.TcpBufferedOutputStream.flush()V (TcpBufferedOutputStream.java:109)
>   at org.activemq.transport.tcp.TcpBufferedOutputStream.write([BII)V (TcpBufferedOutputStream.java:89)
>   at java.io.DataOutputStream.write([BII)V (DataOutputStream.java:90)
>   at org.activemq.io.impl.DefaultWireFormat.writePacket(Lorg/activemq/message/Packet;Ljava/io/DataOutput;)Lorg/activemq/message/Packet; (DefaultWireFormat.java:118)
>   at org.activemq.transport.tcp.TcpTransportChannel.doAsyncSend(Lorg/activemq/message/Packet;)Lorg/activemq/message/Packet; (TcpTransportChannel.java:474)
>   at org.activemq.transport.tcp.TcpTransportChannel.asyncSend(Lorg/activemq/message/Packet;)V (TcpTransportChannel.java:290)
>   at org.activemq.ActiveMQConnection.asyncSendPacket(Lorg/activemq/message/Packet;Z)V (ActiveMQConnection.java:1362)
>   at org.activemq.ActiveMQConnection.asyncSendPacket(Lorg/activemq/message/Packet;)V (ActiveMQConnection.java:1336)
>   at org.activemq.ActiveMQSession.send(Lorg/activemq/ActiveMQMessageProducer;Ljavax/jms/Destination;Ljavax/jms/Message;IIJZ)V (ActiveMQSession.java:1440)
>   at org.activemq.ActiveMQMessageProducer.send(Ljavax/jms/Destination;Ljavax/jms/Message;IIJ)V (ActiveMQMessageProducer.java:426)
>   at org.activemq.ActiveMQMessageProducer.send(Ljavax/jms/Message;)V (ActiveMQMessageProducer.java:337)
>   at org.activemq.ActiveMQTopicPublisher.publish(Ljavax/jms/Message;)V (ActiveMQTopicPublisher.java:129)
> There is no specific way to reproduce the above. It is intermittent and happening for every 3 weeks for our customer.
> We have tried at most to find out the root cause. Assuming that there might be some bugs already filed in version 3.2.2 and we are oblivious of that. 
> Is there any socket write issue in 3.2.2 version ? Or Is this a bug in JDK ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)