September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1086) ClassCastException: EsbActionHandler - while using the jBPM Admin Console's Task Manager

by Burr Sutter (JIRA)

ClassCastException: EsbActionHandler - while using the jBPM Admin Console's Task Manager ---------------------------------------------------------------------------------------- Key: JBESB-1086 URL: http://jira.jboss.com/jira/browse/JBESB-1086 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 IR1 See attached document called jBPM_ESB_Human_Tasks.odt - the steps to reproduce the issue are documented (about 16 pages with screenshots and stack traces). -- 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

17 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-1101) Hibernate config for jbpm taked from wrong place

by Mikhail Kolesnikov (JIRA)

Hibernate config for jbpm taked from wrong place ------------------------------------------------ Key: JBESB-1101 URL: http://jira.jboss.com/jira/browse/JBESB-1101 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Deployment Affects Versions: 4.2 Reporter: Mikhail Kolesnikov Assigned To: Mark Little Fix For: 4.2.1, 4.2 Hibernate config for jbpm taked from jbpm.esb\jbpm-console.war\WEB-INF\classes and not from jbpm.esb folder. It's tend to wrong bechaviour - i must change Hibernate dialect in two places and one of its isn't so logicaly. Please, remove such configuration file from jbpm-console.war Thanks -- 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

17 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-992) Incorrect hibernate configuration file handling for jBPM

by Jiri Pechanec (JIRA)

Incorrect hibernate configuration file handling for jBPM -------------------------------------------------------- Key: JBESB-992 URL: http://jira.jboss.com/jira/browse/JBESB-992 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Jiri Pechanec Assigned To: Mark Little When editing hibernate.cfg.xml file in jbpm.esb to change database settings the changes in file are ignored. Instead the configuration file from jbpm-console.war is processed. There should be only one configuration file - not one for console and one for jbpm itself. -- 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

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-996) MYSQL drivers are bundled in some of the quickstarts

by Tom Fennelly (JIRA)

MYSQL drivers are bundled in some of the quickstarts ---------------------------------------------------- Key: JBESB-996 URL: http://jira.jboss.com/jira/browse/JBESB-996 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2.1 I don't think we should be bundling these drivers in any of our components. These drivers should be added based on the version of the installed Server. -- 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

17 years, 1 month

5
12
0 / 0

[JBoss JIRA] Created: (JBESB-1062) Clean up Content Based Routing guide

by Richard Achmatowicz (JIRA)

Clean up Content Based Routing guide ------------------------------------ Key: JBESB-1062 URL: http://jira.jboss.com/jira/browse/JBESB-1062 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Richard Achmatowicz Assigned To: Mark Little I've been reading through the content based routing guide, as someone who knows nothing about it. Chapter 1,although short, is beautifully written. Chapter 2 is virtually unreadable and doesn't cover the important bases adequately: - possibilities for setting up a content-based router, and all configurable properties - key aspects of specifying rules in DRL - key aspects of specifying rules in XPath - how to link rules with the router defined earlier These aspects were touched on, but not in a way that made any sense to me. I decided to look at a quickstart and guess all of the above rather than read the document, which really defeats the purpose of providing documentation. Sorry to be so harsh, but I think what i'm saying is accurate. -- 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

17 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-994) The security configuration files are missing for jbpm console

by Jiri Pechanec (JIRA)

The security configuration files are missing for jbpm console ------------------------------------------------------------- Key: JBESB-994 URL: http://jira.jboss.com/jira/browse/JBESB-994 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor Attachments: roles.properties, users.properties The jbpm-console.war uses default JBoss security mechanism. Unfortunately the security config files are missing. To get it running the attached files users.properties and groups.properties should be put to server/default/conf directory -- 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

17 years, 1 month

5
10
0 / 0

[JBoss JIRA] Created: (JBESB-735) Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed

