Monitoring Oracle SOA Suite 11g - Oracle SOA Suite 11g Administrator's Topic - page 105

####<Dec 28, 2011 10:08:00 PM EST> <Error> <Deployer> <soahost1> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cb680017c6a0acfe:58ce288b:13487c99be3:-8000-0000000000000002> <1325128080369> <BEA-149205> < Failed to initialize the application 'MQSeriesAdapter' due to error weblogic.application.ModuleException: The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.mq.ConnectionFactoryImpl' could not be loaded from the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory.
The soa_server1.out file is generated when you start up the managed serv-
er via Node Manager or the Oracle WebLogic Server Administration Console.
Review this log for server startup issues. For example, it may include startup in-
formation such as JVM heap and the CLASSPATH settings as well as runtime
infrastructure issues errors:
*******************************************************
** SOA specific environment is already set, skipping...
*******************************************************
.
JAVA Memory arguments: -Xms1536m -Xmx1536m -Xgcprio:throughput -XX:+HeapDumpOnOutOfMemoryError -XXtlasize:min=16k,preferred=128k,wasteLimit=8k
.
WLS Start Mode=Production
.
CLASSPATH=/u01/app/oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/user-patch.jar:/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/soa-startup.jar:...
<Jan 1, 2012 2:59:42 PM EST> <Error> <oracle.sdp.messaging.engine> <SDP-25088> <Unable to refresh the driver locator cache, due to the following error: EJB Exception: : Local Exception Stack:
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.5.0) (Build 110305)): oracle.toplink.exceptions.DatabaseException
Internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection . The DBMS driver exception was: IO Error: Socket read timed out
The soa_server1-diagnostic.log file writes entries in the Oracle Dia-
gnostic Logging (ODL) format. See the following screenshot that provides a
prototype of a log message in the ODL format. This is a text file and entries
in this file conform to an Oracle standard that includes information such as
timestamp, server name, error type, component ID, user, and other log informa-
tion. In the figure, you can see that the JMSProducer composite was deployed
successfully in 15.471 seconds.