Home
TeamSite
JMS exception with activemq for 7.3.1 Search
MikeMiracle
ENV
TS 7.3.1
OS : RHEL 5.3
Index Server is not starting up . Index log has following error
[07 Aug 2012 10:36:45,485] INFO com.interwoven.hunter.index.IndexServer (Thread-0) - Trying to bind to port 6715
[07 Aug 2012 10:36:45,524] INFO com.interwoven.hunter.index.IndexServer (Thread-0) - Bound to port 6715
[07 Aug 2012 10:36:46,170] INFO com.interwoven.hunter.index.IndexServer (Thread-0) - TeamSite server is up, continuing with initialization of index server
[07 Aug 2012 10:36:46,229] INFO com.interwoven.hunter.index.IndexServer (Thread-0) - Starting Event Listeners
[07 Aug 2012 10:36:46,229] INFO com.interwoven.hunter.index.IndexServer (Thread-0) - Number of JMS topics to listen to: 1
[07 Aug 2012 10:36:46,283] INFO com.interwoven.hunter.index.Listener (Thread-0) - Looking for event system ...
[07 Aug 2012 10:36:47,449] FATAL com.interwoven.hunter.index.IndexServer (Thread-0) - Error in initialization of the Index Manager
java.lang.RuntimeException: Error initializing Listener for Interwoven
at com.interwoven.hunter.index.Listener.(Listener.java:94)
at com.interwoven.hunter.index.IndexServer.startListeners(IndexServer.java:367)
at com.interwoven.hunter.index.IndexServer.start(IndexServer.java:333)
at com.interwoven.hunter.index.connector.TeamSiteConnector.initIndexServer(TeamSiteConnector.java:95)
at com.interwoven.hunter.index.connector.TeamSiteConnector.synchronize(TeamSiteConnector.java:111)
Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:3035. Reason: java.net.ConnectException: Connection refused
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:230)
at org.apache.activemq.ActiveMQConnectionFactory.createTopicConnection(ActiveMQConnectionFactory.java:208)
at com.interwoven.hunter.index.Listener.init(Listener.java:118)
at com.interwoven.hunter.index.Listener.(Listener.java:71)
... 4 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
So I checked the port 3035.
Nothing listening at 3035
[root@aa-rhvm02 bin]# netstat -tulpn | grep :3035
[root@aa-rhvm02 bin]#
Seems ActiveMQ is down . How to start/debug activeMQ ? This is a production machine. Is there any method to do this without disturbing end users ?
Regards,
M
Find more posts tagged with
Comments
Rick Poulin
You can attempt to restart the service from the JMX console:
http://yourserver:8080/jmx-console
. Locate the "MainDeployer" service, then invoke operation redeploy(java.lang.String) with e.g. "file:/E:/Interwoven/ApplicationContainer/server/default/deploy/activemq-ear-5.3.0.ear/". If you're unsure what that path should look like, you can use the listDeployedAsString operation to figure it out.
To troubleshoot, inspect your AppContainer's server.log. Post that snippet back here if you need analysis on any diagnostics you find.
Edit: Trailing slash at the end of the URL is required!
MikeMiracle
Thanks rpoulin.
I am getting following error(in server log) on redeploying activemq (as suggested by rpoulin using jboss jmx-console ). seems broker-config.xml is not correct. I have attached that file.
2012-08-10 10:41:13,810 INFO [org.jboss.resource.deployment.RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/activemq.ear/activemq-ra.rar/
2012-08-10 10:41:13,822 INFO [org.apache.xbean.spring.context.ResourceXmlApplicationContext] Refreshing org.apache.xbean.spring.context.ResourceXmlApplicationContext@142d561: display name [org.apache.xbean.spring.context.ResourceXmlApplicationContext@142d561]; startup date [Fri Aug 10 10:41:13 BST 2012]; root of context hierarchy
2012-08-10 10:41:13,823 INFO [org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader] Loading XML bean definitions from class path resource [broker-config.xml]
2012-08-10 10:41:14,094 WARN [org.apache.activemq.ra.ActiveMQResourceAdapter] Could not start up embeded ActiveMQ Broker 'xbean:broker-config.xml': Unexpected exception parsing XML document from class path resource [broker-config.xml]; nested exception is org.springframework.beans.FatalBeanException: Class [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] for namespace [
http://activemq.apache.org/schema/core]
does not implement the [org.springframework.beans.factory.xml.NamespaceHandler] interface
2012-08-10 10:42:06,137 INFO [STDOUT] org.apache.commons.httpclient.methods.GetMethod@1839648
Rick Poulin
I'm not sure what to tell you.. The only difference I can see between your config and mine is that I'm on 7.2.1 (so it's configured for journaledJDBC instead of kahaDB) and mine's going to a database whereas yours is saving to the filesystem. Google says kahaDB sometimes throws this bogus XML problem when it's actually choking on locking your ActiveMQ file path -- this often is a result of a JMS Thread still running and/or holding the lock on the files. I scanned the JMX console for a way to bounce just the thread pool. There's a JmsConnectionPool with stop() and start() methods, but that didn't generate any messages in my log. You can try using the name='activemq-ear-5.3.0.ear#activemq-ra.rar',service=RARDeployment MBean under "jboss.jca" which also has stop() and start() methods, but this restarted the whole deployment exactly like the MainDeployer, except without redeploying it (if that makes any difference).
That's all I've got.
kailash1
Can you check the the below line in your brokerconfig.xml:
<broker useJmx="true" brokerName="ess.broker1" useShutdownHook="false" >
It should have an attribute "datadirectory" and should look like the below line:
<broker useJmx="true" brokerName="ess.broker1" useShutdownHook="false" dataDirectory="/apps/autonomy/teamsite/ApplicationContainer/server/default/log/activemq">
After making changes run iwreset -ui and also check server.log. If required enable log4j.properties for ActiveMQ
MikeMiracle
Thanks rpoulin & kailash .. Initial suggestion of rpoulin to invoke operation redeploy(java.lang.String) has worked now. ActiveMQ is up and running now
