February 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1444) jBPM CommandService is bottleneck of jBPM process processing

by Jiri Pechanec (JIRA)

jBPM CommandService is bottleneck of jBPM process processing ------------------------------------------------------------ Key: JBESB-1444 URL: http://jira.jboss.com/jira/browse/JBESB-1444 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Critical Fix For: 4.2.1 CP1 The problem is that the process is executed in context of the thread of the service. It means that if there are more services that invokes jBPM process than all copntiunations are executed in the context of this single thread. This in turn can lead into large amount of started processes in blocked state waiting for a signal form Callback service. This behaviour should be at least documented with the hint that amount of threads of CallbackService should be increased and where. As a mid/long term solution I would prefer something that resembles following architecture 1) Let's suppose that JBoss Messaging supports message priorities and takes them into consideration when reading messages from the queue 2) Let's suppose we can set message priority when we are invoking service 3) Define a service called jBPM executor which have configured amount of thread 4) When the jBPM process is invoked then the result of invocation is message passed to jBPM executor with low-priority 5) When the jBPM process is to be called back then the message is passed to jBPM executor with high-priority Such solution will prefer completion of started jBPM processes before starting the new ones and will allow manage the resources assgined to jBPM execution at the same place. We can say that this soultion is equivalent to pool of executor threads which prioritizes signal commands to start process commands. -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1511) The jBPM does not work with PostgreSQL/Oracle - constraint violations

by Jiri Pechanec (JIRA)

The jBPM does not work with PostgreSQL/Oracle - constraint violations --------------------------------------------------------------------- Key: JBESB-1511 URL: http://jira.jboss.com/jira/browse/JBESB-1511 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Environment: CR1 - embedded Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Blocker Fix For: 4.2.1 CP1 Attachments: server.log.gz When ESB is under load, the jBPM operations can start to generate constraint violation exceptions - see attached log file. According to Kevin C. it means that there can be race condition when Hibernate generates primary keys. This issue is present on PostgreSQL/Oracle but is not present on MySQL. -- 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

16 years, 3 months

5
13
0 / 0

[JBoss JIRA] Created: (JBESB-1483) Handling suspended jBPM processes

by Kevin Conner (JIRA)

Handling suspended jBPM processes --------------------------------- Key: JBESB-1483 URL: http://jira.jboss.com/jira/browse/JBESB-1483 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.2.1 CP1 We need to come up with a strategy for handling the ESB->jBPM notifications for tokens which are in a suspended state. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1529) DatabaseInitializer requires statements terminated by semi colon

by Kevin Conner (JIRA)

DatabaseInitializer requires statements terminated by semi colon ---------------------------------------------------------------- Key: JBESB-1529 URL: http://jira.jboss.com/jira/browse/JBESB-1529 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.2.1 CP1 The DatabaseInitializer class assumes that the statements being executed will all be terminated using a semi-colon, unfortunately this is not the case for a number of DDL files automatically generated by hibernate. Each statement is, however, on it's own line. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1532) Replace jBPM hypersonic database with another java database

by Kevin Conner (JIRA)

Replace jBPM hypersonic database with another java database ----------------------------------------------------------- Key: JBESB-1532 URL: http://jira.jboss.com/jira/browse/JBESB-1532 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1 We are currently using hypersonic as a test database within the project. Unfortunately we are now at the point where the jBPM integration relies on the transactional isolation for correct behaviour. We need to replace the jBPM DB with another java DB which supports transactional isolation. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1530) ESB project issue SOA-390 - JBPM quickstarts do not deploy processimage.jpg and gpd.xml files

by Len DiMaggio (JIRA)

ESB project issue SOA-390 - JBPM quickstarts do not deploy processimage.jpg and gpd.xml files --------------------------------------------------------------------------------------------- Key: JBESB-1530 URL: http://jira.jboss.com/jira/browse/JBESB-1530 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Len DiMaggio Assigned To: Tom Baeyens Fix For: 4.2.1 CP1 Project JIRA for SOA-P JIRA: SOA-390 -- 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

16 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1526) webservice_mtom quickstart contains inappropriate sources

by Jiri Pechanec (JIRA)

webservice_mtom quickstart contains inappropriate sources --------------------------------------------------------- Key: JBESB-1526 URL: http://jira.jboss.com/jira/browse/JBESB-1526 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Trivial Fix For: 4.2.1 CP1 There is a dir src/org/jboss/soa/esb/samples/quickstart/webservicemtom/test/ but the files inside are apparently just copy of webservice_producer tests. They are not used for this test. -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1527) XML preamble in generated WSDL breaks quickstarts

by Kevin Conner (JIRA)

XML preamble in generated WSDL breaks quickstarts ------------------------------------------------- Key: JBESB-1527 URL: http://jira.jboss.com/jira/browse/JBESB-1527 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1 [java] [Fatal Error] :12:6: The processing instruction target matching "[xX][mM][lL]" is not allowed. [java] Exception in thread "main" org.jboss.ws.metadata.wsdl.WSDLException: Cannot parse wsdlLocation: http://localhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&... [java] at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.getDocument(WSDLDefinitionsFactory.java:183) [java] at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:108) [java] at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:321) Reproduce in webservice_wssecurity - ant deploy - ant runtest -- 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

16 years, 3 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2008