March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1159) ConnectionListener leaked if TSR throws IllegalStateException

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1159?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1159. ------------------------------------ Resolution: Done > ConnectionListener leaked if TSR throws IllegalStateException > ------------------------------------------------------------- > > Key: JBJCA-1159 > URL: https://issues.jboss.org/browse/JBJCA-1159 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.24.Final, 1.1.4.Final > Environment: AS7 EAP6.1 > Reporter: gui borland > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.25.Final, 1.1.5.Final, 1.2.0.Beta1 > > > When a connection is retrieved from the MCP, ironjacamar will register it to ongoing JTA transaction. However, if the ongoing TX is not 'active' anymore the connection is lost. > The code of AbstractPool demonstrates the problem. The call to getLock will throw an exception if the current TX is not active anymore and the cl is not returned to the pool. > This issue can be reproduced on AS7 by using any EJB that requires a tx and does something with a DB connection. Put a breakpoint in the code below after retrieving the connectionlistener, and then wait for the transaction to timeout. Once that's done, continue the thread. The connection is not release (can be seen in JMX) > We have noticed this problem regularly during our performance tests. > {code} > ConnectionListener cl = mcp.getConnection(subject, cri); > if (trace) > log.tracef("Got connection from pool tracked by transaction=%s tx=%s", cl, trackByTransaction); > TransactionSynchronizationRegistry tsr = getTransactionSynchronizationRegistry(); > Lock lock = getLock(); > try > { > lock.lockInterruptibly(); > } > catch (InterruptedException ie) > { > Thread.interrupted(); > throw new ResourceException(bundle.unableObtainLock(), ie); > } > {code} > It seems this issue was introduced by changes done for https://issues.jboss.org/browse/JBJCA-572 -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink reassigned WFLY-3194: -------------------------------------- Assignee: Stuart Douglas > ApplicationClient container can not use a declarative method to activate EJBClientInterceptors > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3194 > URL: https://issues.jboss.org/browse/WFLY-3194 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Client > Affects Versions: 8.0.0.Final > Environment: appclient > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Labels: ejb > > With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. > The file must be added to the client.jar in case of a simple standalone client. > And to the ejb.jar if the interceptor is used inside a server application. > For the appclient I expect that add this file to > EAR/client.jar/META-INF/services > will do the same. > Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. > Also adding the class to the client.jar, as ear module or as server module with dependency did not work. > All theses Interceptors can be used if the client Main method add this with the JBoss API. > A working example can be found here > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... > For the example with the services approach try > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated WFLY-3194: ----------------------------------- Affects Version/s: 8.0.0.Final > ApplicationClient container can not use a declarative method to activate EJBClientInterceptors > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3194 > URL: https://issues.jboss.org/browse/WFLY-3194 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Client > Affects Versions: 8.0.0.Final > Environment: appclient > Reporter: Wolf-Dieter Fink > Labels: ejb > > With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. > The file must be added to the client.jar in case of a simple standalone client. > And to the ejb.jar if the interceptor is used inside a server application. > For the appclient I expect that add this file to > EAR/client.jar/META-INF/services > will do the same. > Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. > Also adding the class to the client.jar, as ear module or as server module with dependency did not work. > All theses Interceptors can be used if the client Main method add this with the JBoss API. > A working example can be found here > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... > For the example with the services approach try > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated WFLY-3194: ----------------------------------- Component/s: Application Client > ApplicationClient container can not use a declarative method to activate EJBClientInterceptors > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3194 > URL: https://issues.jboss.org/browse/WFLY-3194 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Client > Environment: appclient > Reporter: Wolf-Dieter Fink > Labels: application-scoped, ejb > > With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. > The file must be added to the client.jar in case of a simple standalone client. > And to the ejb.jar if the interceptor is used inside a server application. > For the appclient I expect that add this file to > EAR/client.jar/META-INF/services > will do the same. > Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. > Also adding the class to the client.jar, as ear module or as server module with dependency did not work. > All theses Interceptors can be used if the client Main method add this with the JBoss API. > A working example can be found here > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... > For the example with the services approach try > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated WFLY-3194: ----------------------------------- Labels: ejb (was: application-scoped ejb) > ApplicationClient container can not use a declarative method to activate EJBClientInterceptors > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3194 > URL: https://issues.jboss.org/browse/WFLY-3194 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Client > Environment: appclient > Reporter: Wolf-Dieter Fink > Labels: ejb > > With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. > The file must be added to the client.jar in case of a simple standalone client. > And to the ejb.jar if the interceptor is used inside a server application. > For the appclient I expect that add this file to > EAR/client.jar/META-INF/services > will do the same. > Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. > Also adding the class to the client.jar, as ear module or as server module with dependency did not work. > All theses Interceptors can be used if the client Main method add this with the JBoss API. > A working example can be found here > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... > For the example with the services approach try > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-3194: -------------------------------------- Summary: ApplicationClient container can not use a declarative method to activate EJBClientInterceptors Key: WFLY-3194 URL: https://issues.jboss.org/browse/WFLY-3194 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Environment: appclient Reporter: Wolf-Dieter Fink With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. The file must be added to the client.jar in case of a simple standalone client. And to the ejb.jar if the interceptor is used inside a server application. For the appclient I expect that add this file to EAR/client.jar/META-INF/services will do the same. Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. Also adding the class to the client.jar, as ear module or as server module with dependency did not work. All theses Interceptors can be used if the client Main method add this with the JBoss API. A working example can be found here https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... For the example with the services approach try https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3193?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3193: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1082617 > upgrade Generic JMS RA to 1.0.4.Final > ------------------------------------- > > Key: WFLY-3193 > URL: https://issues.jboss.org/browse/WFLY-3193 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA, JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-3193: --------------------------------- Summary: upgrade Generic JMS RA to 1.0.4.Final Key: WFLY-3193 URL: https://issues.jboss.org/browse/WFLY-3193 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JCA, JMS Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 8.0.1.Final -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3192) AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3192?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3192: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901324 > AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3192 > URL: https://issues.jboss.org/browse/WFLY-3192 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation is found in the class. > The specification says: > A class must not declare more than one AroundInvoke method. > The JBoss AS allows more such methods and then it chooses one of them which is used as the interceptor. > It becomes even more important to check the interceptor validity now with the new feature introduced by AS7-5897 (server side non-EE interceptors for EE invocations). -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3192) AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-3192: --------------------------------------- Summary: AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class Key: WFLY-3192 URL: https://issues.jboss.org/browse/WFLY-3192 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EE Affects Versions: 8.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation is found in the class. The specification says: A class must not declare more than one AroundInvoke method. The JBoss AS allows more such methods and then it chooses one of them which is used as the interceptor. It becomes even more important to check the interceptor validity now with the new feature introduced by AS7-5897 (server side non-EE interceptors for EE invocations). -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014