December 2007 - esb-issues - Jboss List Archives

[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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1380) SQLCourier not defending against invalid filter config during prepared statement generation

by Tom Fennelly (JIRA)

SQLCourier not defending against invalid filter config during prepared statement generation ------------------------------------------------------------------------------------------- Key: JBESB-1380 URL: http://jira.jboss.com/jira/browse/JBESB-1380 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 Results in an exception which gets caught in a general catch-all, return null... then a NPE, which in turn gets caught in another general catch-all which assumes a connection failure exception... which causes the whole thing to start all over again. -- 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
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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1394) FTP Notifier incorrectly process String payload

by Jiri Pechanec (JIRA)

FTP Notifier incorrectly process String payload ----------------------------------------------- Key: JBESB-1394 URL: http://jira.jboss.com/jira/browse/JBESB-1394 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2.1 Reporter: Jiri Pechanec Snippet from NotifyFTP.java IOUtils.write((byte[]) payloadProxy.getPayload(message), stream); This is wrong, NotifyFTP should accept generic object or String to be stored in payload as other notifiers. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-1396) jms_topic QS - SendJMSMessage has duplicate close method

by Jaroslaw Kijanowski (JIRA)

jms_topic QS - SendJMSMessage has duplicate close method -------------------------------------------------------- Key: JBESB-1396 URL: http://jira.jboss.com/jira/browse/JBESB-1396 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski Priority: Trivial Fix For: 4.2.1 CP1 SendJMSMessage's stop method is: public void stop() throws JMSException { tc.close(); session.close(); tc.close(); } should be: public void stop() throws JMSException { tc.stop(); session.close(); tc.close(); } -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-1358) ESB does not include security principals when accessing secured JMX domain

by Christopher Brock (JIRA)

ESB does not include security principals when accessing secured JMX domain --------------------------------------------------------------------------- Key: JBESB-1358 URL: http://jira.jboss.com/jira/browse/JBESB-1358 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: SOA Platform IR6 Reporter: Christopher Brock Assigned To: Kevin Conner The ESB server does not appear to be passing any security credentials when it requests resources from inside the JMX context. This is problematic for the SOA platform, as the JMX security domain is secured out of the box. Stack Trace Below: org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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-1359) Wrong deployment order of nested archives

by Martin Vecera (JIRA)

Wrong deployment order of nested archives ----------------------------------------- Key: JBESB-1359 URL: http://jira.jboss.com/jira/browse/JBESB-1359 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Martin Vecera When I have an .esb archive that contains one ESB service and one .war archive. The service uses SOAPProcessor to send messages to the web service inside the nested .war. I have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web service is deployed later than the ESB service. Then the ESB service starts processing the message and the SOAPProcessor fails because the web service is not deployed yet. I think the correct deployer behaviour would be: 1) if there are any nested archives then call the deployer for each of the nested archives 2) deploy the services from the current archive -- 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
10
0 / 0

[JBoss JIRA] Created: (JBESB-1374) Exception handling problem when used integrated jBPM/ESB with JTA

by Jiri Pechanec (JIRA)

Exception handling problem when used integrated jBPM/ESB with JTA ----------------------------------------------------------------- Key: JBESB-1374 URL: http://jira.jboss.com/jira/browse/JBESB-1374 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Jiri Pechanec When used distributed tranasctions the transaction is rolled back when runtime exception is thrown. Unfortunately the jBPM encapsulates RuntimeExceptions into JBPMExceptions that are checked. Thus the rollback is not executed. Also it needs to be checked there there is no other way in ESB that will cause RuntimException to be changed to checked Exception. -- 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
18
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2007