[
https://issues.apache.org/jira/browse/SYNAPSE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705052#action_12705052
]
Ruwan Linton commented on SYNAPSE-536:
--------------------------------------
This has been fixed with the patch on the SYNAPSE-537
> Error while stoping the Synapse server
> --------------------------------------
>
> Key: SYNAPSE-536
> URL: https://issues.apache.org/jira/browse/SYNAPSE-536
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: NIGHTLY
> Reporter: Eric Hubert
> Assignee: Ruwan Linton
> Fix For: 1.3
>
> Attachments: Shutdown.patch
>
>
> Originally reported by Ruwan and confirmed by Hiranya:
> On the latest build I am seeing an error while trying to stop Synapse, by
> killing the process (CTRL+C) on Unix.
> Is this local to me? I do have some local changes but they have nothing to do
> with this I guess. :-(
> 2009-04-25 09:49:40,580 [-] [Thread-9] INFO SynapseServer Shutting down
> Apache Synapse...
> 2009-04-25 09:49:40,582 [-] [HttpCoreNIOListener] INFO HttpCoreNIOListener
> HTTPS Listener Shutdown
> 2009-04-25 09:49:40,583 [-] [Thread-9] INFO VFSTransportListener VFS
> Listener Shutdown
> 2009-04-25 09:49:40,583 [-] [HttpCoreNIOListener] INFO HttpCoreNIOListener
> HTTP Listener Shutdown
> 2009-04-25 09:49:40,584 [-] [Thread-9] INFO MailTransportListener MAILTO
> Listener Shutdown
> 2009-04-25 09:49:40,585 [-] [HttpCoreNIOSender] INFO HttpCoreNIOSender HTTPS
> Sender Shutdown
> 2009-04-25 09:49:40,586 [-] [HttpCoreNIOSender] INFO HttpCoreNIOSender HTTP
> Sender Shutdown
> 2009-04-25 09:49:40,586 [-] [Thread-9] INFO VFSTransportSender VFS Sender
> Shutdown
> 2009-04-25 09:49:40,587 [-] [Thread-9] INFO JMSSender JMS Sender Shutdown
> 2009-04-25 09:49:40,588 [-] [Thread-9] INFO RMIRegistryController Removing
> the RMI registry bound to port : 1099
> 2009-04-25 09:49:40,604 [-] [Thread-9] INFO JmxAdapter JMXConnectorServer
> stopping on service:jmx:rmi:///jndi/rmi://ruwan:1099/synapse
> 2009-04-25 09:49:40,761 [-] [Thread-9] ERROR JmxAdapter Error while stopping
> remote JMX connector
> java.io.IOException: Cannot bind to URL:
> javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in table]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
> at
> javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:572)
> at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140)
> at
> org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseController.java:583)
> at
> org.apache.synapse.Axis2SynapseController.destroy(Axis2SynapseController.java:143)
> at org.apache.synapse.ServerManager.doDestroy(ServerManager.java:252)
> at org.apache.synapse.ServerManager.destroy(ServerManager.java:117)
> at org.apache.synapse.SynapseServer$1.run(SynapseServer.java:88)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in table]
> at
> com.sun.jndi.rmi.registry.RegistryContext.unbind(RegistryContext.java:156)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.unbind(GenericURLContext.java:254)
> at javax.naming.InitialContext.unbind(InitialContext.java:375)
> at
> javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:565)
> ... 6 more
> Caused by: java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
> at sun.rmi.registry.RegistryImpl_Stub.unbind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.unbind(RegistryContext.java:152)
> ... 9 more
> 2009-04-25 09:49:40,772 [-] [Thread-9] INFO SynapseServer Apache Synapse
> shutdown complete
> 2009-04-25 09:49:40,773 [-] [Thread-9] INFO SynapseServer Halting JVM
> Unfortunately I'm not able to reproduce this issue in my environment although
> from looking at the code the obvious reason seems to be the RMI registry is
> shutdown before the JmxAdapter is stopped.
> Attached you'll find a patch which moves the RMI registry stop to a later
> position after stopping the JmxAdapter. This should fix the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
