RE: Error while stoping the Synapse server
Hi all, I'll have a look at this and will fix it. From the stack it looks like the shutdown order is wrong. Unfortunately I'll be travelling today without having access to the net today, but tonight or tomorrow I'll submit a patch to correct this if no one beats me to it. Regards, Eric > -Original Message- > From: Ruwan Linton [mailto:ruwan.lin...@gmail.com] > Sent: Saturday, April 25, 2009 6:28 AM > To: dev@synapse.apache.org > Subject: Error while stoping the Synapse server > > Devs, > > 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(RMIConnector > Server.java:814) > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > a:572) > at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140) > at > org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseContr > oller.java:583) > at > org.apache.synapse.Axis2SynapseController.destroy(Axis2SynapseController.j > ava: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:2 > 54) > at javax.naming.InitialContext.unbind(InitialContext.java:375) > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > a:565) > ... 6 more > Caused by: java.rmi.NoSuchObjectException: no such object in table > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemot > eCall.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 > > Thanks, > Ruwan > > -- > Ruwan Linton > Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: ru...@wso2.com; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > > - > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org
Build failed in Hudson: Synapse - Tru nk » Apache Synapse - Transports #624
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/624/
--
[INFO]
[INFO] Building Apache Synapse - Transports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from wso2-m2
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from wso2-m2
[INFO] [compiler:compile]
Compiling 65 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/classes
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:1.6.1:jar
[INFO] Copying aspectjweaver-1.6.1.jar to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/lib/aspectjweaver-1.6.1.jar
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
186K downloaded
[INFO] [compiler:testCompile]
Compiling 13 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager; nested exception
is org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
at
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221)
at
org.apache.directory.shared.ldap.entry.AbstractValue.(AbstractValue.java:38)
at
org.apache.directory.shared.ldap.filter.FilterParser.parsePresenceEqOrSubstring(FilterParser.java:385)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseItem(FilterParser.java:440)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:599)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parse(FilterParser.java:675)
at
org.apache.axis2.transport.testkit.filter.FilterExpressionParser.parse(FilterExpressionParser.java:73)
at
org.apache.axis2.transport.testkit.ManagedTestSuite.addExclude(ManagedTestSuite.java:61)
at
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest.suite(HttpCoreNIOListenerTest.java:35)
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
org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:180)
at
org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.java:140)
at
org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:247)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:104)
at
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150)
at org.apache.maven.surefire.Surefire.run(Surefire.java:111)
at sun
Build failed in Hudson: Synapse - Tru nk » Apache Synapse - Transports #625
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/625/
--
[INFO]
[INFO] Building Apache Synapse - Transports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from wso2-m2
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from wso2-m2
[INFO] [compiler:compile]
Compiling 65 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/classes
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:1.6.1:jar
[INFO] Copying aspectjweaver-1.6.1.jar to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/lib/aspectjweaver-1.6.1.jar
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
186K downloaded
[INFO] [compiler:testCompile]
Compiling 13 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager; nested exception
is org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
at
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221)
at
org.apache.directory.shared.ldap.entry.AbstractValue.(AbstractValue.java:38)
at
org.apache.directory.shared.ldap.filter.FilterParser.parsePresenceEqOrSubstring(FilterParser.java:385)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseItem(FilterParser.java:440)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:599)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parse(FilterParser.java:675)
at
org.apache.axis2.transport.testkit.filter.FilterExpressionParser.parse(FilterExpressionParser.java:73)
at
org.apache.axis2.transport.testkit.ManagedTestSuite.addExclude(ManagedTestSuite.java:61)
at
org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest.suite(HttpCoreNIOListenerTest.java:35)
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
org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:180)
at
org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.java:140)
at
org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:247)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:104)
at
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150)
at org.apache.maven.surefire.Surefire.run(Surefire.java:111)
at sun
Re: Error while stoping the Synapse server
Eric, I had a rough look and realized that the startJmxAdapter and stopJmxAdapter methods are not properly positioned, for example the startJmxAdapter is inside a createNewInstance method where as it will only be called when you are starting with starting the axis2 as well. This will not be invoked when starting synapse on an existing axis2 container. However the stopJmxAdapter is called in the destroy method without checking whether we started the instance or not, which will be called when you try to stop synapse even on an environment where you started synapse on an existing axis2 container. This will lead to some issues. At the same time the issue is due to the fact that the SynapseConfiguration.destroy calls the RMIRegistryController#shutdown before the JmxAdapter#stop being called. I will have a further look and fix the issue if you like, or you could of course provide a patch. I also realized that we still have to clear out the shutdown process a bit more, but this particular issue is not directly because of the wrong order. Thanks, Ruwan On Sat, Apr 25, 2009 at 2:51 PM, Hubert, Eric wrote: > Hi all, > > I'll have a look at this and will fix it. From the stack it looks like the > shutdown order is wrong. Unfortunately I'll be travelling today without > having access to the net today, but tonight or tomorrow I'll submit a patch > to correct this if no one beats me to it. > > Regards, >Eric > > > -Original Message- > > From: Ruwan Linton [mailto:ruwan.lin...@gmail.com] > > Sent: Saturday, April 25, 2009 6:28 AM > > To: dev@synapse.apache.org > > Subject: Error while stoping the Synapse server > > > > Devs, > > > > 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(RMIConnector > > Server.java:814) > > at > > > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > > a:572) > > at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140) > > at > > > org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseContr > > oller.java:583) > > at > > > org.apache.synapse.Axis2SynapseController.destroy(Axis2SynapseController.j > > ava: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:2 > > 54) > > at javax.naming.InitialContext.unbind(InitialContext.java:375) > > at > > > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > > a:565) > > ... 6 more > > Caused by: java.rmi.NoSuchObjectException: no such object in table > > at > > > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemot > > eCall.java:247) > > at > > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343) > > at sun.rmi
Re: Error while stoping the Synapse server
My first view was wrong the stopJmxAdapter method is inside the block which checks whether we initialized axis2 instance. So it is OK, but the second argument "SynapseConfiguration.destroy calls the RMIRegistryController#shutdown before the JmxAdapter#stop being called" is still valid. Thanks, Ruwan On Sun, Apr 26, 2009 at 12:44 AM, Ruwan Linton wrote: > Eric, > > I had a rough look and realized that the startJmxAdapter and stopJmxAdapter > methods are not properly positioned, for example the startJmxAdapter is > inside a createNewInstance method where as it will only be called when you > are starting with starting the axis2 as well. This will not be invoked when > starting synapse on an existing axis2 container. > > However the stopJmxAdapter is called in the destroy method without checking > whether we started the instance or not, which will be called when you try to > stop synapse even on an environment where you started synapse on an existing > axis2 container. This will lead to some issues. > > At the same time the issue is due to the fact that the > SynapseConfiguration.destroy calls the RMIRegistryController#shutdown before > the JmxAdapter#stop being called. > > I will have a further look and fix the issue if you like, or you could of > course provide a patch. I also realized that we still have to clear out the > shutdown process a bit more, but this particular issue is not directly > because of the wrong order. > > Thanks, > Ruwan > > > On Sat, Apr 25, 2009 at 2:51 PM, Hubert, Eric > wrote: > >> Hi all, >> >> I'll have a look at this and will fix it. From the stack it looks like the >> shutdown order is wrong. Unfortunately I'll be travelling today without >> having access to the net today, but tonight or tomorrow I'll submit a patch >> to correct this if no one beats me to it. >> >> Regards, >>Eric >> >> > -Original Message- >> > From: Ruwan Linton [mailto:ruwan.lin...@gmail.com] >> > Sent: Saturday, April 25, 2009 6:28 AM >> > To: dev@synapse.apache.org >> > Subject: Error while stoping the Synapse server >> > >> > Devs, >> > >> > 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(RMIConnector >> > Server.java:814) >> > at >> > >> javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav >> > a:572) >> > at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140) >> > at >> > >> org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseContr >> > oller.java:583) >> > at >> > >> org.apache.synapse.Axis2SynapseController.destroy(Axis2SynapseController.j >> > ava: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:2 >> > 54) >> > at javax.naming.InitialContext.unbind(InitialContext.java:375) >> >
RE: Error while stoping the Synapse server
Hi Ruwan, I’m right now back and will have a look at the issue. Your analysis reflects my first thought. The idea was to start the JmxAdapter as early as possible and stop it as late as possible to be able to remote monitor and control the server even if it is in state stopped (e.g. to start it again etc.). But if the RMIRegistry has been destroyed before, it will cause the issue you posted. So I will see whether it is possible to move the call to the shutdown to a later position (after the stop call to the JMXAdapter. As my working copy has a lot of changes, I’ll checkout trunk in a separate sandbox and will provide an intermediate fix for this particular issue first. Sorry for missing this one. Regards, Eric From: Ruwan Linton [mailto:ruwan.lin...@gmail.com] Sent: Saturday, April 25, 2009 9:17 PM To: dev@synapse.apache.org Subject: Re: Error while stoping the Synapse server My first view was wrong the stopJmxAdapter method is inside the block which checks whether we initialized axis2 instance. So it is OK, but the second argument "SynapseConfiguration.destroy calls the RMIRegistryController#shutdown before the JmxAdapter#stop being called" is still valid. Thanks, Ruwan On Sun, Apr 26, 2009 at 12:44 AM, Ruwan Linton wrote: Eric, I had a rough look and realized that the startJmxAdapter and stopJmxAdapter methods are not properly positioned, for example the startJmxAdapter is inside a createNewInstance method where as it will only be called when you are starting with starting the axis2 as well. This will not be invoked when starting synapse on an existing axis2 container. However the stopJmxAdapter is called in the destroy method without checking whether we started the instance or not, which will be called when you try to stop synapse even on an environment where you started synapse on an existing axis2 container. This will lead to some issues. At the same time the issue is due to the fact that the SynapseConfiguration.destroy calls the RMIRegistryController#shutdown before the JmxAdapter#stop being called. I will have a further look and fix the issue if you like, or you could of course provide a patch. I also realized that we still have to clear out the shutdown process a bit more, but this particular issue is not directly because of the wrong order. Thanks, Ruwan On Sat, Apr 25, 2009 at 2:51 PM, Hubert, Eric wrote: Hi all, I'll have a look at this and will fix it. From the stack it looks like the shutdown order is wrong. Unfortunately I'll be travelling today without having access to the net today, but tonight or tomorrow I'll submit a patch to correct this if no one beats me to it. Regards, Eric > -Original Message- > From: Ruwan Linton [mailto:ruwan.lin...@gmail.com] > Sent: Saturday, April 25, 2009 6:28 AM > To: dev@synapse.apache.org > Subject: Error while stoping the Synapse server > > Devs, > > 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(RMIConnector > Server.java:814) > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > a:572) > at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140) > at > org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseContr > oller.java:583) > at > org.apache.synapse.Axis2SynapseControl
[jira] Created: (SYNAPSE-536) Error while stoping the Synapse server
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 Fix For: 1.3 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-536) Error while stoping the Synapse server
[ https://issues.apache.org/jira/browse/SYNAPSE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Hubert updated SYNAPSE-536: Attachment: Shutdown.patch > 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 > 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
Re: svn commit: r768473 - in /synapse/trunk/java: modules/transports/pom.xml pom.xml
Ruwan,
The exclusion rule on axis2-transport-testkit is incorrect:
- It breaks the build (see Hudson).
- axis2-transport-testkit _really_ depends on log4j (to produce more
fine grained log files), so it would be conceptually wrong to exclude
it.
- In the parent POM, there is a dependencyManagement entry for log4j
that excludes the dependency on jmxri => synapse-transports has no
transitive dependency on jmxri.
Andreas
On Sat, Apr 25, 2009 at 07:55, wrote:
> Author: ruwan
> Date: Sat Apr 25 05:55:20 2009
> New Revision: 768473
>
> URL: http://svn.apache.org/viewvc?rev=768473&view=rev
> Log:
> log4j-1.2.15 looks for com.sun.jmx:jmxri:jar:1.2.1 which is not available,
> excluding log4j coming from transitive dependencies to workaround
>
> Modified:
> synapse/trunk/java/modules/transports/pom.xml
> synapse/trunk/java/pom.xml
>
> Modified: synapse/trunk/java/modules/transports/pom.xml
> URL:
> http://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/pom.xml?rev=768473&r1=768472&r2=768473&view=diff
> ==
> --- synapse/trunk/java/modules/transports/pom.xml (original)
> +++ synapse/trunk/java/modules/transports/pom.xml Sat Apr 25 05:55:20 2009
> @@ -185,6 +185,12 @@
> axis2-transport-testkit
> ${axis2.transport.version}
> test
> +
> +
> + log4j
> + log4j
> +
> +
>
>
>
>
> Modified: synapse/trunk/java/pom.xml
> URL:
> http://svn.apache.org/viewvc/synapse/trunk/java/pom.xml?rev=768473&r1=768472&r2=768473&view=diff
> ==
> --- synapse/trunk/java/pom.xml (original)
> +++ synapse/trunk/java/pom.xml Sat Apr 25 05:55:20 2009
> @@ -698,6 +698,12 @@
> wso2caching-core
> ${wso2caching.version}
> jar
> +
> +
> + log4j
> + log4j
> +
> +
>
>
>
>
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
RE: [jira] Updated: (SYNAPSE-536) Error while stoping the Synapse server
Hi Ruwan, I submitted a patch which should fix this issue you reported. Fortunately I was not able to reproduce it locally. Could you please first apply this patch locally and test if it fixes the issue for you! By the way, which log4j configuration are we using if running the server from synapse.sh? There is one directly in the lib directory which does not seem to be used and one in the synapse-core.jar and likely others... There are still a couple of other issues in the startup/shutdown logic you will notice once you call stop and start from ServerManager. I'm working on those issues as well. Thanks, Eric > > [ https://issues.apache.org/jira/browse/SYNAPSE- > 536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Eric Hubert updated SYNAPSE-536: > > > Attachment: Shutdown.patch > > > 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 > > 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(RMIConnector > Server.java:814) > > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > a:572) > > at org.apache.synapse.JmxAdapter.stop(JmxAdapter.java:140) > > at > org.apache.synapse.Axis2SynapseController.stopJmxAdapter(Axis2SynapseContr > oller.java:583) > > at > org.apache.synapse.Axis2SynapseController.destroy(Axis2SynapseController.j > ava: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:2 > 54) > > at javax.naming.InitialContext.unbind(InitialContext.java:375) > > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.jav > a:565) > > ... 6 more > > Caused by: java.rmi.NoSuchObjectException: no such object in table > > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemot > eCall.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
Build failed in Hudson: Synapse - Tru nk » Apache Synapse - Transports #626
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/626/
--
[INFO]
[INFO] Building Apache Synapse - Transports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from apache.snapshots
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from wso2-m2
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from apache.snapshots
[INFO] [compiler:compile]
Compiling 65 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/classes
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:1.6.1:jar
[INFO] Copying aspectjweaver-1.6.1.jar to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/lib/aspectjweaver-1.6.1.jar
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
186K downloaded
[INFO] [compiler:testCompile]
Compiling 13 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager; nested exception
is org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
at
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221)
at
org.apache.directory.shared.ldap.entry.AbstractValue.(AbstractValue.java:38)
at
org.apache.directory.shared.ldap.filter.FilterParser.parsePresenceEqOrSubstring(FilterParser.java:385)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseItem(FilterParser.java:440)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:599)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseBranchNode(FilterParser.java:521)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:580)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parse(FilterParser.java:675)
at
org.apache.axis2.transport.testkit.filter.FilterExpressionParser.parse(FilterExpressionParser.java:73)
at
org.apache.axis2.transport.testkit.ManagedTestSuite.addExclude(ManagedTestSuite.java:61)
at
org.apache.synapse.transport.vfs.VFSTransportTest.suite(VFSTransportTest.java:46)
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
Build failed in Hudson: Synapse - Tru nk » Apache Synapse - Transports #627
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/627/
--
[INFO]
[INFO] Building Apache Synapse - Transports
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-http:1.5-SNAPSHOT: checking
for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking
for updates from wso2-m2
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-utils:SNAPSHOT: checking for updates
from wso2-m2
[INFO] [compiler:compile]
Compiling 65 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/classes
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:1.6.1:jar
[INFO] Copying aspectjweaver-1.6.1.jar to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/lib/aspectjweaver-1.6.1.jar
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
186K downloaded
[INFO] [compiler:testCompile]
Compiling 13 source files to
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-transports/ws/target/surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager; nested exception
is org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
org.apache.maven.surefire.testset.TestSetFailedException:
org.apache.synapse.transport.vfs.VFSTransportTest; nested exception is
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
at
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221)
at
org.apache.directory.shared.ldap.entry.AbstractValue.(AbstractValue.java:38)
at
org.apache.directory.shared.ldap.filter.FilterParser.parsePresenceEqOrSubstring(FilterParser.java:385)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseItem(FilterParser.java:440)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:599)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseBranchNode(FilterParser.java:521)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterComp(FilterParser.java:580)
at
org.apache.directory.shared.ldap.filter.FilterParser.parseFilterInternal(FilterParser.java:637)
at
org.apache.directory.shared.ldap.filter.FilterParser.parse(FilterParser.java:675)
at
org.apache.axis2.transport.testkit.filter.FilterExpressionParser.parse(FilterExpressionParser.java:73)
at
org.apache.axis2.transport.testkit.ManagedTestSuite.addExclude(ManagedTestSuite.java:61)
at
org.apache.synapse.transport.vfs.VFSTransportTest.suite(VFSTransportTest.java:46)
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
org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:180)
at
org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.java:140)
at
org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:247)
at
org.apache.ma
