[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3255:
-----------------------------------
Sequences are indeed different. Below are excerpts from 2 different server.logs, with the
timestamps stripped out (although order preserved!) and grepped for relevant lines.
server.log during a hot-deploy of quickstart:
----------------------------------------------------------
Here, you see that soap.esb goes through all it's deploment steps BEFORE
Quickstart_webservice_proxy_basic.esb even starts. Everything works well in this
scenario.
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/soap.esb/
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName soap.esb
with identity: ID-5
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service,
Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName
Quickstart_webservice_proxy_basic.esb with identity: ID-7
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Registering action class
org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Using normal action
pipeline processor for org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
server.log during a restart of jboss:
----------------------------------------------
Here, you see an inter-mingling of deploment steps between
Quickstart_webservice_proxy_basic.esb and soap.esb. In this scenario, the service
deploys, but the WSDL is not available due to a CNFE trying to find SOAPProxy.class (which
lives in a soap.esb jar).
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service,
Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/soap.esb/
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName soap.esb
with identity: ID-5
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName
Quickstart_webservice_proxy_basic.esb with identity: ID-6
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Registering action class
org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Using normal action
pipeline processor for org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL:
https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
Attachments: server.log
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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