August 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBPM-703) Incompatibility with Sybase jConnect 5.5.latest

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-703?page=com.atlassian.jira.plugi... ] Thomas Diesler reopened JBPM-703: --------------------------------- FYI, I've asked Goldman which issues they are still facing with getting jBPM to work on Sybase, and this was their reply: "All the JIRA items [see below] are necessary. The database version we are using are Sybase 12.5 and UDB version is 9.1.5. We are using jconn2.jar and jconn3.jar for Sybase, db2jcc.jar for UDB." Sybase related JIRA items: 1. Usage of 'CLOB' columns instead of 'VARCHAR(4000)' [JBPM-701] 2. Usage of 'BINARY NOT NULL' columns instead of 'VARBINARY' [JBPM-702] 3. Avoid truncation of large context data by using the JCONNECT_VERSION=6 option [JBPM-703] 4. Increase the default page size [JBPM-1176] > Incompatibility with Sybase jConnect 5.5.latest > ----------------------------------------------- > > Key: JBPM-703 > URL: https://jira.jboss.org/jira/browse/JBPM-703 > Project: JBoss jBPM > Issue Type: Sub-task > Affects Versions: jBPM 3.1 > Environment: Sybase 12.5 > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Fix For: JBossBPM-3.3.0.GA > > > When storing data in the jBPM context with size greater than 255 bytes, the data is truncated at some point. > This issue only occurs with the jConnect 5.5 drivers, and not with the jTds opensource drivers. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-703) Incompatibility with Sybase jConnect 5.5.latest

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-703?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-703: -------------------------------- Fix Version/s: JBossBPM-3.3.0.GA Assignee: (was: Ryan Campbell) > Incompatibility with Sybase jConnect 5.5.latest > ----------------------------------------------- > > Key: JBPM-703 > URL: https://jira.jboss.org/jira/browse/JBPM-703 > Project: JBoss jBPM > Issue Type: Sub-task > Affects Versions: jBPM 3.1 > Environment: Sybase 12.5 > Reporter: Ryan Campbell > Fix For: JBossBPM-3.3.0.GA > > > When storing data in the jBPM context with size greater than 255 bytes, the data is truncated at some point. > This issue only occurs with the jConnect 5.5 drivers, and not with the jTds opensource drivers. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-702) Use non-nullable binary fields instead of varbinary on Sybase

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-702?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-702: -------------------------------- Fix Version/s: JBossBPM-3.3.0.GA > Use non-nullable binary fields instead of varbinary on Sybase > ------------------------------------------------------------- > > Key: JBPM-702 > URL: https://jira.jboss.org/jira/browse/JBPM-702 > Project: JBoss jBPM > Issue Type: Sub-task > Components: Core Engine > Reporter: Ryan Campbell > Assignee: Tom Baeyens > Fix For: jBPM 3.1.3, JBossBPM-3.3.0.GA > > > Sybase truncates trailing zeros of blobs which prevents blog retrieval. These fields need to be created as non-nullable binary fields, not varbinary. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBPM-702) Use non-nullable binary fields instead of varbinary on Sybase

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-702?page=com.atlassian.jira.plugi... ] Thomas Diesler reopened JBPM-702: --------------------------------- FYI, I've asked Goldman which issues they are still facing with getting jBPM to work on Sybase, and this was their reply: "All the JIRA items [see below] are necessary. The database version we are using are Sybase 12.5 and UDB version is 9.1.5. We are using jconn2.jar and jconn3.jar for Sybase, db2jcc.jar for UDB." Sybase related JIRA items: 1. Usage of 'CLOB' columns instead of 'VARCHAR(4000)' [JBPM-701] 2. Usage of 'BINARY NOT NULL' columns instead of 'VARBINARY' [JBPM-702] 3. Avoid truncation of large context data by using the JCONNECT_VERSION=6 option [JBPM-703] 4. Increase the default page size [JBPM-1176] > Use non-nullable binary fields instead of varbinary on Sybase > ------------------------------------------------------------- > > Key: JBPM-702 > URL: https://jira.jboss.org/jira/browse/JBPM-702 > Project: JBoss jBPM > Issue Type: Sub-task > Components: Core Engine > Reporter: Ryan Campbell > Assignee: Tom Baeyens > Fix For: jBPM 3.1.3, JBossBPM-3.3.0.GA > > > Sybase truncates trailing zeros of blobs which prevents blog retrieval. These fields need to be created as non-nullable binary fields, not varbinary. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-701) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-701?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-701: -------------------------------- Fix Version/s: JBossBPM-3.3.0.GA > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-701 > URL: https://jira.jboss.org/jira/browse/JBPM-701 > Project: JBoss jBPM > Issue Type: Sub-task > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Tom Baeyens > Fix For: JBossBPM-3.3.0.GA > > Attachments: sybase.build.xml > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Similarly, a CLOB or equivalent should be used on DB2. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBPM-701) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-701?page=com.atlassian.jira.plugi... ] Thomas Diesler reopened JBPM-701: --------------------------------- Martin sais, FYI, I've asked Goldman which issues they are still facing with getting jBPM to work on Sybase, and this was their reply: "All the JIRA items [see below] are necessary. The database version we are using are Sybase 12.5 and UDB version is 9.1.5. We are using jconn2.jar and jconn3.jar for Sybase, db2jcc.jar for UDB." Sybase related JIRA items: 1. Usage of 'CLOB' columns instead of 'VARCHAR(4000)' [JBPM-701] 2. Usage of 'BINARY NOT NULL' columns instead of 'VARBINARY' [JBPM-702] 3. Avoid truncation of large context data by using the JCONNECT_VERSION=6 option [JBPM-703] 4. Increase the default page size [JBPM-1176] > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-701 > URL: https://jira.jboss.org/jira/browse/JBPM-701 > Project: JBoss jBPM > Issue Type: Sub-task > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Tom Baeyens > Attachments: sybase.build.xml > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Similarly, a CLOB or equivalent should be used on DB2. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1690) finish jBPM 3 QA

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1690?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1690: ------------------------------ > finish jBPM 3 QA > ---------------- > > Key: JBPM-1690 > URL: https://jira.jboss.org/jira/browse/JBPM-1690 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > > There are a number of QA jobs set up. > First we need to drop the configurations that are not easily fixed and that are not part of Tier 1 SOA platform jobs. > Secondly, we need to add the configurations until Tier 1 configurations are covered. > Then the jobs should be updated so that they point to the new codebase. We need to determine what codebase that is. Or duplicate the jobs between project and product. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1690) finish jBPM 3 QA

