Sunday, January 25, 2009

ESBRuntimeException: Designtime cache has not been initialized

when I click on the Instances icon on the right on the screen I get the
@ following error text box on the screen :
@ 08/07/22 11:57:33 oracle.tip.esb.infra.exception.ESBRuntimeException:
@ Designtime cache has not been initialized
@ Please look in logs for following signs of failure. Fix them and restart. (a)
@ Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors
@ (d) Product installation errors (e) Export ESB params and verify if host and
@ port parameters are correct. Please contact Oracle Support if unable to fix
@ the issue.
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.CacheManager.getInitializedInstance(CacheManager.java:3
@ 19)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.XMLConsoleManagerImpl.(XMLConsoleManagerImpl.java
@ :218)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.ConsoleManagerFactory.getConsoleManager(ConsoleManagerF
@ actory.java:57)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.configuration.servlet.command.ServiceExplorerCommand.execute(Se
@ rviceExplorerCommand.java:45)

Probable Solution :

Note: Assuming here your esb-dt container name is OC4J_ESBDT

Make sure the directory esb-dt exist in $ORACLE_HOME/j2ee/OC4J_ESBDT/application-deployments/

Check the opmn/logs/default*.log and opmn.log (in the same location) files to see if there are any ESB related
exceptions logged.

If there is a timeout issues in
$ORACLE_HOME/j2ee/OC4J_ESBDT/log/OC4J_ESBDT_ESBDT_GROUP_1/oc4j/log.xml
Then

1. Increase the value of the transaction-timeout parameter in
the $ORACLE_HOME/j2ee/OC4J_ESBDT/config/transaction-manager.xml file.
For eg: transaction-timeout="300"

2. Increase the value of the xa_timeout parameter in the
$ORACLE_HOME/integration/esb/esb_config.ini file.

For Eg:
xa_timeout=3600
jms_receive_timeout=300

3. Login into repoistory DB as system user and then issue: ALTER SYSTEM set OPEN_CURSORS=5000 scope=both;

4. Restart the ESB Server ( opmnctl stopall; opmnctl startall).




Make sure you can connect to your repository database with oraesb schema.
If the passowrd is wrong to reset it for oc4jadmin
Check /oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/system-jazn-data.xml
Refer: Note 470680.1



Check the values for the ESB_PARAMETERS and make sure the 'DT_OC4J_HTTP_PORT' and 'DT_OC4J_HOST' are correct.
This should be your loadbalancer port and host name in HA.
Also make sure other parameters are configured properly according to your type of JMS ( OracleASjms or OracleOJMS)
Refer Note:453355.1
For HA: http://download.oracle.com/docs/cd/E10291_01/core.1013/e10294/webapp.htm#CHDCFDJG


If it is running on HTTPS then refer: Note 461419.1



Make sure the ESB-DT application is running by issuing:
opmnctl status -app
For Eg: If it is running then it wil be listed like this
4513 | esb-dt | started | g_rt_id | internal-ESB | true | default


If it is not running which means the appliction is not installed properly or it is not been started.
Try to start the application:
Opmnctl startproc application=esb-dt
Remember if it is HA dont use restartproc, use startproc or stopproc.


To make it starts automatically everytime we restart the instance check these:

/oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/default-web-site.xml




/oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/server.xml


Courtesy : Thanks to Arun who wrote this note in Metalink.


After ESB Console starts and If Instances are not showingup then set TrackingEnabled=true

If you encounter following error:

Encountered following exception in log.xml
java.lang.NoClassDefFoundError: org/apache/log4j/Category))

The workaround is as follows -

Add the following line to the orion-application.xml file for esbdt


Restart the instance

0 comments: