thank you , the error was because the deployer team deployed my app without
stoppng the exsisting deployment because of this weblogic could not stop jms
server,after they stpped my app first and then redeploy I never got this
error.
--
View this message in context:
http://activemq.2283324.n4.na
when the broker started, was it able to register mbeans with the
weblogic jmx mbean server?
either the credentials are no longer available on the stop, or the
exception should be trapped.
Is it possible that the credentials for jmx changed?
On 16 February 2011 20:56, fachhoch wrote:
>
> here a
here again the complete stack trace
2011-02-16 14:23:23,797 [[ACTIVE] ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] ERROR
org.apache.activemq.broker.jmx.ManagedRegionBroker - Could not stop service:
org.apache.activemq.broker.jmx.ManagedRegionBroker@1cd726b. Reason:
webl