JBoss启动时出问题了 求教高手
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\Jbossnoejb
JAVA: D:\Jbossnoejb\jdk1.5\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: D:\Jbossnoejb\jdk1.5\lib\tools.jar;D:\Jbossnoejb\bin\run.jar
===============================================================================
05:20:18,892 INFO [Server] Starting JBoss (MX MicroKernel)...
05:20:18,892 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
JBoss_4_2_3_GA date=200807181417)
05:20:18,892 INFO [Server] Home Dir: D:\Jbossnoejb
05:20:18,892 INFO [Server] Home URL: file:/D:/Jbossnoejb/
05:20:18,892 INFO [Server] Patch URL: null
05:20:18,892 INFO [Server] Server Name: default
05:20:18,892 INFO [Server] Server Home Dir: D:\Jbossnoejb\server\default
05:20:18,892 INFO [Server] Server Home URL: file:/D:/Jbossnoejb/server/default/
05:20:18,892 INFO [Server] Server Log Dir: D:\Jbossnoejb\server\default\log
05:20:18,892 INFO [Server] Server Temp Dir: D:\Jbossnoejb\server\default\tmp
05:20:18,892 INFO [Server] Root Deployment Filename: jboss-service.xml
05:20:19,220 INFO [ServerInfo] Java version: 1.5.0_03,Sun Microsystems Inc.
05:20:19,235 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_03-b07
,Sun Microsystems Inc.
05:20:19,235 INFO [ServerInfo] OS-System: Windows NT (unknown) 6.1,x86
05:20:19,781 INFO [Server] Core system initialized
05:20:22,324 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
05:20:22,324 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
05:20:22,932 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
05:20:22,932 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
05:20:23,198 INFO [TransactionManagerService] Starting recovery manager
05:20:23,385 INFO [TransactionManagerService] Recovery manager started
05:20:23,385 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
05:20:24,586 WARN [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.List
ener_2] Listener - IOException
05:20:24,602 WARN [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.List
ener_2] Listener - IOException
之后就一直出现这个 不报错 也不停止
[解决办法]
struct i2c_adapter *phy_adap = NULL;
EXPORT_SYMBOL_GPL(phy_adap);
static u32
i2c_dw_scl_hcnt(u32 ic_clk, u32 tSYMBOL, u32 tf, int cond, int offset)
{
/*
* DesignWare I2C core doesn't seem to have solid strategy to meet
* the tHD;STA timing spec. Configuring _HCNT based on tHIGH spec
* will result in violation of the tHD;STA spec.
*/
if (cond)
/*
* Conditional expression:
*
* IC_[FS]S_SCL_HCNT + (1+4+3) >= IC_CLK * tHIGH
*
* This is based on the DW manuals, and represents an ideal
* configuration. The resulting I2C bus speed will be
* faster than any of the others.
*
* If your hardware is free from tHD;STA issue, try this one.
*/
return (ic_clk * tSYMBOL + 5000) / 10000 - 8 + offset;
else
/*
* Conditional expression:
*
* IC_[FS]S_SCL_HCNT + 3 >= IC_CLK * (tHD;STA + tf)
*
* This is just experimental rule; the tHD;STA period turned
* out to be proportinal to (_HCNT + 3). With this setting,
* we could meet both tHIGH and tHD;STA timing specs.
*
* If unsure, you'd better to take this alternative.
*
* The reason why we need to take into account "tf" here,
* is the same as described in i2c_dw_scl_lcnt().
*/
return (ic_clk * (tSYMBOL + tf) + 5000) / 10000 - 3 + offset;
}
