July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBDEPLOY-58) AltDD processing missing from MultipleVFSParsingDeployer

by Ales Justin (JIRA)

AltDD processing missing from MultipleVFSParsingDeployer -------------------------------------------------------- Key: JBDEPLOY-58 URL: http://jira.jboss.com/jira/browse/JBDEPLOY-58 Project: JBoss Deployers Issue Type: Bug Components: deployer Affects Versions: JBDEPLOY-2.0.0.Beta18 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBDEPLOY-2.0.0.CR1 See forum thread for more details. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5711) Get the JBoss-AS-4.2.x-TestSuite-jrockit15 passing

by Dimitris Andreadis (JIRA)

Get the JBoss-AS-4.2.x-TestSuite-jrockit15 passing -------------------------------------------------- Key: JBAS-5711 URL: http://jira.jboss.com/jira/browse/JBAS-5711 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Shelly McGowan Priority: Critical Fix For: JBossAS-4.2.3.GA Parent task for any JBoss-AS-4.2.x-TestSuite-jrockit15 failures. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5772) org.jboss.test.cluster.test/FamilyClusterInfoUnitTestCase(Default-TCP)/testSynchronization

by Dimitris Andreadis (JIRA)

org.jboss.test.cluster.test/FamilyClusterInfoUnitTestCase(Default-TCP)/testSynchronization ------------------------------------------------------------------------------------------ Key: JBAS-5772 URL: http://jira.jboss.com/jira/browse/JBAS-5772 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Priority: Critical Fix For: JBossAS-4.2.3.GA It might be a random failure, however, on the JRockit testsuite this has been failing for 2 test runs in a row: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-Test... Once for TCP and once for UDP ? -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris

by Quenten Alick (JIRA)

run.sh can consume 100% single CPU resources on Solaris ------------------------------------------------------- Key: JBAS-4287 URL: http://jira.jboss.com/jira/browse/JBAS-4287 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Environment: Solaris on SPARC (version 9 & 10) Reporter: Quenten Alick When shutting down jboss the run.sh script remain alive and consumes 100% of a single CPUs resources. run.sh needs to be killed off. To trigger the bug, you need to 1) set LAUNCH_JBOSS_IN_BACKGROUND 2) start the jboss server normally 3) Once it's started stop the server At this point the JVM stops, however the run.sh script remains running consuming 100% of a single CPUs resources. The problem seems to be this bit of script, plus the fact that the script shebang is #!/bin/sh while [ "$WAIT_STATUS" -ne 127 ]; do JBOSS_STATUS=$WAIT_STATUS wait $JBOSS_PID 2>/dev/null WAIT_STATUS=$? done On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man page for wait states that this is the correct behaviour. Therefore wait returns 0 and the while loop continues forever burning up CPU resources (until you kill it with one of the signals not being trapped). Here's a link to the patch that may have introduced the bug. http://jira.jboss.com/jira/browse/JBAS-3748 -- 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

16 years, 2 months

4
16
0 / 0

[JBoss JIRA] Created: (JBAS-5721) Get a JBoss-AS-4.2.x-TestSuite-openjdk16-openjdk16 going

by Dimitris Andreadis (JIRA)

Get a JBoss-AS-4.2.x-TestSuite-openjdk16-openjdk16 going -------------------------------------------------------- Key: JBAS-5721 URL: http://jira.jboss.com/jira/browse/JBAS-5721 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Shelly McGowan Priority: Critical Fix For: JBossAS-4.2.3.GA Get a JBoss-AS-4.2.x-TestSuite-openjdk16-openjdk16 going and create subtasks to address testsuite failures. -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1373) Remove interfaces that implement Cloneable and offer a better alternative.

by Manik Surtani (JIRA)

Remove interfaces that implement Cloneable and offer a better alternative. -------------------------------------------------------------------------- Key: JBCACHE-1373 URL: http://jira.jboss.com/jira/browse/JBCACHE-1373 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.0.0 A bunch of classes and interfaces implement/extend Cloneable and generally this is bad practice and difficult to control. A copy constructor or factory method should be used instead with explicit copy semantics. Perhaps a Duplicable interface, with a public duplicate() method, that will explicitly construct, duplicate state and return the 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1274) Ability to configure zero nodes in memory for a region

by J B (JIRA)

Ability to configure zero nodes in memory for a region ------------------------------------------------------ Key: JBCACHE-1274 URL: http://jira.jboss.com/jira/browse/JBCACHE-1274 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.0.0.GA Reporter: J B Assigned To: Manik Surtani Priority: Minor The ability to configure a region to have no nodes in memory. If you have a cache configured with a cacheloader and you for instance dont want a certain region to have any nodes in memory but just to load the data through the cacheloader. At the moment you cant set maxNodes=0, because this actually means, the region can grow to an unlimited size, so I would like the ability to be able to tell the cache that this region should have no nodes in memory. -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1151) Switch to using MVCC for locking, drop Pessimistic and Optimistic locking

by Manik Surtani (JIRA)

Switch to using MVCC for locking, drop Pessimistic and Optimistic locking ------------------------------------------------------------------------- Key: JBCACHE-1151 URL: http://jira.jboss.com/jira/browse/JBCACHE-1151 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.1.GA, 1.4.0.GA, 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.x Forum ref http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064626#4064626 Wiki with design details http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheMVCC -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1391) update documentation and FAQs

by Mircea Markus (JIRA)

update documentation and FAQs ----------------------------- Key: JBCACHE-1391 URL: http://jira.jboss.com/jira/browse/JBCACHE-1391 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 3.0.0.ALPHA1, 3.0.0.GA Following should be updated in documentation: 1) document how the configuration will still accept old <mbean ... /> tags, but this is deprecated 2) document how the <mbean ... /> tag can cause problems with AS 5 (unintentional deployment), and how this can be done properly with the MC using the new <jbosscache ... /> tag Notes: Currently the XMLConfigurationParser looks for a <mbean ../> element, under which it pulls out more specific JBoss Cache elements. This could easily change so the parser to accept this, or on failing to do so, to pick up a <jbosscache ... /> container element. And log a deprecation warning when using the old <mbean ... /> container tag. -- 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

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1377) Update documentation

by Manik Surtani (JIRA)

Update documentation -------------------- Key: JBCACHE-1377 URL: http://jira.jboss.com/jira/browse/JBCACHE-1377 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani This includes the following: 1. Update FAQs explaining how the XML format converter will work (both on the fly as well as using the command-line scripts) 2. Update user guide sections on configuration, with a section on converting between old and new formats -- 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

16 years, 2 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008