May 2009 - esb-issues - Jboss List Archives

[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-2561) DefaultJMSPropertiesSetter filtering not usable in all circumstances

by Kevin Conner (JIRA)

DefaultJMSPropertiesSetter filtering not usable in all circumstances -------------------------------------------------------------------- Key: JBESB-2561 URL: https://jira.jboss.org/jira/browse/JBESB-2561 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 JBESB-2287 introduced filtering into the DefaultJMSPropertiesSetter but this is only usable in certain circumstances. One area which cannot use this, at present, is the JmsCourier created from EPRs. Listeners can therefore introduce properties which should be filtered. -- 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
7
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

[JBoss JIRA] Created: (JBESB-2570) Quickstarts: Remove usage of "default" JMS queues/[ABCD] from the quickstarts that use these.

by Daniel Bevenius (JIRA)

Quickstarts: Remove usage of "default" JMS queues/[ABCD] from the quickstarts that use these. --------------------------------------------------------------------------------------------- Key: JBESB-2570 URL: https://jira.jboss.org/jira/browse/JBESB-2570 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.6 Go through all quickstart and replace the queue with default queues which ones that are deployed by the quickstart. -- 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-2569) JmsConnectionPool: Add support for "max-xa-sessions-per-connection" config

by Tom Fennelly (JIRA)

JmsConnectionPool: Add support for "max-xa-sessions-per-connection" config -------------------------------------------------------------------------- Key: JBESB-2569 URL: https://jira.jboss.org/jira/browse/JBESB-2569 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 CP3 The JmsConnectionPool currently supports a "max-sessions-per-connection" config. Add support for a "max-xa-sessions-per-connection", allowing specific control over XA resources. So "max-sessions-per-connection" will be the total number of sessions allowed per connection (XA + non-XA) and "max-xa-sessions-per-connection" will be a specific max for XA Sessions. -- 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

[JBoss JIRA] Created: (JBESB-2493) JmsConnectionPool swallows NamingException

by Jiri Pechanec (JIRA)

JmsConnectionPool swallows NamingException ------------------------------------------ Key: JBESB-2493 URL: https://jira.jboss.org/jira/browse/JBESB-2493 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Jiri Pechanec Assignee: Kevin Conner See the following code try { factoryConnection = jndiContext.lookup(connectionFactoryString); } catch (NamingException ne) { logger.info("Received NamingException, refreshing context."); jndiContext = NamingContextPool.replaceNamingContext(jndiContext, JmsConnectionPoolContainer.getJndiEnvironment(poolKey)); factoryConnection = jndiContext.lookup(connectionFactoryString); } If the exception is thrown it is not logged and there is no way to identify the reason of error -- 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
8
0 / 0

[JBoss JIRA] Created: (JBESB-2571) Indeterminstic response to JbpmReplyUnitTest

by Kevin Conner (JIRA)

Indeterminstic response to JbpmReplyUnitTest -------------------------------------------- Key: JBESB-2571 URL: https://jira.jboss.org/jira/browse/JBESB-2571 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 JBESB-2508 introduced an update into the JCA integration in response to a fixed JBPAPP bug, but the base server in this branch is still to be updated to AS 4.2.4 (not yet released). As a consequence the maxThreads attribute is not correctly handled for JCA resulting in an out of order delivery of messages. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBESB-2533) recipient_list quickstart uses "default" messaging queues A, B, C and D

by Daniel Bevenius (JIRA)

recipient_list quickstart uses "default" messaging queues A, B, C and D ----------------------------------------------------------------------- Key: JBESB-2533 URL: https://jira.jboss.org/jira/browse/JBESB-2533 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Fix For: 4.6 The quickstart uses four queues that are configured by default with JBossMQ and JBoss Messaging. But with JBM on AS 5 these queues do not exist causing the quickstart to fail upon deployment. The queues A, B, C and D should be changed and four queues should be added to the quickstart configuration. -- 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-2534) simple_cbr quickstart uses "default" messaging queue B.

by Daniel Bevenius (JIRA)

simple_cbr quickstart uses "default" messaging queue B. ------------------------------------------------------- Key: JBESB-2534 URL: https://jira.jboss.org/jira/browse/JBESB-2534 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.6 The quickstart uses a queue that is configured by default with JBossMQ and JBoss Messaging. But with JBM on AS 5 this queue does not exist causing the quickstart to fail upon deployment. The queues B should be changed and a queue should be added to the quickstart configuration. -- 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
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2009