April 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2492) Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter

by Tom Fennelly (JIRA)

Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter ---------------------------------------------------------------------------- Key: JBESB-2492 URL: https://jira.jboss.org/jira/browse/JBESB-2492 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 Is currently using the DOM filter (default). Should use the SAX filter for performance reasons. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2535) logging for DBMessageStoreImpl

by toby cabot (JIRA)

logging for DBMessageStoreImpl ------------------------------ Key: JBESB-2535 URL: https://jira.jboss.org/jira/browse/JBESB-2535 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: toby cabot Attachments: dbmsgstore-patch.txt Here's a patch to add some logging to DBMessageStoreImpl. It helps the production support guys to be able to see it retrying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2456) Tidy up smooks instance manager

by Kevin Conner (JIRA)

Tidy up smooks instance manager ------------------------------- Key: JBESB-2456 URL: https://jira.jboss.org/jira/browse/JBESB-2456 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 The smooks instance manager listenes to JMS Topics for configuration updates but we do not support this. We need to remove this code along with any other parts which may no longer be used. TomF says that the trunk codebase has already been updated so we need to pull those changes across. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1883) quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory

by Burr Sutter (JIRA)

quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory ---------------------------------------------------------------------------------------- Key: JBESB-1883 URL: https://jira.jboss.org/jira/browse/JBESB-1883 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Burr Sutter Priority: Minor The business_ruleservice_ruleAgent quickstart should have its processDefinition folder removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2525) HttpRouter fire java.lang.NullPointerException if the Response is empty (204)

by Jurij (JIRA)

HttpRouter fire java.lang.NullPointerException if the Response is empty (204) ----------------------------------------------------------------------------- Key: JBESB-2525 URL: https://jira.jboss.org/jira/browse/JBESB-2525 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: Debian Reporter: Jurij [2009-04-16 18:04:53,353][DEBUG][pool-61-thread-2][header]<< "HTTP/1.1 204 No Content [\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Content-Length: 000000000000000[\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Server: IBM_CICS_Transaction_Server/3.1.0(zOS)[\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Date: Thu, 16 Apr 2009 16:04:53 GMT[\r][\n]" java.lang.NullPointerException at org.jboss.soa.esb.actions.routing.http.HttpRouter.process(HttpRouter.java:118) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-2503) Fix JMSEpr address encoding

by Kevin Conner (JIRA)

Fix JMSEpr address encoding --------------------------- Key: JBESB-2503 URL: https://jira.jboss.org/jira/browse/JBESB-2503 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 The JMSEpr encodes the JNDI URI/destination name but the code currently assumes that the URI consists of just a host:port pair rather than a full URI. As a consequence, addresses such as jms://localhost:1414/SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb are interpreted with a queue name of SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb. We need to modify the address encoding to make sure that the URI/destination name can be correctly encoded and retrieved from this information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2523) Thread related InVM resources created by DefaultInVMReplyToEpr not being cleaned up on thread cleanup

by Mark Little (JIRA)

Thread related InVM resources created by DefaultInVMReplyToEpr not being cleaned up on thread cleanup ------------------------------------------------------------------------------------------------------ Key: JBESB-2523 URL: https://jira.jboss.org/jira/browse/JBESB-2523 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 The DefaultInVMReplyToEpr class creates an InVMCourier + InVMEpr for handling async replies on a deliverSync over InVM. It attaches these details to the active thread. The logic at the time was that they could be reused. The obvious flaw in the logic (hindsight) is that when the threads are pooled and the pool is persiodically cleaned... new threads are created... more InVmCouriers are created, resulting in the InVMCourier list (held by the CourierFactory) growing and growing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2529) Need to backport quickstart config to handle EULA name change

by Kevin Conner (JIRA)

Need to backport quickstart config to handle EULA name change ------------------------------------------------------------- Key: JBESB-2529 URL: https://jira.jboss.org/jira/browse/JBESB-2529 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Fix For: 4.2.1 CP5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2446) The update to the message context has broken serialisation with older versions

by Kevin Conner (JIRA)

The update to the message context has broken serialisation with older versions ------------------------------------------------------------------------------ Key: JBESB-2446 URL: https://jira.jboss.org/jira/browse/JBESB-2446 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The message context was previously unused but was modified, by me I must admit, so that we could usefully distinguish between message context and message contents. Unfortunately this breaks when an old version of a serialized message is read by the new version. The fix is straight forward, add the following into the ContextImpl for the serialized format. /** * Deserialise the object, checking for old versions. * @param ois The object input stream. * @throws IOException For IO exceptions during object deserialisation. * @throws ClassNotFoundException If dependent classes cannot be found. */ private void readObject(final ObjectInputStream ois) throws IOException, ClassNotFoundException { ois.defaultReadObject() ; if (context == null) { context = new HashMap<String, Serializable>() ; } } The XML variant is correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2506) Add locale configuration for Smooks date transforms in the quickstarts

by Daniel Bevenius (JIRA)

Add locale configuration for Smooks date transforms in the quickstarts ---------------------------------------------------------------------- Key: JBESB-2506 URL: https://jira.jboss.org/jira/browse/JBESB-2506 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Fix For: 4.6 For example, the bpm_orchestration4 quickstart has to transforms that include date transformations. These do not specify locale configuration information and are therefor dependent on the default locale that this system uses. We should add explicit locales to avoid problems. This can be configures like this: <jb:value property="orderDate" data="Order/@orderDate" decoder="Calendar"> <jb:decodeParam name="format">EEE MMM dd HH:mm:ss z yyyy</jb:decodeParam> <jb:decodeParam name="locale-language">en</jb:decodeParam> <jb:decodeParam name="locale-country">US</jb:decodeParam> </jb:value> All quickstart should be update if they have date transformations. This issue was discovered while investigating the linked forum reference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2009