Trouble with the oracle 11g R1 fusion middleware and OSB intall


Me like a  lot of people face this issue while using the test console of the Oracle
Service Bus 11gR1 .

I am attaching the problem description and then the solution so that it can help all others as well..

Problem :

Every time one tries to execute a business service or a proxy service you end
up getting the following message.

Error Accessing Test Configuration

“Test Console” service is not running. Contact administrator to start
this service.

In fact to add to my frustration I am unable to execute any of my proxy
services from outside clients like SOAPUI as well.

Is anyone else facing this too ??

Attached the whole log at the end below.

To provide an update on my trouble shooting

1. ) I tried to give the IntegrationAdmin and IntegrationDeployer roles
to my admin user. in fact i also tried to give it all the possible
privileges.

Result: Still the same error message.

Error Accessing Test Configuration
“Test Console” service is not running. Contact administrator to start
this service.

2.) I have already tried to change the following entry
<java:alsb-test-console-debug>true</java:alsb-test-console-debug>
in my C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\alsbdebug.xml

I am also attaching the file contents here

<java:sb-debug-logger xmlns:java=”java:com.bea.wli.debug”>

<java:alsb-stages-transform-runtime-debug>false</java:alsb-stages-transform-runtime-debug>

<java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>

<java:alsb-credential-debug>false</java:alsb-credential-debug>

<java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>

<java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>

<java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>

<java:alsb-management-debug>false</java:alsb-management-debug>

<java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>

<java:alsb-module-debug>false</java:alsb-module-debug>

<java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>

<java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>

<java:alsb-pipeline-debug>false</java:alsb-pipeline-debug>

<java:alsb-security-wss-debug>false</java:alsb-security-wss-debug>

<java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>

<java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>

<java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>

<java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>

<java:alsb-service-validation-debug>false</java:alsb-service-validation-debug>

<java:alsb-test-console-debug>true</java:alsb-test-console-debug>

<java:alsb-transports-debug>false</java:alsb-transports-debug>

<java:alsb-uddi-debug>false</java:alsb-uddi-debug>

<java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>

<java:alsb-wspolicy-repository-debug>false</java:alsb-wspolicy-repository-debug>

<java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>

<java:alsb-security-module-debug>false</java:alsb-security-module-debug>

<java:alsb-sources-debug>false</java:alsb-sources-debug>

<java:alsb-custom-resource-debug>false</java:alsb-custom-resource-debug>

<java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>

<java:alsb-throttling-debug>false</java:alsb-throttling-debug>

<java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug>

<java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug>

<java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug>

<java:alsb-debugger-debug>false</java:alsb-debugger-debug>

<java:alsb-console-debug>false</java:alsb-console-debug>

<java:alsb-result-caching-debug>false</java:alsb-result-caching-debug>

<java:alsb-bpel-debug>false</java:alsb-bpel-debug>

<java:alsb-jca-framework-adapter-debug>false</java:alsb-jca-framework-adapter-debug>

</java:sb-debug-logger>

starting weblogic with Java version:

java version “1.6.0_18”

Java(TM) SE Runtime Environment (build 1.6.0_18-b07)

Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)

Starting WLS with line:

C:\Oracle\MIDDLE~1\home11g\JDK160~1\bin\java -client -Xms256m -Xmx512m
-XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
-Dweblogic.Name=AdminServer
-Djava.security.policy=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server\lib\weblogic.policy
-Xverify:none -da
-Dplatform.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3
-Dwls.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server
-Dweblogic.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server
-Ddomain.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1
-Dcommon.components.home=C:\Oracle\MIDDLE~1\home11g\ORACLE~1
-Djrf.version=11.1.1
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger

-Djrockit.optfile=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt

-Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1

-Doracle.server.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\AdminServer

-Doracle.security.jps.config=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol
-Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml

-Digf.arisidstack.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider

-Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.oamprovider_11.1.1
-Dweblogic.jdbc.remoteEnabled=false
-Dweblogic.management.discover=true -Dwlw.iterativeDev=
-Dwlw.testConsole= -Dwlw.logErrorsToConsole=
-Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\home11g\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_oepe1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_ocp353\profiles\default\sysext_manifest_classpath
weblogic.Server

<30-Jun-2010 16:22:43 o’clock BST> <Info>
<WebLogicServer> <BEA-000377> <Starting WebLogic Server
with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems
Inc.>

<30-Jun-2010 16:22:47 o’clock BST> <Info> <Management>
<BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9
00:05:28 PDT 2010 1321401 >

<30-Jun-2010 16:22:48 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
STARTING>

<30-Jun-2010 16:22:48 o’clock BST> <Info>
<WorkManager> <BEA-002900> <Initializing self-tuning
thread pool>

<30-Jun-2010 16:22:49 o’clock BST> <Notice>
<LoggingService> <BEA-320400> <The log file
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log
will be rotated. Reopen the log file if tailing has stopped. This can
happen on some platforms like Windows.>

