June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1101) Replace WSRPUtils.createOperationFailedFault by WSRPUtils.throwOperationFailedFault

by Chris Laprun (JIRA)

Replace WSRPUtils.createOperationFailedFault by WSRPUtils.throwOperationFailedFault ----------------------------------------------------------------------------------- Key: JBPORTAL-1101 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1101 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.Alpha1 so that we don't have to throw the newly created exception each time... -- 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

18 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4428) Method org.jboss.web.tomcat.tc5.session.ClusteredSession.calcMaxUnreplicatedInterval incorrectly treats maxInactiveInterval as milliseconds

by Stephen Burdeau (JIRA)

Method org.jboss.web.tomcat.tc5.session.ClusteredSession.calcMaxUnreplicatedInterval incorrectly treats maxInactiveInterval as milliseconds ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4428 URL: http://jira.jboss.com/jira/browse/JBAS-4428 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP and Unisys MCP system Reporter: Stephen Burdeau When running the testsuite test org.jboss.test.cluster.test.ScopedSetTriggerTestCase, the test fails on the following assertion: junit.framework.ComparisonFailure: Attributes should be the same expected:<...Ben...> but was:<...Joe...> at org.jboss.test.cluster.test.ScopedSetTriggerTestCase.testNonPrimitiveModify(ScopedSetTriggerTestCase.java:94) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) This failure occurs when running on the Unisys MCP system, which demonstrates different timings than when running on a system like Windows. After analyzing the results and the code, the following appears to be the root cause of the test failure: org.jboss.web.tomcat.tc5.session.ClusteredSession has a method calcMaxUnreplicatedInterval that is used to calculate maxUnreplicatedInterval. maxUnreplicatedInterval is the maximum time interval before a session is replicated to the other cluster nodes. When this time period is exceeded, the session is replicated even if the session is not "dirty". maxUnreplicatedInterval is in milliseconds, but maxInactiveInterval is in seconds. However, calcMaxUnreplicatedInterval computes maxUnreplicatedInterval as follows: maxUnreplicatedInterval = maxInactiveInterval * maxUnreplicatedFactor / 100; where maxUnreplicatedFactor is 80. Since maxInactiveInterval is in seconds, the correct computation should be: maxUnreplicatedInterval = maxInactiveInterval * 1000 * maxUnreplicatedFactor / 100; As a result of the incorrect computation of maxUnreplicatedInterval, the session is automatically replicated much more often than was intended. In this case, the session timeout was configured as 30 minutes or 1800 seconds. So, maxUnreplicatedInterval becomes 1440 milliseconds. Therefore, if the test takes more than about a second and a half to run, the test will not produce the expected results. -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4380) Deployers are not working when deploying/undeploying different JARS with the same name

by Clebert Suconic (JIRA)

Deployers are not working when deploying/undeploying different JARS with the same name -------------------------------------------------------------------------------------- Key: JBAS-4380 URL: http://jira.jboss.com/jira/browse/JBAS-4380 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Clebert Suconic Assigned To: Scott M Stark Priority: Blocker Fix For: JBossAS-5.0.0.Beta3 Suppose you have two distinct jars with the same name.. You deploy the first one (using deployers on JMX) and undeploy it. You deploy the second one (using deployers on JMX again)... you will get an exception... and the first jar will be deployed sometimes, as something is cached somewhere. (I will add a replication test for this issue, and a description for how to do it) -- 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

18 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-504) Support direct injection of MBeanServer into JChannelFactory

by Brian Stansberry (JIRA)

Support direct injection of MBeanServer into JChannelFactory ------------------------------------------------------------ Key: JGRP-504 URL: http://jira.jboss.com/jira/browse/JGRP-504 Project: JGroups Issue Type: Feature Request Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Currently org.jgroups.JChannelFactory finds the MBeanServer it should use via a "discovery" algorithm that will: 1) Use the server registered as "jboss" if one exists 2) Else use the first mbean server found, which will be the platform mbean server in a JDK env. This will break if the target mbean server isn't the platform mbean server and isn't named "jboss". I don't see any reason org.jgroups.JChannelFactory can't expose a setter for this. The usage for this would be: The org.jgroups.jmx.JChannelFactory class should implement javax.management.MBeanRegistration. This is the object that external code (e.g. microcontainer or AS 4.x ServiceController, or custom user code) initially registers in JMX. Via the MBeanRegistration.preRegister(MBeanServer server, ObjectName name) callback the org.jgroups.jmx.JChannelFactory is made aware of exactly what mbean server is being used. The org.jgroups.jmx.JChannelFactory then passes this into the org.jgroups.JChannelFactory via the setter. -- 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

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-271) need to decuople test code from build process

