March 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-860) Have the jcr jackrabbit store implement the full MessageStore interface

by Kurt Stam (JIRA)

Have the jcr jackrabbit store implement the full MessageStore interface ----------------------------------------------------------------------- Key: JBESB-860 URL: http://jira.jboss.com/jira/browse/JBESB-860 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 The jcr implementation has some methods stubbed out. For extra credits we can should have it implement the RedeliverStore interface too, -- 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

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-667) Echo action

by Mark Little (JIRA)

Echo action ----------- Key: JBESB-667 URL: http://jira.jboss.com/jira/browse/JBESB-667 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Add an echo Action that simply send back the same message to the sender. Could be used for heart-beat, but also for distributed management. -- 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

16 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-823) Separate DLQ from Message Store

by Mark Little (JIRA)

Separate DLQ from Message Store ------------------------------- Key: JBESB-823 URL: http://jira.jboss.com/jira/browse/JBESB-823 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little The Message Store was intended to logging, debugging etc. It keeps track of what's on the wire. We're now using it for the retry/retransmit and DLQ. Even if the same backend implementation were used, shouldn't that be a separate service? DLQ is for reliability, whereas the Message Store implementation isn't necessarily reliable or available to users, e.g., an organisation may not want to expose it's Message Store details to the world for security reasons, but a general DLQ may be supported by the ESB for reliability reasons. -- 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

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-817) Rename Message to Envelope?

by Mark Little (JIRA)

Rename Message to Envelope? --------------------------- Key: JBESB-817 URL: http://jira.jboss.com/jira/browse/JBESB-817 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little On behalf of our intern: "Wouldn't it be better to call Message Envelope? It might avoid some confusion too amongst WS-* and JMS developers." -- 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

16 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1581) Remember to update the Release Notes

by Mark Little (JIRA)

Remember to update the Release Notes ------------------------------------ Key: JBESB-1581 URL: http://jira.jboss.com/jira/browse/JBESB-1581 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP1 Reporter: Mark Little Fix For: 4.2.1 CP2 -- 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

16 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1491) JMSRouter finalize can throw javax.jms.IllegalStateException: The object is closed

by Daniel Bevenius (JIRA)

JMSRouter finalize can throw javax.jms.IllegalStateException: The object is closed ---------------------------------------------------------------------------------- Key: JBESB-1491 URL: http://jira.jboss.com/jira/browse/JBESB-1491 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 This error can occur when undeploying a service that contains a JMSRouter. 2008-01-16 08:54:00,764 ERROR [.pooling.JmsConnectionPool] JMSException while calling getAcknowledgeMode javax.jms.IllegalStateException: The object is closed at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:157) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$getAcknowledgeMode_N7774033054566619384.invokeNext(ClientSessionDelegate$getAcknowledgeMode_N7774033054566619384.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.getAcknowledgeMode(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.getAcknowledgeMode(JBossSession.java:159) at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.closeSession(JmsConnectionPool.java:257) at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.close(JMSRouter.java:392) at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.access$000(JMSRouter.java:322) at org.jboss.soa.esb.actions.routing.JMSRouter.finalize(JMSRouter.java:300) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) Make checks to avoid the error. -- 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

16 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1631) Quartz scheduling threads killed by exceptions

by Kevin Conner (JIRA)

Quartz scheduling threads killed by exceptions ---------------------------------------------- Key: JBESB-1631 URL: http://jira.jboss.com/jira/browse/JBESB-1631 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1, 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP2, 4.3 Threads from the Quartz scheduling pool are destroyed if the job throws an unexpected runtime exception/error. The consequence of this is that the scheduled processing will lose threads from the pool (undiscovered by Quartz) and that all scheduled activities on that pool will eventually cease. -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1630) Removing JNDI references from jboss-esb.xml

by Tom Cunningham (JIRA)

