This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 31st, when you will be able to use this site as normal.

    Forum Stats

  • 3,890,861 Users
  • 2,269,649 Discussions
  • 7,916,821 Comments

Discussions

HTTP response error :Connection reset

Anuj Dwivedi--Oracle
Anuj Dwivedi--Oracle Member Posts: 7,077 Employee
edited Dec 12, 2008 3:37AM in Integration - B2B
Hi all,

I am getting following error in log while sending message to the trading partner and the main problem is that once this error comes then after that I am not able to send any more message to any of my Trading Partners. Even if I try to send message to any other Trading Partner, nothing comes in the B2B log and report as well. After restarting the B2B I am able to send message again to other Trading Partners.
Can anyone please tell the reason for getting this error? I also want to know that after getting this error once, why am I not able to send message to any Trading Partner?


2008.12.12 at 06:41:07:647: Thread-13: B2B - (WARNING)
Message Transmission Transport Exception
Transport Error Code is OTA-HTTP-SEND-1006
StackTrace oracle.tip.transport.TransportException: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
at oracle.tip.transport.TransportException.create(TransportException.java:91)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:627)
at oracle.tip.transport.b2b.B2BTransport.send(B2BTransport.java:311)
at oracle.tip.adapter.b2b.transport.TransportInterface.send(TransportInterface.java:980)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1744)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1147)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:137)
at oracle.tip.transport.basic.jms.JMSMonitor.processMessages(JMSMonitor.java:610)
at oracle.tip.transport.basic.jms.JMSMonitor.run(JMSMonitor.java:236)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA12275)
at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:112)
at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3018)
at HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2843)
at HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2635)
at HTTPClient.HTTPConnection.Post(HTTPConnection.java:1107)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:590)
... 8 more

2008.12.12 at 06:41:07:647: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
2008.12.12 at 06:41:07:648: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.

Connection reset
2008.12.12 at 06:41:07:651: Thread-13: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.12.12 at 06:41:07:652: Thread-13: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
2008.12.12 at 06:41:07:658: Thread-13: B2B - (DEBUG) Engine:notifyApp Enter
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = null
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AF77A6111E29ED374E000001BDE3D60</b2bMessageId>
<errorCode>AIP-50079</errorCode>
<errorText>Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.

Connection reset</errorText>
<errorDescription>
<![CDATA[Machine Info: (dys094w004)

Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.

Connection reset ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2008.12.12 at 06:41:07:692: Thread-13: B2B - (DEBUG) Engine:notifyApp Exit
2008.12.12 at 06:41:07:693: Thread-13: B2B - (DEBUG) DBContext commit: Enter
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Transaction.commit()
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Leave
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2008.12.12 at 06:41:07:696: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
***** REQUEST MESSAGE *****




Please help.

Thanks & Regards,
Anuj Dwivedi
Tagged:

Answers

  • 558353
    558353 Member Posts: 175
    Please see if your target server is up and running and you have configured ssl properly.

    You should be in a position to send messages even after this error. If this not the case, please verify you patch and upgrade to the latest.

    Thanks,
    Sinkar
    [From Ramesh Team]
  • Anuj Dwivedi--Oracle
    Anuj Dwivedi--Oracle Member Posts: 7,077 Employee
    Hi Sinkar,


    Thanks for the reply. I confirmed it with my Trading Partner and their server is not running but still I want to know that why am I not able to send message to any other Trading Partner after getting this error once. And if I restart the server, it again acts normally and I am able to send message to other Trading Partners.

    SSL is configured properly because I was able to communicate with this Trading Partner earlier when their server was up.
    We are working on 10.1.2.3.0 with 7457066 MLR 5 patch. Please guide if any other patch required.

    Thanks for the help.

    Warm Regards,
    Anuj Dwivedi
  • 558353
    558353 Member Posts: 175
    Please get us the b2b.log and transport log through Suhas.

    Make sure transport log is enabled and the few properties are set as follows,

    b2b.oracle.tip.DiagnosticLevel.Repository = ERROR
    b2b.oracle.tip.DiagnosticLevel.BusinessLogicLayer = ERROR
    b2b.oracle.tip.DiagnosticLevel.B2B = DEBUG

    Regards,
    Sinkar
    [From Ramesh Team]
This discussion has been closed.