<30-Jun-2010 16:22:49 o’clock BST> <Notice>
<LoggingService> <BEA-320401> <The log file has been
rotated to
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log00005.
Log messages will continue to be logged in
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log.>

<30-Jun-2010 16:22:49 o’clock BST> <Notice> <Log
Management> <BEA-170019> <The server log file
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log
is opened. All server side log events will be written to this file.>

<30-Jun-2010 16:22:56 o’clock BST> <Notice> <Security>
<BEA-090082> <Security initializing using security realm
myrealm.>

<30-Jun-2010 16:22:58 o’clock BST> <Notice>
<LoggingService> <BEA-320400> <The log file
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log
will be rotated. Reopen the log file if tailing has stopped. This can
happen on some platforms like Windows.>

<30-Jun-2010 16:22:58 o’clock BST> <Notice>
<LoggingService> <BEA-320401> <The log file has been
rotated to
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log00005.
Log messages will continue to be logged in
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log.>

<30-Jun-2010 16:23:06 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
STANDBY>

<30-Jun-2010 16:23:06 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
STARTING>

<30-Jun-2010 16:23:59 o’clock BST> <Warning> <JDBC>
<BEA-001110> <No test table set up for pool
“wlsbjmsrpDataSource”. Connections will not be tested.>

<30-Jun-2010 16:23:59 o’clock BST> <Warning> <JDBC>
<BEA-001552> <The Logging Last Resource (LLR) data source
wlsbjmsrpDataSource will not function when it is a participant in a
global transaction that spans multiple WebLogic Server instances because
remote JDBC support is disabled. LLR will function in single-server
configurations.>

<30-Jun-2010 16:25:35 o’clock BST> <Alert> <OSB
Security> <BEA-387068> <There is no PKI credential mapper
provider configured in your security realm. Service key provider
management will be disabled. Configure a PKI credential mapper provider
if you need service provider support. This is typically the case if you
have Oracle Service Bus proxy services with web service security enabled
or outbound 2-way SSL connections.>

<30-Jun-2010 16:25:40 o’clock BST> <Warning>
<WliSbTransports> <BEA-381917> <MQ Transport could not be
registered due to : Missing MQ Library>

[ERROR] AdapterManager – ServletContainerAdapter manager not initialized
correctly.

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<LoggingService> <BEA-320400> <The log file
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log
will be rotated. Reopen the log file if tailing has stopped. This can
happen on some platforms like Windows.>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<LoggingService> <BEA-320401> <The log file has been
rotated to
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log00005.
Log messages will continue to be logged in
C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log.>

<30-Jun-2010 16:26:11 o’clock BST> <Notice> <Log
Management> <BEA-170027> <The Server has established
connection with the Domain level Diagnostic Service successfully.>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
ADMIN>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
RESUMING>

<30-Jun-2010 16:26:11 o’clock BST> <Notice> <Server>
<BEA-002613> <Channel “Default[1]” is now listening on
127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>

<30-Jun-2010 16:26:11 o’clock BST> <Notice> <Server>
<BEA-002613> <Channel “Default” is now listening on
10.128.2.170:7001 for protocols iiop, t3, ldap, snmp, http.>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<WebLogicServer> <BEA-000331> <Started WebLogic Admin
Server “AdminServer” for domain “OSB_domain” running in Development
Mode>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<WebLogicServer> <BEA-000365> <Server state changed to
RUNNING>

<30-Jun-2010 16:26:11 o’clock BST> <Notice>
<WebLogicServer> <BEA-000360> <Server started in RUNNING
mode>

This is really putting me off and its really disappointing to see all
these issues in this new release.

Solution:

“Test Console” service is not running. Contact administrator to start this service.

From 11g onwards
Test console will work only when OSB server is up and running (Along with admin server); and all deployments on OSB server are in active state. Make sure to check this.

In fact to add to my frustration I am unable to execute any of my proxy services from outside clients like SOAPUI as well.

Again it requires your OSB server to be up and running to access proxy services from outside. If proxy service’s URI is – “/services/exampleService” then you may access it from SOAUI using URL – “http://host:<OSB_Server_port>/services/exampleService&#8221;

By default, OSB server’s port number is 8011

What normally one does is just use the default options while creating the domain and expect it to work.

But now I have configured my domain creation and created a managed server and a node manager.

After starting my managed server I am able to run the test console.

I have attached the installation guide for OSB 11gR1 below

Installation guide OSB 11gR1

Advertisements

6 comments

  1. BEA-001552- The Logging Last Resource (LLR) data source ApplicationDB-rac1 will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.

  2. Hi,

    I have de propertie: true, Listerner Address in AdminServer is: 10.101.127.241 and restar AdminServer, osb_server1
    but error persist:
    “Test Console” service is not running. Contact administrator to start this service.

    Any Idea ?
    Thank

  3. I do not know whether it’s just me or if everyone else encountering issues with your site. It appears as though some of the text within your posts are running off the screen. Can someone else please provide feedback and let me know if this is happening to them too? This may be a problem with my browser because I’ve had this
    happen before. Appreciate it

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s