Hello,
what GIOP/IIOP are you using on MICO side? Perhaps you might try 1.2
forced by -ORBGIOPVersion 1.2 -ORBIIOPVersion 1.2 command-line parameters.
Yes, JBoss developers used MICO to invoke EJBs operations from C++.
Cheers,
Karel
PS: If you are not using MICO 2.3.12, also please make sure you test it
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
---> http://www.objectsecurity.com/mico_commsup_referral.html <---
---
On Wed, 1 Mar 2006, Denis McHugh wrote:
Thanks Karel,
doing that provided a lot of information. It turns out the problem is in the
J2EE server; when it (the IIOP dispatcher service) is unmarshalling a String
parameter, it hits a java.lang.OutOfMemory exception. With an alternative
orb, the J2EE server goes through the exact same unmarshalling steps, but
doesn't hit any exceptions, and the invocation works fine. What could account
for this difference ? And, has an EJB been successfully invoked by a C++
client via mico ?
Many thanks,
Denis.
Denis,
please try to add `-ORBDebug All' command-line param for your MICO-based
client and see what this produce. And no, it's not known issue.
Cheers,
Karel
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
---> http://www.objectsecurity.com/mico_commsup_referral.html <---
---
_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel
