Why is JMS messaging client unable to start, with fedora-commons 3.8.1?

328 views Asked by At

I am trying to upgrade my fedora-commons and tomcat repository, so I run the .jar with the install.properties that was used for the old install of fedora-commons. It seems to start up fine without any issues but a few seconds after start up I get this error message in catalina.out:

Exception in thread "Thread-5" java.lang.RuntimeException: Unable to start JMS Messaging Client, 5 attempts were made, each attempt resulted in a java.net.ConnectException. The messaging broker at tcp://localhost:61616 is not available
at com.yourmediashelf.fedora.client.messaging.MessagingClient$JMSBrokerConnector.connect(MessagingClient.java:389)
at com.yourmediashelf.fedora.client.messaging.MessagingClient$JMSBrokerConnector.run(MessagingClient.java:349)

I found an error message in the fedora.log, here it is:

ERROR 2015-06-10 11:41:57.966 [http-bio-8080-exec-23] (ContextLoader) Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.fcrepo.server.Server' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Fatal error while starting server

I am not able to get to the fedora/admin page but I can get to the tomcat page. Thanks for any help!

1

There are 1 answers

2
SketchyTurtle On BEST ANSWER

My problem was that I was copying over all my old files into the fedora directory before running the server startup that deploys the new fedora.war,fop.war...etc. So it was mixing outdated code with new code.