[esb-issues] [JBoss JIRA] Created: (JBESB-1212) bpm_orchestration : deployProcess should be cleaner

Tom Cunningham (JIRA) jira-events at lists.jboss.org
Fri Oct 19 22:59:03 EDT 2007


bpm_orchestration : deployProcess should be cleaner
---------------------------------------------------

                 Key: JBESB-1212
                 URL: http://jira.jboss.com/jira/browse/JBESB-1212
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Examples
    Affects Versions: 4.2.1 IR2
            Reporter: Tom Cunningham
         Assigned To: Mark Little
             Fix For: 4.2.1


In bpm_orchestration3 (and I think in the other bpm_orchestration examples) deployProcess depends on the appserver running to work correctly.      If we deployProcess gets a java.naming.CommunicationException, we should catch it and throw a log message telling the user that they need to start their app server.

Here's the exception thrown if the app server isn't running:
deployProcess:
     [echo] Sends a message to deploy the process definition
     [java] javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
     [java] Exception in thread "main" java.lang.NullPointerException
     [java]     at org.jboss.soa.esb.samples.quickstart.bpm_orchestration3.test.SendJMSMessage.stop(SendJMSMessage.java:52)
     [java]     at org.jboss.soa.esb.samples.quickstart.bpm_orchestration3.test.SendJMSMessage.main(SendJMSMessage.java:80)


-- 
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

        



More information about the esb-issues mailing list