April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1252) @PersistenceContext injection from a different jar fails

by jaikiran pai (JIRA)

@PersistenceContext injection from a different jar fails -------------------------------------------------------- Key: EJBTHREE-1252 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1252 Project: EJB 3.0 Issue Type: Bug Components: injection Affects Versions: AS 4.2.2.GA Environment: JBoss-4.2.2GA, Windows 2003 Server, Sun Java 1.5 Reporter: jaikiran pai I have a sample application with an EJB3 SLSB which is being injected with a PersistenceContext which is configured in a different jar file as follows package org.myapp.ejb.impl; import javax.ejb.Remote; import javax.ejb.Stateless; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import org.jboss.annotation.ejb.RemoteBinding; import org.myapp.ejb.AppManager; @Stateless @Remote ({AppManager.class}) @RemoteBinding (jndiBinding = "AppManagerBean") public class AppManagerBean implements AppManager { @PersistenceContext (unitName="myapp_ejb3.jar#EJB3Persistence") private EntityManager em; public String getVersion() { System.out.println("EM is " + em); return "1.0"; } } The application is deployed as an EAR file in the following structure: EJB3Persistence.ear | |--- META-INF | | | |--- META-INF | | | | | |--- application.xml | | | | | |--- jboss-app.xml | | |--- myapp_ejb3.jar (contains the persistence.xml) | | | |--- META-INF | | | | | |--- persistence.xml | | | |--- another_ejb3.jar (contains the SLSB) | | | | | |--- META-INF | | | |--- org.myapp.ejb.impl.AppManagerBean When this application is deployed in 4.2.2 the deployment fails with an exception. Part of the exception is pasted below. The relevant log files (ConsoleLog_Fail.txt and serverLog_fail.txt in the logs.zip file) are attached. 22:45:41,137 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 22:45:41,152 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 with dependencies: 22:45:41,152 INFO [JmxKernelAbstraction] persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence 22:45:41,152 INFO [EJB3Deployer] Deployed: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/default/tmp/deploy/tmp53619EJB3Persistence.ear-contents/another_ejb3.jar 22:45:41,168 INFO [EARDeployer] Started J2EE application: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/default/deploy/EJB3Persistence.ear 22:45:41,184 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 State: NOTYETINSTALLED I Depend On: persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence State: NOTYETINSTALLED Depends On Me: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 If i change the PersistenceContext injection, in the bean, to prefix 3 random letters to the unitName as follows: @PersistenceContext (unitName="XXXmyapp_ejb3.jar#EJB3Persistence") private EntityManager em; and deploy the application, then everything works fine (have also attached the successful logs ConsoleLogs_Success.txt and serverLogs_Success.txt in the logs.zip file). -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-661) Allow server sending a stream to the client

by Helmut Wick (JIRA)

Allow server sending a stream to the client ------------------------------------------- Key: JBREM-661 URL: http://jira.jboss.com/jira/browse/JBREM-661 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Helmut Wick Assigned To: Tom Elrod As of release 2.0.0 GA, there is no way for a server to send a stream to the client (only the other way around). This is to request something like java.io.InputStream Client.invoke(java.lang.Object param) that allows for true streaming (like java.lang.Object invoke(java.io.InputStream inputStream, java.lang.Object param) does). -- 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

16 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBREM-566) update jbossws to include 2.0.0 in component-info.xml

by Tom Elrod (JIRA)

update jbossws to include 2.0.0 in component-info.xml ----------------------------------------------------- Key: JBREM-566 URL: http://jira.jboss.com/jira/browse/JBREM-566 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: External_issues Have already e-mailed ws team. Need this to be updated in repository or won't be able to update build-thirdpary.xml within jbossas. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-567) Update ejb3 project for use of 2.0.0 of remoting

by Tom Elrod (JIRA)

Update ejb3 project for use of 2.0.0 of remoting ------------------------------------------------ Key: JBREM-567 URL: http://jira.jboss.com/jira/browse/JBREM-567 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: External_issues Need to make sure 'xmbean-dd="org/jboss/remoting/transport/Connector.xml" is removed from all the service descriptors, as Connector is now a standard mbean and not an xmbean. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-565) integration testing for 2.0.0 release