Removing JNDI references from jboss-esb.xml ------------------------------------------- Key: JBESB-1630 URL: http://jira.jboss.com/jira/browse/JBESB-1630 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP2 Removing the JNDI references from jboss-esb.xml - fixing some of the QS for CP2 and then will fix the rest for either CP3 or FP1 (what we agreed on in the F2F meeting on Thursday). JBESB-1595 references the rest of the QS being changed to match. +++ simple_cbr/jboss-esb.xml (working copy) +++ transform_XML2POJO2/jboss-esb.xml (working copy) +++ spring_jpetstore/jboss-esb.xml (working copy) +++ spring_aop/jboss-esb.xml (working copy) +++ helloworld_db_registration/jboss-esb.xml (working copy) +++ transform_EDI2XML_Groovy_XSLT/jboss-esb.xml (working copy) +++ helloworld_sql_action/jboss-esb.xml (working copy) +++ helloworld_hibernate_action/jboss-esb.xml (working copy) +++ transform_CSV2XML/jboss-esb.xml (working copy) +++ spring_helloworld/jboss-esb.xml (working copy) +++ exceptions_faults/jboss-esb.xml (working copy) +++ transform_XML2XML_simple/jboss-esb.xml (working copy) +++ helloworld_topic_notifier/jboss-esb.xml (working copy) +++ helloworld/jboss-esb.xml (working copy) +++ transform_XML2XML_date_manipulation/jboss-esb.xml (working copy) -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1525) Create a quickstart that demonstrates handling huge file (via ftp)

by Daniel Bevenius (JIRA)

Create a quickstart that demonstrates handling huge file (via ftp) ------------------------------------------------------------------ Key: JBESB-1525 URL: http://jira.jboss.com/jira/browse/JBESB-1525 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 This quickstart will configure an FTP provider to pickup a file, have a custom MessageComponer that does not put the content of the file into the ESB Message object, but instead puts the path to the file in the message body or as a message property. The action pipeline will consist of a Smooks transformation with a FileRouter, which will append the output of the transformation to a new file. Once the transformation has been performed an ftp notifier or a file router will be used to send the file to a target destination. This will be possible after the upgrade to Smooks version 1.0 (SAX support and FileRouter) The intent of this quickstart is to demonstrate that the ESB can handle large file without causing memory issues while processing. This might require a minor update to the AbstractFileGateway to ensure that the gateway does not distribute the call to the listener on another node. It must stay on the same node if there is not network file system in place, as the file would not exist on the other node. -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1629) Support a "duplicates okay" QoS across a service (akin to that in JBoss Messaging's Bridge) when the source is JMS

by David Smiley (JIRA)

Support a "duplicates okay" QoS across a service (akin to that in JBoss Messaging's Bridge) when the source is JMS ------------------------------------------------------------------------------------------------------------------ Key: JBESB-1629 URL: http://jira.jboss.com/jira/browse/JBESB-1629 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Smiley This is NOT the same thing as setting DUPS_OK_ACKNOWLEDGE on the gateway's jms-message-filter. This is about the QoS of the whole service, not just the inbound JMS listener. To get the same behavior as QOS_DUPLICATES_OK in the JBM Bridge, basically, the ESB needs to set the ack mode to CLIENT_ACKNOWLEDGE on the source, then wait until the service has finished processing the message (which may or may not involve the message moving on to other queues), then finally acknowledge the message. This shouldn't be that hard to implement. One way I propose this might be configured, is to have this behavior occur automatically when the jms-message-filter is configured with CLIENT_ACKNOWLEDGE. This could be decided to mean that it'll get acknowledge when the service completes, but then a service developer could optionally acknowledge it themselves in an action if they wanted too. (speaking of which, that'd make a nice built-in action to provide with the ESB). See the following source code file to gain incite into this: http://fisheye.jboss.org/browse/Messaging/trunk/src/main/org/jboss/messag... And finally the forum reference below should be highly relevant. -- 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

16 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008