By definition I am. A conflicting fact is the only CORBA client program
works with Tomcat 3!
I guess the original program might indeed have an issue as it registers
callback twice(different id though, and orb object shares the same callback
port:2468 ):
callbacks = new Callbacks( orb );
mWebCallback = new MwebWebCallbackImpl(m_Queue);
mWapCallback = new MwebWapCallbackImpl(m_Queue);
// register callbacks
registerCallback(mWebCallback, web_callback);
registerCallback(mWapCallback, wap_callback);
Opinion?
Thanks!!
David
-Original Message-
From: Bodycombe, Andrew [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 9:49 AM
To: 'Tomcat Users List'
Subject: RE: CORBA initialization error with Tomcat 4.1
Sounds like you have hit your CORBA implementation limit.
See the CORBA documentation for more details.
Andy
-Original Message-
From: Xu, David [mailto:[EMAIL PROTECTED]]
Sent: 08 January 2003 17:49
To: '[EMAIL PROTECTED]'
Subject: CORBA initialization error with Tomcat 4.1
Importance: High
Hi, there,
I use a Bea Tuxedo CORBA client and the CORBA client object within a servlet
has been working fine with Tomcat 3. Now with Tomcat 4.1.18, the servelet
start up with errors:
Exception err=org.omg.CORBA.IMP_LIMIT: vmcid: 0x0 minor code: 0
completed: No
Has anyone has a clue? or doing the same?
Regards,
David
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
