activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: ActiveMQ 5.3 issues with Big IP
Date Thu, 17 Dec 2009 15:41:06 GMT
Hi,

in 5.3 we changed how localhost is treated. Take a look at comments in
this issue http://issues.apache.org/activemq/browse/AMQ-2094. Do you
by any change resolve bigip to localhost in your dns (/etc/hosts or
something)?

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Wed, Dec 16, 2009 at 10:53 PM, vasans <vasanth_subramanian@yahoo.com> wrote:
>
> Hi,
>
> My application has issues with activeMQ 5.3 when used with F5 Big-IP.
>
> It is a J2SE application, running on Solaris and using Spring 2.5.
> Messages are sent from the producer to the consumer through a Big-IP virtual
> server.
>
> If the application is run with activemq 5.1 or 5.2 and through the big-ip,
> everyting is working.
>
> If the application is run with activemq 5.3 and bypass the big-ip,
> everything is fine.
>
> If the application is run with activemq 5.3 and through the big-ip, then the
> following error occurs:
>
>
> org.springframework.jms.UncategorizedJmsException: Uncategorized exception
> occured during JMS processing; nested exception is javax.jms.JMSException:
> Could not connect to broker URL: tcp://big-ip server: port. Reason:
> java.net.SocketException: Broken pipe
>        at
> org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:308)
>        at
> org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168)
>        at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:474)
>        at
> org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:539)
>        :
>        :
>        :
>
>
> Caused by: javax.jms.JMSException: Could not connect to broker URL:
> tcp://big-ip-server: port. Reason: java.net.SocketException: Broken pipe
>        at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
>        at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:283)
>        at
> com.expd.arch.persistence.server.JMXEnabledActiveMQPooledConnectionFactory$1.createActiveMQConnection(JMXEnabledActiveMQPooledConnectionFactory.java:167)
>        at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:227)
>        at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:175)
>        at
> org.apache.activemq.pool.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:125)
>        at
> org.apache.activemq.pool.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:110)
>        at
> org.apache.activemq.pool.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:81)
>        at
> com.expd.arch.persistence.server.JMXEnabledActiveMQPooledConnectionFactory.createConnection(JMXEnabledActiveMQPooledConnectionFactory.java:69)
>        at
> org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184)
>        at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:461)
>        ... 16 more
> Caused by: java.net.SocketException: Broken pipe
>        at java.net.SocketOutputStream.socketWrite0(Native Method)
>        at
> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>        at
> org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
>        at java.io.DataOutputStream.flush(DataOutputStream.java:106)
>        at
> org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:167)
>        at
> org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:237)
>        at
> org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:168)
>        at
> org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:84)
>        at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:74)
>        at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
>        at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
>        at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:263)
>
>
> Here is the spring settings on the producer side
> <bean id="consumerJmsConnectionFactory"
>
> class="com.expd.arch.persistence.server.JMXEnabledActiveMQPooledConnectionFactory"
>                abstract="true">
>                <property name="brokerURL"
>                        value="tcp://big-ip-server: port" />
>                <property name="maxConnections" value="3" />
>                <property name="exceptionListener">
>                        <bean class="com.expd.arch.persistence.server.JMSExceptionListener">
>                                <property name="originCode" value="${repository_location}"/>
>                                <property name="destinationCode" value="CENT"
/>
>                        </bean>
>                </property>
>        </bean>
>
>
>
>
> Is this a bug in the 5.3 version ?
> Thanks in advance for any help on resolving this issue.
>
>
> -----
> -thanks
> -vasans
> --
> View this message in context: http://old.nabble.com/ActiveMQ-5.3-issues-with-Big-IP-tp26819128p26819128.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
View raw message