Bug 777644 (SOA-154)

Summary: helloworld quickstart - sendesb ant target fails - can't create a ServiceInvoker
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2 IR6   
Target Milestone: ---   
Target Release: 4.2 IR8   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-154
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
standalone-soa-4.2.0-IR6.0.zip RHEL5
Last Closed: 2007-12-05 03:11:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2007-11-19 19:11:43 UTC
Date of First Response: 2007-11-20 04:27:14
project_key: SOA

Description of problem:
helloworld quickstart - sendesb ant target fails - can't create a ServiceInvoker

Version-Release number of selected component (IR or RC #, component ver)
standalone-soa-4.2.0-IR6.0.zip

How reproducible:
100%

Steps to Reproduce: 
1. Just compile, deploy, run helloworld quickstart ant "sendesb" target

Actual results:
sendesb:
     [echo] Runs Test ESB Message Sender
     [java] Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_helloworld_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]] to Service [JBossESB-Internal:DeadLetterService].  Check for errors.
     [java]     at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:279)
     [java]     at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:184)
     [java]     at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:226)
     [java]     at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:194)
     [java]     at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:55)

BUILD FAILED
/opt/IR6/jboss-soa-p-standalone.4.2.0/samples/quickstarts/helloworld/build.xml:23: Java returned: 1

Expected results:
This should work - bug SOA-113 was fixed in IR5

Additional info: (e.g., stack trace)
The offending statement is:
   new ServiceInvoker(args[0], args[1]).deliverAsync(esbMessage);

Attachments (e.g., server log)

Comment 1 Kevin Conner 2007-11-20 09:27:14 UTC
SOA-113 hasn't been fixed yet, but will be for the next IR

Comment 2 Kevin Conner 2007-11-20 09:28:28 UTC
Link: Added: This issue is duplicated by SOA-113


Comment 3 Kevin Conner 2007-11-20 12:57:02 UTC
Apologies, SOA-113 is not the issue I thought it was and has been fixed.

Unfortunately this is another issue which has just been fixed in the ESB project, due to the introduction of a new coded jar in the serialisation code.

Comment 4 Kevin Conner 2007-11-20 12:57:33 UTC
Link: Added: This issue depends JBESB-1314


Comment 5 Kevin Conner 2007-11-20 12:58:00 UTC
Link: Removed: This issue is duplicated by SOA-113 


Comment 6 Len DiMaggio 2007-12-06 18:55:07 UTC
Verified fixed in IR8.