May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2247) Datasource not available during clean shutdown

by Tom Ross (JIRA)

Datasource not available during clean shutdown ---------------------------------------------- Key: EJBTHREE-2247 URL: https://issues.jboss.org/browse/EJBTHREE-2247 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-1.0.1 Environment: JBoss EAP 5.1 (standalone) Reporter: Tom Ross This is a scenario where there is an EJB 2.1 deployed in standalone JBoss environment. It depends on data source for its operations. If a shut-down command is issued the container will unload the data source even though the EJB may still need it. If the EJB tries to lookup the data source in JNDI after shut-down command has been issued the following exception is thrown: Caused by: javax.naming.NameNotFoundException: JBossDBDriverTester-XA2 not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.lookup(NamingServer.java:443) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at com.${company name}.util.db.DBHelper.getDataSource(DBHelper.java:115) Any explicit dependencies defined between EJB and the data source are ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2998) MVEL performance regression

by Lukáš Petrovický (JIRA)

MVEL performance regression --------------------------- Key: JBRULES-2998 URL: https://issues.jboss.org/browse/JBRULES-2998 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M2 Reporter: Lukáš Petrovický Assignee: Mark Proctor Priority: Blocker Fix For: 5.2.0.CR1 I'm filing this JIRA to track the performance regression talked over recently at the rules-dev mailing list. Blocker priority per Ḿark's off-list suggestion. Quote follows: On 26/04/2011 15:53, Wolfgang Laun wrote: > A simple rule containing an eval with a % b == 0 exhibits a considerable slowdown when comparing execution times between a Drools core built in February and the one there is now. > > The slow-down factor is 15. There is a performance issue with MVEL. We moved to indexed (array based) mvel factories, which is suppose to give faster performance. However the MVEL author has not finished that work completely and so far they give a performance regression :( I'm pestering him daily on this. Mark -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9384) Conflict using JBoss AOP with no-interface session beans

by Marco Strauch (JIRA)

Conflict using JBoss AOP with no-interface session beans -------------------------------------------------------- Key: JBAS-9384 URL: https://issues.jboss.org/browse/JBAS-9384 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Affects Versions: 6.0.0.Final Environment: Windows 7 Reporter: Marco Strauch Assignee: Kabir Khan See discussion in forum thread: http://community.jboss.org/thread/164703 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9378) Add Infinispan module dependency to Hibernate module

by Scott Marlow (JIRA)

Add Infinispan module dependency to Hibernate module ---------------------------------------------------- Key: JBAS-9378 URL: https://issues.jboss.org/browse/JBAS-9378 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-706) baseline i18n support for the console

by Heiko Braun (JIRA)

baseline i18n support for the console ------------------------------------- Key: AS7-706 URL: https://issues.jboss.org/browse/AS7-706 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 provide message bundles and constants for 'en_US' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-699) create a new service to activate RA with method activate(ra.xml, ironjacamar.xml, classloader)

by Stefano Maestri (JIRA)

create a new service to activate RA with method activate(ra.xml, ironjacamar.xml, classloader) ---------------------------------------------------------------------------------------------- Key: AS7-699 URL: https://issues.jboss.org/browse/AS7-699 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.Beta4 the method will get the necessary metadata representation and the classloader and will activate a ra. The necessary java code for ra is not deployed but it's cosidered already loaded by the given classloader. Consider also a variant taking ra.xml and ij.xml as string containing the xml and proved parse too. Anyway the priority is on metadata variant -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-688) standalone: user needs should be able to to query server state (startup finished?) by management API

by Andre Dietisheim (JIRA)

standalone: user needs should be able to to query server state (startup finished?) by management API ---------------------------------------------------------------------------------------------------- Key: AS7-688 URL: https://issues.jboss.org/browse/AS7-688 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Andre Dietisheim Assignee: Jason Greene The as7 tooling in Eclipse displays the server state in a label decoration. I therefore need the capability to query the server state so that I can reliably display if the server is still starting up or the bootstrap successfully started all components. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-682) add --disabled option to deploy command

by Alexey Loubyansky (JIRA)

add --disabled option to deploy command --------------------------------------- Key: AS7-682 URL: https://issues.jboss.org/browse/AS7-682 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta4 --disabled would just add the content to the repository w/o actually deploying it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Resolved: (AS7-668) Missing error when CLI connection fails

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-668?page=com.atlassian.jira.plugin.sy... ] Alexey Loubyansky resolved AS7-668. ----------------------------------- Resolution: Done Merged. > Missing error when CLI connection fails > --------------------------------------- > > Key: AS7-668 > URL: https://issues.jboss.org/browse/AS7-668 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Reporter: Heiko Braun > Assignee: Alexey Loubyansky > > [localhost:9999 /] connect > Closed connection to localhost:9999 > Connected to localhost:9999 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-679) add --keep-content to undeploy

by Alexey Loubyansky (JIRA)

add --keep-content to undeploy ------------------------------ Key: AS7-679 URL: https://issues.jboss.org/browse/AS7-679 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta4 Would be useful to have an option to keep the deployment content in the repository after undeploy command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011