February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3892) Replace TxManager with JBoss Transactions 4.2.2

by Dimitris Andreadis (JIRA)

Replace TxManager with JBoss Transactions 4.2.2 ----------------------------------------------- Key: JBAS-3892 URL: http://jira.jboss.com/jira/browse/JBAS-3892 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transaction Manager Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

19 years, 2 months

2
13
0 / 0

[JBoss JIRA] Commented: (JBAS-1443) Add a flag to allow concurrent calls on stateful session beans

by c c (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1443?page=comments#action_12353651 ] c c commented on JBAS-1443: --------------------------- hold/queue requests cannot be used in all the problems Take the case where there is recursive use of a function and the recursive function is called through the Remote Interface which again goes through JBoss Layer and so thus this hold/queue will not hold. So there has to be way by which some beans have to be allowed to make concurrent calls Bye for now CSJakharia > Add a flag to allow concurrent calls on stateful session beans > -------------------------------------------------------------- > > Key: JBAS-1443 > URL: http://jira.jboss.com/jira/browse/JBAS-1443 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Priority: Minor > > Weblogic has an allow-concurrent-calls proprietary tag for stateful session beans. The allow-concurrent-calls specifies whether a stateful session bean instance will allow concurrent method calls. The value of this element may be either "True" or "False". The default value is "False". When a stateful session bean instance is currently in a method call and another (concurrent) method call arrives on the server, the EJB specification requires that the server throw a RemoteException. By default, allow-concurrent-calls is false, and the EJB container will follow the EJB specification. When this value is set to true, the EJB container will block the concurrent method call and allow it to proceed when the previous call has completed. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-621) Decision 'otherwise' choice does not appear to work.

by youngm (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-621?page=comments#action_12353649 ] youngm commented on JBPM-621: ----------------------------- I'm satisfied if you are > Decision 'otherwise' choice does not appear to work. > ---------------------------------------------------- > > Key: JBPM-621 > URL: http://jira.jboss.com/jira/browse/JBPM-621 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1 > Reporter: youngm > Assigned To: Tom Baeyens > > The following decision appears to always result in the "to_print" transition choosen. The decision node doesn't appear to ever check transisions who don't have conditions. So it assumes there is only one transition so it chooses the 'default' or first transition. > <decision name="data_needed"> > <transition name="to_print" to="print_application"> > <condition expression="#{true == false}"/> > </transition> > <transition name="to_get_approval" to="get_approval"/> > </decision> -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-437) Beans based configuration option for actions

by Rex Sheridan (JIRA)

Beans based configuration option for actions -------------------------------------------- Key: JBESB-437 URL: http://jira.jboss.com/jira/browse/JBESB-437 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Configuration Reporter: Rex Sheridan Assigned To: Mark Little Priority: Minor Attachments: ActionProcessingPipeline.java, NotificationTarget.java This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

19 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4122) JBAS-1489 patch for 3.2.6

by Galder Zamarreno (JIRA)

JBAS-1489 patch for 3.2.6 ------------------------- Key: JBAS-4122 URL: http://jira.jboss.com/jira/browse/JBAS-4122 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-3.2.6 Final Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Port JBAS-1489 to 3.2.6 -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1489) MessageListener does not invoke ExceptionListener on error

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1489?page=all ] Galder Zamarreno closed JBAS-1489. ---------------------------------- Resolution: Done > MessageListener does not invoke ExceptionListener on error > ---------------------------------------------------------- > > Key: JBAS-1489 > URL: http://jira.jboss.com/jira/browse/JBAS-1489 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assigned To: Galder Zamarreno > Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.2RC1 > > > If SpyMessageConsumer detects an error on the MessageListener thread > it should invoke the ExceptionListener. > Also, to avoid potential deadlocks with exceptions detected on the MessageListener > thread, a new thread should be started to invoke the ExceptionListener. > Otherwise the ExceptionListener will not be able to close the consumer. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1489) MessageListener does not invoke ExceptionListener on error

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1489?page=all ] Galder Zamarreno reopened JBAS-1489: ------------------------------------ Assignee: Galder Zamarreno (was: Adrian Brock) > MessageListener does not invoke ExceptionListener on error > ---------------------------------------------------------- > > Key: JBAS-1489 > URL: http://jira.jboss.com/jira/browse/JBAS-1489 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assigned To: Galder Zamarreno > Fix For: JBossAS-4.0.2RC1, JBossAS-3.2.8 Final > > > If SpyMessageConsumer detects an error on the MessageListener thread > it should invoke the ExceptionListener. > Also, to avoid potential deadlocks with exceptions detected on the MessageListener > thread, a new thread should be started to invoke the ExceptionListener. > Otherwise the ExceptionListener will not be able to close the consumer. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1489) MessageListener does not invoke ExceptionListener on error

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1489?page=all ] Galder Zamarreno updated JBAS-1489: ----------------------------------- Affects Version/s: JBossAS-3.2.6 Final It also affects 3.2.6 > MessageListener does not invoke ExceptionListener on error > ---------------------------------------------------------- > > Key: JBAS-1489 > URL: http://jira.jboss.com/jira/browse/JBAS-1489 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assigned To: Galder Zamarreno > Fix For: JBossAS-4.0.2RC1, JBossAS-3.2.8 Final > > > If SpyMessageConsumer detects an error on the MessageListener thread > it should invoke the ExceptionListener. > Also, to avoid potential deadlocks with exceptions detected on the MessageListener > thread, a new thread should be started to invoke the ExceptionListener. > Otherwise the ExceptionListener will not be able to close the consumer. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4100) Introduce v4_2 dtds/schemas

by Dimitris Andreadis (JIRA)

Introduce v4_2 dtds/schemas --------------------------- Key: JBAS-4100 URL: http://jira.jboss.com/jira/browse/JBAS-4100 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4104) Remove namespace.jar from the build

by Dimitris Andreadis (JIRA)

Remove namespace.jar from the build ----------------------------------- Key: JBAS-4104 URL: http://jira.jboss.com/jira/browse/JBAS-4104 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: XML services Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 The classes in lib/namespace.jar are not used when running under jdk5. -- 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

19 years, 2 months

1
1
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 February 2007