Menu
▾
▴
openorb-users
|
From: <ros...@wi...> - 2007-05-22 12:12:29
|
Hi,=20
I am facing problem with CORBA service. The corba goes down frequently
in this site and because of that related services also goes down. Can
anyone help me in finding why CORBA is getting restarted in this site?
Please provide your inputs on this.=20
Following are the errors, I could see from the related log files.
CORBA.COMM_FAILURE failure error was shown once as shown below.=20
07.04.26 05:25:53.303 VRB (MI2Server) [main]
GWCAlarmNotifListener::cleanup()-caught Exception,
Ex=3Dorg.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: =
No=20
Main exceptions thrown are=20
Error receiving message in process_or_enqueue=20
Apr 26 10:32:49 anycmt OpenORB NamingService: java.io.EOFException=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.recvMessage(IIOPTransport.java:489)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.process_or_enqueue(SocketQueue.java:254)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.receive(SocketQueue.java:203)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.run_recv(IIOPServerChannel.java:567)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.net.ServerManagerImpl$ChannelRecvRunner.run(ServerManagerImp
l.java:922)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
java.lang.Thread.run(Thread.java:534)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: java.io.EOFException=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.recvMessage(IIOPTransport.java:489)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.close(IIOPTransport.java:298)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.close(SocketQueue.java:168)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.close(IIOPServerChannel.java:425)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.process_or_enqueue(SocketQueue.java:275)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.receive(SocketQueue.java:203)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.run_recv(IIOPServerChannel.java:567)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.net.ServerManagerImpl$ChannelRecvRunner.run(ServerManagerImp
l.java:922)=20
Apr 26 10:32:49 anycmt OpenORB NamingService: at
java.lang.Thread.run(Thread.java:534)=20
=20
07.04.26 05:25:52.593 CRT (TrunkProv@1.0) [main]
org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: OMG minor code: 2 completed:
No=20
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)=20
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)=20
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)=20
at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)=20
at java.lang.Class.newInstance0(Class.java:308)=20
at java.lang.Class.newInstance(Class.java:261)=20
at
com.sun.corba.se.internal.iiop.messages.ReplyMessage_1_2.getSystemExcept
ion(ReplyMessage_1_2.java:90)=20
at
com.sun.corba.se.internal.iiop.ClientResponseImpl.getSystemException(Cli
entResponseImpl.java:105)=20
at
com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.jav
a:314)=20
at
org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)=20
at
org.omg.CosNaming._NamingContextExtStub.unbind(_NamingContextExtStub.jav
a:440)=20
at easynaming.EasyNaming.unbind_from_string(EasyNaming.java:134)
at
com.nortelnetworks.mi2.mi2server.MI2Application.removeFromNameService(MI
2Application.java:282)=20
at
com.nortelnetworks.mi2.mi2server.MI2Application.shutdown(MI2Application.
java:587)=20
at
com.nortelnetworks.mi2.mi2server.MI2ApplicationRegistry.shutdown(MI2Appl
icationRegistry.java:373)=20
at
com.nortelnetworks.mi2.mi2server.MI2ApplicationRegistry.shutdown(MI2Appl
icationRegistry.java:317)=20
at
com.nortelnetworks.mi2.mi2server.MI2Server.shutdown(MI2Server.java:246)=20
at
com.nortelnetworks.mi2.mi2main.MI2Main.waitForShutdown(MI2Main.java:204)
at
com.nortelnetworks.mi2.mi2main.MI2Main.<init>(MI2Main.java:103)=20
at com.nortelnetworks.mi2.mi2main.MI2Main.main(MI2Main.java:62)=20
=20
=20
Regards,=20
Rosmi
|
|
From: rosmi <ros...@wi...> - 2007-05-22 12:13:17
|
Hi,
I am facing problem with CORBA service. The corba goes down frequently in
this site and because of that related services also goes down. Can anyone
help me in finding why CORBA is getting restarted in this site? Please
provide your inputs on this.
Following are the errors, I could see from the related log files.
CORBA.COMM_FAILURE failure error was shown once as shown below.
07.04.26 05:25:53.303 VRB (MI2Server) [main]
GWCAlarmNotifListener::cleanup()-caught Exception,
Ex=org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
Main exceptions thrown are
Error receiving message in process_or_enqueue
Apr 26 10:32:49 anycmt OpenORB NamingService: java.io.EOFException
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.recvMessage(IIOPTransport.java:489)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.process_or_enqueue(SocketQueue.java:254)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.receive(SocketQueue.java:203)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.run_recv(IIOPServerChannel.java:567)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.net.ServerManagerImpl$ChannelRecvRunner.run(ServerManagerImpl.java:922)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
java.lang.Thread.run(Thread.java:534)
Apr 26 10:32:49 anycmt OpenORB NamingService: java.io.EOFException
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.recvMessage(IIOPTransport.java:489)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPTransport.close(IIOPTransport.java:298)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.close(SocketQueue.java:168)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.close(IIOPServerChannel.java:425)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.process_or_enqueue(SocketQueue.java:275)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.SocketQueue.receive(SocketQueue.java:203)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.iiop.IIOPServerChannel.run_recv(IIOPServerChannel.java:567)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
org.openorb.net.ServerManagerImpl$ChannelRecvRunner.run(ServerManagerImpl.java:922)
Apr 26 10:32:49 anycmt OpenORB NamingService: at
java.lang.Thread.run(Thread.java:534)
07.04.26 05:25:52.593 CRT (TrunkProv@1.0) [main]
org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: OMG minor code: 2 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at
com.sun.corba.se.internal.iiop.messages.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:90)
at
com.sun.corba.se.internal.iiop.ClientResponseImpl.getSystemException(ClientResponseImpl.java:105)
at
com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:314)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at
org.omg.CosNaming._NamingContextExtStub.unbind(_NamingContextExtStub.java:440)
at easynaming.EasyNaming.unbind_from_string(EasyNaming.java:134)
at
com.nortelnetworks.mi2.mi2server.MI2Application.removeFromNameService(MI2Application.java:282)
at
com.nortelnetworks.mi2.mi2server.MI2Application.shutdown(MI2Application.java:587)
at
com.nortelnetworks.mi2.mi2server.MI2ApplicationRegistry.shutdown(MI2ApplicationRegistry.java:373)
at
com.nortelnetworks.mi2.mi2server.MI2ApplicationRegistry.shutdown(MI2ApplicationRegistry.java:317)
at
com.nortelnetworks.mi2.mi2server.MI2Server.shutdown(MI2Server.java:246)
at
com.nortelnetworks.mi2.mi2main.MI2Main.waitForShutdown(MI2Main.java:204)
at com.nortelnetworks.mi2.mi2main.MI2Main.<init>(MI2Main.java:103)
at com.nortelnetworks.mi2.mi2main.MI2Main.main(MI2Main.java:62)
Regards,
Rosmi
--
View this message in context: http://www.nabble.com/OpenORB-NamingService%3A-java.io.EOFException-tf3794338.html#a10731794
Sent from the OpenORB - User mailing list archive at Nabble.com.
|
|
From: <lak...@t-...> - 2007-05-22 18:45:21
|
rosmi.jose wrote: > Hi, > I am facing problem with CORBA service. The corba goes down What do you mean by this? Does the NamingService process stop on the OS level, similar to System.exit()? Or do you just see the EOF exceptions below? > frequently in this site and because of that related services also goes > down. Can anyone help me in finding why CORBA is getting restarted in > this site? Please provide your inputs on this. > > Following are the errors, I could see from the related log files. > CORBA.COMM_FAILURE failure error was shown once as shown below. > > 07.04.26 05:25:53.303 VRB (MI2Server) [main] > GWCAlarmNotifListener::cleanup()-caught Exception, > Ex=org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No > > Main exceptions thrown are > > Error receiving message in process_or_enqueue > Apr 26 10:32:49 anycmt OpenORB NamingService: java.io.EOFException > Apr 26 10:32:49 anycmt OpenORB NamingService: at > org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650) > Apr 26 10:32:49 anycmt OpenORB NamingService: at ... I think what you see is a timeout on a socket read. In older versions of OpenOrb this was logged as an error, but it is actually not. It's perfectly normal, the server is waiting for more requests from the same client - if no further requests arrive within a certain amount of time the server closes the connection to save system resources. Are you running OpenORB 1.4? > 07.04.26 05:25:52.593 CRT (TrunkProv@1.0) [main] > org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: OMG minor code: 2 > completed: No > at > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at ... > at > org.omg.CosNaming._NamingContextExtStub.unbind(_NamingContextExtStub.java:440) > This is also normal. The client tries to unbind an entry from the NamingService which does not exist (any more). The server throws an OBJECT_NOT_EXIST exception, because such a request can't be handled in a meaningful way. Either the calling client code needs to be very sure that the object exists before calling unbind, or it needs to handle the exception. If other services go down because of exceptions like this, which system causes that behavior? Do you have some monitoring software installed? Regards, Lars |
|
From: <ros...@wi...> - 2007-05-23 04:54:35
|
Thank you for the response... Answers for your queries is as follows: It is not that I am seeing only the EOF exceptions. Yes, the Naming = service process stop on the OS level. CORBA also stopped. We are facing = this problem System Verification phase. OpenORB Version - 1.3.1 Since corba is going down, client and server side applications undergo = shutdown. It causes the related services to go down. Can you explain me the scenario's(general) where in CORBA keep = restarting/failing? Why does Corba keep restarting/failing? Regards, Rosmi=20 -----Original Message----- From: ope...@li... = [mailto:ope...@li...] On Behalf Of Lars = K=FChne Sent: Wednesday, May 23, 2007 12:15 AM To: ope...@li... Subject: Re: [openorb-users] OpenORB NamingService: java.io.EOFException rosmi.jose wrote: > Hi, > I am facing problem with CORBA service. The corba goes down What do you mean by this? Does the NamingService process stop on the OS = level, similar to System.exit()? Or do you just see the EOF exceptions = below? > frequently in this site and because of that related services also goes = > down. Can anyone help me in finding why CORBA is getting restarted in = > this site? Please provide your inputs on this. > > Following are the errors, I could see from the related log files.=20 > CORBA.COMM_FAILURE failure error was shown once as shown below. > > 07.04.26 05:25:53.303 VRB (MI2Server) [main]=20 > GWCAlarmNotifListener::cleanup()-caught Exception, > Ex=3Dorg.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: = > No > > Main exceptions thrown are > > Error receiving message in process_or_enqueue Apr 26 10:32:49 anycmt=20 > OpenORB NamingService: java.io.EOFException > Apr 26 10:32:49 anycmt OpenORB NamingService: at=20 > org.openorb.iiop.IIOPTransport.readMagic(IIOPTransport.java:650) > Apr 26 10:32:49 anycmt OpenORB NamingService: at ... I think what you see is a timeout on a socket read. In older versions of = OpenOrb this was logged as an error, but it is actually not. It's = perfectly normal, the server is waiting for more requests from the same = client - if no further requests arrive within a certain amount of time = the server closes the connection to save system resources. Are you running OpenORB 1.4? > 07.04.26 05:25:52.593 CRT (TrunkProv@1.0) [main]=20 > org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: OMG minor code: 2=20 > completed: No > at > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at ... > at > org.omg.CosNaming._NamingContextExtStub.unbind(_NamingContextExtStub.j > ava:440) > This is also normal. The client tries to unbind an entry from the = NamingService which does not exist (any more). The server throws an = OBJECT_NOT_EXIST exception, because such a request can't be handled in a = meaningful way. Either the calling client code needs to be very sure = that the object exists before calling unbind, or it needs to handle the = exception. If other services go down because of exceptions like this, which system = causes that behavior? Do you have some monitoring software installed? Regards, Lars -------------------------------------------------------------------------= This SF.net email is sponsored by DB2 Express Download DB2 Express C - = the FREE version of DB2 express and take control of your XML. No limits. = Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ openorb-users mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/openorb-users |
|
From: <lk...@us...> - 2007-05-23 18:55:20
|
On 5/23/07, rosmi.jose wrote: > Yes, the Naming service process stop on the OS level. I haven't rechecked it, but as far as I know there is no explicit System.exit() call in the core ORB classes or the NamingService. Here are a few questions that might lead towards finding the problem: * Are you using tns or ins? If ins, which persistence mechanism (file, db)? Any error messages on startup? * Under which circumstances does the NamingServer terminate, during it's startup, during the first client request, or any other specific situation? * Have you tried to increase logging output or to attach to the NamingService with a debugger? * Are you sure that nothing in your system sends the OS process a termination signal (or whatever it's called on non-UNIX platforms)? > CORBA also stopped. What do you mean by this? CORBA is a not something that starts and stops (like a OS process). It's a specification, much like EJB. What exactly stops? > We are facing this problem System Verification phase. > > OpenORB Version - 1.3.1 OpenORB 1.4.0 has been released about 2 years ago. Why are you using a version that is even older than that? Loads of bugs have been fixed since 1.3.1. Have you tried upgrading? > Since corba is going down, You mean the NamingService process is going down? > client and server side applications undergo > shutdown. It causes the related services to go down. I'm pretty sure that this is either caused by something in your system monitoring (some monitoring program decides "oh, process XYZ depends on the NamingService, that went down so I'll kill XYZ as well") or by badly written client code that doesn't handle SystemExceptions gracefully. > Can you explain me the scenario's(general) where in CORBA keep restarting/failing? Why does Corba keep restarting/failing? Nothing in CORBA / OpenORB does this. Regards, Lars |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X