October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1071) Possible problem in concurrent signalling from multiple threads

by Jiri Pechanec (JIRA)

Possible problem in concurrent signalling from multiple threads --------------------------------------------------------------- Key: JBPM-1071 URL: http://jira.jboss.com/jira/browse/JBPM-1071 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux MySQL 5.0.22 Reporter: Jiri Pechanec Assigned To: Tom Baeyens Priority: Critical Attachments: expl.tar.gz Attached is a simple test case that 1) Deploys process definition with two nodes 2) Starts the process instance that will go to the wait state on first node 3) Starts 20 threads that tries concurrently signal the same process instance 4) The second node writes a record to the database The test case needs to be executed multiple times to see the incorrect behaviour. This is an example of run output Isol 8 Action 1 Action 2 Action 2 Action 2 Action 2 Action 2 1 Action 2 1 Action 2 1 Action 2 1 Signalist 5 Signalist 6 Signalist 8 Signalist 12 Signalist 7 Signalist 13 Signalist 14 Signalist 15 Signalist 9 Signalist 16 Signalist 17 Signalist 18 Signalist 4 Success 7 Failure 13 Explanation of the outcome 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created) 3 threads successfully executed the signal operation but no real action was performed 13 threads attempted to execute the signal operation but ended with an exception -- 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, 8 months

6
24
0 / 0

[JBoss JIRA] Created: (JBAS-4293) Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation

by Vladimir Piskarev (JIRA)

Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4293 URL: http://jira.jboss.com/jira/browse/JBAS-4293 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Vladimir Piskarev Assigned To: Scott M Stark According to 18.3.9 of EJB 2.1 spec "the container should not throw the java.rmi.RemoteException or javax.ejb.EJBException if the container performs a transaction rollback because the instance has invoked the setRollbackOnly method on its EJBContext object. In this case, the container must rollback the transaction and pass the business method result or the application exception thrown by the business method to the client.". Also 17.6.2.8 says "If the container initiated the transaction immediately before dispatching the business method to the instance (as opposed to the transaction being inherited from the caller), the container must note that the instance has invoked the setRollbackOnly method. When the business method invocation completes, the container must roll back rather than commit the transaction. If the business method has returned normally or with an application exception, the container must pass the method result or the application exception to the client after the container performed the rollback.". However, if exception-on-rollback is true, JBoss EJB Container throws the TransactionRolledbackException when the transaction should be rolled back because of the setRollbackOnly invocation. This clearly violates the EJB spec requirements mentioned above. It seems that the TxInterceptorCMT.checkTransactionStatus method should not throw the exception when the transaction status is STATUS_MARKED_ROLLBACK. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-425) Fix maven bug in release plugin

by Paul Gier (JIRA)

Fix maven bug in release plugin ------------------------------- Key: JBBUILD-425 URL: http://jira.jboss.com/jira/browse/JBBUILD-425 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 There is an issue when using a test-jar in during a release. http://jira.codehaus.org/browse/MRELEASE-285 This should be fixed since a few of our projects have dependencies like this. -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-828) Interceptor negotiation mechanism

by David Lloyd (JIRA)

Interceptor negotiation mechanism --------------------------------- Key: JBREM-828 URL: http://jira.jboss.com/jira/browse/JBREM-828 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assigned To: David Lloyd Fix For: Remoting 3 M1 The participants need to negotiate what interceptors should exist on a per-service basis. Work out further requirements, and implement. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1706) Ability to secure access to certain modes

by Thomas Heute (JIRA)

Ability to secure access to certain modes ----------------------------------------- Key: JBPORTAL-1706 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1706 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.6.3 Final We should be able to restrict the access to the different modes: VIEW, EDIT, HELP, ADMIN, custom... -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-765) EJB3 documentation on website is out of date

by Jeff Schnitzer (JIRA)

