Org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation

Hello,
I'm getting a following error message in .trc file (in udump):
org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation
This error is caused by very simple construction in my stored
java procedure
org.omg.CORBA.ORB orb = org.omg.CORBA.ORB.init();
While loading my java procedure into Oracle 8.1.6.1 for NT,
there are no error messages nor warning during resolving.
I found, it's only problem of 8.1.6 version for NT,
I can run my stored java programs on 8.1.5 for Linux.
Doe's anybody have any idea what wrong with internal ORB
in 8.1.6 Oracle RDBMS ?
Thank you very much.
null

Laurent,
When are you getting this error ? Is this error coming from Oc4J or are you getting this error from JDeveloper 9i ?
regards
Debu Panda
Oracle

Similar Messages

RROR : org.omg.CORBA.INITIALIZE: can't instantiate default ORB

When a try to call stored procedure in java i have this error:
ERROR : org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation
com.sun.corba.se.internal.iiop.ORB minor code: 0 completed: No
org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation
com.sun.corba.se.internal.iiop.ORB minor code: 0 completed: No
at org.omg.CORBA.ORB.create_impl(ORB.java)
at org.omg.CORBA.ORB.init(ORB.java)
at HelloClient.hola(HelloClient.java:31)

Laurent,
When are you getting this error ? Is this error coming from Oc4J or are you getting this error from JDeveloper 9i ?
regards
Debu Panda
Oracle

Can't instantiate default ORB implementation ....

I'm developing a J2EE application, and I have this ERROR :
java.lang.ExceptionInInitializerError: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.visigenic.vbroker.orb.ORB minor code: 0 completed: No
     at java.lang.Throwable.fillInStackTrace(Native Method)
     at java.lang.Throwable.fillInStackTrace(Compiled Code)
     at java.lang.Throwable.(Compiled Code)
     at java.lang.Exception.(Compiled Code)
     at java.lang.RuntimeException.(RuntimeException.java:47)
     at org.omg.CORBA.SystemException.(SystemException.java:49)
     at org.omg.CORBA.INITIALIZE.(INITIALIZE.java:73)
     at org.omg.CORBA.INITIALIZE.(INITIALIZE.java:47)
     at org.omg.CORBA.ORB.create_impl(ORB.java:305)
     at
     at com.bo.wibean.WIServerImpl.init(WIServerImpl.java:214)
     at com.bo.wibean.WIServerImpl.(WIServerImpl.java:142)
     at retry.jspService(_retry.java:51)
I'm using the OC4J r2. Some boby can help me ?

Laurent,
When are you getting this error ? Is this error coming from Oc4J or are you getting this error from JDeveloper 9i ?
regards
Debu Panda
Oracle

DACF,BC4J,EJB,Java Web Start: org.omg.CORBA.INITIALIZE

