August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-669) end-tasks attribute on task-node causes all tasks to be ended, not just tasks for the current token

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-669?page=all ] Tom Baeyens updated JBPM-669: ----------------------------- Fix Version/s: jBPM 3.1.3 jBPM 3.2 alpha 1 > end-tasks attribute on task-node causes all tasks to be ended, not just tasks for the current token > --------------------------------------------------------------------------------------------------- > > Key: JBPM-669 > URL: http://jira.jboss.com/jira/browse/JBPM-669 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.1, jBPM 3.1 > Environment: Windows XP, JDK1.4.2_06 > Reporter: Michael Holtzman > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM 3.1.3, jBPM 3.2 alpha 1 > > Attachments: TaskInstanceEndTest.java > > > When the "end-tasks" attribute is set to true leaving the task-node causes all pending tasks to end, even tasks that are associated with different nodes. > NOTE: See forum post for suggested patch. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-70) Create separate Nagios plugin

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-70?page=all ] Mark Little updated JBESB-70: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > Create separate Nagios plugin > ----------------------------- > > Key: JBESB-70 > URL: http://jira.jboss.com/jira/browse/JBESB-70 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Johan Kumps > Fix For: 4.0 > > > - common\src\org\jboss\soa\esb\util\NagiosStandaloneHeartbeat.java > 1) Refactor into a nagios specific plugin package? -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3183) Integration with WebSphere MQ 5.x

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=all ] Dimitris Andreadis updated JBAS-3183: ------------------------------------- Priority: Blocker (was: Critical) > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Blocker > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1 > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3183) Integration with WebSphere MQ 5.x

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340400 ] Dimitris Andreadis commented on JBAS-3183: ------------------------------------------ We'll try to push more to get the MQ server installed. In the meantime, have you tried installing MQ locally? This is really a blocker for this 4.0.5.CR1 release, so let's say that the end of the next week (Aug/11th) is the absolute deadline. > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1 > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-321) performance tuning

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-321?page=comments#action_12340396 ] Tom Elrod commented on JBREM-321: ---------------------------------- Have tuned some things along the way. Issue for publishing benchmarks is JBREM-562. > performance tuning > ------------------ > > Key: JBREM-321 > URL: http://jira.jboss.com/jira/browse/JBREM-321 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Need to do some profiling to help increase the performance over the different transports within remoting. > Ideally, this will result in benchmark results for publishing. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBREM-321) performance tuning

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-321?page=all ] Tom Elrod resolved JBREM-321. ------------------------------ Resolution: Done > performance tuning > ------------------ > > Key: JBREM-321 > URL: http://jira.jboss.com/jira/browse/JBREM-321 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Need to do some profiling to help increase the performance over the different transports within remoting. > Ideally, this will result in benchmark results for publishing. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JGRP-242) FD_PING

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-242?page=all ] Bela Ban resolved JGRP-242. --------------------------- Resolution: Done Left as is: FD_PING uses a script, whereas FD_ICMP calls InetAddress.isReachable() > FD_PING > ------- > > Key: JGRP-242 > URL: http://jira.jboss.com/jira/browse/JGRP-242 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9.2, 2.2.9.1, 2.2.9, 2.2.8, 2.3 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.4 > > > Uses a script or executable to ping a node, the script could be /sbin/ping. This will use ICMP pings to see whether a host is still alove -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-466) Take a final decision on whether to use &tools or keep only parts of jbossbuild under "tools"

by Ovidiu Feodorov (JIRA)

Take a final decision on whether to use &tools or keep only parts of jbossbuild under "tools" --------------------------------------------------------------------------------------------- Key: JBMESSAGING-466 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-466 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.Alpha1 Decide if to integrate the whole "tools" module with & tools in CVSROOT/modules or just copy tools.jar in lib. "tools" seems to contain a lot of extra junk that I don't directly need. I would rather maintain a jarred "toools.jar" or "jbossbuild.jar" by hand in a lib directory. -- 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-3336) Destroy connections after a ResourceManager failure

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3336?page=all ] Weston Price resolved JBAS-3336. -------------------------------- Resolution: Done Connections are no longer returned to the pool upon XA enlistment failure. Changes to XAManagedConnection prevent this from occuring. > Destroy connections after a ResourceManager failure > --------------------------------------------------- > > Key: JBAS-3336 > URL: http://jira.jboss.com/jira/browse/JBAS-3336 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-4.0.5.CR1 > > > In TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.enlist() > we don't check the XAException for a total failure. > If the XAException has error code XAER_RMERR or XAER_RMFAIL > we should just destroy the connection straightaway. > We don't want these connections being returned to the pool, > only for the valid connection checker to close them next time the connection is used. > There is no point. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-461) Post on the development forum an announcement that the SVN is complete

by Ovidiu Feodorov (JIRA)

Post on the development forum an announcement that the SVN is complete ---------------------------------------------------------------------- Key: JBMESSAGING-461 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-461 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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

17 years, 11 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 August 2006