GC11g - AD4J Deployment Timeout

(Doc ID 1265218.1)

Last updated on JULY 30, 2012

Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 and later
Information in this document applies to any platform.

Symptoms

Trying to deploy AD4J to existing OEM11g as per the Install Guide.

The deploy script reports some timeouts.

Below is the output of the DeployAD4JManager.sh script:


Deployment Summary:
WEBLOGICHOSTNAME servername.xxx.yyy.com
WEBLOGICPORTNUMBER: 7101
USERNAME: weblogic
MACHINENAME: EMGC_MACHINE1
ORACLEHOME: /u01/app/oracle/product/middleware/oms11g
WLHOME: /u01/app/oracle/product/middleware/wlserver_10.3
MODULEHOME: /u01/app/oracle/product/middleware/modules
SERVERNAME EMAD4JMANAGER
LISTENADDRESS servername.xxx.yyy.com
LISTENPORT 3800
SSL LISTENPORT 3801
Existing OMS server name EMGC_OMS1
Existing EMGC DOMAIN Home path /u01/app/oracle/product/middleware/../gc_inst/user_projects/domains/GCDomain
Existing Instance Home /u01/app/oracle/product/middleware/../gc_inst/user_projects/domains/GCDomain/em/EMGC_OMS1

Connecting to t3s://servername.xxx.yyy.com:7101 with userid weblogic ...
Successfully connected to Admin Server 'EMGC_ADMINSERVER' that belongs to domain 'GCDomain'.

Dummy deploying on EMGC_OMS1
This will make jammanager entry to system-jazn-data.xml

Deploying application from /u01/app/oracle/product/middleware/oms11g/ad4j/./jammanager.ear to targets EMGC_OMS1 (upload=false) ...
<Jun 10, 2010 11:24:17 AM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, jammanager [archive: /u01/app/oracle/product/middleware/oms11g/ad4j/./jammanager.ear], to EMGC_OMS1 .>
.......................................................................................................................................................................................................No stack trace available.
This Exception occurred at Thu Jun 10 11:34:19 EDT 2010.
weblogic.management.scripting.ScriptException: Error occured while performing deploy :
The action you performed timed out after 600,000 milliseconds.
at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:188)
...

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms