Oracle Weblogic Server (MOSC)

MOSC Banner

Client Thread hangs after Weblogic server call using RMI T3 HTTP

edited Feb 7, 2013 3:16AM in Oracle Weblogic Server (MOSC) 6 commentsAnswered
Our weblogic client application has a runnable thread that calls a server method using RMI (T3) but does not return after the call. We are using the library generated by the Weblogic sever.
When dumping the stacktrace of this thread the following information is available. It looks like that it's waiting for socket data but isn't receiving anything.
Any Ideas?

2012-12-18 13:57:48,591 <Thread-122:RUNNABLE>
           <java.net.SocketInputStream:socketRead0:-2|>
           <java.net.SocketInputStream:read:-1|>
           <java.io.BufferedInputStream:fill:-1|>
           <java.io.BufferedInputStream:read:-1|>
           <weblogic.net.http.MessageHeader:isHTTP:206|>
           <weblogic.net.http.MessageHeader:parseHeader:134|>

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center