6 a.m.
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:24 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2134:
-------------------------------------
Am I to assume that the description for this issue is incorrect?
It is possibly to do this, as one of the quickstarts already does, but it appears that
there may be an issue with the order of deployments in some circumstances. Is this
correct?
If so then please amend the description of this issue to reflect that and include a
description of the specific set of circumstances which fail.
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:47 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2134:
--------------------------------------
Which QS do you refer to? For me it doesn't work in any circumstances because
onInitialisation() is always called earlier than EJB is deployed.
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2134:
-------------------------------------
I believe ejbprocessor does this.
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Martin Vecera updated JBESB-2134:
---------------------------------
Attachment: Quickstart_SLSBFun.esb
Try deploying the attached file...
09:20:04,450 INFO [JBoss4ESBDeployer] create esb service, Quickstart_SLSBFun.esb
09:20:04,462 INFO [QueueService] Queue[/queue/quickstart_slsbfun_Request1_esb] started,
fullSize=200000, pageSize=2000, downCacheSize=2000
09:20:04,466 INFO [QueueService] Queue[/queue/quickstart_slsbfun_Request1_esb_reply]
started, fullSize=200000, pageSize=2000, downCacheSize=2000
09:20:04,470 INFO [QueueService] Queue[/queue/quickstart_slsbfun_Request2_esb] started,
fullSize=200000, pageSize=2000, downCacheSize=2000
09:20:04,475 INFO [QueueService] Queue[/queue/quickstart_slsbfun_Request2_esb_reply]
started, fullSize=200000, pageSize=2000, downCacheSize=2000
09:20:04,575 WARN [ServiceController] Problem starting service
jboss.esb:deployment=Quickstart_SLSBFun.esb
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action
processing pipeline
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:188)
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:134)
at
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:105)
at
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:62)
at
org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:105)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.soa.esb.ConfigurationException: Unexpected exception during lifecycle
initialisation
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.initialise(ActionProcessingPipeline.java:336)
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:184)
... 51 more
Caused by: org.jboss.soa.esb.actions.ActionLifecycleException: Could not lookup
ServiceCallerBean/remote
at org.jboss.soa.esb.actions.EJBProcessor.getEjb3FromJndi(EJBProcessor.java:306)
at org.jboss.soa.esb.actions.EJBProcessor.initialise(EJBProcessor.java:255)
at
org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.initialise(OverriddenActionLifecycleProcessor.java:123)
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.initialise(ActionProcessingPipeline.java:331)
... 52 more
Caused by: javax.naming.NameNotFoundException: remote not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at sun.reflect.GeneratedMethodAccessor88.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)
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:126)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.soa.esb.actions.EJBProcessor.getEjb3FromJndi(EJBProcessor.java:303)
... 55 more
09:20:04,588 INFO [JmxKernelAbstraction] creating wrapper delegate for:
org.jboss.ejb3.stateful.StatefulContainer
09:20:04,588 INFO [JmxKernelAbstraction] installing MBean:
jboss.j2ee:jar=slsb_fun-ejb.jar,name=ServiceCallerBean,service=EJB3 with dependencies:
09:20:04,592 INFO [EJBContainer] STARTED EJB:
org.jboss.soa.esb.samples.quickstart.servicecaller.ServiceCallerBean ejbName:
ServiceCallerBean
09:20:04,595 INFO [EJB3Deployer] Deployed:
file:/home/mvecera/work/soa/43CR1/jboss-as/server/production/tmp/deploy/tmp42611Quickstart_SLSBFun.esb-contents/slsb_fun-ejb.jar
09:20:04,597 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.esb:deployment=Quickstart_SLSBFun.esb
State: FAILED
Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error
configuring action processing pipeline
I Depend On:
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request2_esb_reply
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request1_esb_reply
jboss.esb:deployment=jbossesb.esb
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request1_esb
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request2_esb
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.esb:deployment=Quickstart_SLSBFun.esb
State: FAILED
Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error
configuring action processing pipeline
I Depend On:
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request2_esb_reply
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request1_esb_reply
jboss.esb:deployment=jbossesb.esb
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request1_esb
jboss.esb.quickstart.destination:service=Queue,name=quickstart_slsbfun_Request2_esb
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2134:
-------------------------------------
Okay, so this is definitely a dependency issue given the above.
I assume you tried the ejbprocessor quickstart and found that it worked, correct?
EJBProcessor cannot use EJBs deployed within .esb archive
---------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2134) Dependency ordering of EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2134:
--------------------------------
Summary: Dependency ordering of EJBs deployed within .esb archive (was:
EJBProcessor cannot use EJBs deployed within .esb archive)
Description:
The EJB jar may not be deployed until after the initialise method of EJBProcessor has been
called. As a consequence the EJBs may not be registered at that time.
was:
Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in
custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB
in onInitialisation() method. It would be good to
1) put this information into release notes
2) implement new <depends> feture for deployment.xml like in case of .war archives
Dependency ordering of EJBs deployed within .esb archive
--------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
The EJB jar may not be deployed until after the initialise method of EJBProcessor has
been called. As a consequence the EJBs may not be registered at that time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2134) Dependency ordering of EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2134:
-------------------------------------
There doesn't appear to be a dependency for the jar added to deployment.xml, is there
a reason for this?
Why is jboss.j2ee:module=slsb_fun-ejb.jar,service=EJB3 not sufficient?
Dependency ordering of EJBs deployed within .esb archive
--------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
The EJB jar may not be deployed until after the initialise method of EJBProcessor has
been called. As a consequence the EJBs may not be registered at that time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:40 a.m.
New subject: [JBoss JIRA] Resolved: (JBESB-2134) Dependency ordering of EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Martin Vecera resolved JBESB-2134.
----------------------------------
Resolution: Rejected
Mea culpa. I was not aware of the possibility of such a dependency specification.
Dependency ordering of EJBs deployed within .esb archive
--------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
The EJB jar may not be deployed until after the initialise method of EJBProcessor has
been called. As a consequence the EJBs may not be registered at that time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2134) Dependency ordering of EJBs deployed within .esb archive
[
https://jira.jboss.org/jira/browse/JBESB-2134?page=com.atlassian.jira.plu...
]
Martin Vecera closed JBESB-2134.
--------------------------------
Dependency ordering of EJBs deployed within .esb archive
--------------------------------------------------------
Key: JBESB-2134
URL: https://jira.jboss.org/jira/browse/JBESB-2134
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
Attachments: Quickstart_SLSBFun.esb
The EJB jar may not be deployed until after the initialise method of EJBProcessor has
been called. As a consequence the EJBs may not be registered at that time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5896
days inactive
5897
days old
9 comments
2 participants
participants (2)
-
Kevin Conner (JIRA) -
Martin Vecera (JIRA)