graphs failing on execution

amrit

• February 11, 2013 00:00

• Answered

Follow

Hi All,

When I run my graphs below issue is coming:

INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.3.0 build#021 compiled 15/10/2012 15:10:55
INFO [main] - Running on 2 CPU(s), OS Windows 7, architecture amd64, Java version 1.7.0_07, max available memory for JVM 1343488 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/InitDataStore.grf
INFO [main] - Graph revision: 1.160 Modified by: yfeng Modified: Mon Feb 11 17:01:17 CST 2013
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (InitDataStore)
INFO [main] - [Clover] Initializing phase: 0
ERROR [main] - Error during graph initialization !
Element [1331002769234:InitDataStore]-Phase 0 can't be initialized.
at org.jetel.graph.TransformationGraph.init(TransformationGraph.java:477)
at org.jetel.graph.runtime.EngineInitializer.initGraph(EngineInitializer.java:272)
at org.jetel.graph.runtime.EngineInitializer.initGraph(EngineInitializer.java:239)
at org.jetel.main.runGraph.runGraph(runGraph.java:377)
at org.jetel.main.runGraph.main(runGraph.java:341)
Caused by: WEB_SERVICE_CLIENT0 ...FAILED !
at org.jetel.graph.Phase.init(Phase.java:174)
at org.jetel.graph.TransformationGraph.init(TransformationGraph.java:475)
... 4 more
Caused by: Unable to establish Web Service proxy.
at com.opensys.cloveretl.component.WebServiceClient.g(Unknown Source)
at com.opensys.cloveretl.component.WebServiceClient.init(Unknown Source)
at org.jetel.graph.Phase.init(Phase.java:169)
... 5 more
Caused by: com.opensys.cloveretl.component.ws.exception.WSMessengerConfigurationException: Unable to establish WSDL analyzer.
at com.opensys.cloveretl.component.ws.proxy.a.a(Unknown Source)
... 8 more
Caused by: com.opensys.cloveretl.component.ws.exception.WSDLAnalyzeException: Unable to read WSDL file from location 'http://localhost:7770/ws/control?wsdl'.
Response status: HTTP/1.1 503 java.lang.NullPointerException
at com.opensys.cloveretl.component.ws.WSDLAnalyzer.<init>(Unknown Source)
... 9 more
Caused by: oracle.j2ee.ws.wsdl.LocalizedWSDLException: WSDLException: faultCode=INVALID_WSDL: The document: http://localhost:7770/ws/control?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.parseDefinition(WSDLReaderImpl.java:779)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:707)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:338)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:294)
at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:278)
... 10 more

Can somone please let me know how can this issue be resolved.

Thanks a lot

• 

  slechtaj

  • February 12, 2013 13:45

  0

  Comment actions Permalink

  Hi,
  
  At first make sure the WSDL file is available and valid. If this does not solve your issue and you evaluate CloverETL Designer, you may contact us using eval-support@cloveretl.com. In order to better analyze this issue we need more information (graph and WSDL used in this graph; CloverETL Designer version you use to execute the graph).
• 

  swathi shankar

  • February 12, 2013 14:57

  0

  Comment actions Permalink

  Hi,
  
  this exception occurs when there is problem in WSDL file. Or If the port used by Web service client is already in use.
  
  Chk the port of web service client.
  
  One more possible issue may be ur datastore has not yet started properly.
  
  chk ur datastore status using following command
  
  [SERVER_HOME]/endeca-cmd/endeca-cmd status-ds <data_store_name>
  
  
  Thanks,
  
  Swathi
• 

  amrit

  • February 13, 2013 06:07

  0

  Comment actions Permalink

  issue is resolved now

Please sign in to leave a comment.