PK92796: WSWS3259E ERROR READING DATA STREAM MIME START BOUNDRY NOT FOUND

Fixes are available

APAR status

Closed as program error.

Error description

The following error occurs while reading a message sent from a
web service application running on a WebSphere Application
Server.

[7/6/09 14:50:09:444 MDT] 00000068 Message       E
com.ibm.ws.webservices.engine.Message setup WSWS3239E: Error:
InvocationTargetException: WebServicesFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
on

faultString: WSWS3259E: Error: Error reading data stream:
WSWS3261E: Error: Error in MIME data stream, start boundary not
found, expected:  ------=_Part_10580_226561409.1246913408895
.
faultActor: null
faultDetail:

WSWS3259E: Error: Error reading data stream:  WSWS3261E: Error:
Error in MIME data stream, start boundary not found, expected:
------=_Part_10580_226561409.1246913408895
.
at
com.ibm.ws.webservices.engine.attachments.MultiPartRelatedInputS
tream.<init>(MultiPartRelatedInputStream.java:426)
at
com.ibm.ws.webservices.engine.attachments.AttachmentsImpl.<init>
(AttachmentsImpl.java:187)
at
com.ibm.ws.webservices.engine.Message.setup(Message.java:379)
at
com.ibm.ws.webservices.engine.Message.<init>(Message.java:258)
at
com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannel
Connection.receiveSOAPResponse(HttpOutboundChannelConnection.jav
a:1060)
at
com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(H
TTPSender.java:502)
at
com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa
ndlerWrapper.java:228)
at
com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa
ndlerWrapper.java:228)
at
com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa
ndlerWrapper.java:228)
at
com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServic
esEngine.java:283)
at
com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Con
nection.java:850)
at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:702)
at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:653)
at
com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
n.java:481)
at
com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.jav
a:838)
####

If viewed in a tcp trace, the incoming message has HTTP MIME
headers, but the rest of the message is missing.


The root of the problem is in the WebSphere Application Server
that sent the message.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  JAX-RPC web services                        *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-RPC web service is sending a      *
*                      truncated message.  The node that       *
*                      receives this message fails.            *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR on   *
*                  the WebSphere Application Server that       *
*                  sends the message.                          *
****************************************************************
Application Server issues the following message:

WSWS3259E: Error: Error reading data stream:  WSWS3261E: Error:
Error in MIME data stream, start boundary not found, expected:
------=_Part_10580_226561409.1246913408895
.
at
com.ibm.ws.webservices.engine.attachments.MultiPartRelatedInputS
tream.<init>(MultiPartRelatedInputStream.java:426)
at
com.ibm.ws.webservices.engine.attachments.AttachmentsImpl.<init>
(AttachmentsImpl.java:187)
at
com.ibm.ws.webservices.engine.Message.setup(Message.java:379)
at
com.ibm.ws.webservices.engine.Message.<init>(Message.java:258)
at
com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannel
Connection.receiveSOAPResponse(HttpOutboundChannelConnection.jav
a:1060)
...

This indicates that the incoming message is incomplete.

No failures are observed on the Application Server
instance that sends the message.

Problem conclusion

The JAX-RPC engine is sending an incomplete message.

It uses a javax.xml.mail.MimeMessage to construct the contents
of the outbound HTTP message.  In some cases, the logic fails
without issuing an error.

Logic has been added to detect the failure. When a failure is
detected, a new algorithm is used to construct the HTTP message.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.39, 6.1.0.29 and 7.0.0.9.  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
PK92796
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-30
Closed date
2009-09-01
Last modified date
2009-09-01

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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:
29 December 2021

Tips

PK92796: WSWS3259E ERROR READING DATA STREAM MIME START BOUNDRY NOT FOUND

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?