[omniORB] Freequent Crashes

[Jaskirat Singh]

I'm using the -ORBendPoint giop:tcp:<host>:<port> parameter for running
my server application in sun cluster environment.

The host given is the ip of the cluster rather than the cluster rather
than physical ip of the machine where the application is running.

The Omni Orb version 4.0.1 is being used.



This is resulting in frequent crashes of the server application.

The thread stack is given below:



fe3205e8 __1cEomniQSocketCollectionKfindSocket6Mib_pn0AKSocketLink__ (0,
22af, 1, 0, a, fd879a30) + 68

fe340a5c __1cEomniLtcpEndpointOnotifyReadable6Mi_b_ (ecd348, 22af,
ffffffe2, ffffffe1, ec98d8, ec18d8) + b0

fe31ff10 __1cEomniQSocketCollectionGSelect6M_b_ (ecd350, da7ed7fe,
fffffac1, ec8224, ec0224, fd87baf8) + 3d8

fe340914
__1cEomniLtcpEndpointQAcceptAndMonitor6MpFpvpn0AOgiopConnection__v2_4_
(ecd348, fe304d5c, ecdce8, fe3af59c, fe3408b0, 2000) + 64

fe304e34 __1cEomniQgiopRendezvouserHexecute6M_v_ (ecdce8, 2944,
fe3a9624, 0, f0ad8, fd87bde0) + ac

fe2aff18 __1cPomniAsyncWorkerIreal_run6M_v_ (ecdd18, ecdce8, 1,
fe3abb9c, fe304d88, 0) + 20c

fe2af418 __1cTomniAsyncWorkerInfoDrun6M_v_ (fd87bf34, ecdd18, 0, 0, 0,
0) + 38

fe2b0108 __1cPomniAsyncWorkerDrun6Mpv_v_ (ecdd18, 0, 0, 0, 0, 0) + 14

fe3e28d4 omni_thread_wrapper (ecdd18, fe3f44c8, 0, 0, 0, 0) + d4



I would also like to know in more detail whether this stack is being
shown because of me specifying the ORBendPoint or can this crash happen
without even specifying this parameter.





Any help on this will be much appreciated.



Thanks,



JASKIRAT SINGH



Phone: [phone]



CONFIDENTIALITY NOTICE
This e-mail transmission and any documents, files, or previous e-mail
messages appended or attached to it, may contain information that is
confidential or legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that you must not read this
transmission and that any disclosure, copying, printing, distribution,
or use of the information contained or attached to this transmission is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender by telephone [phone] or return
e-mail message ***@quark.com <mailto:***@quark.com> and
delete the original transmission, its attachments, and any copies
without reading or saving in any manner. Thank you.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070307/22ad979f/attachment.htm

[Duncan Grisby]

Post by Jaskirat Singh
I'm using the -ORBendPoint giop:tcp:<host>:<port> parameter for running
my server application in sun cluster environment.
The host given is the ip of the cluster rather than the cluster rather
than physical ip of the machine where the application is running.
The Omni Orb version 4.0.1 is being used.

Please update to version 4.0.7, or the latest CVS version in the 4.0.x
branch. There are quite a few bugs that have been fixed since 4.0.1. I'm
not sure it will fix your crash, but there is no point trying to track
down the issue with such an old release.

Cheers,

Duncan.

[Jaskirat Singh]

Hello Duncan,



Further to my previous mail, I have analyzed that it does not matter
whether I start my server application with ORBendpoint or not.



I am getting the following stack when ever the application crashes
(usually once in a day or two).



fe3205e8 __1cEomniQSocketCollectionKfindSocket6Mib_pn0AKSocketLink__ (0,
22af, 1, 0, a, fd879a30) + 68

fe340a5c __1cEomniLtcpEndpointOnotifyReadable6Mi_b_ (ecd348, 22af,
ffffffe2, ffffffe1, ec98d8, ec18d8) + b0

fe31ff10 __1cEomniQSocketCollectionGSelect6M_b_ (ecd350, da7ed7fe,
fffffac1, ec8224, ec0224, fd87baf8) + 3d8

fe340914
__1cEomniLtcpEndpointQAcceptAndMonitor6MpFpvpn0AOgiopConnection__v2_4_
(ecd348, fe304d5c, ecdce8, fe3af59c, fe3408b0, 2000) + 64

fe304e34 __1cEomniQgiopRendezvouserHexecute6M_v_ (ecdce8, 2944,
fe3a9624, 0, f0ad8, fd87bde0) + ac

fe2aff18 __1cPomniAsyncWorkerIreal_run6M_v_ (ecdd18, ecdce8, 1,
fe3abb9c, fe304d88, 0) + 20c

fe2af418 __1cTomniAsyncWorkerInfoDrun6M_v_ (fd87bf34, ecdd18, 0, 0, 0,
0) + 38

fe2b0108 __1cPomniAsyncWorkerDrun6Mpv_v_ (ecdd18, 0, 0, 0, 0, 0) + 14

fe3e28d4 omni_thread_wrapper (ecdd18, fe3f44c8, 0, 0, 0, 0) + d4



Any help on this will be much appreciated.



Thanks,

Jaskirat



-----Original Message-----
From: Duncan Grisby [mailto:***@grisby.org]
Sent: Friday, March 09, 2007 9:07 PM
To: Jaskirat Singh
Cc: omniorb-***@omniorb-support.com
Subject: Re: [omniORB] Freequent Crashes

Post by Jaskirat Singh
I'm using the -ORBendPoint giop:tcp:<host>:<port> parameter for

running

Post by Jaskirat Singh
my server application in sun cluster environment.
The host given is the ip of the cluster rather than the cluster rather
than physical ip of the machine where the application is running.
The Omni Orb version 4.0.1 is being used.

Please update to version 4.0.7, or the latest CVS version in the 4.0.x

branch. There are quite a few bugs that have been fixed since 4.0.1. I'm

not sure it will fix your crash, but there is no point trying to track

down the issue with such an old release.



Cheers,



Duncan.
--
-- Duncan Grisby --

-- ***@grisby.org --

-- http://www.grisby.org --

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070314/557f6d1f/attachment.htm