November 2007 - esb-issues - Jboss List Archives

[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

18 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-1382) SQL Listener XSD definition assigning suspicious defaults

by Tom Fennelly (JIRA)

SQL Listener XSD definition assigning suspicious defaults --------------------------------------------------------- Key: JBESB-1382 URL: http://jira.jboss.com/jira/browse/JBESB-1382 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 It's assigning defaults to some of the column names. I'd have thought it shouldn't be defaulting these - they either exist and are configured and used... or they're not and the code should check for that and/or give an error because it allows code to continue on blindly thinking everything is cool. <xsd:attribute default="message_id" name="message-id-column" <xsd:attribute default="message" name="message-column" <xsd:attribute default="status" name="status-column" -- 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

18 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1296) scripting groovy QS causes intermittent CI errors

by Kevin Conner (JIRA)

scripting groovy QS causes intermittent CI errors ------------------------------------------------- Key: JBESB-1296 URL: http://jira.jboss.com/jira/browse/JBESB-1296 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.3 There have been a number of transient failures with the scripting_groovy quickstart running within the CI system. We need to investigate why this is happening and fix. One possible source may be the access of an external web resource in one of the scripts (http://ax.phobos.apple.com.edgesuite.net/WebObjects/MZStore.woa/wpa/MRSS/...) -- 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

18 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1244) Put in juddi-2.0.jar release jar

by Kurt Stam (JIRA)

Put in juddi-2.0.jar release jar -------------------------------- Key: JBESB-1244 URL: http://jira.jboss.com/jira/browse/JBESB-1244 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 triage Juddi is in the process of releasing the latest code under version 2.0. JBESB should contains this jar and not a snapshot. -- 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

18 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1367) Unsafe handling of exception in CommandInterpreter

by Jiri Pechanec (JIRA)

Unsafe handling of exception in CommandInterpreter -------------------------------------------------- Key: JBESB-1367 URL: http://jira.jboss.com/jira/browse/JBESB-1367 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Minor Method CommandInterpreter.endState process exception thrown in jBPM process. The code fails when the message of exception is null. -- 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

18 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1236) bpm_orchestration4 - LazyInitializationException

by Jaroslaw Kijanowski (JIRA)

bpm_orchestration4 - LazyInitializationException ------------------------------------------------ Key: JBESB-1236 URL: http://jira.jboss.com/jira/browse/JBESB-1236 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jaroslaw Kijanowski Assigned To: Mark Little I clicked on "Save & close" in the jbpm console and after the Discount Services finished I got: 12:45:51,012 INFO [STDOUT] ************ END ORDER DISCOUNT FIXER ************ 12:45:51,148 WARN [ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.TaskNode - this operation breaks == 12:45:51,332 ERROR [LazyInitializationException] could not initialize proxy - no Session org.hibernate.LazyInitializationException: could not initialize proxy - no Session -- 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

18 years, 4 months

8
21
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

18 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1272) CommandInterpreter.doTheJob does not make sense in error condition

by Mark Little (JIRA)

CommandInterpreter.doTheJob does not make sense in error condition ------------------------------------------------------------------ Key: JBESB-1272 URL: http://jira.jboss.com/jira/browse/JBESB-1272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 IR2 Reporter: Mark Little Fix For: 4.3 Message response = Helper.commandMessageTemplate(); Body body = response.getBody(); try { Object obj = getJbpmCommandService().execute(command); body.add(Constants.RETURN_CODE, Constants.RETCODE_OK); if (null!=obj) body.add(Constants.JBPM_RETURN_OBJECT, obj); } catch (JbpmException e) { body.add(Constants.RETURN_CODE, Constants.RETCODE_EXCEPTION); body.add(Constants.EXCEPTION, e); throw e; } return response; Why does the code modify the body when the message isn't going to be returned? -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1381) SQLCourier logging fatal exceptions as debug i.e. hidding the errors

by Tom Fennelly (JIRA)

SQLCourier logging fatal exceptions as debug i.e. hidding the errors -------------------------------------------------------------------- Key: JBESB-1381 URL: http://jira.jboss.com/jira/browse/JBESB-1381 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 -- 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

18 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1383) SqlTableCourier.pickup returns null on SQLException

by Mark Little (JIRA)

SqlTableCourier.pickup returns null on SQLException --------------------------------------------------- Key: JBESB-1383 URL: http://jira.jboss.com/jira/browse/JBESB-1383 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 CP1 It really shouldn't, because that is also masking the failure from the application. -- 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

18 years, 4 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2007