Hi,
I'm trying to use Java Web Start with DACF-application having AMs deployed as Session EJB to O9IAS 1.0.2.0.0 NT.
During opening first iiop-session I get the error:
java.lang.ExceptionInInitializerError: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.visigenic.vbroker.orb.ORB minor code: 0 completed: No
at org.omg.CORBA.ORB.create_impl(Unknown Source)
at org.omg.CORBA.ORB.<clinit>(Unknown Source)
at oracle.aurora.jndi.orb_dep.Orb.init(Orb.java:287)
at oracle.aurora.jndi.orb_dep.IRFinder.getObject(IRFinder.java:75)
at oracle.aurora.jndi.orb_dep.IRFinder.getInitialReference(IRFinder.java:124)
at oracle.aurora.jndi.sess_iiop.SessionCtx.initialContext(SessionCtx.java:637)
at oracle.aurora.jndi.sess_iiop.SessionCtx.<init>(SessionCtx.java:67)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSession(ServiceCtx.java:161)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSession(ServiceCtx.java:177)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSubcontext(ServiceCtx.java:205)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSubcontext(ServiceCtx.java:189)
at oracle.jbo.client.remote.ejb.aurora.AuroraEJBAmHomeImpl.createSession(AuroraEJBAmHomeImpl.java:155)
at oracle.jbo.client.remote.ejb.aurora.AuroraEJBAmHomeImpl.initRemoteHome(AuroraEJBAmHomeImpl.java:125)
at oracle.jbo.client.remote.ejb.aurora.AuroraEJBAmHomeImpl.<init>(AuroraEJBAmHomeImpl.java:59)
at oracle.jbo.client.remote.ejb.aurora.AuroraEJBInitialContext.createJboHome(AuroraEJBInitialContext.java:47)
at oracle.jbo.common.JboInitialContext.lookup(JboInitialContext.java:72)
at javax.naming.InitialContext.lookup(InitialContext.java:276)
at oracle.dacf.dataset.connections.Connection._createAppModule(Connection.java:256)
at oracle.dacf.dataset.connections.Connection.connect(Connection.java:169)
at oracle.dacf.dataset.SessionInfo.connect(SessionInfo.java:1771)
at oracle.dacf.dataset.DbAccessImpl.connect(DbAccessImpl.java:450)
at oracle.dacf.control.swing.LoginDlg._connectToDB(LoginDlg.java:1754)
at oracle.dacf.control.swing.LoginDlg._okButtonClicked(LoginDlg.java:1689)
Could anybody comment the case and/or propose a workaround ?
(or even say that this works in someone's implementation)
Thanks,
Arkadi

<<
java.lang.ExceptionInInitializerError: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation
com.visigenic.vbroker.orb.ORB minor code: 0 completed: No
<<
com.visigenic.vbroker.orb.ORB is part of vbjorb.jar. make sure this file is listed in your archive tag. The jar file can be found in the lib directory of JDev installation
null

What is the Java default ORB implementation class?

I have a web application deployed on the Sun Java System Application Server 8. This application will also act as a CORBA client by invoking remote methods on another CORBA server.
Our first approach was to use the ORB provided by the Sun App Server. But whenever the code reaches the point to initialize the ORB:
orb = ORB.init(as, null); we encountered such exceptions:
[#|2005-02-03T00:38:43.912-0600|WARNING|sun-appserver-pe8.0.0_01|javax.enterpris
e.resource.corba._DEFAULT_.rpc.transport|_ThreadID=14;|"IOP00710209: (INTERNAL)
Unable to create listener thread on the specific port"
org.omg.CORBA.INTERNAL:   vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFa
iled(ORBUtilSystemException.java:3142)
        at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFa
iled(ORBUtilSystemException.java:3160)     When we deployed the same app on Tomcat, it worked fine. We later reasoned the exception was happening on the Sun App Server because perhaps it was trying to initialize another ORB with the same properties as the one initialized by the Sun App Server, and thus was trying to create another listener on a port already in use.
On tomcat, the ORB used was the default ORB provided by Java. Thus, we thought we would try 'overriding' the ORB properties for the Sun App Server by specifiying this in the ORB.init() method:
        String as[] = null;
     Properties orbProperties = new Properties();
     orbProperties.put("org.omg.CORBA.ORBClass","com.sun.corba.se.internal.iiop.ORB");
     orbProperties.put("org.omg.CORBA.ORBSingletonClass","com.sun.corba.se.internal.iiop.ORB");
        orb = ORB.init(as, orbProperties);But when executing this, we get the exception as follows:
Caused by: org.omg.CORBA.INITIALIZE: can't instantiate custom socket factory: co
m.sun.enterprise.iiop.IIOPSSLSocketFactory vmcid: 0x0 minor code: 0 completed
: No
        at com.sun.corba.se.internal.corba.ORB.parseProperties(ORB.java:1250)
        at com.sun.corba.se.internal.POA.POAORB.parseProperties(POAORB.java:267)
        at com.sun.corba.se.internal.Interceptors.PIORB.parseProperties(PIORB.ja
va:341)
        at com.sun.corba.se.internal.corba.ORB.set_parameters(ORB.java:460)
        at com.sun.corba.se.internal.POA.POAORB.set_parameters(POAORB.java:153)
        at com.sun.corba.se.internal.Interceptors.PIORB.set_parameters(PIORB.jav
a:333)
        at org.omg.CORBA.ORB.init(ORB.java:337)
        at com.covansys.ipceuc.corbalogic.SessionManager.<clinit>(SessionManager
.java:159)      Some Sun sites mentioned that com.sun.CORBA.iiop.ORB is the Java ORB implementation. When trying to use this, we got a ClassNotFoundException.
Also tried the following classes:
com.sun.corba.se.internal.corba.ORB
com.sun.corba.se.internal.core.ORB
com.sun.corba.se.internal.org.omg.ORBAll of them reported exceptions as follows:
Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementati
n org.omg.CORBA.ORB vmcid: 0x0 minor code: 0 completed: No
        at org.omg.CORBA.ORB.create_impl(ORB.java:297)
        at org.omg.CORBA.ORB.init(ORB.java:336)
        at com.covansys.ipceuc.corbalogic.SessionManager.<clinit>(SessionManage
.java:158)
        ... 55 more
Caused by: java.lang.InstantiationException
        at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstanc
(InstantiationExceptionConstructorAccessorImpl.java:30)
        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 org.omg.CORBA.ORB.create_impl(ORB.java:295)
        ... 57 more
|#]                                                                            Anyone know what the Java ORB implementation class is, or whether this is possible at all?
Thanks in advance.

Hello
The defaults for JDK 1.4.2 (at least) are shown it the code below:
        Properties p = new Properties ();
        p.put ("org.omg.CORBA.ORBSingletonClass",
               "com.sun.corba.se.internal.corba.ORBSingleton");
        p.put ("org.omg.CORBA.ORBClass",
               "com.sun.corba.se.internal.Interceptors.PIORB");
        p.put ("javax.rmi.CORBA.UtilClass",
               "com.sun.corba.se.internal.POA.ShutdownUtilDelegate");
        p.put ("javax.rmi.CORBA.PortableRemoteObjectClass",
               "com.sun.corba.se.internal.javax.rmi.PortableRemoteObject");
        System.setProperties (p);Of course you can use this code to set these defaults back. Be careful, if you do this inside Weblogic, for instance, it will likely abend.
[]'s
Marcond

Org.omg.CORBA.BAD_OPERATION:   vmcid: 0x2000 minor code: 2049 completed:

Hi,
I have a stupid CORBA error, can someone please help me to have a clue why this client gives me a hart time?
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", "1570");
props.put("org.omg.CORBA.ORBInitialHost", "192.168.10.44");
ORB orb = ORB.init(args, props);
org.omg.CORBA.Object obj = orb.resolve_initial_references("NameService");
NamingContextExt ctx = NamingContextExtHelper.narrow(obj);
org.omg.CORBA.BAD_OPERATION: vmcid: 0x2000 minor code: 2049 completed: No
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(Unknown Source)
     at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_0.getSystemException(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(Unknown Source)
     at com.sun.corba.se.impl.resolver.BootstrapResolverImpl.invoke(Unknown Source)
     at com.sun.corba.se.impl.resolver.BootstrapResolverImpl.resolve(Unknown Source)
     at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source)
     at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source)
     at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source)
     at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(Unknown Source)

