jbpm-issues October 2009

jbpm-issues@lists.jboss.org

1 participants
225 discussions

[JBoss JIRA] Created: (JBPM-2281) figure out dependecies for Element.setUserData

by Tom Baeyens (JIRA)

figure out dependecies for Element.setUserData ---------------------------------------------- Key: JBPM-2281 URL: https://jira.jboss.org/jira/browse/JBPM-2281 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.CR1 Burr reported it while running the demo.setup script: BUILD FAILED C:\demo\jbpm-4.0.0.Beta2\jboss\build.xml:54: The following error occurred while executing this line: java.lang.AbstractMethodError: org.apache.xerces.dom.ElementNSImpl.setUserData(L java/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Obje ct; And I have seen it before when running an example in the enterprise module classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Resolved: (JBPM-2551) Prevent token modification if logging is disabled

by Julian Coleman (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2551?page=com.atlassian.jira.plug... ] Julian Coleman resolved JBPM-2551. ---------------------------------- Resolution: Done Fixes are integrated as part of the one-off build for SOA-1514. > Prevent token modification if logging is disabled > ------------------------------------------------- > > Key: JBPM-2551 > URL: https://jira.jboss.org/jira/browse/JBPM-2551 > Project: jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Runtime Engine > Affects Versions: jBPM 3.2.7 > Reporter: Len DiMaggio > Assignee: Julian Coleman > Fix For: jBPM 3.2.8 > > > jBPM project issue related to SOA-1507/JBESB-2846 (bpm_orchestration2 process is not safe) > The jBPM logging is currently handled through Token.addLog and, regardless of whether the log object is persisted or not, results in the modification of the associated token. > This happens because the ProcessLog.setToken method invokes the Token.nextLogIndex method, causing a change in the token and, therefore, a potential conflict with any other tokens in the process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-2551) Prevent token modification if logging is disabled

by Julian Coleman (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2551?page=com.atlassian.jira.plug... ] Julian Coleman updated JBPM-2551: --------------------------------- Fix Version/s: jBPM 3.2.8 Assignee: Julian Coleman > Prevent token modification if logging is disabled > ------------------------------------------------- > > Key: JBPM-2551 > URL: https://jira.jboss.org/jira/browse/JBPM-2551 > Project: jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Runtime Engine > Affects Versions: jBPM 3.2.7 > Reporter: Len DiMaggio > Assignee: Julian Coleman > Fix For: jBPM 3.2.8 > > > jBPM project issue related to SOA-1507/JBESB-2846 (bpm_orchestration2 process is not safe) > The jBPM logging is currently handled through Token.addLog and, regardless of whether the log object is persisted or not, results in the modification of the associated token. > This happens because the ProcessLog.setToken method invokes the Token.nextLogIndex method, causing a change in the token and, therefore, a potential conflict with any other tokens in the process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-2551) Prevent token modification if logging is disabled

by Len DiMaggio (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2551?page=com.atlassian.jira.plug... ] Len DiMaggio updated JBPM-2551: ------------------------------- Security: Public (was: JBoss Internal) > Prevent token modification if logging is disabled > ------------------------------------------------- > > Key: JBPM-2551 > URL: https://jira.jboss.org/jira/browse/JBPM-2551 > Project: jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Runtime Engine > Affects Versions: jBPM 3.2.7 > Reporter: Len DiMaggio > > jBPM project issue related to SOA-1507/JBESB-2846 (bpm_orchestration2 process is not safe) > The jBPM logging is currently handled through Token.addLog and, regardless of whether the log object is persisted or not, results in the modification of the associated token. > This happens because the ProcessLog.setToken method invokes the Token.nextLogIndex method, causing a change in the token and, therefore, a potential conflict with any other tokens in the process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2549) jBPM cannot be certified on SOA-P for HP

by Jiri Pechanec (JIRA)

jBPM cannot be certified on SOA-P for HP ---------------------------------------- Key: JBPM-2549 URL: https://jira.jboss.org/jira/browse/JBPM-2549 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.7 Environment: HP.UX risc, ia64 HP Java 5, 6 PostgreSQL, oracle 9i, Oracle 10g Reporter: Jiri Pechanec Priority: Critical Attachments: jbpm1755.tar.gz It is not possible to certify jBPM on HP-UX with database other than MySQL. The testsuite consistently fails on the test org.jbpm.jbpm1755.JBPM1755Test Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 9.576 sec <<< FAILURE! testUpgradeLock(org.jbpm.jbpm1755.JBPM1755Test) Time elapsed: 1.616 sec <<< ERROR! org.jbpm.persistence.JbpmPersistenceException: could not delete ProcessDefinition(raceCondition) at org.jbpm.db.GraphSession.deleteProcessDefinition(GraphSession.java:262) at org.jbpm.db.GraphSession.deleteProcessDefinition(GraphSession.java:231) at org.jbpm.jbpm1755.JBPM1755Test.tearDown(JBPM1755Test.java:30) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: org.hibernate.exception.JDBCConnectionException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2216) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.jbpm.db.GraphSession.deleteProcessDefinition(GraphSession.java:237) ... 22 more Caused by: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend. at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:255) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2213) ... 30 more Caused by: java.io.IOException: Stream closed at sun.nio.cs.StreamEncoder.ensureOpen(StreamEncoder.java:38) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:151) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at org.postgresql.core.PGStream.flush(PGStream.java:507) at org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:675) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:190) ... 38 more Moreover with SOA-P config in place it frequently happens that this issue happens also on the other TestCases and in worst case if it happens first time than the all following tests fails with the same reason. This behaviour is not observed on any other platform than HP. This behaviour is not observed on MySQL database -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
10
0 / 0

← Newer
1
...
20
21
22
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009