by Tom Elrod (JIRA)

integration testing for 2.0.0 release ------------------------------------- Key: JBREM-565 URL: http://jira.jboss.com/jira/browse/JBREM-565 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Need to do some integration testing with new 2.0.0.CR1 of remoting with JBossAS 4 & 5 to make sure everything is working correctly. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5332) Container artifacts should have symmetric lifecycles

by Adrian Brock (JIRA)

Container artifacts should have symmetric lifecycles ---------------------------------------------------- Key: JBAS-5332 URL: http://jira.jboss.com/jira/browse/JBAS-5332 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Adrian Brock Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA The container artifacts i.e. [Session|Entity|MessageDriven]Container, interceptors, cache, pool, ProxyBindings should have symmetric create/start/stop/destroy methods. e.g. The MessageDrivenContainer does this in destroy // Destroy container invoker for (Iterator it = proxyFactories.keySet().iterator(); it.hasNext();) { String invokerBinding = (String) it.next(); EJBProxyFactory ci = (EJBProxyFactory) proxyFactories.get(invokerBinding); ci.destroy(); ci.setContainer(null); try { ObjectName containerName = super.getJmxName(); Hashtable props = containerName.getKeyPropertyList(); props.put("plugin", "invoker"); props.put("binding", invokerBinding); ObjectName invokerName = new ObjectName(containerName.getDomain(), props); server.unregisterMBean(invokerName); } catch(Throwable ignore) { } } The setContainer(null) is wrong since it isn't the one that sets the container in create() that is done by EjbModule in its createService() method In this case, the fix is to either move the setting of container to MessageDrivenContainer::createService() or move the nulling of the container to EjbModule::destroyService() Other artifacts also need checking and fixing with tests writing to validate that each container can go through a stop/destroy/create/start lifecycle and still function correctly. -- 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

16 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4194) Configurable Default TX attribute for CMT

by Vicky Kak (JIRA)

Configurable Default TX attribute for CMT ----------------------------------------- Key: JBAS-4194 URL: http://jira.jboss.com/jira/browse/JBAS-4194 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vicky Kak Assigned To: Vicky Kak Priority: Minor The default transaction attribute for the CMT is TX_REQUIRED , this should be configurable . -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5174) Provide Configuration for disabling the logging in ManagedConnectionFactory .

by Vicky Kak (JIRA)

Provide Configuration for disabling the logging in ManagedConnectionFactory . ------------------------------------------------------------------------------ Key: JBAS-5174 URL: http://jira.jboss.com/jira/browse/JBAS-5174 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Vicky Kak Assigned To: Vicky Kak Priority: Minor -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4764) NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .

by Vicky Kak (JIRA)

NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock . ------------------------------------------------------------------------------ Key: JBAS-4764 URL: http://jira.jboss.com/jira/browse/JBAS-4764 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-3.2.8.SP1 Reporter: Vicky Kak Assigned To: Vicky Kak Fix For: JBossAS-4.2.2.GA http://forum.java.sun.com/thread.jspa?threadID=752201 -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3770) JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool

by Weston Price (JIRA)

JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool -------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3770 URL: http://jira.jboss.com/jira/browse/JBAS-3770 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Weston Price Assigned To: Weston Price Priority: Minor By default, when we return a JDBC connection to the pool we execute the following in the ManagedConnection.cleanup() method: if (jdbcTransactionIsolation != transactionIsolation) { try { con.setTransactionIsolation(jdbcTransactionIsolation); jdbcTransactionIsolation = transactionIsolation; } catch (SQLException e) { mcf.log.warn("Error resetting transaction isolation ", e); } } In this scenario we don't return the original isolation level on the underlying connection. The spec doesn't prohibit this, and I can't see any reason why we shouldn't do this, or provide a configurable option. -- 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

16 years, 4 months

3
4
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 2008