January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3978) One off patch for ASPATCH-137: JConsole throws exception on connect post

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3978?page=all ] Galder Zamarreno updated JBAS-3978: ----------------------------------- Summary: One off patch for ASPATCH-137: JConsole throws exception on connect post (was: One off patch for ASPATCH-136: JConsole throws exception on connect post ) > One off patch for ASPATCH-137: JConsole throws exception on connect post > ------------------------------------------------------------------------- > > Key: JBAS-3978 > URL: http://jira.jboss.com/jira/browse/JBAS-3978 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.5.GA > Reporter: Scott M Stark > Assigned To: Pavel Tsekov > Attachments: jboss-system.jar, run.jar > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Need a one off patch for the ASPATCH-137(jconsole issue) since 4.0.5CP1 did not go out. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-298) Need ability to add transport specific info to invocation payload

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-298?page=all ] Ron Sigal updated JBREM-298: ---------------------------- Assignee: Ron Sigal (was: Tom Elrod) > Need ability to add transport specific info to invocation payload > ----------------------------------------------------------------- > > Key: JBREM-298 > URL: http://jira.jboss.com/jira/browse/JBREM-298 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta1 (Bluto) > > > Specific example would be to add ssl client cert from the ssl socket to the invocation payload. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-663) Put org.jboss.remoting.LeasePinger on separate thread.

by Ron Sigal (JIRA)

Put org.jboss.remoting.LeasePinger on separate thread. ------------------------------------------------------ Key: JBREM-663 URL: http://jira.jboss.com/jira/browse/JBREM-663 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) It has been observed in running JBossMessaging test suite that sometimes org.jboss.remoting.LeasePinger and org.jboss.remoting.ConnectionValidator, which both use the single java.util.Timer in org.jboss.remoting.util.TimerUtil, can get in each others way. In particular, LeasePinger got hung up trying to ping a dead server and held up the ConnectionValidator until it timed out. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-610) Need to add in support for date-effective, date-expires and enabled attributes

by Michael Neale (JIRA)

Need to add in support for date-effective, date-expires and enabled attributes ------------------------------------------------------------------------------ Key: JBRULES-610 URL: http://jira.jboss.com/jira/browse/JBRULES-610 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.1-m1 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m1 Some examples: rule "foo" date-effective "10-Jul-2007" date-expires "10-Dec-2007" enabled false ... IDE should provide a popup list of these options, like with the others. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-326) Create the concept of a "priority queue" to speed execution of certain remote method invocations

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-326?page=all ] Manik Surtani updated JBCACHE-326: ---------------------------------- Fix Version/s: 3.x (was: 2.1.0.GA) > Create the concept of a "priority queue" to speed execution of certain remote method invocations > ------------------------------------------------------------------------------------------------ > > Key: JBCACHE-326 > URL: http://jira.jboss.com/jira/browse/JBCACHE-326 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Vladimir Blagojevic > Fix For: 3.x > > > Change the handling of requests in JBossCache (another interceptor on top of ReplicationInterceptor): > - Create 2 queues (of MethodCall objects), one thread for each queue > - The regular MethodCalls like put(), remove() etc go into the default queue (A), where they are processed according to order (FIFO) > - The special calls like block(), _getState(), commit() or acks for PREPARE/COMMIT calls go into the other (priority) queue (B), these calls *CAN* be received out of sequence > - This way, an _getState() would always be processed and would be able to (1) stop the processing of queue A and (2) force- release any locks held > by on the tree. > _ This way commit() calls can promptly release locks, without having to wait behind other prepare calls. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-326) Create the concept of a "priority queue" to speed execution of certain remote method invocations

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-326?page=comments#action_12350753 ] Manik Surtani commented on JBCACHE-326: --------------------------------------- I would have thought the concurrent stack would solve this. Let's push this to 3.0.0 for now and most likely close it once we're closer to finishing with the 2.x.x series. > Create the concept of a "priority queue" to speed execution of certain remote method invocations > ------------------------------------------------------------------------------------------------ > > Key: JBCACHE-326 > URL: http://jira.jboss.com/jira/browse/JBCACHE-326 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Vladimir Blagojevic > Fix For: 3.x > > > Change the handling of requests in JBossCache (another interceptor on top of ReplicationInterceptor): > - Create 2 queues (of MethodCall objects), one thread for each queue > - The regular MethodCalls like put(), remove() etc go into the default queue (A), where they are processed according to order (FIFO) > - The special calls like block(), _getState(), commit() or acks for PREPARE/COMMIT calls go into the other (priority) queue (B), these calls *CAN* be received out of sequence > - This way, an _getState() would always be processed and would be able to (1) stop the processing of queue A and (2) force- release any locks held > by on the tree. > _ This way commit() calls can promptly release locks, without having to wait behind other prepare calls. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-517) Port ReteOO viewer from Jung /Swing to GEF

by Philippe Ombredanne (JIRA)

Port ReteOO viewer from Jung /Swing to GEF ------------------------------------------ Key: JBRULES-517 URL: http://jira.jboss.com/jira/browse/JBRULES-517 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5 Reporter: Philippe Ombredanne Assigned To: Mark Proctor Priority: Minor Port the Jung based ReteOO viewer to GEF -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-719) Create ws dir, resources, build.xml under the project root

by Ronald van Kuijk (JIRA)

Create ws dir, resources, build.xml under the project root ---------------------------------------------------------- Key: JBPM-719 URL: http://jira.jboss.com/jira/browse/JBPM-719 Project: JBoss jBPM Issue Type: Feature Request Environment: n/a Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 Create <jbpm.home>/ws and all relevant subdirs according to what already exists (take console as an example) Create a build.xml file according to what already exists (take console as an example) Initially add jbossws from <jboss.home> if set, see other issue for getting jbossws in the repository -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Resolved: (JBPM-596) task forms based on facelets

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-596?page=all ] Ronald van Kuijk resolved JBPM-596. ----------------------------------- Resolution: Done By David and Koen, not by me :-( > task forms based on facelets > ---------------------------- > > Key: JBPM-596 > URL: http://jira.jboss.com/jira/browse/JBPM-596 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.2 > > > the task forms should be based on facelets technology. > Advantages: > * facelets dynamic nature fits much better with the process versioning and process files > * much easier to create tooling around this cause the xhtml files are rederable by a plain browser and it's plain XML > * much more flexible then the previous flat list appoach. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-596) task forms based on facelets

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-596?page=all ] Ronald van Kuijk updated JBPM-596: ---------------------------------- Fix Version/s: jBPM 3.2 David worked his ass off to implement this. As did Koen to get default forms generated from the GPD. So closing this issue since it WILL be in 3.2 and the current GPD > task forms based on facelets > ---------------------------- > > Key: JBPM-596 > URL: http://jira.jboss.com/jira/browse/JBPM-596 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.2 > > > the task forms should be based on facelets technology. > Advantages: > * facelets dynamic nature fits much better with the process versioning and process files > * much easier to create tooling around this cause the xhtml files are rederable by a plain browser and it's plain XML > * much more flexible then the previous flat list appoach. -- 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, 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 January 2007