January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1477) SOAPClient does not cleanup resources on undeploy

by Kevin Conner (JIRA)

SOAPClient does not cleanup resources on undeploy ------------------------------------------------- Key: JBESB-1477 URL: http://jira.jboss.com/jira/browse/JBESB-1477 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1, 4.3 We need to add support for shutting down the HttpClient and it's associated connection manager. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1466) CallbackCommand should detect when process was deleted

by Jiri Pechanec (JIRA)

CallbackCommand should detect when process was deleted ------------------------------------------------------ Key: JBESB-1466 URL: http://jira.jboss.com/jira/browse/JBESB-1466 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Minor Fix For: 4.2.1 CP1 It is possible to delete process instance from GUI. The CallbackCOmmand should cope with this situation by logging the problem and put the message to DLQ. Now only NPE is thrown. The same probably applies for tokens. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1472) DataCollector does not check for NP during getClassPatterns

by Mark Little (JIRA)

DataCollector does not check for NP during getClassPatterns ----------------------------------------------------------- Key: JBESB-1472 URL: http://jira.jboss.com/jira/browse/JBESB-1472 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 CP1 09:52:08,935 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <ws\ a:Address jms://localhost/queue/DataCollectorQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:spec\ ification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true\ />, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-0 RelatesTo: jms:correlationID#3690b2f9-6fea-48f6-b987-e4aab46de89c ] java.lang.NullPointerException at org.jboss.soa.esb.monitoring.client.DataCollector.getClassPatterns(DataCollector.java:89) at org.jboss.soa.esb.monitoring.client.DataCollector.collectData(DataCollector.java:159) at org.jboss.soa.esb.monitoring.client.DataCollectorAction.collectStatistics(DataCollectorAction.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) 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:347) 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) -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1453) If exception transition is present then it has faultTo to the same value as replyTo but these should differ

by Jiri Pechanec (JIRA)

If exception transition is present then it has faultTo to the same value as replyTo but these should differ ----------------------------------------------------------------------------------------------------------- Key: JBESB-1453 URL: http://jira.jboss.com/jira/browse/JBESB-1453 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Blocker 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)

by Jiri Pechanec (JIRA)

Default values are ignored in jBPM to ESB mapper (ESB side) ----------------------------------------------------------- Key: JBESB-1431 URL: http://jira.jboss.com/jira/browse/JBESB-1431 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Priority: Critical Fix For: 4.2.1 CP1 The old behaviour was that the defaut value was used when there was no such key in message body. Now when the ObjectMapper is used the default is used only when the exception is thrown. This is significant change that breaks backward compatibility. -- 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, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1471) Consider adding in JGroups support

by Mark Little (JIRA)

Consider adding in JGroups support ---------------------------------- Key: JBESB-1471 URL: http://jira.jboss.com/jira/browse/JBESB-1471 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 Reporter: Mark Little Fix For: 5.0 And done flexibly, so other group comms implementations could be swapped in if necessary. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1154) Integrate remaining QSes into the Ci system

by Kevin Conner (JIRA)

Integrate remaining QSes into the Ci system ------------------------------------------- Key: JBESB-1154 URL: http://jira.jboss.com/jira/browse/JBESB-1154 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 Some of the QSes are now integrated into the CI system. We need to look at the remaining ones and integrate those as well. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1469) Review list of QS's and integrate any new QS into CI testing

by Tom Cunningham (JIRA)

Review list of QS's and integrate any new QS into CI testing ------------------------------------------------------------ Key: JBESB-1469 URL: http://jira.jboss.com/jira/browse/JBESB-1469 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 5.0 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 5.0 Review the list of QS's and add a CI test for any QS's that do not have them. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1448) Invalid Callback message is not sent to DLQ

by Jiri Pechanec (JIRA)

Invalid Callback message is not sent to DLQ ------------------------------------------- Key: JBESB-1448 URL: http://jira.jboss.com/jira/browse/JBESB-1448 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Critical Fix For: 4.2.1 CP1 Snippet from Wiki doc Verify that the version is still the same and that the process is still at that node. If either of these conditions are not met, a warning should be logged, and the message should be send to the DLS. Warning is logged but message is not stored to DLQ. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1456) Load balancing over JMS - interresting behaviour

by Martin Vecera (JIRA)

Load balancing over JMS - interresting behaviour ------------------------------------------------ Key: JBESB-1456 URL: http://jira.jboss.com/jira/browse/JBESB-1456 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Environment: SOA-P 4.2.0 beta 1 Reporter: Martin Vecera Priority: Minor During failover testing I found out very interresting behaviour... I had two nodes (JBossESB servers) in a cluster. I deployed identical service to both of them. Each service had: 1) clustered gateway queue served by 2 threads 2) clustered queue for ESB aware messages served by 2 threads. I send several messages to the first node and expected them to be load balanced among the nodes. This didn't happend. I figured out that the load balancing came in to the play twice: 1) while sending the message to GW 2) while sending the message from GW to ESB-aware queue Because there were more than one thread for each queue the loadbalancing went in the way where some messages were really sent to the GW on the second node but then they returned back to the first one. This is definitely configuration failure (the queue for ESB aware messages mustn't be clustered) but we should document this I think. -- 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, 3 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008