April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-704) Allow the registration of a listener for Datasource connection events

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBJCA-704?page=com.atlassian.jira.plugin.... ] George Gastaldi updated JBJCA-704: ---------------------------------- Forum Reference: https://community.jboss.org/message/808900 > Allow the registration of a listener for Datasource connection events > ---------------------------------------------------------------------- > > Key: JBJCA-704 > URL: https://issues.jboss.org/browse/JBJCA-704 > Project: IronJacamar > Issue Type: Feature Request > Components: Common, Deployer, JDBC > Reporter: George Gastaldi > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > When using Oracle Proxy feature, there are cases where you need to run custom SQL commands before returning the connection to the application and also when returning to the pool. I propose the creation of a _ConnectionActivationListener_ interface (or even split it into two interfaces - _ConnectionPassivationListener_) where you could find the following methods: > {code:java} > void connectionActivated(Connection con) throws SQLException; > void connectionPassivated(Connection con) throws SQLException; > {code} > And then allow adding this class to a datasource configuration. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-704) Allow the registration of a listener for Datasource connection events

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-704?page=com.atlassian.jira.plugin.... ] Jesper Pedersen commented on JBJCA-704: --------------------------------------- Please, use https://community.jboss.org/en/ironjacamar?view=all for discussions/questions > Allow the registration of a listener for Datasource connection events > ---------------------------------------------------------------------- > > Key: JBJCA-704 > URL: https://issues.jboss.org/browse/JBJCA-704 > Project: IronJacamar > Issue Type: Feature Request > Components: Common, Deployer, JDBC > Reporter: George Gastaldi > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > When using Oracle Proxy feature, there are cases where you need to run custom SQL commands before returning the connection to the application and also when returning to the pool. I propose the creation of a _ConnectionActivationListener_ interface (or even split it into two interfaces - _ConnectionPassivationListener_) where you could find the following methods: > {code:java} > void connectionActivated(Connection con) throws SQLException; > void connectionPassivated(Connection con) throws SQLException; > {code} > And then allow adding this class to a datasource configuration. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-704) Allow the registration of a listener for Datasource connection events

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBJCA-704?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on JBJCA-704: --------------------------------------- Good job! Where should ConnectionListener implementations be placed ? > Allow the registration of a listener for Datasource connection events > ---------------------------------------------------------------------- > > Key: JBJCA-704 > URL: https://issues.jboss.org/browse/JBJCA-704 > Project: IronJacamar > Issue Type: Feature Request > Components: Common, Deployer, JDBC > Reporter: George Gastaldi > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > When using Oracle Proxy feature, there are cases where you need to run custom SQL commands before returning the connection to the application and also when returning to the pool. I propose the creation of a _ConnectionActivationListener_ interface (or even split it into two interfaces - _ConnectionPassivationListener_) where you could find the following methods: > {code:java} > void connectionActivated(Connection con) throws SQLException; > void connectionPassivated(Connection con) throws SQLException; > {code} > And then allow adding this class to a datasource configuration. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-704) Allow the registration of a listener for Datasource connection events

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-704?page=com.atlassian.jira.plugin.... ] Jesper Pedersen resolved JBJCA-704. ----------------------------------- Resolution: Done > Allow the registration of a listener for Datasource connection events > ---------------------------------------------------------------------- > > Key: JBJCA-704 > URL: https://issues.jboss.org/browse/JBJCA-704 > Project: IronJacamar > Issue Type: Feature Request > Components: Common, Deployer, JDBC > Reporter: George Gastaldi > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > When using Oracle Proxy feature, there are cases where you need to run custom SQL commands before returning the connection to the application and also when returning to the pool. I propose the creation of a _ConnectionActivationListener_ interface (or even split it into two interfaces - _ConnectionPassivationListener_) where you could find the following methods: > {code:java} > void connectionActivated(Connection con) throws SQLException; > void connectionPassivated(Connection con) throws SQLException; > {code} > And then allow adding this class to a datasource configuration. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6924: -------------------------------- Fix Version/s: 8.0.0.Alpha1 > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > Fix For: 8.0.0.Alpha1 > > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5432: ---------------------------------------------- wfink(a)redhat.com changed the Status of [bug 952629|https://bugzilla.redhat.com/show_bug.cgi?id=952629] from NEW to ON_QA > TransactionRolledbackLocalException doesn't reference the originating runtime-exception > --------------------------------------------------------------------------------------- > > Key: AS7-5432 > URL: https://issues.jboss.org/browse/AS7-5432 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: Barnabas Bodnar > Assignee: jaikiran pai > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()). > The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here. > This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException(). -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside commented on AS7-6924: -------------------------------------- Never noticed that before, but that does look a little strange. FYI this deploys on Felix and Equinox, I remember reading something about OSGi always interpreting versions in the format *.*.* even if they are not in that format. I.e 2.0 is expanded to be 2.0.0, so I assume that 0 is expanded to be 0.0.0? > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside edited comment on AS7-6924 at 4/17/13 11:47 AM: ---------------------------------------------------------------- Never noticed that before, but that does look a little strange. FYI this deploys on Felix and Equinox, I remember reading something about OSGi always interpreting versions in the format {code}*.*.*{code} even if they are not in that format. I.e 2.0 is expanded to be 2.0.0, so I assume that 0 is expanded to be 0.0.0? was (Author: Aaron.Whiteside): Never noticed that before, but that does look a little strange. FYI this deploys on Felix and Equinox, I remember reading something about OSGi always interpreting versions in the format *.*.* even if they are not in that format. I.e 2.0 is expanded to be 2.0.0, so I assume that 0 is expanded to be 0.0.0? > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6925) ignore CNFE when scanning for entity classes in deployment

by Daniel Wehrle (JIRA)

[ https://issues.jboss.org/browse/AS7-6925?page=com.atlassian.jira.plugin.s... ] Daniel Wehrle commented on AS7-6925: ------------------------------------ It looks like the cnfe only occurs if permgen is to small. It is possible that without your change the oom is hidden by the cnfe? > ignore CNFE when scanning for entity classes in deployment > ---------------------------------------------------------- > > Key: AS7-6925 > URL: https://issues.jboss.org/browse/AS7-6925 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > Attachments: cnfe.jar > > > Deployments may contain non-entity classes that can not be loaded (see above forum reference for example). -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-6924 at 4/17/13 11:25 AM: --------------------------------------------------------------- Yes, thats good enough ... Need to research a little bit on how this is supposed to work {code} Import-Package: javax.xml.stream;version="0";resolution:="optional",javax.xml.stream.events;version="0" {code} was (Author: thomas.diesler): Yes, thats good enough > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013