September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-454) Allow no inputSuffix on the FileGateway

by Kurt Stam (JIRA)

Allow no inputSuffix on the FileGateway --------------------------------------- Key: JBESB-454 URL: http://jira.jboss.com/jira/browse/JBESB-454 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Make the suffix on input Files optional so that it simply picks up all the files in the directory. Check to see that in this case the output directory is not the same as the input 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

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1072) JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger

by Mark Little (JIRA)

JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger ------------------------------------------------------------------------------------------- Key: JBESB-1072 URL: http://jira.jboss.com/jira/browse/JBESB-1072 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-768) Quickstart that demos JMS custom_correlation

by Daniel Bevenius (JIRA)

Quickstart that demos JMS custom_correlation -------------------------------------------- Key: JBESB-768 URL: http://jira.jboss.com/jira/browse/JBESB-768 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Optional Burr suggested that we add a quickstart that demos a custom correlation using jms. An example could be an application that creates a custom correlation id which it sets on the JMSMessage before posting to the ESB. It then needs to wait for a response and use a selector for that that specific correlation id. This would call for them to create a custom JMSRouter/JMSNotifier. -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-904) A number of QSes complain about message attribute not being set

by Kevin Conner (JIRA)

A number of QSes complain about message attribute not being set --------------------------------------------------------------- Key: JBESB-904 URL: http://jira.jboss.com/jira/browse/JBESB-904 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 This is coming from SystemPrintln, error message is "'message' attribute not set" -- 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, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-901) bpm_orchestration1 QS generates lock warning on console

by Kevin Conner (JIRA)

bpm_orchestration1 QS generates lock warning on console ------------------------------------------------------- Key: JBESB-901 URL: http://jira.jboss.com/jira/browse/JBESB-901 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 WARN [org.jbpm.graph.exe.Token] lock owner 'token[1]' tries to unlock token '1' which is not locked -- 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, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-746) Potential memory leak in Aggregator

by Jiri Pechanec (JIRA)

Potential memory leak in Aggregator ----------------------------------- Key: JBESB-746 URL: http://jira.jboss.com/jira/browse/JBESB-746 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor There is minor potential memory leak in Aggregator action. 1) The message is in timeout 2) The process method is started by receiveing one part of timeout message 3) Timeout checker checks the same message 4) Regular process creates aggregated message and removes the record in notification HashMap 5) Timout checker sends a notfificaion message and creates the record in notification HashMap 6) Regular process method receives notification message and ignores it as already timed out 7) The record remains in notification map Recommended solution Add _notified.remove(uuId) call to the branch that handles ignoring already timed out messages. -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1004) Quickstarts that don't require JMS dest deployment should warn if user tries "ant deploy-jms-dests"

by Tom Fennelly (JIRA)

Quickstarts that don't require JMS dest deployment should warn if user tries "ant deploy-jms-dests" --------------------------------------------------------------------------------------------------- Key: JBESB-1004 URL: http://jira.jboss.com/jira/browse/JBESB-1004 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Could simply check for the availability of the destination deployment files and <echo> a "not relevant for this quickstart" message if there are none. -- 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

3
14
0 / 0

[JBoss JIRA] Created: (JBESB-1003) jBPM log facilities are not properly configured in some cases

by Jiri Pechanec (JIRA)

jBPM log facilities are not properly configured in some cases ------------------------------------------------------------- Key: JBESB-1003 URL: http://jira.jboss.com/jira/browse/JBESB-1003 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Process flow Affects Versions: 4.2 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor When stopping ESB, the following error messages are printed to console 08:48:12,833 ERROR [STDERR] java.lang.NullPointerException 08:48:12,855 ERROR [STDERR] at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:82) The problem is that log facility is set to null. The JBMP internaly uses commons logging which apparently is not properly configured at least for this instance. Moreover the error happends when another exception has to be logged - this can contain another problem. -- 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
12
0 / 0

[JBoss JIRA] Created: (JBESB-719) The messages can be lost in case of ESB termination

by Jiri Pechanec (JIRA)

The messages can be lost in case of ESB termination --------------------------------------------------- Key: JBESB-719 URL: http://jira.jboss.com/jira/browse/JBESB-719 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Even if the ESB is using internally reliable JMS as a transport the messages can be lost during ESB termination. The reasons for this behaviour are two 1) ESB uses internally queue sessions with AUTO_ACK flag 2) Pick-up and deliver couriers works in different session Proposed solution 1) Change flag to CLIENT_ACK 2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If the allocated session is stored into ThreadLocal variable and returned by the subsequent calls by the same thread and get commited on call JMSConnectionPool.closeSession() then all internal message transfers via JMS will be done in transaction - one transfer/one transaction. -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-1035) jbpm admin console throws exceptions on shutdown of App Server/ESB Server

by Burr Sutter (JIRA)

jbpm admin console throws exceptions on shutdown of App Server/ESB Server ------------------------------------------------------------------------- Key: JBESB-1035 URL: http://jira.jboss.com/jira/browse/JBESB-1035 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 12:08:56,040 ERROR [JDBCExceptionReporter] You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is nul l.) 12:08:56,041 ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds org.hibernate.exception.GenericJDBCException: Cannot open connection at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.j ava:103) -- 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

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007