You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Cybexion <cy...@email.de> on 2007/12/18 16:20:58 UTC
Hotdeploy issue - BeanFactory not initialized or already closed -
call 'refresh' before accessing beans via the Application
Hi,
I tought deployment / hotdeployment can be done just by dropping/removing a
jar inside the hotdeploy folder (working with 3.2.1).
However, after undeploying (deleting my jar) of a SA I have to restart
servicemix, before I can redeploy a new jar.
If I just delete the jar (undeploy) and copy a new version into the
hotdeploy folder, I get an error like this:
INFO - DeploymentService - Error in start
java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
start
FAILED
ERROR
servicemix-cxf-se
start
FAILED
ERROR
Unable to start service unit
1
BeanFactory not initialized or
already closed - call 'refresh' before accessing beans via the Application
Context
Does anyone also has this issue?
How and where do I call refresh?
Thanks in advance!
Cybexion
--
View this message in context: http://www.nabble.com/Hotdeploy-issue---BeanFactory-not-initialized-or-already-closed---call-%27refresh%27-before-accessing-beans-via-the-Application-tp14398899s12049p14398899.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Hotdeploy issue - BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the Application
Posted by Chris Custine <cc...@apache.org>.
This was fixed this weekend and should be working in 3.2.2 SNAPSHOT from
SVN. This issue only affected the CXF components.
https://issues.apache.org/activemq/browse/SM-1168
Thanks,
Chris
On Dec 19, 2007 11:56 AM, Cybexion <cy...@email.de> wrote:
>
> Nobody else experiencing this?
> Is Hotdeployment working everywhere?
>
> Regards Cybexion
>
>
>
> Cybexion wrote:
> >
> > Hi,
> >
> > I tought deployment / hotdeployment can be done just by
> dropping/removing
> > a jar inside the hotdeploy folder (working with 3.2.1).
> >
> > However, after undeploying (deleting my jar) of a SA I have to restart
> > servicemix, before I can redeploy a new jar.
> > If I just delete the jar (undeploy) and copy a new version into the
> > hotdeploy folder, I get an error like this:
> >
> > INFO - DeploymentService - Error in start
> > java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
> > <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
> > version="1.0">
> > <jbi-task-result>
> > <frmwk-task-result>
> > <frmwk-task-result-details>
> > <task-result-details>
> > <task-id>start</task-id>
> > <task-result>FAILED</task-result>
> > <message-type>ERROR</message-type>
> > </task-result-details>
> > </frmwk-task-result-details>
> > </frmwk-task-result>
> > <component-task-result
> > xmlns="http://java.sun.com/xml/ns/jbi/management-message">
> > <component-name>servicemix-cxf-se</component-name>
> > <component-task-result-details>
> > <task-result-details>
> > <task-id>start</task-id>
> > <task-result>FAILED</task-result>
> > <message-type>ERROR</message-type>
> > <task-status-msg>
> > <msg-loc-info>
> > <loc-token />
> > <loc-message>Unable to start service unit</loc-message>
> > </msg-loc-info>
> > </task-status-msg>
> > <exception-info>
> > <nesting-level>1</nesting-level>
> > <msg-loc-info>
> > <loc-token />
> > <loc-message>BeanFactory not
> > initialized or already closed - call 'refresh' before accessing beans
> via
> > the Application
> > Context</loc-message>
> >
> > <stack-trace><![CDATA[java.lang.IllegalStateException: BeanFactory not
> > initialized or already closed - call 'refresh' before accessing beans
> via
> > the ApplicationContext at
> >
> org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory
> (AbstractRefreshableApplicationContext.java:121)
> > org.springframework.context.support.AbstractApplicationContext.getBean(
> AbstractApplicationContext.java:733)
> > org.apache.cxf.configuration.spring.SpringBeanMap.get(SpringBeanMap.java
> :193)
> > org.apache.cxf.configuration.spring.SpringBeanMap.values(
> SpringBeanMap.java:239)
> >
> org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri
> (DestinationFactoryManagerImpl.java:114)
> > org.apache.cxf.frontend.AbstractEndpointFactory.createEndpointInfo(
> AbstractEndpointFactory.java:168)
> > org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(
> AbstractEndpointFactory.java:110)
> > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java
> :107)
> > org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(
> JaxWsServerFactoryBean.java:147)
> > org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:287)
> > org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:227)
> > org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:179)
> > org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:201)
> > org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(
> SimpleEndpoint.java:55)
> > org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
> > org.apache.servicemix.common.BaseServiceUnitManager.start(
> BaseServiceUnitManager.java:151)
> > org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(
> ServiceUnitLifeCycle.java:103)
> > org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(
> ServiceAssemblyLifeCycle.java:132)
> > org.apache.servicemix.jbi.framework.DeploymentService.start(
> DeploymentService.java:378)
> >
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly
> (AutoDeploymentService.java:352)
> > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(
> AutoDeploymentService.java:253)
> >
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory
> (AutoDeploymentService.java:647)
> > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
> AutoDeploymentService.java:60)
> > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(
> AutoDeploymentService.java:611)
> > java.util.TimerThread.mainLoop(Timer.java:512)
> > java.util.TimerThread.run(Timer.java:462) ]]></stack-trace>
> > </msg-loc-info>
> > </exception-info>
> > </task-result-details>
> > </component-task-result-details>
> > </component-task-result>
> > </jbi-task-result>
> >
> > Does anyone also has this issue?
> > How and where do I call refresh?
> >
> > Thanks in advance!
> >
> > Cybexion
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Hotdeploy-issue---BeanFactory-not-initialized-or-already-closed---call-%27refresh%27-before-accessing-beans-via-the-Application-tp14398899s12049p14423010.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
Re: Hotdeploy issue - BeanFactory not initialized or already closed
- call 'refresh' before accessing beans via the Application
Posted by Cybexion <cy...@email.de>.
Nobody else experiencing this?
Is Hotdeployment working everywhere?
Regards Cybexion
Cybexion wrote:
>
> Hi,
>
> I tought deployment / hotdeployment can be done just by dropping/removing
> a jar inside the hotdeploy folder (working with 3.2.1).
>
> However, after undeploying (deleting my jar) of a SA I have to restart
> servicemix, before I can redeploy a new jar.
> If I just delete the jar (undeploy) and copy a new version into the
> hotdeploy folder, I get an error like this:
>
> INFO - DeploymentService - Error in start
> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
> version="1.0">
> <jbi-task-result>
> <frmwk-task-result>
> <frmwk-task-result-details>
> <task-result-details>
> <task-id>start</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> </task-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
> <component-name>servicemix-cxf-se</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>start</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token />
> <loc-message>Unable to start service unit</loc-message>
> </msg-loc-info>
> </task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <msg-loc-info>
> <loc-token />
> <loc-message>BeanFactory not
> initialized or already closed - call 'refresh' before accessing beans via
> the Application
> Context</loc-message>
>
> <stack-trace><![CDATA[java.lang.IllegalStateException: BeanFactory not
> initialized or already closed - call 'refresh' before accessing beans via
> the ApplicationContext at
> org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:121)
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:733)
> org.apache.cxf.configuration.spring.SpringBeanMap.get(SpringBeanMap.java:193)
> org.apache.cxf.configuration.spring.SpringBeanMap.values(SpringBeanMap.java:239)
> org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri(DestinationFactoryManagerImpl.java:114)
> org.apache.cxf.frontend.AbstractEndpointFactory.createEndpointInfo(AbstractEndpointFactory.java:168)
> org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(AbstractEndpointFactory.java:110)
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:107)
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:147)
> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:287)
> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:227)
> org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:179)
> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:201)
> org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(SimpleEndpoint.java:55)
> org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
> org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:151)
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:378)
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:352)
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:253)
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:60)
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
> java.util.TimerThread.mainLoop(Timer.java:512)
> java.util.TimerThread.run(Timer.java:462) ]]></stack-trace>
> </msg-loc-info>
> </exception-info>
> </task-result-details>
> </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
>
> Does anyone also has this issue?
> How and where do I call refresh?
>
> Thanks in advance!
>
> Cybexion
>
>
--
View this message in context: http://www.nabble.com/Hotdeploy-issue---BeanFactory-not-initialized-or-already-closed---call-%27refresh%27-before-accessing-beans-via-the-Application-tp14398899s12049p14423010.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.