Bug? RMI Locked Threads
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
Bug? RMI Locked Threads
by glassfish-2
::
Rate this Message:
I'm consistently getting blocked threads piling up behind an RMI thread that seems to be waiting for IO. What do I do next?
Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs) This thread (below) has object 0x00007f006c3edbb8 locked and other RMI threads are blocking on that lock. I'm assuming com.sun.corba.ee.impl.orbutil.ORBUtility is not open source, so I can't look at the code. Line 105 seems like the place to look. The code that is driving this is pretty simple stuff. Calling a stateless session bean from a Swing client. I can see the call on the swing client get made, but then it never reaches my session bean method, it just hangs. Calls to other methods in the same bean seem to work. Really weird. [code] "p: thread-pool-1; w: 16" daemon prio=10 tid=0x00000000404a1000 nid=0x37a1 runnable [0x00007f0055ba8000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507) - locked <0x00007f00831a1b70> (a java.lang.Object) - locked <0x00007f00831a1b90> (a java.lang.Object) - locked <0x00007f00831a1b80> (a java.lang.Object) at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192) - locked <0x00007f006c3edbb8> (a java.lang.Object) ........ [/code] [Message sent by forum member 'culli' (culli)] http://forums.java.net/jive/thread.jspa?messageID=361020 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Bug? RMI Locked Threads
by glassfish-2
::
Rate this Message:
This sounds like the threads are blocked, not locked, waiting on this guy's connect call to finish. AFAIK the usual reasons for a connect call to block are network or DNS issues, although IIOP can do some funny stuff. My point is, I suggest you first check your IIOP settings to make sure you are connecting to the right server.
[Message sent by forum member 'matterbury' (matterbury)] http://forums.java.net/jive/thread.jspa?messageID=361150 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Bug? RMI Locked Threads
by glassfish-2
::
Rate this Message:
Connecting to the right server? Yes it is, because it works most of the time. Just certain conditions would lock it up. But it's working now, see other post in this thread.
[Message sent by forum member 'culli' (jim.cullison@...)] http://forums.java.net/jive/thread.jspa?messageID=361996 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Bug? RMI Locked Threads
by glassfish-2
::
Rate this Message:
The good news is that Glassfish is now working very well. The bad news is I don't know exactly what fixed it. Here's the scenario that fixed it though:
* Inherited Glassfish install from previous developers. * Found out that they had always done upgrades by copying the domain folder to a new Glassfish install. * Created a new domain and reinstalled all war, jar, and ear files. * Now it doesn't lock up any more and performs much better. What were the offending configuration items? I can't tell. But at least it's working. My faith in Glassfish is much restored because we did some load testing and it easily handled what we threw at it. [Message sent by forum member 'culli' (jim.cullison@...)] http://forums.java.net/jive/thread.jspa?messageID=361997 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Bug? RMI Locked Threads
by glassfish-2
::
Rate this Message:
Turns out this problem came back. But this time I think it's fixed. The key was setting the orb iiop listener's network address. The default is 0.0.0.0, which works for most clients, but we particularly had problems with people coming in on VPN and possibly different subnets. Once we set the address to the dns name of the machine, it works MUCH better. No lockups for a whole day.
Count this is as an advertisement for glassfish support. We bought it a couple weeks ago and they gave us the clue we needed to fix the problem. [Message sent by forum member 'culli' (jim.cullison@...)] http://forums.java.net/jive/thread.jspa?messageID=370921 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
