With iordump, I see IIOP Profile information which states that the Version
is 1.1, but no GIOP data.
How did you make your mico use GIOP/IIOP 1.2 in the first place ? Is this an
installation option or a specific version of mico ? (I'm using 2.3.12).
Thanks,
Colm.
Hello,
this is probably
Hello,
this is probably not feature but requirement. i.e. if your server is using
GIOP 1.0, MICO needs to "downgrade" and use also 1.0. Try to iordump your
server (ejb's) reference to get more information about what GIOP version
it uses.
Yes, I'm able to use exactly your parameters below to
Thanks Karel,
I am using mico 2.3.12, and it defaults to GIOP/IIOP version 1.0. I tried to
specify 1.2 as you advised, but I am not sure how to force the client to use
GIOP version 1.2.
I run the client like this:
client -ORBGIOPVersion 1.2 -ORBIIOPVersion 1.2
-ORBDebug All
and in the d
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 sur
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 un
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, fa
I have just downloaded mico and it looks very promising. I want to be able
to connect a C++ client to an EJB service in a J2EE engine, and I am porting
a client from using orbacus to mico. It goes well, until the client attempts
to invoke the EJB object.
Here is a synopsis of the code and ho
