Jacorb ClientMessageReceptor threads not released after jacorb.connection.client.idle_timeout expires

Grupa gmane.comp.corba.jacorb.devel

Jacorb ClientMessageReceptor threads not released after jacorb.connection.client.idle_timeout expires 2009-06-29 11:02
Hi

I have an issue with jacorb, the scenario is as below:

1) Server A implements one object and the same performs invocations on 4 Remote objects of Server B.

2) Server B implements 4 objects on which invocations would be from Server A and it makes invocations to the one object implmented in server A

In Server A, from the thread dump, I see may ClientMessageReceptor waiting with the trace as below

===========================
"ClientMessageReceptor39" daemon prio=10 tid=0x00466bd0 nid=0xc6 in
Object.wait(
) [0x6747f000..0x6747faf0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at
org.jacorb.orb.giop.GIOPConnection.waitUntilConnected(GIOPConnection.
java:346)
- locked <0xd21e1698> (a java.lang.Object)
at
org.jacorb.orb.giop.GIOPConnection.getMessage(GIOPConnection.java:388
)
at
org.jacorb.orb.giop.GIOPConnection.receiveMessages(GIOPConnection.jav
a:519)
at
org.jacorb.orb.giop.MessageReceptor.doWork(MessageReceptor.java:71)
at
org.jacorb.util.threadpool.ConsumerTie.run(ConsumerTie.java:61)
at java.lang.Thread.run(Thread.java:595)
===========================

These threads dont seem to complete. This is obviously resulting in a
thread leak and I quickly run out of the client_receptor threads once
jacorb.connection.client.max_receptor_threads reaches its limit.

Jacorb ClientMessageReceptor threads not released even after jacorb.connection.client.idle_timeout
expires, they remain in  waitUntilConnected state.

I have to use <objectReference>._release() to release the ClientMessageReceptor Thread.

I would be really thankful if someone can let me know what is going
wrong. In case something more is needed,  I can provide the necessary
information.

Regards,
Abhishek
_______________________________________________
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
Menu
Re: Jacorb ClientMessageReceptor threads not released after jacorb.connection.client.idle_timeout expires 2009-06-29 11:33
Hi,

Could you supply the version number of JacORB you are using (e.g. the
output of 'idl -v'

Thanks

Nick

>Hi
>
>I have an issue with jacorb, the scenario is as below:
>
>1) Server A implements one object and the same performs invocations on 4 Remote objects of Server B.
>
>2) Server B implements 4 objects on which invocations would be from Server A and it makes invocations to the one object implmented in server A
>
>In Server A, from the thread dump, I see may ClientMessageReceptor waiting with the trace as below
>
>===========================
>"ClientMessageReceptor39" daemon prio=10 tid=0x00466bd0 nid=0xc6 in
>Object.wait(
>) [0x6747f000..0x6747faf0]
>        at java.lang.Object.wait(Native Method)
>        at java.lang.Object.wait(Object.java:474)
>        at
>org.jacorb.orb.giop.GIOPConnection.waitUntilConnected(GIOPConnection.
>java:346)
>        - locked <0xd21e1698> (a java.lang.Object)
>        at
>org.jacorb.orb.giop.GIOPConnection.getMessage(GIOPConnection.java:388
>)
>        at
>org.jacorb.orb.giop.GIOPConnection.receiveMessages(GIOPConnection.jav
>a:519)
>        at
>org.jacorb.orb.giop.MessageReceptor.doWork(MessageReceptor.java:71)
>        at
>org.jacorb.util.threadpool.ConsumerTie.run(ConsumerTie.java:61)
>        at java.lang.Thread.run(Thread.java:595)
>===========================
>
>These threads dont seem to complete. This is obviously resulting in a
>thread leak and I quickly run out of the client_receptor threads once
>jacorb.connection.client.max_receptor_threads reaches its limit.
>
>Jacorb ClientMessageReceptor threads not released even after jacorb.connection.client.idle_timeout
>expires, they remain in  waitUntilConnected state.
>
>I have to use <objectReference>._release() to release the ClientMessageReceptor Thread.
>
>I would be really thankful if someone can let me know what is going
>wrong. In case something more is needed,  I can provide the necessary
>information.
>
>Regards,
>Abhishek
>_______________________________________________
>https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
>


_______________________________________________
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
Jacorb ClientMessageReceptor threads not... 2009-06-29 11:02
Re: Jacorb ClientMessageReceptor threads not... 2009-06-29 11:33