by Tom Baeyens (JIRA)

finish jBPM 3 QA ---------------- Key: JBPM-1690 URL: https://jira.jboss.org/jira/browse/JBPM-1690 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Tom Baeyens There are a number of QA jobs set up. First we need to drop the configurations that are not easily fixed and that are not part of Tier 1 SOA platform jobs. Secondly, we need to add the configurations until Tier 1 configurations are covered. Then the jobs should be updated so that they point to the new codebase. We need to determine what codebase that is. Or duplicate the jobs between project and product. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ] Alejandro Guizar resolved JBPM-1452. ------------------------------------ Resolution: Done > JbpmConfiguration assumes the object factory has a jbpm.job.executor entry > -------------------------------------------------------------------------- > > Key: JBPM-1452 > URL: https://jira.jboss.org/jira/browse/JBPM-1452 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossBPM-3.3.0 > Environment: 3.3 snapshot > Spring > Reporter: Alejandro Guizar > Assignee: Alejandro Guizar > Fix For: JBossBPM-3.3.0 > > > The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR. > org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size] > at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76) > at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603) > at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51) > at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32) > at org.jbpm.svc.Services.getService(Services.java:156) > at org.jbpm.svc.Services.getCurrentService(Services.java:94) > at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328) > at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329) > at org.jbpm.graph.exe.Token.end(Token.java:301) > at org.jbpm.graph.exe.Token.end(Token.java:251) > at org.jbpm.graph.node.EndState.execute(EndState.java:59) > The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-1452: ---------------------------------------- Feedback: "The development team has reported that using the null entry for jbpm.job.executor allows tasks to complete." > JbpmConfiguration assumes the object factory has a jbpm.job.executor entry > -------------------------------------------------------------------------- > > Key: JBPM-1452 > URL: https://jira.jboss.org/jira/browse/JBPM-1452 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossBPM-3.3.0 > Environment: 3.3 snapshot > Spring > Reporter: Alejandro Guizar > Assignee: Alejandro Guizar > Fix For: JBossBPM-3.3.0 > > > The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR. > org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size] > at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76) > at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603) > at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51) > at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32) > at org.jbpm.svc.Services.getService(Services.java:156) > at org.jbpm.svc.Services.getCurrentService(Services.java:94) > at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328) > at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329) > at org.jbpm.graph.exe.Token.end(Token.java:301) > at org.jbpm.graph.exe.Token.end(Token.java:251) > at org.jbpm.graph.node.EndState.execute(EndState.java:59) > The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2008