Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1072334

Summary: WSDL app fails to deploy correctly in cluster
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Gary Brown <gbrown>
Component: SwitchYardAssignee: Aileen <aileenc>
Status: CLOSED UPSTREAM QA Contact: Matej Melko <mmelko>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.0.0 GACC: rcernich, soa-p-jira, tcunning
Target Milestone: DR4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:35:15 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:
Embargoed:
Attachments:
Description Flags
Switchyard app
none
Log with failure (search for ERROR)
none
Log from standalone config which worked correctly none

Description Gary Brown 2014-03-04 12:00:26 UTC 
Created attachment 870375 [details]
Switchyard app

Description of problem:

While investigating https://bugzilla.redhat.com/show_bug.cgi?id=1071923, I deployed the Overlord rtgov quickstart order management app (based on the switchyard orders quickstart), to a cluster based on two nodes, using the instructions in the switchyard cluster quickstart for guidance.

When I tried to invoke the wsdl interface it returned a html error page, even though the app had deployed successfully. I checked the log and found this:

11:50:51,835 ERROR [org.apache.catalina.core] (MSC service thread 1-5) JBWEB001100: Error starting context: java.lang.IllegalArgumentException: JBWEB006706: Document base /home/gbrown/testing/fsw/fsw6.0.0.GA/jboss-eap-6.1/node1/tmp/node1/tmp/demo-orders does not exist or is not a readable directory

This occurred in a server started using:

bin/standalone.sh -Djboss.node.name=node1 -Djboss.server.base.dir=node1 --server-config=standalone-full-ha.xml


I then deployed the same swyd app to standalone, and ran:

bin/standalone.sh -c standalone-full.xml

and this started with no problem, and responded correctly to the soap message.

Will attach swyd app, and logs from the standalone and node1 runs.


Version-Release number of selected component (if applicable):

FSW6.0.0.GA

How reproducible:


Steps to Reproduce:
1. Create a copy of standalone folder called 'node1'
2. Set the 'cluster-password' in standalone-full-ha.xml to 'overlord'
3. Use the first server startup commandline above
4. Use "mvn exec:java -Dreq=order3 (with appropriate mvn repo settings)" to submit the soap message
Comment 1 Gary Brown 2014-03-04 12:02:07 UTC 
Created attachment 870376 [details]
Log with failure (search for ERROR)
Comment 2 Gary Brown 2014-03-04 12:02:50 UTC 
Created attachment 870377 [details]
Log from standalone config which worked correctly
Comment 3 Rob Cernich 2014-08-30 00:29:45 UTC 
I think the issue here is that the temp path used by jboss web services has the "suffix" added twice (..../node1/tmp/node1/tmp).  We should look at how the context path is initialized in JBossWebMetaData, as that is what is appended to jboss.server.temp.dir.
Comment 4 Rob Cernich 2014-10-21 17:41:58 UTC 
Hey Magesh, could you please take a look at this?  See my previous comment for details.  Thanks in advance.
Comment 5 tcunning 2014-11-17 19:15:47 UTC 
The solution here is either to :

- leave out the jboss.server.base.dir option
or
- give an absolute path for jboss.server.base.dir 

Put in a pull request to remove the jboss.server.base.dir option from the SwitchYard clustering quickstart - we don't recommend using it in SwitchYard clustering documentation, and it isn't necessary.    In the cluster quickstart, it works fine because we aren't exposing a WSDL, but in the example Gary provides, there is a WSDL exposed so we run into an issue with EndpointPublisherImpl calculating the server.tmp.dir.
Comment 6 Rob Cernich 2014-11-17 23:06:00 UTC 
updated readme
Comment 11 Red Hat Bugzilla 2025-02-10 03:35:15 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.