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


i trying upgrade fedora-commons , tomcat repository, run .jar install.properties used old install of fedora-commons. seems start fine without issues few seconds after start error message in catalina.out:

exception in thread "thread-5" java.lang.runtimeexception: unable start jms messaging client, 5 attempts made, each attempt resulted in java.net.connectexception. messaging broker @ tcp://localhost:61616 not available @ com.yourmediashelf.fedora.client.messaging.messagingclient$jmsbrokerconnector.connect(messagingclient.java:389) @ com.yourmediashelf.fedora.client.messaging.messagingclient$jmsbrokerconnector.run(messagingclient.java:349) 

i found error message in fedora.log, here 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 name 'org.fcrepo.server.server' defined in servletcontext resource [/web-inf/applicationcontext.xml]: invocation of init method failed; nested exception java.lang.runtimeexception: fatal error while starting server 

i not able fedora/admin page can tomcat page. help!

my problem was copying on old files fedora directory before running server startup deploys new fedora.war,fop.war...etc. mixing outdated code new code.


Comments

Popular posts from this blog

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -

javascript - oscilloscope of speaker input stops rendering after a few seconds -