IAS 6.0 SP2 - IPS 3.0 SP2 integration

Question

Hi
I am faced with a problem related to IAS 6.0 SP2 and iPlanet Portal
Server 3.0 SP2. I have deployed the beans on IAS and can access it from
a rich client.
I've servlets running in IPS and from these, I want to access the beans
on IAS. I'm getting an unsatisfied link error. Theexception thrown is as
follows :
03/Jul/2001:14:37:02] info (15110): PortalInterface: init
[03/Jul/2001:14:37:09] failure (15110): Internal error: exception thrown
from the servlet service function (uri=/PortalInterface):
java.lang.UnsatisfiedLinkError: specialLoadClass, Stack:
java.lang.UnsatisfiedLinkError: specialLoadClass
at
com.sun.corba.ee.internal.util.JDKClassLoader.loadClass(JDKClassLoader.java:58)
at
com.sun.corba.ee.internal.util.JDKBridge.loadClassM(JDKBridge.java:180)
at
com.sun.corba.ee.internal.util.JDKBridge.loadClass(JDKBridge.java:83)
at javax.rmi.CORBA.Util.loadClass(Util.java:215)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:306)
at <Unloaded Method>
at
javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
at <Unloaded Method>
at
com.iplanet.portalserver.api.SabreFlightDetails.getPriceAvailabilityInfo(Compiled
Code)
at
com.iplanet.portalserver.api.SabreFlightDetails.getSabreFlights(SabreFlightDetails.java:74)
at com.iplanet.portalserver.api.PortalInterface.doPost(Compiled
Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at
com.netscape.server.http.servlet.NSServletRunner.Service(Compiled Code)
I've set classpaths for the rich client in kjs and also in jvm12.conf of
IPS 3.0. But going by the rich client examples given with IAS, like the
converter client example, we have to set
a LD_LIBRARY_PATH as in runclient.sh. There is no place in IPS where we
can set the LD_LIBRARY_PATH. Is that the reason ?
I would appreciate your thoughts on this issue.
Thanks
Partha

Answer 1

One work around for this is to have only one copy in the system class path and have it loaded one only once and one copy. Then both the applications A and B can have access to this library, with out any ambiguity.
So, put the library in the application server's system class path.
I am little confused with your statements in 4th and 5th paragraphs, that shared library has been modified and packed in Application B and then deployed. So, you have two libraries alomost the same in Application A as well as Application B.
According to my understanding, since the library in App B is superset to the library (shared library??, as you call. Is this really a shared library now?) in Application A, we can only have one only one library in the Application Server System class path. Am I correct?
If this answer does not answer your question accurately, please get back. And please let me know about the answer.
Rakesh.