ESB Server connection could not be established via Jdeveloper or using ant
595977Nov 23 2007 — edited Jun 5 2009When I try to deploy a ESB project using ant in a remote virtual linux machine
via command mode,I am getting deployment failed message as below suggesting to check whether ESB server is running.
./ant outputs the following:
Buildfile: build.xml
deployProjects:
[echo] deploying esb project files
[deployESBProjects] Deployment Failed ...Check if server at 132.146.44.93 is running
[deployESBProjects] ESB Project </data/ESB_Samples/CPL_US_001> successfully deployed
[echo] esb project files deployed
BUILD SUCCESSFUL
Total time: 0 seconds
./opmnctl status -l oututs the following:
Processes in Instance: SOA_NFT.RHEL4AS
-------------------------------------------------------------------------------------------------------+------
ias-component | process-type | pid | status | uid | mused | uptime | ports
-------------------------------------------------------------------------------------------------------+------
OC4JGroup:default_group | OC4J:home | 1051 | Alive | 1610238535 |3616 | 20:41:30 | jms:12601,http:8888,rmis:12701,rmi:12401
ASG | ASG | N/A | Down | N/A | N/A | N/A | N/A
HTTP_Server | HTTP_Server | 1050 | Alive | 1610238534 |1820 | 20:41:20 | https1:4443,http2:7200,http1:7777
---------------------------------------------------------------------------
./opmnctl status -app outputs the following:
Applications in Instance: SOA_NFT.RHEL4AS
application type: OC4J
------------------------------------------------------------------------
pid | name | state | rtid | classification | routable | parent
------------------------------------------------------------------------
1051 | hw_services | started | g_rt_id | internal-BPEL | true | orabpel
1051 | ruleauthor | started | g_rt_id | internal-Rules | true | default
1051 | system | started | g_rt_id | external | true |
1051 | WSIL-App | started | g_rt_id | internal | true | default
1051 | orainfra | started | g_rt_id | internal | true | default
1051 | datatags | started | g_rt_id | internal | true | default
1051 | orabpel | started | g_rt_id | internal-BPEL | true | default
1051 | gateway | started | g_rt_id | internal-WSM | true | default
1051 | rulehelp | started | g_rt_id | internal-Rules | true | default
1051 | ccore | started | g_rt_id | internal-WSM | true | default
1051 | policymanager | started | g_rt_id | internal-WSM | true | default
1051 | default | started | g_rt_id | external | true | system
1051 | esb-rt | started | g_rt_id | internal-ESB | true | esb-dt
1051 | ascontrol | started | g_rt_id | external | true | system
1051 | coreman | started | g_rt_id | internal-WSM | true | default
1051 | esb-dt | started | g_rt_id | internal-ESB | true | default
1051 | javasso | started | g_rt_id | internal | true | default
------------------------------------------------------------------------------
Also when I try to create Appliocation Server connection using opmn port 6003 from my local Jdeveloper,the test connection fails.
While creating Application Server connection in Jdeveloper, the connection Test succeeds when I select Standalone server and
using RMI port 12401.Maenwhile, the Integration Server connection using the above Application Server connection created and port 8888 when tested
displays
Application Server: OK
BPEL Process Manager Server: OK
ESB Server: FAILED
ESB Server failue detail: ESB connection failed.
ESB Server connection could not be established.
The SOA was installed in silent mode after resolving many issues detailed in SR 6622260.992