weblogic11 启动报错：weblogic.transaction.internal.TimedOutException
麻烦大家积极帮忙解决，将非常感激！
启动时，打印的报错信息如下，日志信息多，请大家看完了：
starting weblogic with Java version:
java version "1.6.0"
Starting WLS with line:
/usr/java6_64/bin/java -Xms1024m -Xmx2048m -da -Dplatform.home=/software/bea11g/wlserver_10.3 -Dwls.home=/software/bea11g/wlserver_10.3/server -Dweblogic.home=/software/bea11g/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/software/bea11g/patch_wls1033/profiles/default/sysext_manifest_classpath -Dweblogic.Name=150.18.31.50 -Djava.security.policy=/software/bea11g/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<May 25, 2012 3:27:39 PM GMT+08:00> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with IBM J9 VM Version 2.4 from IBM Corporation>
<May 25, 2012 3:27:39 PM GMT+08:00> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<May 25, 2012 3:27:41 PM GMT+08:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<May 25, 2012 3:27:41 PM GMT+08:00> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<May 25, 2012 3:27:41 PM GMT+08:00> <Notice> <LoggingService> <BEA-320400> <The log file /software/gg_dir/domain/servers/150.18.31.50/logs/150.18.31.50.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<May 25, 2012 3:27:41 PM GMT+08:00> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /software/gg_dir/domain/servers/150.18.31.50/logs/150.18.31.50.log02334. Log messages will continue to be logged in /software/gg_dir/domain/servers/150.18.31.50/logs/150.18.31.50.log.>
<May 25, 2012 3:27:41 PM GMT+08:00> <Notice> <Log Management> <BEA-170019> <The server log file /software/gg_dir/domain/servers/150.18.31.50/logs/150.18.31.50.log is opened. All server side log events will be written to this file.>
<May 25, 2012 3:27:44 PM GMT+08:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm ggRealm.>
<May 25, 2012 3:27:46 PM GMT+08:00> <Notice> <LoggingService> <BEA-320400> <The log file /software/gg_dir/domain/servers/150.18.31.50/logs/access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<May 25, 2012 3:27:46 PM GMT+08:00> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /software/gg_dir/domain/servers/150.18.31.50/logs/access.log00008. Log messages will continue to be logged in /software/gg_dir/domain/servers/150.18.31.50/logs/access.log.>
<May 25, 2012 3:27:46 PM GMT+08:00> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>
<May 25, 2012 3:27:47 PM GMT+08:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<May 25, 2012 3:27:47 PM GMT+08:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<May 25, 2012 3:27:55 PM GMT+08:00> <Warning> <EJB> <BEA-010099> <WARNING(S) from EJB QL Compiler.
Query:
EJB Name: GroupBean
Method Name: findByGroupBean_bb5s68__WebLogic_CMP_RDBMS_accounts__WL_
Parameter Types: ()
SELECT OBJECT(bean.accounts ) FROM GroupBean AS bean
Warning: [EJB:013094]The SELECT clause of this query contains an identifier 'bean.accounts' that ends in a cmr-field. The EJB 2.1 specification section 11.2.7.1 requires that any related null objects belonging to the set corresponding to this cmr-field must be returned by this query however the database that will be used to execute this query does not sufficiently support SQL outer joins, therefore this query will not return any null objects that might otherwise be returned.
>
<May 25, 2012 3:27:55 PM GMT+08:00> <Warning> <EJB> <BEA-010099> <WARNING(S) from EJB QL Compiler.
Query:
EJB Name: AccountBean
Method Name: findByAccountBean_2lqacg__WebLogic_CMP_RDBMS_groups__WL_
Parameter Types: ()
SELECT OBJECT(bean.groups ) FROM Account AS bean
Warning: [EJB:013094]The SELECT clause of this query contains an identifier 'bean.groups' that ends in a cmr-field. The EJB 2.1 specification section 11.2.7.1 requires that any related null objects belonging to the set corresponding to this cmr-field must be returned by this query however the database that will be used to execute this query does not sufficiently support SQL outer joins, therefore this query will not return any null objects that might otherwise be returned.
>
<May 25, 2012 3:29:11 PM GMT+08:00> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'gdsc-server'.
weblogic.transaction.internal.TimedOutException: Transaction timed out after 63 seconds
BEA1-001477C7941A9B86F83E
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
Truncated. see log file for complete stacktrace
Caused By: weblogic.transaction.internal.TimedOutException: Transaction timed out after 63 seconds
BEA1-001477C7941A9B86F83E
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
Truncated. see log file for complete stacktrace
>
[解决办法]
问题本人已经解决，没人回答我的帖子，只好自己送自己了