I too have the same error my friend.
I am trying to call a remote method of an entity bean when I get the same org.omg.CORBA.BAD_OPERATION message.

Why the stub throws org.omg.CORBA.TRANSACTION_ROLLEDBACK?

Hi,
I have a stateless session bean with a business method createAccount(). In the createAccount() implementation I call create() method on home interface of Account entity bean. I am using IBM Websphere and VisualAge3.5 environment. I have tested the Entity been in Isolation and account is created without any problems but when I try to achieve this via session bean, I get the following error:
org.omg.CORBA.TRANSACTION_ROLLEDBACK
Can anyone tell me how to correct this problem?
Thanks,
Sanjiv

it seems you use JTS and database process has problem

Org.omg.CORBA.IDLEntity Marshalling

I am using JDK 1.4 beta. I am working with 3 objects, one serializable object, one remote object, and one control object. The Control interface implements org.omg.CORBA.IDLEntity which implements Serializable.
The way the objects are embedded is as follows:-
Serializable object [ Remote object [Control object] ]
Now i want to send across the serializable object to the client but i want to send the remote object stub. Therefore i need to override the way the object is written into the output stream. But I have found no documentation on how IDLEntity types are marshalled across. So i am looking on how to invoke this marshalling.
Any help on this topic will be appreciated as i have been stuck on this for weeks now.
Thanks

