Error: Remote request refused because authentication is not configured

This error can occur because of wrong configuration at opmn.xml. OPMN supports remote requests to other OPMN servers in the same cluster, but for security reasons all process control requests (start, restart and stop) are only enabled if SSL is enabled in the opmn.xml file and a wallet file is configured. If neither SSL nor a wallet file are configured, OPMN will reject any remote process control request with HTTP code 403."

To fix this, 

• Make sure the rmi connectivity against the remote OC4J instances is working.
• Make sure the OC4J instances are configured using only one nic card ip address. If not edit rmi.xml at
  $ORACLE_HOME/j2ee/j2ee/my_instance/config/rmi.xml

<rmi-server
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/rmi-server-10_0.xsd"
host="<localhostname>"
port="23791"
ssl-port = "23943"
schema-major-version="10"
schema-minor-version="0"
>

where <localhostname> is the localhostname, as it is defined in /etc/hosts associated to you
local ip address

• Make sure you have configured SSL authentication is implemented.

<notification-server interface="ipv4">
<port local="6100" remote="6200" request="6003"/>
<ssl enabled="true" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
</notification-server>

• Restart OPMN

Error: Missing ormi[s]://:

The issue is related to Sun’s JDK bug when using JDK 1.5 with IPv6 enabled. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527

To implement the solution,

1. Set the command line option -Djava.net.preferIPv4Stack=true in the oc4j java-options for both start and stop categories.
2. Restart the server. After restart you should not be seeing these error any more.

Response: Remote request with weak authentication.

The ‘weak authentication’ message means that ONS is using the default wallet (or some other demo wallet) that ships with the product. Note that this wallet is a DEMO-only wallet, and is not secure! For security it is necessary to configure a real wallet for use with OPMN. You will need to either create a real wallet to replace the existing demo wallet, or to configure OPMN to use one that has already been created for another component, such as Oracle HTTP Server.

Error Resolution

• JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Premature EOF encountered

  The cause is a timeout on the load balancer. The fix is to add the following java parameter to the container
  -DHTTPClient.disableKeepAlives=true

• LPX-00200: could not convert from encoding UTF-8 to WINDOWS-1252
  • Open document in Notepad and goto File > Save As > Select Encoding as “UTF-8” and save it. Your problem is solved.

 

• WARNING: OC4J will not send ONS ProcReadyPort messages to opmn for service: OC4JServiceInfo id: null protocol: jms hostname: null port: 12601 description: null
  • Try deleting jms.state file located in <ORACLE_HOME>\j2ee\<OC4J>\persistence\<OC4J>_<OC4J_GROUP>_1
  • Also delete .lock files in the <ORACLE_HOME>\j2ee\<OC4J>\persistence folder
  • Restart the server
• OPMN on IPv6
  • -Djava.net.preferIPv4Stack=true to the java start and stop parameters in the OC4J module sections
• OPATCH_JAVA_ERROR: Wrong number of arguments.  VerifyPatch needs ORACLE_HOME, OUI location, patch location, patch ID and path to ‘ar’ command, no_inventory, OS_ID.
  • Set OPATCH_PLATFORM_ID environment variable to 0. This should fix the problem.

Error: Process time out while waiting for a managed process to stop

This generally happens with OC4J takes longer than timeout parameter in opmn.xml. There can be lot of reasons behind this like slow machine or too many processes to unload or both. This is not a “show-stopper” error however if you don’t want to see this error, just open your opmn.xml located in <SOA_HOME>/opmn/conf folder and increase your stop timeout parameter from default 120 to 300 (or whatever you like). This will prevent that error from coming again.

<stop timeout="300" />