This content has been marked as final.
Show 5 replies
-
1. Re: Wise Consumer SOA-P sample/quickstarts not working...
a_jb_user Jul 15, 2010 3:26 PM (in response to a_jb_user)This is with version:
JBoss SOA Platform: Embedded Server - Version 5.0.1.GA
-
2. Re: Wise Consumer SOA-P sample/quickstarts not working...
kconner Jul 16, 2010 5:56 AM (in response to a_jb_user)Can you enable DEBUG and see what the underlying exception is?
Kev
-
3. Re: Wise Consumer SOA-P sample/quickstarts not working...
a_jb_user Jul 16, 2010 10:20 AM (in response to kconner)Thanks, that helps.
Is the cause of this a missing backslash?
Caused by: java.io.FileNotFoundException: C:Temp\Wise0.xml (The system cannot find the path specified)
FYI, I'm using Windows 7.
Log:
2010-07-16 10:06:29,158 INFO [STDOUT] (pool-28-thread-1) &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2010-07-16 10:06:29,158 INFO [STDOUT] (pool-28-thread-1) Request map is: {toWhom=Jimbo}2010-07-16 10:06:29,174 INFO [STDOUT] (pool-28-thread-1) &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2010-07-16 10:06:29,174 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-28-thread-1) executing processor 1 Wise SOAPClient [wsdl=http://127.0.0.1:8080/Quickstart_webservice_consumer_wise/HelloWorldWS?wsdl, soapAction=sayHello, endPointName=HelloWorldPort, serviceName=HelloWorldWS, smooksRequestMapperURL=null, smooksResponseMapperURL=null]2010-07-16 10:06:29,330 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] (http-127.0.0.1-8080-1) provide SPI 'class org.jboss.wsf.spi.management.EndpointRegistryFactory'2010-07-16 10:06:29,346 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] (http-127.0.0.1-8080-1) class org.jboss.wsf.spi.management.EndpointRegistryFactory Implementation: org.jboss.wsf.stack.jbws.EndpointRegistryFactoryImpl@58be937b2010-07-16 10:06:29,361 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] (http-127.0.0.1-8080-1) handleWSDLRequest: jboss.ws:context=Quickstart_webservice_consumer_wise,endpoint=HelloWorldWS2010-07-16 10:06:29,361 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] (http-127.0.0.1-8080-1) WSDL request, using host: 127.0.0.12010-07-16 10:06:29,377 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-28-thread-1) Unexpected exception caught while processing the action pipelineorg.jboss.soa.esb.actions.ActionProcessingException: Wsdl download failed!at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClient.java:281)at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:238)at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634)at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588)at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419)at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)at java.lang.Thread.run(Thread.java:619)Caused by: it.javalinux.wise.core.exceptions.WiseConnectionException: Wsdl download failed!at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.transferWSDL(WSDynamicClientFactory.java:144)at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.downloadWsdl(WSDynamicClientFactory.java:80)at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSDynamicClientFactory.java:68)at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClient.java:277)... 8 moreCaused by: java.io.FileNotFoundException: C:Temp\Wise0.xml (The system cannot find the path specified)at java.io.FileOutputStream.open(Native Method)at java.io.FileOutputStream.<init>(FileOutputStream.java:179)at java.io.FileOutputStream.<init>(FileOutputStream.java:131)at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.transferWSDL(WSDynamicClientFactory.java:132)... 11 more2010-07-16 10:06:29,392 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-28-thread-1) No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:localhost#queue/quickstart_webservice_consumer_wise_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_webservice_consumer_wise_esb/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:R -
4. Re: Wise Consumer SOA-P sample/quickstarts not working...
beve Jul 17, 2010 6:29 AM (in response to a_jb_user)What is the 'wise.tmpDir' property in wise-core.properties set to? (you can find this file in the wise quickstart directory)
Regards,
/Daniel
-
5. Re: Wise Consumer SOA-P sample/quickstarts not working...
joe_boy12 Jul 12, 2011 2:58 PM (in response to beve)have you guys figured that out? I am having same issue. it works if I give absolute path there e.g. c:/jboss-as/server/esb/tmp