September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1082) Finding jars not in drools 4.0.1.GA in ESB's jbrules.esb

by Len DiMaggio (JIRA)

Finding jars not in drools 4.0.1.GA in ESB's jbrules.esb -------------------------------------------------------- Key: JBESB-1082 URL: http://jira.jboss.com/jira/browse/JBESB-1082 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 IR1 Environment: ESB: svn update Updated to revision 15241. Reporter: Len DiMaggio Assigned To: Mark Little Priority: Minor Finding jars not in drools 4.0.1.GA in ESB's jbrules.esb We found these jars - jxl-2.4.2.jar, xpp3_min-1.1.3.4.O.jar, janino-2.5.7.jar - in the ESB's jbrules.esb - but the jars are not in drools 4.0.1.GA - is the inclusion of these files intentional? -- 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

6
9
0 / 0

[JBoss JIRA] Created: (JBESB-832) ${jboss.bind.address} support in ESB configuration files

by Matt Hicks (JIRA)

${jboss.bind.address} support in ESB configuration files -------------------------------------------------------- Key: JBESB-832 URL: http://jira.jboss.com/jira/browse/JBESB-832 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Environment: RHEL 5 / JBoss 4.2.1 Reporter: Matt Hicks Assigned To: Mark Little Fix For: 4.2 Milestone Release 3 We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh -c esb -b 172.17.0.1). However, there are several problems with the ESB configuration when doing this. The first file is simple: * <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml This file needs every instance of 'localhost' changed to '${jboss.bind.address}' and it works. The next 3 files aren't as simple since JBoss doesn't support property replacement in properties files to my knowledge: * <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties * <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties * <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties These files need to have the same property dynamically looked up based on the binding or might need to be converted to XML to have the property replaced. -- 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

6
13
0 / 0

[JBoss JIRA] Created: (JBESB-1078) Create Quickstart Guide

by Mark Little (JIRA)

Create Quickstart Guide ----------------------- Key: JBESB-1078 URL: http://jira.jboss.com/jira/browse/JBESB-1078 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Burr Sutter Fix For: 4.2.1 As per previous discussions. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-871) Configure core ESB services using ServiceBindingManager

by Kevin Conner (JIRA)

Configure core ESB services using ServiceBindingManager ------------------------------------------------------- Key: JBESB-871 URL: http://jira.jboss.com/jira/browse/JBESB-871 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Kevin Conner Assigned To: Kevin Conner We should be able to configure the core ESB services using the ServiceBindingManager. The configuration should include the following esb.juddi.properties smooks.esb.properties jbossesb-properties.xml -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-1104) Make esb dependencies implicit

by Kevin Conner (JIRA)

Make esb dependencies implicit ------------------------------ Key: JBESB-1104 URL: http://jira.jboss.com/jira/browse/JBESB-1104 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 The jbossesb.esb dependency is now implicit. Similar dependencies can be created by checking the actions in use. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-989) Quickstart: dynamic_router - ReceiveJMSMessage has a memory leak

by Burr Sutter (JIRA)

Quickstart: dynamic_router - ReceiveJMSMessage has a memory leak ---------------------------------------------------------------- Key: JBESB-989 URL: http://jira.jboss.com/jira/browse/JBESB-989 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 The dynamic_router quickstart has the user execute 3 JMS "listeners" for the purposes of the demonstration. It uses the class called org.jboss.soa.esb.samples.quickstart.dynamicRouter.test.ReceiveJMSMessage.java to perform this this capability. This causes the ESB/AS that is hosting the JMS broker to put on about 20K in memory every 1 to 2 seconds which eventually leads to an out of memory error. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-736) ReceiveJMSMessage class is confusing and partly buggy

by Jiri Pechanec (JIRA)

