The BPEL Admin/Console And ESB Control URLs Can be Logged Into, But No Data Is Visible (Doc ID 739680.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle ESB - Version 10.1.3.1 to 10.1.3.3.1 [Release AS10gR3]
Oracle(R) BPEL Process Manager - Version 10.1.3.1 to 10.1.3.5.0
Information in this document applies to any platform.
Checked for relevance on 14-June-2010
***Checked for relevance on 12-Dec-2011***
***Checked for relevance on 21-June-2013***

Symptoms

The system has been running fine and BPEL and ESB data is normally accessible from the normal URLs, but without any changes to BPEL or ESB, data at these URLs is no longer accessible.

The SOA suite containers with BPEL and ESB installed start up, but when accessing the following BPEL and ESB related URLs, the following errors are seen:

At the BPEL Admin URL at http://<hostname>:<port>/BPELAdmin logging in is successful, at the "BPEL Domains" tab there are no Domains visible, though it is known that Domains exist.

At the BPEL Console URL at http://<hostname>:<port>/BPELConsole logging in is successful, but the following message is output:  "No domains accessible to the user logged in."

At the ESB Control URL at http://<hostname>:<port>/ESBControl logging in is successful, but the following message is output:  "Contact Oracle Support"

Checking the ESB Designtime logfile following a system startup at $ORACLE_HOME/j2ee/<ESB Designtime container name>/log/*_group_*/oc4j, the following error is seen:

<MESSAGE>
  <HEADER>
...
    <MODULE_ID>esb.server.bootstrap</MODULE_ID>
    <THREAD_ID>10</THREAD_ID>
    <USER_ID>oracle</USER_ID>
  </HEADER>
... 
  <PAYLOAD>
    <MSG_TEXT>ESB bootstrap: Unknown error occured in constructor of ESB resource adapter</MSG_TEXT>
    <SUPPL_DETAIL><![CDATA[oracle.tip.esb.model.repository.exception.RepositoryException: Unable to get connection to Repository
Ensure repository is accessible
        at oracle.tip.esb.model.repository.database.DatabaseRepository.getConnection(DatabaseRepository.java:1228)
        at oracle.tip.esb.model.repository.database.DatabaseRepository.getESBParameters(DatabaseRepository.java:1057)
        at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.<init>(ESBBaseResourceAdapter.java:184)
        at oracle.tip.esb.server.bootstrap.DesignTimeResourceAdapter.<init>(DesignTimeResourceAdapter.java:76)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.evermind.server.connector.deployment.ConnectorArchive.createJavaBeanInstance(ConnectorArchive.java:1211)
        at com.evermind.server.connector.deployment.ConnectorArchive.startResourceAdapter(ConnectorArchive.java:922)
        at oracle.j2ee.connector.DeployedAdapter.start(DeployedAdapter.java:102)
.
.
.



Checking the opmn container logfile *_group~<BPEL/ESB Runtime container name or ESB Designtime container name>~*_group~*.log where BPEL/ESB is running in $ORACLE_HOME/opmn/logs will have the following errors:

For ESB:

08/09/25 14:59:04 Warning: Unable to set up connection factory for a resource adapter in esb-dt: Error creating a ResourceAdapter implementation class. Error creating a JavaBean of class 'oracle.tip.esb.server.bootstrap.DesignTimeResourceAdapter: javax.resource.spi.ResourceAdapterInternalException: oracle.tip.esb.model.repository.exception.RepositoryException: Unable to get connection to Repository
Ensure repository is accessible
08/09/25 14:59:07 Warning: Unable to set up connection factory for a resource adapter in esb-rt: Error creating a ResourceAdapter implementation class. Error creating a JavaBean of class 'oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter: javax.resource.spi.ResourceAdapterInternalException: oracle.tip.esb.model.repository.exception.RepositoryException: Unable to get connection to Repository
Ensure repository is accessible


For BPEL:

<2008-09-25 14:59:15,552> <INFO> <collaxa> <ConnectionFactoryImpl::init> Initialized connection factory jdbc/BPELServerDataSourceWorkflow
<2008-09-25 14:59:15,552> <INFO> <collaxa> <ConnectionFactoryImpl::init> Initialized connection factory jdbc/BPELServerDataSource
08/09/25 14:59:38 java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
08/09/25 14:59:38       at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
08/09/25 14:59:38       at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
08/09/25 14:59:38       at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:287)
08/09/25 14:59:38       at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
08/09/25 14:59:38       at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:430)
08/09/25 14:59:38       at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
08/09/25 14:59:38       at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
08/09/25 14:59:38       at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
08/09/25 14:59:38       at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:116)
08/09/25 14:59:38       at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:75)
.
.
.


08/09/25 14:59:38 ORABPEL-03001

Cannot lookup datasource type.
The process domain was unable to determine the database type.  The version table contains the vendor type for the current datasource.  The exception reported is: Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "jdbc/BPELServerDataSourceWorkflow".  The exception reported is: Io exception: The Network Adapter could not establish the connection
Please check that the machine hosting the datasource is physically connected to the network.  Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Please check that:
     + the machine hosting the datasource is physically connected to the network.
     + the connection pool properties as defined in the application server startup properties are valid.
     + the database schema for OraBPEL has been installed in the datasource.

08/09/25 14:59:38       at com.collaxa.cube.engine.adaptors.util.DataSourceSchemaUtils.getDataSourceType(DataSourceSchemaUtils.java:197)
08/09/25 14:59:38       at com.collaxa.cube.engine.adaptors.util.DataSourceSchemaUtils.getServerDataSourceType(DataSourceSchemaUtils.java:148)
08/09/25 14:59:38       at com.collaxa.cube.admin.adaptors.ServerAdaptorManager.init(ServerAdaptorManager.java:72)
08/09/25 14:59:38       at com.collaxa.cube.admin.ServerManager.__init(ServerManager.java:212)
08/09/25 14:59:38       at com.collaxa.cube.admin.ServerManager.init(ServerManager.java:120)
08/09/25 14:59:38       at com.collaxa.cube.ejb.impl.ServerBean.init(ServerBean.java:254)
.
.
.




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