EJB3 documentation on website is out of date -------------------------------------------- Key: EJBTHREE-765 URL: http://jira.jboss.com/jira/browse/EJBTHREE-765 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: Jeff Schnitzer Two things: The docs at http://docs.jboss.org/ejb3/ are for EJB3 RC6 The "Notes" link on http://labs.jboss.com/portal/jbossejb3/download/index.html points at the release notes for RC4. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-188) Make it possible to jump to a category from Jumpbox

by Ryszard Kozmik (JIRA)

Make it possible to jump to a category from Jumpbox --------------------------------------------------- Key: JBFORUMS-188 URL: http://jira.jboss.com/jira/browse/JBFORUMS-188 Project: JBoss Forums Issue Type: Task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor Fix For: 1.2.0 Alpha Now it is only possible to jump to specified forum from Jumpbox. It should be also possible to jump to category. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-125) BBCode URL Tag improvement

by Ryszard Kozmik (JIRA)

BBCode URL Tag improvement -------------------------- Key: JBFORUMS-125 URL: http://jira.jboss.com/jira/browse/JBFORUMS-125 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.1.0 Alpha BBCode's URL tag could work similar to html "a href" style like : [url=http://www.example.com]My Example[/url] -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-728) Improve access to HTTP response headers

by Thomas Diesler (JIRA)

Improve access to HTTP response headers --------------------------------------- Key: JBREM-728 URL: http://jira.jboss.com/jira/browse/JBREM-728 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha7 Reporter: Thomas Diesler Assigned To: Tom Elrod JAXWS needs access to the HTTP response headers /** * Standard property: HTTP response headers. * <p>Type: java.util.Map<java.lang.String, java.util.List<java.lang.String>> */ public static final String HTTP_RESPONSE_HEADERS = "javax.xml.ws.http.response.headers"; Currently remoting copies these headers to the metadata and I can access them doing a little guess work like this // Get the HTTP response headers Map<String, List> headers = new HashMap<String, List>(); for (Map.Entry en : msgContext.entrySet()) { if (en.getKey() instanceof String && en.getValue() instanceof List) headers.put((String)en.getKey(), (List)en.getValue()); } msgContext.put(MessageContext.HTTP_RESPONSE_HEADERS, headers); I suggest remoting copies the concept of accessing the headers through a single property -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4643) Fix org.jboss.test.xml.DDValidatorUnitTestCase (5 failures)

by Dimitris Andreadis (JIRA)

Fix org.jboss.test.xml.DDValidatorUnitTestCase (5 failures) ----------------------------------------------------------- Key: JBAS-4643 URL: http://jira.jboss.com/jira/browse/JBAS-4643 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta3 testEjbJar Failure 5 from 165 are invalid expected:<0> but was:<5> junit.framework.AssertionFailedError: 5 from 165 are invalid expected:<0> but was:<5> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testEjbJar(DDValidatorUnitTestCase.java:76) 9.162 testJBossXml Failure 3 from 143 are invalid expected:<0> but was:<3> junit.framework.AssertionFailedError: 3 from 143 are invalid expected:<0> but was:<3> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossXml(DDValidatorUnitTestCase.java:81) 2.797 testJBossCmpJdbc Success 0.994 testWebXml Success 1.930 testJBossWeb Failure 4 from 39 are invalid expected:<0> but was:<4> junit.framework.AssertionFailedError: 4 from 39 are invalid expected:<0> but was:<4> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossWeb(DDValidatorUnitTestCase.java:96) 0.455 testApplicationXml Failure 8 from 50 are invalid expected:<0> but was:<8> junit.framework.AssertionFailedError: 8 from 50 are invalid expected:<0> but was:<8> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testApplicationXml(DDValidatorUnitTestCase.java:101) 0.635 testJBossApp Failure 2 from 37 are invalid expected:<0> but was:<2> junit.framework.AssertionFailedError: 2 from 37 are invalid expected:<0> but was:<2> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossApp(DDValidatorUnitTestCase.java:106) 0.825 -- 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, 8 months

3
9
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 October 2007