Wednesday, May 5, 2010

ESB Console: no systems. Error in log.xml: WSDL parsing failed : WSDL Parsing Failed: Connection timed out

In the metalink note: 467440.1 a possible solution is provided but in our case this was not working. We had a big application which was using Oracle BPEL en Oracle ESB. In the new release the Oracle ESB was replaced by another ESB (mule) but the old ESB systems were still deployed in the Oracle ESB. The ESB Console was not able to retrieve the ESB systems anymore, so everything was empty in the screen. The only error in log.xml in $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j/.../log.xml was

WSDL parsing failed :WSDL Parsing Failed: Connection timed out

We did an undeploy of the esb system with ant and this solved the problem.

This is how we did the undeployment:


<?xml version="1.0" encoding="windows-1252" ?>
<project name="deploy" default="undeploy-esb">

<property file=""/>

<import file="../etc/ESBMetadataMigrationTaskdefs.xml"/>
<target name="undeploy-esb">

<system guid="[ESBSYSTEM GUID]"/>



[ESBSYSTEM GUID] can be found in de dehydration store of the SOA suite:

select name, guid from oraesb.wf_systems;

You need some extra files to make ant work, these files can be found in $ORACLE_HOME/integration/esb/deployment there is an zip file: In this zip file the files you need are there.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

No comments:

Post a Comment