Hi,
Now i want to send across the serializable object to
the client but i want to send the remote object stub.
Therefore i need to override the way the object is
written into the output stream. But I have found no
documentation on how IDLEntity types are marshalled
across. So i am looking on how to invoke this
marshalling.I'm a little unclear about your situation. How can a Remote object contain the IDLEntity object? If you want to send the Remote object (which would be done by default serialization or a writeObject method on your Serializable), it would get sent basically as an IOR, right?
More to your real question, though -- I believe an IDLEntity type is sent by the ORB by finding its Helper class and calling the write/read method. If you're programming in RMI-IIOP, though, and you're writing a class's writeObject method and you wish to send across an IDLEntity, you should still just call writeObject(<the object to send>) on the given ObjectOutputStream -- the ORB implementation should take care of finding and invoking on the Helper.
- Everett

REP-50125: Caught exception: org.omg.CORBA.OBJECT_NOT_EXIST: minor code:

i have a problem with the users who request a report, the following error appears
REP-50125: Caught exception: org.omg.CORBA.OBJECT_NOT_EXIST: minor code: 0 completed: No
i don have any idea, what it's mean. and sometimes only appears in some users, and others can execute the reports ok.
please really i need some help

Juan, we are having the same problem, and my cluster of 2 servers 9.0.2.2.
I was explained by support, and they were explained by developers that this error is caused by the NULL instead of 0 returned parameter, when no engine available.
This means if you hit refresh long enough it will work.
I personally found this error happens when server's content in cluster is not in synch and just could not explain some other situations, our TAR is still open.
Let me know where are you on this issue

Org.omg.CORBA.Any

Hi there
I'm not sure if this is the right forum to post my question on but if not just ignore it.
In many EJB examples people use the corba class Any.
My q is: how can I get the type of an Any object?
Please have a look at the following code:
ORB orb = ORB.init();
org.omg.CORBA.Any anytest = orb.create_any();
anytest.insert_string("mystring");
TypeCode tc = anytest.type();
Now how can I get back that the type is String??
Regards
Brian

Hi
I dont think extract_TypeCode is the right method according to javadoc extract_TypeCode extracts the TypeCode object in this Any object's value field.
BAD_OPERATION will be thrown - if this Any object contains something other than a TypeCode object.
In my case the Any object might contain anything and not a TypeCode.
Extract_string does give you a string but you need to know in advance that the Any object contain a string type..
What if I dont know??
Regards
Brian

How to get the type of org.omg.CORBA.Any ?

Hi there
My q is: how can I get the type of an Any object?
Please have a look at the following code:
ORB orb = ORB.init();
org.omg.CORBA.Any anytest = orb.create_any();
anytest.insert_string("mystring");
TypeCode tc = anytest.type();
Now how can I get back that the type is String??
Regards
Brian

Hi,
Try using anytest.type().kind().value() -> should yield TCKind._tk_string. See the javadoc for more info.
I think that the only way to check types is by comparing the codes; as far as I know there is no easy way to get the equivalent Java Class object or so. But I could be wrong on that one.
Best,
Guy

Org.omg.CORBA.MARSHAL exception For JMX Notification

