[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, 2 months
[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, 2 months
[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, 3 months