Post Install: Running weblogic.deploy

[Gart Watson]

Has anyone tried to deploy and application on the command-line
using the weblogic.deploy class?

The command I'm running is to list the deployed apps
on the server:

java -cp %WL_HOME%\lib\weblogic.jar weblogic.deploy -port 7001 -host 145.246.40.115
list systemad

which is failing with the following error:
java.io.StreamCorruptedException: Type code out of range, is 0
at java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1280)
at java.io.ObjectInputStream.SkipToEndOfBlockData(ObjectInputStream.java
:1211)
at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java
:776)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:978)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedO
bjectInputStream.java:107)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedO
bjectInputStream.java:115)
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:6
86)
at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(Connecti
onManagerClient.java:140)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:
311)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:2
25)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested except
ion:
[java.io.StreamCorruptedException: Type code out of range, is 0]
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:6
88)
at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(Connecti
onManagerClient.java:140)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:
311)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:2
25)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
JNDI naming exception: Naming exception trying to connect to: t3://145.246.40.11
5:7001 as: system: systemad

I get this kind of error on both Windows NT and Solaris. I get the same error
if I target the Admin or a Managed server. Could
this be a bug in the weblogic.deploy class?

Thanks,
Gary

[Michael Young]

Hi.

Hmm. It appears to work for me. I'm not sure which version of WLS you are running,
but I have a fresh install of WLS 6.1 with sp1 on NT. If you are not already using sp1
please upgrade to that and let me know if it makes a difference.

D:\>java -cp %WL_HOME%\lib\weblogic.jar weblogic.deploy -port 7001 -host localhost list
mypasswd
wl_management_internal2 <DEPLOYED>, source: .\config\mydomain\.wlstaging components:
wl_management_internal2
certificate <DEPLOYED>, source: .\config\mydomain\applications components: certificate
console <DEPLOYED>, source: .\config\mydomain\.wlstaging components: console
wl_management_internal1 <DEPLOYED>, source: .\config\mydomain\.wlstaging components:
wl_management_internal1
DefaultWebApp <DEPLOYED>, source: .\config\mydomain\applications components:
DefaultWebApp
5 deployments.

Thanks,
Michael

Gart Watson wrote:

--

Developer Relations Engineer
BEA Support