Topic
  • 1 reply
  • Latest Post - ‏2012-06-22T11:02:43Z by KrishnaKandi
KrishnaKandi
KrishnaKandi
12 Posts

Pinned topic Error when using "deploy configuration" of MDMWorkbench

‏2012-06-14T08:14:14Z |
Hi All,

I am facing the below exception when running the "deploy configuration" option of the MDMWorkbench.

I am using the RSA7.5.4, Oracle 11g, MDM9.02 version. Please help..

Deploy Configuration
Start operation runExternalTools
Thu Jun 14 13:29:23 GMT+05:30 2012
Buildfile: D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\build_external.xml

runExternalTools:
runExternalTools D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation
runExternalTools Config path -> D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\Log4J.properties
runExternalTools DEBUG - RunExternalToolsClientTask start server cmd -> D:/PROGRA~1/IBM/SDP75/plugins\MDMDevEnvTooling\controller/startwas.bat AppSrv02 D:\PROGRA~1\IBM\SDP75\runtimes\base_v7
runExternalTools ADMU0116I: Tool information is being logged in file
runExternalTools D:\Programfile\IBM\SDP75\runtimes\base_v7\profiles\AppSrv02\logs\server1\stopServer.log
runExternalTools ADMU0128I: Starting tool with the AppSrv02 profile
runExternalTools ADMU3100I: Reading configuration for server: server1
runExternalTools ADMU3201I: Server stop request issued. Waiting for stop status.
runExternalTools ADMU4000I: Server server1 stop completed.
runExternalTools
runExternalTools ADMU0116I: Tool information is being logged in file
runExternalTools D:\Programfile\IBM\SDP75\runtimes\base_v7\profiles\AppSrv02\logs\server1\startServer.log
runExternalTools ADMU0128I: Starting tool with the AppSrv02 profile
runExternalTools ADMU3100I: Reading configuration for server: server1
runExternalTools ADMU3200I: Server launched. Waiting for initialization status.
runExternalTools ADMU3000I: Server server1 open for e-business; process id is 2168

stopAgent:

check-cond-is-WASType-61:

runAgentWAS61Stop:

check-cond-is-WASType-70:

runAgentWAS70Stop:
echo runAgent Stop for WAS70

startAgent:

check-cond-is-WASType-61:

runAgentWAS61Start:

check-cond-is-WASType-70:

runAgentWAS70Start:
echo runAgent Start for WAS70

undeployConfiguration:
java WARN - ManagementConsole Process ID: 5928@PC183073
java
java Configuration and Management Console
java
java
java Connecting to the management agent on: localhost Port: 9999
java WARN - An IO exception occured when connecting to the MBeanServer java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect
java An error occurred during the initialization of the console session.
java Check the log for more details.
java ERROR - com.dwl.management.ManagementException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect com.dwl.management.ManagementException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect

deployConfiguration:
java WARN - ManagementConsole Process ID: 192@PC183073
java
java Configuration and Management Console
java
java
java Connecting to the management agent on: localhost Port: 9999
java WARN - An IO exception occured when connecting to the MBeanServer java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect
java An error occurred during the initialization of the console session.
java Check the log for more details.
java ERROR - com.dwl.management.ManagementException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect com.dwl.management.ManagementException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java] java.net.ConnectException: Connection refused: connect

viewApplication:
delete Deleting: D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\validateDeployConfigTask.log

stopAgent:

check-cond-is-WASType-61:

runAgentWAS61Stop:

check-cond-is-WASType-70:

runAgentWAS70Stop:
echo runAgent Stop for WAS70

BUILD FAILED
D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\common_build.xml:178: There was a problem executing the task.

Total time: 4 minutes 35 seconds
org.eclipse.core.runtime.CoreException: D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\common_build.xml:178: There was a problem executing the task.
at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(Unknown Source)
at org.eclipse.ant.core.AntRunner.run(Unknown Source)
at org.eclipse.ant.core.AntRunner.run(Unknown Source)
at com.ibm.mdm.config.common.automation.engine.AntTaskRunner.run(Unknown Source)
Caused by: D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation\common_build.xml:178: There was a problem executing the task.
at com.ibm.mdm.setup.tooling.tasks.RunExternalToolsClientTask.execute(Unknown Source)
at org.apache.tools.ant.UnknownElement.execute(Unknown Source)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(Unknown Source)
at org.apache.tools.ant.Task.perform(Unknown Source)
at org.apache.tools.ant.Target.execute(Unknown Source)
at org.apache.tools.ant.Target.performTasks(Unknown Source)
at org.apache.tools.ant.Project.executeSortedTargets(Unknown Source)
at org.apache.tools.ant.Project.executeTarget(Unknown Source)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(Unknown Source)
at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(Unknown Source)
at org.apache.tools.ant.Project.executeTargets(Unknown Source)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Unknown Source)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
... 3 more

Total time taken : 4 minutes 37 seconds
The log can be found at : D:\ABSAWS\.metadata\.plugins\com.ibm.mdm.config.external.automation/automationLog.log
Updated on 2012-06-22T11:02:43Z at 2012-06-22T11:02:43Z by KrishnaKandi
  • KrishnaKandi
    KrishnaKandi
    12 Posts

    Re: Error when using "deploy configuration" of MDMWorkbench

    ‏2012-06-22T11:02:43Z  
    this time re-tried with AIX.tar and it worked well..not sure what was the problem with linux.tar