by Burr Sutter (JIRA)

Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed --------------------------------------------------------------------- Key: JBESB-735 URL: http://jira.jboss.com/jira/browse/JBESB-735 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 My notes on how to make it run with AS 4.2 with Java 5 are here: http://jboss.org/index.html?module=bb&op=viewtopic&t=112908 And here: Steps (for AS 4.2 + Messaging 1.3 + ESB 4.2MR3) 1. Deploy attached hypersonic databases to the server\messaging\data\hypersonic director. jbpmDB.properties, jbpmDB.script 2. Deploy attached datasource - jbpm-ds.xml into the server\messaging\deploy directory 3. Deploy attached jbpm-console.war - created from CVS because the one in the jBPM3.2.1 suite do not work with Java 5 4. Modify the conf\login-config.xml be inserting the following: <application-policy name = "jbpm"> <authentication> <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required"> <module-option name="dsJndiName">java:/JbpmDS</module-option> <module-option name="principalsQuery"> SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=? </module-option> <module-option name="rolesQuery"> SELECT g.NAME_ ,'Roles' FROM JBPM_ID_USER u, JBPM_ID_MEMBERSHIP m, JBPM_ID_GROUP g WHERE g.TYPE_='security-role' AND m.GROUP_ = g.ID_ AND m.USER_ = u.ID_ AND u.NAME_=? </module-option> </login-module> </authentication> </application-policy> 5. Modify the server\messaging\deploy\jbpm.esb\hibernate.cfg.xml so that it uses the DS defined in step 2. The result should look something like the following: <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property>  <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>  <property name="hibernate.connection.datasource">java:/JbpmDS</property>  6. Start your server with run -c messaging N . http://localhost:8080/jbpm-console -- 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

17 years, 1 month

6
15
0 / 0

[JBoss JIRA] Created: (JBESB-858) Make sure we use the right versions of dependant components (part 2)

by Kurt Stam (JIRA)

Make sure we use the right versions of dependant components (part 2) -------------------------------------------------------------------- Key: JBESB-858 URL: http://jira.jboss.com/jira/browse/JBESB-858 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2.1 For 4.2 we have: JBM 1.4 CR1 Drools 4.0GA JBWS 2.0.0GA JBAS 4.2.1GA jBPM 3.2.1 For 4.2.1 we need to upgrade to JBM 1.4 GA Drools 4.0.x maintenance release JBWS 2.0x? look at removing ejb3 dependency (may not need an update, but maybe a config issue) jBPM 3.2.2 to fix currently known issues for the ESB with the 3.2.1 build. -- 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

17 years, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-1061) Update wiki documentation and tidy up Admin guide

by Kevin Conner (JIRA)

Update wiki documentation and tidy up Admin guide ------------------------------------------------- Key: JBESB-1061 URL: http://jira.jboss.com/jira/browse/JBESB-1061 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor Fix For: 4.2.1 The documentation page on the wiki includes an attachment describing how to setup JBoss Messaging with JBoss ESB. This document is out of date and is referred to from the Administration Guide. The wiki document page is at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBDocumentation -- 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

17 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-855) JMSCourier does not return JMS Session to pool in jmsConnectRetry

by Daniel Bevenius (JIRA)

JMSCourier does not return JMS Session to pool in jmsConnectRetry ----------------------------------------------------------------- Key: JBESB-855 URL: http://jira.jboss.com/jira/browse/JBESB-855 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Reporter: Daniel Bevenius Assigned To: Mark Little Fix For: 4.2.1 Google group ref : http://groups.google.se/group/jbossesb/browse_frm/thread/477d6a3bca232ab2... We started to see this message in our ESB server log: [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] The connection pool was exhausted. Waiting 1 second before trying again I took a look at JMSCouriers jmsConnectRetry() method and this section caught my attention: private void jmsConnectRetry (Exception exc) { _logger.debug("JMS error. Attempting JMS reconnect.", exc); _jmsSession = null; _messageProducer = null; _messageConsumer = null; ... } Should the session be returned to the pool instead of only setting it to null? Something like this perhaps: _pool.releaseSession( _jmsSession ); /Daniel -- 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

17 years, 1 month

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007