PM01453: A JAX-RPC CLIENT USING DYNAMIC INVOCATION INTERFACE (DII) MIGHT FAIL WITH FILENOTFOUNDEXCEPTION AND SERIALIZATION ERRORS

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-RPC client that uses the DII model (that is, uses the
javax.xml.rpc.Call API), when invoking a service, might
encounter an error like the following:

java.io.IOException: WSWS3701E: Error: An exception was
encountered.  Use the wsdeploy command to deploy your
application.  The exception is java.io.IOException: WSWS3031E:
Error: Serialization cannot occur for
com.example.HelloGreeting.  There are no
registered type mappings. Debug deploy artifact build
numbers={pre-WAS 6.0 build}
at
com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
icesFault.java:192)
at
com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:901
)
at
com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:816
)
at
com.ibm.ws.webservices.engine.SOAPPart._getWebServicesInputSourc
e(SOAPPart.java:950)
at
com.ibm.ws.webservices.engine.SOAPPart.getString(SOAPPart.java:5
59)
at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:661)
at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:495)
at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1729)
at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1680)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:236)
...
Caused by: java.io.IOException: WSWS3701E: Error: An exception
was encountered.  Use the wsdeploy command to deploy your
application.  The exception is java.io.IOException: WSWS3031E:
Error: Serialization cannot occur for
com.example.HelloGreeting.  There are no
registered type mappings. Debug deploy artifact build
numbers={pre-WAS 6.0 build}
at
com.ibm.ws.webservices.engine.utils.MCUtils.interceptSerializati
onException(MCUtils.java:141)
...

Local fix

```
<none>
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of JAX-RPC Dynamic Invocation         *
*                  Interface (DII) clients in IBM WebSphere    *
*                  Application Server V6.1 and V7.0            *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-RPC DII client might fail with    *
*                      FileNotFoundException and               *
*                      serialization errors.                   *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR.  *
****************************************************************
A JAX-RPC client that uses the Dynamic Invocation Interface
(DII) (i.e., uses the javax.xml.rpc.Call API), when invoking a
service, might encounter an error like the following:

[7/23/09 12:51:31:316 EDT] 0000002b Call          1
com.ibm.ws.webservices.engine.client.Call getWSDLQuery Call::
WSDLQuery failed, exception ignored, processing continues.
HelloWorld.xsd (The system cannot find the file specified.)

java.io.FileNotFoundException: HelloWorld.xsd (The system
cannot find the file specified.)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>
(FileInputStream.java:135)
 at java.io.FileInputStream.<init>
(FileInputStream.java:95)
 at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
ction.java:85)
 at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
RLConnection.java:176)
 at
com.ibm.ws.webservices.wsdl.symbolTable.Resolver._makeAbsoluteUR
L(Resolver.java:534)
 at
com.ibm.ws.webservices.wsdl.symbolTable.Resolver.setInfoDoc(Reso
lver.java:614)
 at
com.ibm.ws.webservices.wsdl.symbolTable.Resolver._resolveXSD(Res
olver.java:312)
 at
com.ibm.ws.webservices.wsdl.symbolTable.Resolver.resolveXSDInclu
de(Resolver.java:247)
 at
...
com.ibm.ws.webservices.engine.client.Call.invokeWSDLQueryParse(C
all.java:2529)
 at
com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
:2630)
 at
com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
esc(Call.java:2672)
 at
com.ibm.ws.webservices.engine.client.Call.copyOptionsFromWSDLOpe
ration(Call.java:2739)
 at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1723)
 at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1680)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:236)
...

Shortly after, problems with serializing the request might
occur:

java.io.IOException: WSWS3701E: Error: An exception was
encountered.  Use the wsdeploy command to deploy your
application.  The exception is java.io.IOException: WSWS3031E:
Error: Serialization cannot occur for
com.example.HelloGreeting.  There are no
registered type mappings. Debug deploy artifact build
numbers={pre-WAS 6.0 build}
 at
com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
icesFault.java:192)
 at
com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:901
)
 at
com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:816
)
 at
com.ibm.ws.webservices.engine.SOAPPart._getWebServicesInputSourc
e(SOAPPart.java:950)
 at
com.ibm.ws.webservices.engine.SOAPPart.getString(SOAPPart.java:5
59)
 at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:661)
 at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:495)
 at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1729)
 at
com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1680)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:236)
...
Caused by: java.io.IOException: WSWS3701E: Error: An exception
was encountered.  Use the wsdeploy command to deploy your
application.  The exception is java.io.IOException: WSWS3031E:
Error: Serialization cannot occur for
com.example.HelloGreeting.  There are no
registered type mappings. Debug deploy artifact build
numbers={pre-WAS 6.0 build}
 at
com.ibm.ws.webservices.engine.utils.MCUtils.interceptSerializati
onException(MCUtils.java:141)
...

This problem happens only when the client does the following:

1) Uses the DII model (javax.xml.rpc.Call API), as mentioned
previously, and
2) Uses a WSDL that imports or includes a separate schema file.

This problem will not happen if the JAX-RPC DII client's WSDL
contains an embedded schema, or if the client uses the static
stub model (javax.xml.rpc.Stub).

Problem conclusion

The JAX-RPC runtime was fixed to avoid the
FileNotFoundException when resolving the WSDL's referenced
schema file, and this will avoid the serialization problem.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.31 and 7.0.0.11.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM01453
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-17
Closed date
2010-01-05
Last modified date
2010-01-05

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PM01453: A JAX-RPC CLIENT USING DYNAMIC INVOCATION INTERFACE (DII) MIGHT FAIL WITH FILENOTFOUNDEXCEPTION AND SERIALIZATION ERRORS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?