by Nathan Egge (JIRA)

need to decuople test code from build process --------------------------------------------- Key: JGRP-271 URL: http://jira.jboss.com/jira/browse/JGRP-271 Project: JGroups Issue Type: Patch Environment: Gentoo Linux dev-java/jgroups-2.2.7-r2 Reporter: Nathan Egge Assigned To: Bela Ban Priority: Minor Attachments: jgroups-2.2.7-build.patch I recently made a patch to the build.xml for JGroups 2.2.7 so that the unittest code could be compiled separately from the core classes. This was done to remove the build time dependency on junit.jar. More information can be found here: http://bugs.gentoo.org/show_bug.cgi?id=143282 -- 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

18 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-327) Certify JGroups 2.2.9 SP4 with JBossAS 4.0.3 and 4.0.4

by Bela Ban (JIRA)

Certify JGroups 2.2.9 SP4 with JBossAS 4.0.3 and 4.0.4 ------------------------------------------------------ Key: JGRP-327 URL: http://jira.jboss.com/jira/browse/JGRP-327 Project: JGroups Issue Type: Support Patch Affects Versions: 2.2.9 SP4 Reporter: Bela Ban Assigned To: Bela Ban Attachments: jgroups-all.jar -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1005) Adding diagram layout functions in the Eclipse designer

by Holger Sachse (JIRA)

Adding diagram layout functions in the Eclipse designer ------------------------------------------------------- Key: JBPM-1005 URL: http://jira.jboss.com/jira/browse/JBPM-1005 Project: JBoss jBPM Issue Type: Feature Request Environment: NA Reporter: Holger Sachse Assigned To: Tom Baeyens In real world erp development scenarios workflows charts get quickly very complex. To handle this complexity it is vital to have layout support functionalities. Having the same possibilities like the Eclipse build in graphics functionalities (f.e. UML2 tools) for arranging and formatting would be helpful. -- 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

18 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-4481) Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread

by Gavin King (JIRA)

Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread ----------------------------------------------------------------------------------------------- Key: JBAS-4481 URL: http://jira.jboss.com/jira/browse/JBAS-4481 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-4.2.0.GA Reporter: Gavin King Assigned To: Mark Little Priority: Blocker If a transaction timeout occurs, the UserTransaction object does not get cleaned up from the thread, even after the request ends and the thread returns to the pool. Future requests will not be able to begin() a transaction, since the STATUS_ROLLEDBACK UserTransaction throws this exception: Caused by: javax.transaction.NotSupportedException at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:79) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:77) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:124) at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:29) This means that any transaction timeout that occurs will leave the application server in a permanently broken state and require a server restart. Hence 4.2.0.GA is currently unusable in production! This needs to be fixed in an immediate patch release. -- 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

18 years, 10 months

7
36
0 / 0

[JBoss JIRA] Created: (BPEL-252) constraint violation deleting process instance

by Alejandro Guizar (JIRA)

constraint violation deleting process instance ---------------------------------------------- Key: BPEL-252 URL: http://jira.jboss.com/jira/browse/BPEL-252 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA When removing a process definition using graphSession.deleteProcessDefinition(), the following exception is thrown: 2007-04-02 11:28:12,558 DEBUG [org.hibernate.util.JDBCExceptionReporter] Could not execute JDBC batch update [/* delete com.ibm.wsdl.MessageImpl */ delete from WSDL_MESSAGE where ID_=?] java.sql.BatchUpdateException: ORA-02292: integrity constraint (JBPM.FK_MESSAGETYPE_MESSAGE) violated - child record found Cascade settings for the delete operation have to be reviewed. -- 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

18 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4336) Remove XLevel trace example from jboss-log4j.xml as it is not needed anymore.

by Dimitris Andreadis (JIRA)

Remove XLevel trace example from jboss-log4j.xml as it is not needed anymore. ----------------------------------------------------------------------------- Key: JBAS-4336 URL: http://jira.jboss.com/jira/browse/JBAS-4336 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Logging Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA -- 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

18 years, 10 months

1
3
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 June 2007