Bug 680943 - JMS client fails with Connection timed out with a large no. (100) of durable topic subscriptions
Summary: JMS client fails with Connection timed out with a large no. (100) of durable ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-28 15:34 UTC by Kim van der Riet
Modified: 2021-03-16 12:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
Client test script run from qpid/java/tools/bin directory (4.38 KB, application/x-sh)
2011-02-28 15:34 UTC, Kim van der Riet
no flags Details

Description Kim van der Riet 2011-02-28 15:34:01 UTC
Created attachment 481396 [details]
Client test script run from qpid/java/tools/bin directory

When running the JMS client using attached script to measure topic scalability,
the test fails on the 100 test with a Connection timed out error. The test
increases the number of subscribers to a single topic with a single producer
using the progression 1, 3, 10, 30, 100, 300 ..., but has never succeeded
beyond the 30 test. This bug is one of two possible failure outcomes while
running the 100 test. The chance of failure is 100%, however the probability of
this bug's outcome is approximately 50%.


Error when running test Connection timed out
org.apache.qpid.AMQConnectionFailureException: Connection timed out
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:472)
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:246)
	at org.apache.qpid.tools.PerfBase.setUp(PerfBase.java:55)
	at org.apache.qpid.tools.PerfConsumer.setUp(PerfConsumer.java:105)
	at org.apache.qpid.tools.PerfConsumer.test(PerfConsumer.java:222)
	at org.apache.qpid.tools.PerfConsumer$1.run(PerfConsumer.java:301)
	at java.lang.Thread.run(Thread.java:636)
Caused by: org.apache.qpid.transport.TransportException: Error connecting to broker
	at org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:78)
	at org.apache.qpid.transport.TransportBuilder.init(TransportBuilder.java:44)
	at org.apache.qpid.transport.Connection.connect(Connection.java:239)
	at org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:178)
	at org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:396)
	... 6 more
Caused by: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
	at java.net.Socket.connect(Socket.java:546)
	at java.net.Socket.connect(Socket.java:495)
	at org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:74)
	... 11 more

Comment 1 Kim van der Riet 2011-02-28 15:35:19 UTC
The other outcome described above (connection reset) is in BZ680938.


Note You need to log in before you can comment on or make changes to this bug.