Maybe this is a silly question, but I'm completely stuck :-(
I have an application, which is sending/receiving JMS messages using Spring JMS MDP, which is running on a WLS 11 cluster (containing one admin and two managed instances). The application is deployed only on the managed instances. So is the JMS stuff: It's deployed to the WLS Cluster.
Now: When starting up the WLS I receive on one of the instances an exception like this:
2012-12-11 14:44:36,508 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'JMSQueue' defined in class path resource [applicationContext-techarch.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException:
Unable to resolve 'queue.AKKResponses'. Resolved 'queue'; remaining name 'AKKResponses'
which causes the startup of the application to fail.
On the second instance, the application start succeeds successfully. (That's the silly point !)
When I log on to Admin Console, stop and start the application again, the EAR starts fine on both instances.
The application keeps up running fine, until I restart the WLS again. At this time the same error reappears.
Does anybody of you have an idea how to prevent that error ?
The same is happening on prod with 1 admin and 4 managed servers (distributed over two machines): The ear starts on one and fails on three managed servers - but there I don't have the permission to restart the ear :-(