Before you begin
For information on resolving WebSphere-level problems, see Diagnosing and fixing problems.Why and when to perform this task
To identify and resolve Web Services Invocation Framework (WSIF)-related problems, you can use the standard WebSphere Application Server trace and logging facilities. If you encounter a problem that you think might be related to WSIF, you can check for error messages in the WebSphere Application Server administrative console, and in the application server stdout.log file. You can also enable the application server debug trace to provide a detailed exception dump.
A list of the WSIF run-time system messages, with details of what each message means, is provided in Message reference for WSIF.
A list of the main known restrictions that apply when using WSIF is provided in WSIF - Known restrictions.
Here is a checklist of major WSIF activities, with advice on common problems associated with each activity:
Here is a list of common errors, and information on their probable causes:
This problem usually indicates an error in the class path setup. Check that the relevant JAR files are included.
Some likely causes are:
You might also try the following checks:
It is likely that the EAR file is badly formed. Verify the installation by completing the following steps:
Check that the WebSphere Application Server server.policy file (in the /properties directory) has the correct security settings. For more information, see Enabling security for WSIF.
Before you deploy a Web service to WebSphere Application Server, you must decide on the scope of the Web service. The deployment descriptor file dds.xml for the Web service includes the following line:
<isd:provider type="java" scope="Application" ......
You can set the Scope attribute to Application or Session. The default setting is Application, and this value is correct if each request to the Web service does not require objects to be maintained for longer than a single instance. If Scope is set to Application the objects are not available to another request during the execution of the single instance, and they are released on completion. If your Web service needs objects to be maintained for multiple requests, and to be unique within each request, you must set the scope to Session. If Scope is set to Session, the objects are not available to another request during the life of the session, and they are released on completion of the session. If scope is set to Application instead of Session, you might get the following SOAP error:
SOAPException: SOAP-ENV:ClientParsing error, response was: FWK005 parse may not be called while parsing.; nested exception is: [SOAPException: faultCode=SOAP-ENV:Client; msg=Parsing error, response was: FWK005 parse may not be called while parsing.; targetException=org.xml.sax.SAXException: FWK005 parse may not be called while parsing.]