ReceiveJMSMessage class is confusing and partly buggy ----------------------------------------------------- Key: JBESB-736 URL: http://jira.jboss.com/jira/browse/JBESB-736 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Optional The class used in samples for reading JMS messages from the queue is confusing and partly buggy. The class repeatedly reads from the queue directly and repeatedly sets up own listener. Also it creates an infinite number of sessions that are not closed. Recommended solution In method main cut the call of method receive one from the infinite loop and put it before the loop. Place a sleep method inside the infinite loop. In that way both direct reading and listener pattern will be demonstrated. Initialization of all resources will be executed only once. -- 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
7
0 / 0

[JBoss JIRA] Created: (JBESB-1069) GDP deployer servlet not working

by Bruno Unna (JIRA)

GDP deployer servlet not working -------------------------------- Key: JBESB-1069 URL: http://jira.jboss.com/jira/browse/JBESB-1069 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Bruno Unna Assigned To: Mark Little Fix For: 4.2.1 The jBPM Designer is unable to test the connection to jBPM in order to deploy a process definition. It is unable, as well, to perform the deployment. The "Test Connection..." button delivers a very uninformative error, but the JBoss AS console shows this line: 12:04:49,344 INFO [[GDP Deployer Servlet]] Servlet GDP Deployer Servlet is currently unavailable -- 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-1050) DBMessageStoreImpl: Cannot change transaction isolation level in the middle of a transaction. Postgres

by Daniel Bevenius (JIRA)

DBMessageStoreImpl: Cannot change transaction isolation level in the middle of a transaction. Postgres ------------------------------------------------------------------------------------------------------ Key: JBESB-1050 URL: http://jira.jboss.com/jira/browse/JBESB-1050 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Reporter: Daniel Bevenius Priority: Minor Fix For: 4.2.1 IR1 We have been seeing this DEBUG level message when we have more then one message with the same classification in the message store: 2007-09-14 10:08:05,376 DEBUG [org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl] Deadlocks may occur under normal processing 2007-09-14 10:08:05,376 DEBUG [org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl] Cannot change transaction isolation level in the middle of a transaction. org.postgresql.util.PSQLException: Cannot change transaction isolation level in the middle of a tran saction. at org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection. java:733) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.setJdbcTransactionIsolation(Base WrapperManagedConnection.java:534) at org.jboss.resource.adapter.jdbc.WrappedConnection.setTransactionIsolation(WrappedConnection.j ava:390) at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.redeliver(DBMessageStoreI mpl.java:318) at org.jboss.soa.esb.actions.MessageRedeliverer.process(MessageRedeliverer.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline .java:265) at org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:108) at org.jboss.soa.esb.schedule.ScheduleProvider$ESBScheduledJob.execute(ScheduleProvider.java:212 ) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) The code lines above might not directly match the ones in the current trunk as I've made a few modifications locally to support a simple redelivery of messages described in this dev forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116023&start=10 This following line of code in the redeliver method is causing this message: con = mgr.getConnection(); con.setAutoCommit(false); con.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED); The redeliver method is called by MessageRedeliverer action. The first message uid is successful but the second call will log the above message. But I do think that this will be an issue when using postgres. Some info about postgres and its transaction isolation levels: Quote: "In postgres, you can use all four possible transaction isolation levels. Internally, there are only two distinct isolation levels, which correspond to the levels Read Committed and Serializable. When you select the level Read Uncommitted you actually get Read Committed, and when you select Repeatable Read you really get Serializable, so the actual isolation level may be stricter than what you select." -- 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
8
0 / 0

[JBoss JIRA] Created: (JBESB-810) jBPM Admin Console Build

by Burr Sutter (JIRA)

jBPM Admin Console Build ------------------------ Key: JBESB-810 URL: http://jira.jboss.com/jira/browse/JBESB-810 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 The build script for jBPM's Admin Console must be augmented to allow for the creation of an ESB "friendly" .war file. Currently the jbpm-console.war contains JSF libs which are incompatible with App Server 4.2. Plus, the ESB version of the jbpm-console.war should NOT include the jbpm/jpdl jars since those are already found in the jbpm.esb directory. Finally, the jbpm-console.war should be deployed in the jbpm.esb via ESB deployment build/installation script. -- 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
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007