Excpetion while shutdownGracefully and startMaintenance
--------------------------------------------------------
Key: ESBJAVA-495
URL: https://wso2.org/jira/browse/ESBJAVA-495
Project: WSO2 ESB
Issue Type: Bug
Affects Versions: 1.7
Reporter: Eric Hubert
Assignee: Asankha Perera
Priority: Minor
While calling the mentioned MBean operations the following exception is thrown:
ERROR ServiceBusManager Error pausing scheduled tasks
org.quartz.SchedulerException: you must call createRemoteScheduler or
createScheduler methods before calling getScheduler()
at
org.quartz.impl.DirectSchedulerFactory.getScheduler(DirectSchedulerFactory.java:454)
at
org.wso2.esb.ServiceBusManager.startMaintenance(ServiceBusManager.java:383)
at
org.wso2.esb.ServiceBusManager.shutdownGracefully(ServiceBusManager.java:251)
at
org.wso2.esb.jmx.mbean.ServiceBusControl.shutdownGracefully(ServiceBusControl.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
I guess this is due to additions of handling tasks while going to maintenance
and only happens if the user has no tasks defined. So it doesn't "influence"
the functionality. That's why I have set the priority to minor. But I think the
fix will also be quite simple and not dangerous. So maybe you can fix this for
the final 1.7.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
