ServiceMix wsn2005 doesn't start correctly on SMX3
--------------------------------------------------
Key: SMXCOMP-871
URL: https://issues.apache.org/jira/browse/SMXCOMP-871
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-wsn2005
Affects Versions: 2011.01
Environment: Linux,
JDK Sun 1.6
Reporter: Jean-Baptiste Onofré
Fix For: 2011.02
On ServiceMix 3.4-SNAPSHOT, at startup, the ServiceMix WSN2005 component
doesn't start:
INFO - ComponentMBeanImpl - Initializing component:
servicemix-wsn2005
ERROR - ComponentMBeanImpl - Could not start component
javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:211)
at
org.apache.servicemix.common.SyncLifeCycleWrapper.init(SyncLifeCycleWrapper.java:46)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java:201)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.java:287)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.java:216)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:331)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateComponent(AutoDeploymentService.java:288)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:658)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:63)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:622)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.naming.NamingException: scheme java not recognized
at
org.apache.xbean.spring.jndi.DefaultContext.lookup(DefaultContext.java:131)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.apache.servicemix.wsn.component.WSNComponent.lookupConnectionFactory(WSNComponent.java:255)
at
org.apache.servicemix.wsn.component.WSNComponent.doInit(WSNComponent.java:144)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:205)
... 12 more
ERROR - InstallationService - Failed to start Component:
servicemix-wsn2005
javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:211)
at
org.apache.servicemix.common.SyncLifeCycleWrapper.init(SyncLifeCycleWrapper.java:46)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java:201)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.java:287)
at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.java:216)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:331)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateComponent(AutoDeploymentService.java:288)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:658)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:63)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:622)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.naming.NamingException: scheme java not recognized
at
org.apache.xbean.spring.jndi.DefaultContext.lookup(DefaultContext.java:131)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.apache.servicemix.wsn.component.WSNComponent.lookupConnectionFactory(WSNComponent.java:255)
at
org.apache.servicemix.wsn.component.WSNComponent.doInit(WSNComponent.java:144)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:205)
... 12 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