I am running Weblogic 9.2 java version 1.5.0_04 and I am tring to recieve JMX Notifications from a Custom MBean running in Weblogic but I keep recieving the following exception:
Jan 5, 2007 12:55:25 PM ClientNotifForwarder NotifFetcher-run
SEVERE: Failed to fetch notification, stopping thread. Error is: java.rmi.MarshalException: CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
java.rmi.MarshalException: CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
     at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:197)
     at javax.rmi.CORBA.Util.mapSystemException(Util.java:67)
     at org.omg.stub.javax.management.remote.rmi._RMIConnection_Stub.fetchNotifications(Unknown Source)
     at javax.management.remote.rmi.RMIConnector$RMINotifClient.fetchNotifs(RMIConnector.java:1285)
     at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.fetchNotifs(ClientNotifForwarder.java:508)
     at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:399)
     at com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:83)
Caused by: org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
I received this first by trying JConsole that comes with JDK 1.5. This only occurs with JMX Notifications because I am able to execute the MBean operation of the MBean and I can see my custome MBean being executed in WebLogic but my custom mbean sends out a JMX Notifications and that causes
the above exception.
I wrote my own NotificationListener program to make sure that it is not a JConsole problem and I got the same problem. I tried using t3 and rmi protocol to see if one of them would work but neither worked. See the code below for the Notification Listener:
          // String protocol = "t3";
          //String jndiroot = "/jndi/";
          String protocol = "rmi";
          String jndiroot = new String("/jndi/iiop://" + hostName + ":" + port + "/");
          String myserver = "weblogic.management.mbeanservers.domainruntime";
          JMXServiceURL serviceURL = null;
          try {
               serviceURL = new JMXServiceURL(protocol, hostName, port, jndiroot + myserver);
          } catch (MalformedURLException e1) {
               logger.debug("malformedURLexception caught");
               e1.printStackTrace();
          Hashtable h = new Hashtable();
          h.put(Context.SECURITY_PRINCIPAL, userName);
          h.put(Context.SECURITY_CREDENTIALS, password);
          // h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote");
          try {
               connector = JMXConnectorFactory.connect(serviceURL, h);
               connection = connector.getMBeanServerConnection();
          } catch (IOException e1) {
               e1.printStackTrace();
          logger.debug("The connection is : " + connection.toString());
          ObjectName mbeanName = null;
          try {
               mbeanName = new ObjectName("Mbean:Name=com.test.bean,Type=TestMBean,Location=AdminServer");
               logger.debug("Created MBeanObjectName: " + mbeanName.toString());
          } catch (MalformedObjectNameException e) {
               e.printStackTrace();
          } catch (NullPointerException e) {
               e.printStackTrace();
          try {
               logger.debug("The mbean is registered " + connection.isRegistered(mbeanName));
          } catch (IOException e1) {
               e1.printStackTrace();
          try {
               connection.addNotificationListener(mbeanName, this,null, null);
               logger.debug("the connection is added a listener : " + connection.isInstanceOf(mbeanName, "com.test.bean.MBean"));
               logger.debug("Listener registered ...");
               //Keeping the remote client active.
               System.out.println("waiting for notifications, got to log file for details....");
               System.in.read();
          } catch (InstanceNotFoundException e) {
               e.printStackTrace();
          } catch (IOException e) {
               e.printStackTrace();
          public void handleNotification(Notification n, Object arg1) {
               logger.debug("******************************************");
               logger.debug("* Notification count : " + counter++ + ", Notification received at "
                         + new Date().toString());
               logger.debug("* type = " + n.getType());
               logger.debug("* message = " + n.getMessage());
               logger.debug("* source = " + n.getSource());
               logger.debug("* seqNum = "
                         + Long.toString(n.getSequenceNumber()));
               logger.debug("* timeStamp = " + new Date(n.getTimeStamp()));
               logger.debug("* userData = " + n.getUserData());
               logger.debug("*******************************************");
I commented out the t3 protocol but it doesn't work for both protocol types. I implemented a Notification Listener within WebLogic and that
worked right away using the following code below:
     InitialContext ctx = new InitialContext();
rmbs = (MBeanServer) ctx.lookup("java:comp/env/jmx/runtime");
As the document "Developing Custom Management Utilities with JMX" on page 4-7 "Make Local Connections to the Runtime MBean Server" described.
Has anyone seem the above exception "Failed to fetch notification, stopping thread. Error is: java.rmi.MarshalException: CORBA MARSHAL 0" when a client is trying to receive JMX Notification? All help would be greatly appreciated.
Thanks,
Ajay

Hi ajay,
How did u manage to access the mbeanserver in BEA ? Can u pls brief on that. Even I am trying the same. But, the MBEANSERVEROBJECT i create, eventhough has NO NULL value, is not able to acces the mbean. Any method access through this object creates an EXCEPTION. Please help me too. I will try solving ur problem too.:-)
Also, do i need to put my MBEAN CLASS in the weblogic server ? Should i create an APP SERVER in BEA ?
I appreciate ur early response, dude..

Org.omg.CORBA.INTERNAL

Here's my problem; I have a CORBA object thats able to launch
any native process through the use of Runtime.exec(...). When I use
this CORBA Object to launch a batch file that starts a JavaVM
to run another CORBA Object (say OBJ2) I get an error. The error happens
when OBJ2 tries to use the ORB.resolveinitialereferences("Rootpoa"). It raises the following
exception.
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
     at com.sun.corba.se.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:253)
     at com.sun.corba.se.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:202)
     at com.sun.corba.se.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:130)
     at com.sun.corba.se.internal.POA.POAORB.getServerEndpoint(POAORB.java:489)
     at com.sun.corba.se.internal.POA.POAImpl.pre_initialize(POAImpl.java:153)
     at com.sun.corba.se.internal.POA.POAImpl.<init>(POAImpl.java:111)
     at com.sun.corba.se.internal.POA.POAORB.makeRootPOA(POAORB.java:111)
     at com.sun.corba.se.internal.POA.POAORB$1.evaluate(POAORB.java:129)
     at com.sun.corba.se.internal.core.Future.evaluate(Future.java:28)
     at com.sun.corba.se.internal.corba.ORB.resolveInitialReference(ORB.java:2485)
     at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2420)
     at services.LogServer.main(LogServer.java:94)
Does anyone know why this happens??
Thanks in advance

Resolving the root POA tries to create a listener thread. Since your initial process already uses an ORB, it's already using that port, so OBJ2 can't use it.
Try specifying a different port for the second ORB to listen on.

Org.omg.CORBA.BAD_PARAM

hi,
while porting Web application using EJB's to Sun One appserver I've found very strange error message which occurs in automaticaly generated stub:
org.omg.CORBA.BAD_PARAM: osiris.setting.internet.InternetDayTypeBean_EJBLocalObjectImpl vmcid: OMG minor code: 6 completed: Maybe
I tried to found what does it means, but there is only one minor code with number 1.
And the code which results to this exception works on other place (with different classes, but same algorithm) correctly.
Does anybodhy have clue what's the matter?
Thanks,
Off

You're getting this error because javax.ejb.EJBLocal objects can't be passed through an ejb Remote interface. Either
1) define the same method on a local interface and have the client use that
or
2) assuming BeanB exposes a Remote interface as well, convert the EJBLocalObjects to EJBObjects and return those.
--ken

Help for org.omg.CORBA.TRANSACTION_ROLLEDBACK Exception

when code like :
try{...}catch(x){throw new RuntimeException("XX");}Then we can saw the Exception is RuntimeException XX
when modify the code like
try{...}catch(x){return;}then Exception is changed as
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:
com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly vmcid: 0x0 minor code: 0 completed: No
>>
The code is running in another Server and the exception will be back to the client machine, using EJB to communicate

it seems you use JTS and database process has problem

Org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation

Similar Messages

Maybe you are looking for