[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
7:39 a.m.
Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: isActive(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:09 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King reassigned JBSEAM-456:
---------------------------------
Assignee: Gavin King
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: isActive(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:09 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King updated JBSEAM-456:
------------------------------
Fix Version/s: 1.1.0.BETA2
Priority: Critical (was: Major)
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: isActive(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:59 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Guy Veraghtert updated JBSEAM-456:
----------------------------------
Description:
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
was:
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: isActive(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
The method tried to call is of course getStatus() instead of isActive()
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:37 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King closed JBSEAM-456.
-----------------------------
Resolution: Done
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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
5:06 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Guy Veraghtert reopened JBSEAM-456:
-----------------------------------
This issue is not fixed yet.
A UserTransaction method (getStatus()) is still called in a business method (interceptor
method) which is not allowed by the EJB 3.0 spec (p. 81 "The UserTransaction
interface is unavailable to enterprise beans with container-managed transaction
demarcation.", see also table 1 p.79), when calling getEntityManager() on
org.jboss.seam.core.ManagedPersistenceContext.
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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
6:22 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=comments#action_12346769 ]
Guy Veraghtert commented on JBSEAM-456:
---------------------------------------
Stacktrace:
[#|2006-11-13T11:46:59.204+0100|INFO|sun-appserver-pe9.1|javax.enterprise.system.container.ejb|_ThreadID=15;_ThreadName=httpWorkerThread-8080-1;|
javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested
exception is: java.lang.IllegalStateException: Operation not allowed.
java.lang.IllegalStateException: Operation not allowed.
at
com.sun.enterprise.distributedtx.UserTransactionImpl.checkUserTransactionMethodAccess(UserTransactionImpl.java:112)
at
com.sun.enterprise.distributedtx.UserTransactionImpl.getStatus(UserTransactionImpl.java:247)
at org.jboss.seam.util.Transactions.isTransactionActive(Transactions.java:33)
at
org.jboss.seam.core.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:102)
at org.jboss.seam.Component.callComponentMethod(Component.java:1738)
at org.jboss.seam.Component.unwrap(Component.java:1764)
at org.jboss.seam.Component.getInstance(Component.java:1597)
at org.jboss.seam.Component.getInstance(Component.java:1557)
at org.jboss.seam.Component.getInstance(Component.java:1551)
at
org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.entityRefsToIds(ManagedEntityIdentityInterceptor.java:114)
at
org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
at
org.jboss.seam.interceptors.OutcomeInterceptor.interceptOutcome(OutcomeInterceptor.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
at
org.jboss.seam.interceptors.ConversationInterceptor.endOrBeginLongRunningConversation(ConversationInterceptor.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
at
org.jboss.seam.intercept.RootInterceptor.createSeamInvocationContext(RootInterceptor.java:144)
at org.jboss.seam.intercept.RootInterceptor.invokeInContexts(RootInterceptor.java:129)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:102)
at
org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:505)
at
com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:415)
at
com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:189)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3862)
at
com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:184)
at
com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:118)
at $Proxy140.executeQuery(Unknown Source)
at
be.aca.mytrack.service.SkillGroupFinder$$FastClassByCGLIB$$6de278f6.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:45)
at
org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:68)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:55)
at
org.jboss.seam.interceptors.RemoveInterceptor.removeIfNecessary(RemoveInterceptor.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
at
org.jboss.seam.interceptors.ExceptionInterceptor.handleExceptions(ExceptionInterceptor.java:28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
at
org.jboss.seam.intercept.RootInterceptor.createSeamInvocationContext(RootInterceptor.java:144)
at org.jboss.seam.intercept.RootInterceptor.invokeInContexts(RootInterceptor.java:129)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:102)
at
org.jboss.seam.intercept.ClientSideInterceptor.interceptInvocation(ClientSideInterceptor.java:77)
at
org.jboss.seam.intercept.ClientSideInterceptor.intercept(ClientSideInterceptor.java:47)
at
be.aca.mytrack.service.SkillGroupFinder$$EnhancerByCGLIB$$106333c2.executeQuery(<generated>)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:102)
at org.jboss.seam.Component.callComponentMethod(Component.java:1738)
at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1630)
at org.jboss.seam.Component.getInstance(Component.java:1573)
at org.jboss.seam.Component.getInstance(Component.java:1557)
at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:45)
at
com.sun.faces.el.VariableResolverChainWrapper.getValue(VariableResolverChainWrapper.java:93)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:62)
at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:68)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
at javax.faces.component.UIData.getValue(UIData.java:582)
at javax.faces.component.UIData.getDataModel(UIData.java:1061)
at javax.faces.component.UIData.setRowIndex(UIData.java:417)
at com.sun.faces.renderkit.html_basic.TableRenderer.encodeBegin(TableRenderer.java:85)
at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:810)
at javax.faces.component.UIData.encodeBegin(UIData.java:878)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:881)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:828)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:883)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:889)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:133)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:246)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:185)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.processNonBlocked(DefaultProcessorTask.java:549)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:789)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:328)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:251)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:205)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:04 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King resolved JBSEAM-456.
-------------------------------
Resolution: Done
Well, then this is a bug in Glassfish, not Seam, since the EJB spec says:
"The container must not make the UserTransaction interface available to the
enterprise beans that
are not allowed to use this interface. The container should throw
javax.naming.NameNotFoundException
if an instance of an enterprise bean that is not allowed to use the UserTransaction
interface attempts to look up the interface in JNDI using the JNDI APIs."
And that is the behavior in JBoss, and the behavior expected by Seam:
public static boolean isTransactionActive() throws SystemException, NamingException
{
try
{
return getUserTransaction().getStatus()==STATUS_ACTIVE;
}
catch (NamingException ne)
{
try
{
return !EJB.getEJBContext().getRollbackOnly();
}
catch (IllegalStateException ise)
{
return false;
}
}
}
So I suggest you report this bug to the Glassfish team. Nevertheless I will code a
workaround for the bug in the Seam Transactions class.
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:04 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King closed JBSEAM-456.
-----------------------------
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:32 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=comments#action_12346912 ]
Gavin King commented on JBSEAM-456:
-----------------------------------
OK, I have committed a workaround for this bug in Glassfish to CVS. The underlying bug
needs to be fixed though.
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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
4:12 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Guy Veraghtert reopened JBSEAM-456:
-----------------------------------
You are completely right, we will file a bug report to the GlassFish-team.
Thx for the workaround, however, the workaround contains a bug on GlassFish, well, in
fact, the EJB-class does:
In org.jboss.seam.util.EJB the EJBContext is looked up using name:
java:comp.ejb3/EJBContext. This works fine on JBoss, but not on GlassFish (resulting in a
NameNotFoundException). The EJB-spec states (section 16.15, p.451) :
"The container must make a component's EJBContext interface available either
through injection
using the Resource annotation or in JNDI under the name java:comp/EJBContext. "
Patched locally this way in class org.jboss.seam.util.EJB:
public static final String STANDARD_EJBCONTEXT_NAME =
"java:comp/EJBContext";
public static EJBContext getEJBContext() throws NamingException
{
try
{
return (EJBContext) Naming.getInitialContext().lookup(STANDARD_EJBCONTEXT_NAME);
}
catch (NameNotFoundException nnfe)
{
return (EJBContext) Naming.getInitialContext().lookup(EJBCONTEXT_NAME);
}
}
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:54 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=all ]
Gavin King closed JBSEAM-456.
-----------------------------
Resolution: Done
oops! Thanks, nice catch.
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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:45 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT
[ http://jira.jboss.com/jira/browse/JBSEAM-456?page=comments#action_12347352 ]
Stijn Van den Enden commented on JBSEAM-456:
--------------------------------------------
Submitted this bug in Glassfish (see
https://glassfish.dev.java.net/issues/show_bug.cgi?id=1538)
Interceptor tries to access UserTransaction interface, but this is
not allowed for CMT
--------------------------------------------------------------------------------------
Key: JBSEAM-456
URL: http://jira.jboss.com/jira/browse/JBSEAM-456
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.BETA1
Environment: Glassfish
Reporter: Guy Veraghtert
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.BETA2
In method getEntityManager() in class ManagedPersistenceContext a call is made to the
UserTransaction interface: getStatus(). According to the EJB 3.0 specification (p.81) this
is not allowed for CMT. Seam requires the usage of CMT.
(Occurs when adding @In to an entityManager-field, according to seam doc 11.4).
Patched locally in class ManagedPersistenceContext :
@Unwrap
public EntityManager getEntityManager() throws NamingException, SystemException
{
if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ )
{
try
{
entityManager.joinTransaction();
} catch (TransactionRequiredException e) {
}
}
return entityManager;
}
--
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
7087
days inactive
7102
days old
12 comments
3 participants
participants (3)
-
Gavin King (JIRA) -
Guy Veraghtert (JIRA)
-
Stijn Van den Enden (JIRA)