[JBoss JIRA] Created: (JBESB-646) NON_PERSISTENT JMS messaging.
by Daniel Bevenius (JIRA)
NON_PERSISTENT JMS messaging.
-----------------------------
Key: JBESB-646
URL: http://jira.jboss.com/jira/browse/JBESB-646
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assigned To: Mark Little
Priority: Minor
The current classes that deal with sending JMS messages, like JMSCourier, do not specify a delivery mode when sending messages. The default is then that the messages are sent with a delivery mode of persistent.
The request (see forum reference) is to be able have the delivery mode configurable so one can avoid the persisting to stable storage.
--
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, 7 months
[JBoss JIRA] Created: (JBESB-1091) WARN messages when deploying helloworld_ftp_action QS
by Jaroslaw Kijanowski (JIRA)
WARN messages when deploying helloworld_ftp_action QS
-----------------------------------------------------
Key: JBESB-1091
URL: http://jira.jboss.com/jira/browse/JBESB-1091
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation, Examples
Affects Versions: 4.2, 4.2.1 IR1
Reporter: Jaroslaw Kijanowski
Assigned To: Mark Little
When deploying the helloworld_ftp_action QS I get follwoing WARN messages:
16:11:15,426 WARN [ScheduleMapper] Property 'pollLatencySeconds' is DEPRECATED. Please change your configuration to use 'schedule-frequency'.
16:11:15,485 WARN [AbstractFileGateway] No value specified for: max-millis-for-response - This will be an 'inbound-only' gateway
Also the Programmers Guide doesn't mention, that schedule-frequency should be used for a FTP listener.
--
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, 7 months
[JBoss JIRA] Created: (JBESB-1119) DataFilerJob leaks couriers
by Kevin Conner (JIRA)
DataFilerJob leaks couriers
---------------------------
Key: JBESB-1119
URL: http://jira.jboss.com/jira/browse/JBESB-1119
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.2.1 IR1
Reporter: Kevin Conner
Assigned To: Tom Cunningham
Fix For: 4.2.1 IR2
Just seen the following on a running system
org.jboss.soa.esb.couriers.CourierException: Failed to get JMS Session from pool.
at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:150)
at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:307)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:175)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:188)
at org.jboss.soa.esb.monitoring.server.DataFilerJob.execute(DataFilerJob.java:93)
A quick look at the DataFilerJob code shows that it is leaking couriers.
--
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, 7 months