[esb-issues] [JBoss JIRA] Created: (JBESB-2133) Connection failed still called method in "okMethod" ?
Connection failed still called method in "okMethod" ?
-----------------------------------------------------
Key: JBESB-2133
URL: https://jira.jboss.org/jira/browse/JBESB-2133
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Environment: jbossesb-server-4.4.GA
OS : Windows-XP
Reporter: Chris Au
I used below config to test the okMethod and exceptionMethod and found that the okMethod
will still be called even the console throws exception about connection failed :
<action name="displayMessage"
class="com.oi.test.MyJMSListenerAction"
process="displayMessage" >
<property name="exceptionMethod" value="myHandle"/>
<property name="okMethod" value="displayMessage"/>
</action>
<action name="notificationAction"
class="org.jboss.soa.esb.actions.Notifier">
<property name="okMethod" value="notifyOK"
/>
<property name="destinations">
<NotificationList type="OK">
<target class="NotifyQueues" >
<queue connection-factory="SonicMQQueueConnectionFactory"
jndi-URL="jnp://@domain@:1099"
jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"
jndiName="SonicMQ_Queue_test" />
</target>
</NotificationList>
<NotificationList type="err">
<target class="NotifyConsole" />
<target class="NotifyFiles" >
<file URI="/error.log" />
</target>
</NotificationList>
</property>
</action>
The connection to sonicMQ tested successful when I did not shut that down on purpose to
test the connectivity problem. What I am trying to do is to catch exception when the
connection fails. But there does not seem to be a suitable workflow for that.
--
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