4 Replies Latest reply: Jan 6, 2011 4:53 PM by Mikereiche-Oracle RSS

    WLP 9.2.3 integration problem with ALDSP 2.5

    user738507
      HI,

      I am having the following issue when using WLP 9.2.3 and ALDSP 2.5 on WebLogic 8.1.

      We have recently upgraded from WLP 9.2.1 to WLP 9.2.3,
      We were initially getting this error,

      following error observed if accessed via application or a standalone test case.

      context :: javax.naming.InitialContext
      com.bea.dsp.dsmediator.client.exception.SDOMediatorException: weblogic.rjvm.PeerGoneException: ; nested exception is:
      java.io.EOFException
      at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:322)
      at authenticationdataservices.logical.FirmUser.getFirmUserId(FirmUser.java:98)
      at src.AuthenticationUtil.main(AuthenticationUtil.java:27)
      Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
      java.io.EOFException
      at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
      at com.bea.ld.Server_ydm4ie_EOImpl_816_WLStub.executeFunction(Unknown Source)
      at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:312)
      ... 2 more
      Caused by: java.io.EOFException
      at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
      at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:737)
      at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:684)
      at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:845)
      at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:792)
      at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
      at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
      at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

      To overcome this issue we have read this [ information |http://download.oracle.com/docs/cd/E13167_01/aldsp/docs25/appdev/intro.html] and have done the required.

      Re: ALDSP 2.1 QName problem

      To enable interop from 9.x client to DSP 2.1 server, follow the following steps.

      1. Put ${WL_HOME}/liquiddata/lib/wls90interop.jar in PRE_CLASSPATH on
      2.1 server by editing setDomainEnv.cmd
      2. Put ${WL_HOME}/liquiddata/lib/wls90interop.jar in workshop's classpath
      by modifying -cp key's value in Workshop.cfg
      3. Build the application inside the workshop.
      4. Build the client side jar using ${WL_HOME}/liquiddata/bin/ld_clientapi.xml
      with following arguments on the command line:
      -Dapproot=<application directory>
      -Dxbeanjarpath=${WEBLOGIC9x}/server/lib/xbean.jar
      5. Copy ${WL_HOME}/liquiddata/lib/wlsdo90interop.jar, ld-client.jar and
      <appName>-ld-client.jar in WEB-INF/lib or classpath of the 9.x side.

      Since network classloading is turned off in any WebLogic server, we need to copy wlsdo.jar and ld-client.jar on the client side.
      Also added the flag -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 on the startup of the server (JDK 1.50_12 which is used WLP 9.2.3). We also downgraded the JVM version (JDK 1.5.0_06) for WLP server (as explained in the BUG to JDK 1.5.0_06.)

      Now we are getting another issue:
      Here is the exception observed:
      com.bea.control.servicecontrol.util.memento.ServiceClassMementoUtil> <000000> <com.bea.control.servicecontrol.util.memento.ServiceClassMementoUtil: Cou
      ld not load the ServiceClassMemento from the following resource file: uk/gov/fsa/mer/csadminservice/servicecontrol/AdministrationServiceControlServiceClassMemento.ser. This is probably due to a v
      ersioning issue and if the developer was astute when they made the change then this should not be the reason. Another possibility is that this resource has become corrupt. The good news is a reb
      uild of your app should fix it.

      Throwable: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local class serialVersionUID = 4418622981026545151
      Stack Trace:
      java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local class serialVersionUID = 4418622981026545151
      at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)
      at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546)
      at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
      at java.util.HashMap.readObject(HashMap.java:1012)
      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:919)
      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1813)
      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)

      Please advice on how to overcome this issue.

      Your attention to this issue will be highly appreciated.

      Regards,

      Edited by: user738507 on Jan 6, 2011 12:46 PM