[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
12:38 a.m.
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Priority: Critical
As specified in the forum reference I have an MDB which uses a SLSB (also declared as Seam
component) with business logic. If I deploy the application and there are already messages
in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to
invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Pete Muir updated JBSEAM-2286:
------------------------------
Fix Version/s: 2.0.2.GA
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Priority: Critical
Fix For: 2.0.2.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Pete Muir updated JBSEAM-2286:
------------------------------
Component/s: EJB3
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Priority: Critical
Fix For: 2.0.2.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Pete Muir updated JBSEAM-2286:
------------------------------
Priority: Major (was: Critical)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: 2.0.2.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:31 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Pete Muir updated JBSEAM-2286:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.2.GA)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: 2.1.0.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Norman Richards updated JBSEAM-2286:
------------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.A1)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: 2.1.0.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:29 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[ http://jira.jboss.com/jira/browse/JBSEAM-2286?page=all ]
Pete Muir updated JBSEAM-2286:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: http://jira.jboss.com/jira/browse/JBSEAM-2286
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: 2.1.0.GA
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-2286:
------------------------------
Fix Version/s: The future
(was: 2.1.0.GA)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
1:23 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
sdfsd fsdfs commented on JBSEAM-2286:
-------------------------------------
Hello, any chance it's going to be implemented soon ? We're having the same
problem .. MDB with SEAM components inside. All fine, except the situation when the
messages are already in the queue. Workaround ?
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
8:18 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
Christian Bauer updated JBSEAM-2286:
------------------------------------
Comment: was deleted
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
8:08 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
Elias Ross updated JBSEAM-2286:
-------------------------------
Attachment: deploy-hack.zip
For JBoss, you can use these files to create a Seam dependency for your MDB.
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
8:14 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
Elias Ross commented on JBSEAM-2286:
------------------------------------
Let me expand on the last comment.
Seam gets deployed as part of a .war deployment, which occurs after your EJB deployment.
The solution is on JBoss is to add a
@Depends("com.example:type=DummyService")
to your MDB class. What the attached .zip contains is a Seam component for creating a
'dummy service' as part of the Seam initialization. It works by reading in an .xml
file, creates a virtual URL with those contents, and passes it to the JBoss MainDeployer.
On JBoss 5, I think this could be simplified a lot.
What JBoss should do is to create a trigger that will enable your EJBs to depend on .war
deployments to complete. There are MBeans registered, under
"jboss.web.deployment", but there are random IDs attached to them, e.g
"id=1174003084,war=jbossws-context.war".
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
1:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/jira/browse/JBSEAM-2286?page=com.atlassian.jira.pl...
]
Karl Max commented on JBSEAM-2286:
----------------------------------
Any solution under JBoss5.1GA, because it does not work.
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/jira/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
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
10:47 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugin....
]
Simon Cigoj commented on JBSEAM-2286:
-------------------------------------
I have the sam isue, using jboss5.1GA but the solution mentioned doesnt work for me also.
I got
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.j2ee:ear=convert_it-ear.ear,jar=convert_it-ejb.jar,name=VideoConverter,service=EJB3"
is missing the following dependencies:
Dependency "<UNKNOWN
jboss.j2ee:ear=convert_it-ear.ear,jar=convert_it-ejb.jar,name=VideoConverter,service=EJB3>"
(should be in state "Described", but is actually in state "** UNRESOLVED
Demands 'si.arctur.convertit.BL:type=DummyService' **")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN
jboss.j2ee:ear=convert_it-ear.ear,jar=convert_it-ejb.jar,name=VideoConverter,service=EJB3>"
is in error due to the following reason(s): ** UNRESOLVED Demands
'si.arctur.convertit.BL:type=DummyService' **
it was metioned that on JBoss 5, I think this could be simplified a lot.
Could you give some example?
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:52 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://jira.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugin....
]
Marcel Sebek commented on JBSEAM-2286:
--------------------------------------
On jboss 5 and ear type of deployment, I have been successful with the following
workaround: each MDB annotate with
@org.jboss.ejb3.annotation.Depends({"jboss.web.deployment:war=/my-war-name"}).
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://jira.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:49 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Atul Yadav commented on JBSEAM-2286:
------------------------------------
Hi
I am using jboss-4.2.3.GA , and i tried to attached zip file approach , still i am getting
the same exception.
Do anybody implemented this hack successfully???
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:49 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Atul Yadav edited comment on JBSEAM-2286 at 12/29/10 7:49 AM:
--------------------------------------------------------------
Hi
I am using jboss-4.2.3.GA , and i tried - attached zip file approach by creating dummy
service, still i am getting the same exception.
Do anybody implemented this hack successfully???
was (Author: atulyadav):
Hi
I am using jboss-4.2.3.GA , and i tried to attached zip file approach , still i am getting
the same exception.
Do anybody implemented this hack successfully???
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Leonardo Lima commented on JBSEAM-2286:
---------------------------------------
Have you seen this "solution"? http://community.jboss.org/message/548610#548610
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:03 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Siarhei Dudzin commented on JBSEAM-2286:
----------------------------------------
As I mentioned in the description of the problem the solution is not portable.
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:07 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Tomaz Cerar commented on JBSEAM-2286:
-------------------------------------
And you need it to be portable how? or better where? it is portable between different
version of jboss..
What is you use case? This does not work on some other app server? if that is so, this is
totally different issue..
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:28 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Siarhei Dudzin commented on JBSEAM-2286:
----------------------------------------
Seam itself is portable, I.e. it works on any jee compliant server. The proposed solution
will not work outside JBoss on a platform that is jee compliant besides it is a
workaround.
Again, as I mentioned in the problem description the JBoss specific solution was known at
the moment of reporting this issue which makes it *not* a different issue.
If you have this problem on JBoss (i.e. the JBoss-specific fix does not work on JBoss) you
can report a different issue.
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Leonardo Lima commented on JBSEAM-2286:
---------------------------------------
Did you reproduce the problem in other JEE Server?
I mean, I agree it should be fixed despite this workaround; we're just trying to
provide a workaround while this isn't properly fixed!
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:46 p.m.
New subject: [JBoss JIRA] (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB
[
https://issues.jboss.org/browse/JBSEAM-2286?page=com.atlassian.jira.plugi...
]
Andrei Ivanov commented on JBSEAM-2286:
---------------------------------------
I've just ran into this problem using GlassFish.
It would be very nice if someone could give this issue some attention :)
MDB activated too early to use Seam components as a standard EJB
----------------------------------------------------------------
Key: JBSEAM-2286
URL: https://issues.jboss.org/browse/JBSEAM-2286
Project: Seam 2
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Reporter: Siarhei Dudzin
Fix For: The future
Attachments: deploy-hack.zip
As specified in the forum reference I have an MDB which uses a SLSB (also declared as
Seam component) with business logic. If I deploy the application and there are already
messages in the queue I get the following exception:
javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted
to invoke a
Seam component outside the an initialized application
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy111.onMessage(Unknown Source)
Looks like the MDB processing the message before Seam is initialized?
This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate
business logic if I want to re-use the same functionality of the SLSB in Seam.
I could use the solution from
http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me
to use vendor-specific API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4233
days inactive
6002
days old
22 comments
13 participants
participants (13)
-
Andrei Ivanov (JIRA) -
Atul Yadav (JIRA)
-
Christian Bauer (JIRA)
-
Elias Ross (JIRA)
-
Karl Max (JIRA)
-
Leonardo Lima (JIRA)
-
Marcel Sebek (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)
-
sdfsd fsdfs (JIRA)
-
Siarhei Dudzin (JIRA)
-
Simon Cigoj (JIRA)
-
Tomaz Cerar (JIRA)