[
https://jira.jboss.org/jira/browse/JBSEAM-4196?page=com.atlassian.jira.pl...
]
Vladyslav Kutsenko updated JBSEAM-4196:
---------------------------------------
Attachment: jbpmseamtest.zip
attached is a seam gen project reproducing the described bahavior. The problem can be
reproduced only on tomcat; Jboss as seams not to be affected.
the project is created using Seam 2.2.0.GA. For running the project it is necessary to add
the libs and modify some configuration files like persistence-dev.xml and
hibernate.cfg.xml. The zip archived is stripped of libraries. To run the test, click on
the button "start process". The process definition contains three nodes. On
entering of one of them a seam managed action handler is called. It creates a
synchronous and an ansynchronous event. The synchronous event can be processed; the
asynchronous one leads to infinite loop and subsequently to StackOverflowError.
Infinite Loop bug in JBPM integration
-------------------------------------
Key: JBSEAM-4196
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4196
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.1.GA
Reporter: Elias Ross
Assignee: Norman Richards
Fix For: 2.2.1.CR1
Attachments: jbpmseamtest.zip
See this forum post:
http://seamframework.org/Community/InfiniteLoopBugInJBPMIntegration
Stack trace (repeating):
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:154)
at org.jboss.seam.Component.callComponentMethod(Component.java:2211)
at org.jboss.seam.Component.unwrap(Component.java:2237)
at org.jboss.seam.Component.getInstance(Component.java:2004)
at org.jboss.seam.Component.getInstance(Component.java:1967)
at org.jboss.seam.Component.getInstance(Component.java:1961)
at org.jboss.seam.Component.getInstance(Component.java:1934)
at org.jboss.seam.Component.getInstance(Component.java:1929)
at org.jboss.seam.bpm.ProcessInstance.instance(ProcessInstance.java:65)
at
org.jboss.seam.contexts.BusinessProcessContext.getProcessInstance(BusinessProcessContext.java:229)
at
org.jboss.seam.contexts.BusinessProcessContext.getContextInstance(BusinessProcessContext.java:217)
at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:68)
at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:209)
at org.jboss.seam.Component.getInstance(Component.java:1949)
at org.jboss.seam.Component.getInstance(Component.java:1944)
at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55)
at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50)
at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166)
at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112)
at
org.jboss.seam.transaction.EntityTransaction.initEntityManager(EntityTransaction.java:67)
at org.jboss.seam.transaction.EntityTransaction.begin(EntityTransaction.java:79)
at org.jboss.seam.util.Work.workInTransaction(Work.java:42)
at org.jboss.seam.bpm.ProcessInstance.getProcessInstance(ProcessInstance.java:39)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144)
etc.
There is code to reproduce the issue there.
--
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