Search our Resources

Problem

Depending on how your OSB projects are restructured/architected, you might run into an weblogic.rjvm.PeerGoneException error during deployment time. This might look something below in the logs:

Log file

java.lang.RuntimeException:com.rubiconred.myst.exceptions.ActionException: Execution error at /opt/myst/lib/targets/deploy-osb.py

Traceback(innermost last):

 File"/opt/myst/lib/targets/deploy-osb.py", line 87, in myst

 File"/opt/myst//lib/targets/common/osb_utils.py", line 93, in importJar

weblogic.rjvm.PeerGoneException:; nested exception is:

java.io.EOFException

                  at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:1230)

                  at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1206)

                  atweblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:582)

                  at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:673)

                  at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:845)

                  at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:773)

                  at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:972)

                  at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:907)

                  at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:385)

                  at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30)

                  at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)

                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147)

                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)

Causedby: java.io.EOFException

                  ... 10 more

‍

Cause

The issue was due to the size of the artifact and the current value for the maximum message size for the WebLogic AdminServer. If the OSB deployment file is larger than this value, Weblogic will terminate the connection and throw the exception. As a result, you will be unable to import the OBS jar because of its size.

‍

Solution

Update the Maximum Message Size to 20 MB

1. Go to specific Platform Blueprint -> Admin Server
2. Click on Show advanced properties‍
3. Set the Maximum Message size to a value larger than the artifact size. For example 10000000 (is 10MB)
4. Click on Save and Commit
5. ‍Run the Update action from Platform Model
6. ‍Restart the servers so the change will take effect (this happens at the JVM level during initialization)
7. The OSB artifact can now be deployed
   ‍