cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to partner broken error message

Former Member
0 Kudos

Hi everyone,

We have an issue with uploading of large files on NetWeaver 7.1 SP3 (it works fine for small files). After some time of upload running, the following exception is thrown:

....................................................

Caused by: org.jvnet.mimepull.MIMEParsingException: com.sap.bc.proj.jstartup.fca.FCAException: Cannot get InBuffer: -7 connection to partner broken.

at org.jvnet.mimepull.MIMEParser.fillBuf(MIMEParser.java:416)

at org.jvnet.mimepull.MIMEParser.readBody(MIMEParser.java:191)

at org.jvnet.mimepull.MIMEParser.access$500(MIMEParser.java:62)

at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:143)

at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:117)

at org.jvnet.mimepull.MIMEMessage.makeProgress(MIMEMessage.java:186)

at org.jvnet.mimepull.DataHead$ReadMultiStream.fetch(DataHead.java:201)

at org.jvnet.mimepull.DataHead$ReadMultiStream.read(DataHead.java:172)

at java.io.InputStream.read(InputStream.java:89)

................................................

Is it possible to tune the http service like in NW 6.4 version?

Thanks,

Radu

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

What do you mean by uploading large files, what is the method you using? Can you pls give more details

Cheers

Former Member
0 Kudos

Hi Shaji,

we have two possibilities to upload large files:

1. Using MTOM Web Services. Here we provided our own Web Services implementation layer based on JAX-WS 2.1.3 reference implementation. For larger files we got the “connection broken” exception, with the following NW related stack trace:

…………………….

Caused by: com.sap.bc.proj.jstartup.fca.FCAException: Cannot get InBuffer: -7 connection to partner broken.

at com.sap.bc.proj.jstartup.fca.impl1.FCAConnection.nativeRead(Native Method)

at com.sap.bc.proj.jstartup.fca.impl1.FCAConnection.read(FCAConnection.java:272)

at com.sap.bc.proj.jstartup.fca.impl1.FCAInputStream.read(FCAInputStream.java:102)

at com.sap.bc.proj.jstartup.fca.impl1.FCAInputStream.read(FCAInputStream.java:67)

at com.sap.engine.services.httpserver.server.io.HttpInputStreamImpl.read(HttpInputStreamImpl.java:167)

at com.sap.engine.services.httpserver.server.io.ChunkedInputStream.unchunkNext(ChunkedInputStream.java:95)

at com.sap.engine.services.httpserver.server.io.ChunkedInputStream.read(ChunkedInputStream.java:57)

at org.jvnet.mimepull.MIMEParser.fillBuf(MIMEParser.java:414)

……………………….

2. Using the HttpServletRequest input stream. In this case, the NW related stack trace is:

……………………………..

Caused by: com.sap.bc.proj.jstartup.fca.FCAException: Cannot get InBuffer: -7 connection to partner broken.

at com.sap.bc.proj.jstartup.fca.impl1.FCAConnection.nativeRead(Native Method)

at com.sap.bc.proj.jstartup.fca.impl1.FCAConnection.read(FCAConnection.java:272)

at com.sap.bc.proj.jstartup.fca.impl1.FCAInputStream.read(FCAInputStream.java:102)

at com.sap.bc.proj.jstartup.fca.impl1.FCAInputStream.read(FCAInputStream.java:67)

at com.sap.engine.services.httpserver.server.io.HttpInputStreamImpl.read(HttpInputStreamImpl.java:167)

at com.opentext.ecm.services.streaming.impl.Streaming.read(Streaming.java:313)

…………………………………

Again, it works well for small files.

Thanks in advance,

Radu

Former Member
0 Kudos

The solution to our problem was to update NW from SP3 to SP5 and to install all patches released after SP5 !