Hiram,
Here is the activemq log message:
ERROR MulticastDiscoveryAgent - failed to process packet:
java.net.SocketException: Socket closed
Here is the log4j messages when it happens:
[DEBUG] InactivityMonitor - No message sent since last write check, sending
a KeepAliveInfo
[DEBUG] InactivityMonitor - Message received since last read check,
resetting flag:
[DEBUG] InactivityMonitor - No message sent since last write check, sending
a KeepAliveInfo
[DEBUG] InactivityMonitor - No message sent since last write check, sending
a KeepAliveInfo
[DEBUG] InactivityMonitor - Message received since last read check,
resetting flag:
[WARN] ActiveMQConnection - Async exception with no exception listener:
java.io.EOFException <java.io.EOFException>java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:358)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:274)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:142)
at java.lang.Thread.run(Thread.java:613)
[WARN] ActiveMQConnection - Async exception with no exception listener:
java.io.EOFException <java.io.EOFException>java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:358)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:274)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:142)
at java.lang.Thread.run(Thread.java:613)
Thanks Peter
Hiram Chirino wrote:
>
> On 10/25/06, petera <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hiram,
>>
>> I can't ignore the message because it signifies the broker has gone down
>> and
>> so I can not produce and consume messages. I could of course restart the
>
>
> Ah. so your broker is shutting down. Well that message is just a symptom
> of
> it going through it's shutdown process. The question is why is the broker
> going down. Are you sure someone is not killing it? Do the logs show any
> out of memory errors? Typically the broker does not shutdown on it's own.
>
> broker but I can hardly be asking our help desk to do this everytime it
>> happens. Also I can hardly recommend to my bosses that we use a RC when
>> we
>> go into production !
>>
>> I enclose the configuration file I use (ACTIVEMQ.XML) and the CONTEXT.XML
>> files used by the web apps running under Tomcat.
>>
>> Peter
>>
>> ACTIVEMQ.XML
>> -----------------
>> <beans>
>>
>> <!-- Allows us to use system properties as variables in this
>> configuration
>> file -->
>>
>> <bean
>> class="
>> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
>>
>> <broker useJmx="true" xmlns="http://activemq.org/config/1.0";>
>>
>> <persistenceAdapter>
>> <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"
>> dataSource="#postgres-ds"/>
>> </persistenceAdapter>
>>
>> <transportConnectors>
>> <transportConnector name="default" uri="tcp://localhost:61616" />
>> <transportConnector name="stomp" uri="stomp://localhost:61613"/>
>> </transportConnectors>
>>
>> <networkConnectors>
>> <!-- by default just auto discover the other brokers -->
>> <!--
>> <networkConnector name="default" uri="multicast://default"/>
>> -->
>> <!--
>> <networkConnector name="host1 and host2"
>> uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/>
>> -->
>> </networkConnectors>
>>
>> </broker>
>>
>> <!-- This xbean configuration file supports all the standard spring
>> xml
>> configuration options -->
>>
>> <!-- Postgres DataSource Sample Setup -->
>> <bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource">
>> <property name="serverName" value="localhost"/>
>> <property name="databaseName" value="efed-messaging"/>
>> <property name="portNumber" value="0"/>
>> <property name="user" value="activemq"/>
>> <property name="password" value="activemq"/>
>> <property name="dataSourceName" value="postgres"/>
>> <property name="initialConnections" value="1"/>
>> <property name="maxConnections" value="10"/>
>> </bean>
>>
>> </beans>
>> <!-- END SNIPPET: example -->
>>
>> CONTEXT.XML
>> ----------------
>> <Resource
>> name="jms/ConnectionFactory"
>> auth="Container"
>> type="org.apache.activemq.ActiveMQConnectionFactory"
>> description="JMS Connection Factory"
>> factory="org.apache.activemq.jndi.JNDIReferenceFactory"
>> brokerName="LocalActiveMQBroker"
>> brokerURL="tcp://localhost:61616"
>> useEmbeddedBroker="false"/>
>>
>> <Resource name="jms/InvoiceQueue"
>> auth="Container"
>> type="org.apache.activemq.command.ActiveMQQueue"
>> factory="org.apache.activemq.jndi.JNDIReferenceFactory"
>> physicalName="INVOICE"/>
>>
>>
>>
>>
>> Hiram Chirino wrote:
>> >
>> > It looks a message that can be safely ignored. Is there any other bad
>> > behaviours besides the log message?
>> >
>> > I would recommend you try the 4.0.2 release candidate that you can get
>> > from:
>> >
>> http://hiramchirino.com/~chirino/incubator-activemq-4.0.2-RC6/maven1/incubator-activemq/distributions/
>> >
>> > I has had many bugs fixed and much more stable.
>> >
>> > On 10/25/06, petera <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> Hiram,
>> >>
>> >> Thanks for replying. I am using version 4.0.1 on an Apple Mac server.
>> >>
>> >> The problem seems to be the broker going down. Please see my more
>> recent
>> >> post "Broker going down"
>> >> it contains the ActiveMQ configurations I am using.
>> >>
>> >> We are in a testing phase at the moment so I really need to find a
>> >> solution
>> >> soon.
>> >>
>> >> Thanks Peter
>> >>
>> >>
>> >> Hiram Chirino wrote:
>> >> >
>> >> > the remote side of the connection disconnected. What ActiveMQ
>> version
>> >> are
>> >> > you using?
>> >> >
>> >> > On 10/23/06, petera <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> I am getting the following exception being thrown after the message
>> >> >> broker
>> >> >> has been up and running for a while:
>> >> >>
>> >> >> 2006-10-20 20:06:48,381 WARN [
>> org.apache.activemq.ActiveMQConnection]
>> >> -
>> >> >> Async exception with no exception listener: java.io.EOFException
>> >> >> java.io.EOFException
>> >> >> at
>> java.io.DataInputStream.readInt(DataInputStream.java:358)
>> >> >> at
>> >> >> org.apache.activemq.openwire.OpenWireFormat.unmarshal(
>> >> OpenWireFormat.java
>> >> >> :274)
>> >> >> at
>> >> >>
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java
>> >> :142)
>> >> >> at java.lang.Thread.run(Thread.java:613)
>> >> >>
>> >> >> What is the problem ?
>> >> >>
>> >> >> TIA Peter
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >> http://www.nabble.com/Async-exception-tf2493195.html#a6950761
>> >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Regards,
>> >> > Hiram
>> >> >
>> >> > Blog: http://hiramchirino.com
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >> http://www.nabble.com/Async-exception-tf2493195.html#a6992133
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Regards,
>> > Hiram
>> >
>> > Blog: http://hiramchirino.com
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Async-exception-tf2493195.html#a6993608
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>
--
View this message in context:
http://www.nabble.com/Async-exception-tf2493195.html#a6995980
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
