Communication Issues between WebLogic Admin and Managed Servers

<BEA-101215><Malformed request “Can not parse URI from http request”. Request parsing failed, Code: -1>

Go to WLS console->Environment->Servers->->Protocols->HTTP and uncheck “Enable Keepalives”

<BEA-149535><JMX Resiliency Activity Server=xxxxxx :
Received a DISCONNECT EVENT

We need to specify the listen address on each server.

<BEA-000405><Uncaught Throwable in processSockets
java.lang.NullPointerException.
java.lang.NullPointerException

This is known issue with 12.1.3.0. It has been addressed by Bug 19212729 – NON BLOCKING IO WRITE THROW NULLPOINTEREXCEPTION

<BEA-149504><The Administration Server was unable to establish JMX Connectivity with the xxx at the JMX Service URL of service:jmx:t3://xxxx:xx/jndi/weblogic.management.mbeanservers.runtime.>

This was due to incorrect DNS resolution.Please add the below flag

-Dweblogic.ResolveDNSName=true

<BEA-000503><Incoming message header or abbreviation processing failed.
java.io.InvalidClassException: filter status: REJECTED
java.io.InvalidClassException: filter status: REJECTED
at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1255)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1878)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1885)

Please refer Doc 2490561.1 and Doc ID 2421487.1

-Dweblogic.oif.serialFilter=maxdepth=200

<BEA-000572><The server rejected a connection attempt JVMMessage from: ‘1503149755270330151C:251.192.5.138R:xxxx’ to: ‘0B:192.168.1.227:[15102,-1,-1,-1,-1,-1,-1]’ cmd: ‘CMD_IDENTIFY_REQUEST’, QOS: ‘101’, responseId: ‘-1’, invokableId: ‘-1’, flags: ‘JVMIDs Sent, TX Context Not Sent, 0x1’, abbrev offset: ‘106’ probably due to an incorrect firewall configuration or administrative command.>

You can try this JVM flag
-Dweblogic.rjvm.enableprotocolswitch=true

Leave a Reply