November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3870) Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package

by Dimitris Andreadis (JIRA)

Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package --------------------------------------------------------------------------------- Key: JBAS-3870 URL: http://jira.jboss.com/jira/browse/JBAS-3870 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.0.CR1 There are indications that the jdk5 implementation of javax.management.timer.Timer uses internally a single-threaded implementation for executing scheduled tasks, so scheduling of multiple tasks is affected when moving from jdk1.4 and the jboss implementation of Timer, to a jdk5 runtime. The JBossMX Timer implementation in contrast uses a dynamically extensible thread pool to execute scheduled tasks. Since we don't control the jdk5 implementation, a simple solution is to clone the jboss timer into a new package, e.g. org.jboss.javax.management.timer.Timer, for those that want to stick with the jboss implementation. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3615) failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase

by Dimitris Andreadis (JIRA)

failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase ------------------------------------------------------------------------------ Key: JBAS-3615 URL: http://jira.jboss.com/jira/browse/JBAS-3615 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testMalformed Failure invalid object name: domain:=,foo=bar junit.framework.AssertionFailedError: invalid object name: domain:=,foo=bar at org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase$FullNameTEST.testMalformed(MalformedTestCase.java:152) -- 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, 6 months

2
16
0 / 0

[JBoss JIRA] Created: (JBPM-695) Have the GPD add all default attributes to nodes instead of leaving them out

by Ronald van Kuijk (JIRA)

Have the GPD add all default attributes to nodes instead of leaving them out ---------------------------------------------------------------------------- Key: JBPM-695 URL: http://jira.jboss.com/jira/browse/JBPM-695 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Environment: N/A Reporter: Ronald van Kuijk Assigned To: Tom Baeyens It would be nice if the GPD added the defaults of attributes to nodes (e.g. task-end="false" on a tasknode) this way, even with no graphical support, users often think further, search for it etc, that it would help (even for me!!! ;-)) -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-302) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBAOP-302 URL: http://jira.jboss.com/jira/browse/JBAOP-302 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Fix For: 1.5.3.GA, 2.0.0.alpha2 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-892) Patch to use Java 1.5 concurrent classes for src/ tree

by Elias Ross (JIRA)

Patch to use Java 1.5 concurrent classes for src/ tree ------------------------------------------------------ Key: JBCACHE-892 URL: http://jira.jboss.com/jira/browse/JBCACHE-892 Project: JBoss Cache Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1, 2.0.0.ALPHA2 Reporter: Elias Ross Assigned To: Manik Surtani Attachments: java5.diff Simple changes to use JDK 1.5 concurrent classes -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-157) Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time

by Esteban Schifman (JIRA)

Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time --------------------------------------------------------------------------------------------------------------------------- Key: JBESB-157 URL: http://jira.jboss.com/jira/browse/JBESB-157 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Reporter: Esteban Schifman Assigned To: Esteban Schifman Fix For: 4.0 GpListener has at present two mechanisms to reload it's configuration parameters: a) timer driven 2) message driven. At parameter reload time, the controlling instance of GpListener will try to instantiate new child processes according to the new configuration values. It will allow active child threads to gracetully finish. New listener classes that are accepting connections on specific sockets will have a conflict when the new instance tries to listen on a port that is being used by the active instance. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-869) Use Marshaller for all forms of serialization, not just replication.

by Manik Surtani (JIRA)

Use Marshaller for all forms of serialization, not just replication. -------------------------------------------------------------------- Key: JBCACHE-869 URL: http://jira.jboss.com/jira/browse/JBCACHE-869 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.ALPHA2 Use Marshallers for all forms of serialization in JBC, including cache loaders. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-747) Add configuration type of "normal" or "default" to the gpd action handler configuration dialog

by Sam Healy (JIRA)

Add configuration type of "normal" or "default" to the gpd action handler configuration dialog ---------------------------------------------------------------------------------------------- Key: JBPM-747 URL: http://jira.jboss.com/jira/browse/JBPM-747 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Affects Versions: jBPM 3.1.2 Environment: Win XP Pro, Eclipse 3.1.2 Reporter: Sam Healy Assigned To: Tom Baeyens When configuring action handlers on nodes using the gpd, no option is provided in the configuration window to use a configuration type of "default" or "normal" where a simple instantiation of the action class would suffice. As it is now, the implication is that an action class of this nature cannot be used. -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3473) Fix DistributedStateImpl.nodeRemove

by Brian Stansberry (JIRA)

Fix DistributedStateImpl.nodeRemove ----------------------------------- Key: JBAS-3473 URL: http://jira.jboss.com/jira/browse/JBAS-3473 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta AFAICT, this is not correct. Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node. Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed. Also, remove() itself notifies listeners of a removal, and then the listener does as well. Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-698) gpd is not working with latest version of commons-fileupload jar.

by Olivier Debels (JIRA)

gpd is not working with latest version of commons-fileupload jar. ----------------------------------------------------------------- Key: JBPM-698 URL: http://jira.jboss.com/jira/browse/JBPM-698 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Reporter: Olivier Debels Assigned To: Tom Baeyens When trying to used the graphical process designer with the latest version of commons-upload (version 1.1.1) it is not longer possible to deploy process definitions. You get the exception 'The process definition was rejected because no multiplart boundary was found'. The reason is that the gpd is using a ',' to separate its content type (in the url used to trigger the upload servlet) where it must be a ';' according to RFC1341. So instead of 'multipart/form-data,boundary=AaB03x' it must be 'multipart/form-data;boundary=AaB03x'. The webapp must work with the latest version of commons-fileupload. -- 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, 6 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 November 2006