February 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1997) API package refactoring

by Heiko Braun (JIRA)

API package refactoring ----------------------- Key: JBPM-1997 URL: https://jira.jboss.org/jira/browse/JBPM-1997 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 * api - the public api (client services, client, activity, eventlisteners) - all other modules should have package names that include ..internal.. -- 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

2
1
0 / 0

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

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-2057: --------------------------------- Fix Version/s: jBPM-3.2.5.SP2 (was: jBPM 3.2.x) > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2 > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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-2012) Split jars into *-api.jar and *-impl.jar

by Heiko Braun (JIRA)

Split jars into *-api.jar and *-impl.jar ---------------------------------------- Key: JBPM-2012 URL: https://jira.jboss.org/jira/browse/JBPM-2012 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0 Alpha2 Otherwise test suite dependencies cannot be sorted out. Examples should only refer to public API at compile time -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2011) Move non public classes to **/internal

by Heiko Braun (JIRA)

Move non public classes to **/internal -------------------------------------- Key: JBPM-2011 URL: https://jira.jboss.org/jira/browse/JBPM-2011 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 -- 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

2
3
0 / 0

[JBoss JIRA] Commented: (JBPM-2043) Add jBPM performance test coverage

by Pavel Macik (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2043?page=com.atlassian.jira.plug... ] Pavel Macik commented on JBPM-2043: ----------------------------------- I configured 2 jobs on hudson running those tests. Each runs the SimplePerformanceTest N-times (to avoid glitches) on jBPM 3.2.2 and 3.2.5 taken from SVNs: https://svn.jboss.org/repos/jbpm/jbpm3/branches/jpdl-3.2.2-SOA-4.2 https://svn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2.5.SP First job- using hsqldb http://hudson.qa.jboss.com/hudson/job/jira-jbpm-2043 Second job - using MySQL (dev02.qa.atl2.redhat.com server) http://hudson.qa.jboss.com/hudson/job/jira-jbpm-2043-mysql > Add jBPM performance test coverage > ---------------------------------- > > Key: JBPM-2043 > URL: https://jira.jboss.org/jira/browse/JBPM-2043 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Productization > Affects Versions: jBPM 3.2.5 GA > Environment: SOA 4.3.0 CP01 CR2 > Reporter: Pavel Macik > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA > > > Performance of jBPM has dropped significantly according to > http://hudson.qa.jboss.com/hudson/view/SOA-Performance/job/SOA-Platform-P... > Other performance has not changed much so the performance drop is isolated to jBPM. -- 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-2043) Add jBPM performance test coverage

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2043?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-2043: --------------------------------- Fix Version/s: jBPM 3.2.6 GA > Add jBPM performance test coverage > ---------------------------------- > > Key: JBPM-2043 > URL: https://jira.jboss.org/jira/browse/JBPM-2043 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Productization > Affects Versions: jBPM 3.2.5 GA > Environment: SOA 4.3.0 CP01 CR2 > Reporter: Pavel Macik > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA > > > Performance of jBPM has dropped significantly according to > http://hudson.qa.jboss.com/hudson/view/SOA-Performance/job/SOA-Platform-P... > Other performance has not changed much so the performance drop is isolated to jBPM. -- 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-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-2057: --------------------------------- Comment: was deleted > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM 3.2.x > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-2057: --------------------------------- Fix Version/s: jBPM 3.2.x (was: jBPM-3.2.5.SP2) > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM 3.2.x > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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] Work stopped: (JBPM-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Work on JBPM-2057 stopped by Thomas Diesler. > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM 3.2.x > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-2057: -------------------------------------- I'm rolling back this fix, which effectively restores the original jbpm322 schema except for the JBPM-1755 related additional column. Looking at the email exchange below, it seems that Goldman Sachs does not strictly require a switch to type="text". I propose that we work directly with them to find out what they actually need. This issue is moved to 3.2.x ------------------------------------------ Also, to migrate, can not we just manually convert the data from <4000> to <text> columns? -----Original Message----- From: Xu, Xiangdong Sent: Friday, February 20, 2009 3:20 PM To: Xu, Xiangdong; 'Burr Sutter' Cc: 'Thomas Diesler'; 'Scott Sajer' Subject: RE: https://jira.jboss.org/jira/browse/JBPM-2057 Hi, just read the case and Thomas' comments. Due to migration issue. Thomas suggested a adding additional columns. Would that be the approach for other varchar(4000) columns? Does it completely solve the migration problem? -----Original Message----- From: Xu, Xiangdong Sent: Friday, February 20, 2009 11:00 AM To: 'Burr Sutter' Cc: Thomas Diesler; Scott Sajer Subject: RE: https://jira.jboss.org/jira/browse/JBPM-2057 Burr, thanks for getting back to me. Just to be clear that we have not seen truncation so far. We only see the warning message from Sybase since the page size of our Sybase server is 2k which could potentially cause truncation if the object size is larger than 2k. My questions is should we go with CLOB just to be safe? If we go CLOB, what is the related change has to be made? Thanks -xiangdong -----Original Message----- From: Burr Sutter [mailto:bsutter@redhat.com] Sent: Friday, February 20, 2009 7:51 AM To: Xu, Xiangdong Cc: Thomas Diesler; Scott Sajer Subject: https://jira.jboss.org/jira/browse/JBPM-2057 Xiangdong, We are working on a solution to address jBPM-2057 - truncating data into varchar(4000) columns. Thomas Diesler on our team is researching how we could accomplish this adjustment and has made some comments on the jira task. Our goal is to make a database portable solution and we have to be concerned about jBPM production databases as well. Can you tell us which columns are specifically the problem for your usage scenarios? Thomas may have some questions for you and your team as well. Thank you, Burr > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2 > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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 February 2009