I'd recommend you upgrade to 4.0.2. Though a common cause of 'hangs'
is the broker running out of memory (particularly for non-pesistent
messaging) - try increase the usageManager setting to something large.


On 10/25/06, shital <[EMAIL PROTECTED]> wrote:

i start active MQ and it runs fine for some time. and after sometime if i try
to connect client just hangs and server does not respond.

below is the log from server.log ( I am using activeMq 4.0)
is there any settings i am missing in activeMQ.xml ( i just use default one
but using port 80 instead of default port)
basically i get Socket closed error.

Please help..





2006-10-25 05:02:46,567 [main           ] INFO  BrokerService
- ActiveMQ 4.0.1 JMS Message Broker (localhost) is starting
2006-10-25 05:02:46,568 [main           ] INFO  BrokerService
- For help or more information please see:
http://incubator.apache.org/activemq/
2006-10-25 05:02:47,368 [main           ] INFO  JDBCPersistenceAdapter
- Database driver recognized: [apache_derby_embedded_jdbc_driver]
2006-10-25 05:02:48,280 [main           ] INFO  JournalPersistenceAdapter
- Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at:
/home/spatel/activemq-4.0.1/activemq-data/journal
2006-10-25 05:02:48,353 [main           ] INFO  JournalPersistenceAdapter
- Journal Recovered: 1 message(s) in transactions recovered.
2006-10-25 05:02:48,532 [main           ] INFO  TransportServerThreadSupport
- Listening for connections at: tcp://jms2:80
2006-10-25 05:02:48,539 [main           ] WARN  MulticastDiscoveryAgent
- brokerName not set
2006-10-25 05:02:48,559 [main           ] INFO  TransportConnector
- Connector default Started
2006-10-25 05:02:48,567 [main           ] INFO  TransportServerThreadSupport
- Listening for connections at: tcp://jms2:61613?wireFormat=stomp
2006-10-25 05:02:48,568 [main           ] INFO  TransportConnector
- Connector stomp Started
2006-10-25 05:02:48,568 [main           ] INFO  BrokerService
- ActiveMQ JMS Message Broker (localhost, ID:jms2-1209-1161766965098-1:0)
started
2006-10-25 06:50:47,317 [: tcp://jms2:80] WARN  ManagedTransportConnection
- Failed to unregister mbean:
org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=68
2006-10-25 08:11:54,279 [: tcp://jms2:80] WARN  ManagedTransportConnection
- Failed to unregister mbean:
org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=92
2006-10-25 08:31:43,245 [: tcp://jms2:80] WARN  ManagedTransportConnection
- Failed to unregister mbean:
org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=99
2006-10-25 08:48:03,214 [: tcp://jms2:80] ERROR TransportConnector
- Could not accept connection: java.net.SocketException: Socket closed
java.net.SocketException: Socket closed
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)

8016,1-8      99%

--
View this message in context: 
http://www.nabble.com/active-MQ-does-not-accept-connections-after-a-while-tf2509787.html#a6999120
Sent from the ActiveMQ - User mailing list archive at Nabble.com.




--

James
-------
http://radio.weblogs.com/0112098/

Reply via email to