錯誤在運行Java服務包裝器JBoss應用服務器7

我試圖使JBoss應用服務器7.1.0運行爲使用Java服務包裝服務，我已經解決了很多問題，但對於每一個我解決我得到一個新的一。目前我使用這個配置：錯誤在運行Java服務包裝器JBoss應用服務器7

# Java Application 
#wrapper.java.command=java 
wrapper.java.command=%JAVA_HOME%/bin/java.exe 


# Java Main class. This class must implement the WrapperListener interface 
# or guarantee that the WrapperManager class is initialized. Helper 
# classes are provided to do this for you. See the Integration section 
# of the documentation for details. 
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp 

# Java Classpath (include wrapper.jar) Add class path elements as 
# needed starting from 1 
wrapper.java.classpath.1=%OG_HOME%/bin/wrapper-3.2.3.jar 
wrapper.java.classpath.2=%JBOSS_HOME%/modules/org/jboss/as/server/main/jboss-as-server-7.1.0.Final.jar 
wrapper.java.classpath.3=%JBOSS_HOME%/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar 
wrapper.java.classpath.4=%JBOSS_HOME%/modules/org/jboss/stdio/main/jboss-stdio-1.0.1.GA.jar 
wrapper.java.classpath.5=%JBOSS_HOME%/modules/org/jboss/as/controller/main/jboss-as-controller-7.1.0.Final.jar 
wrapper.java.classpath.6=%JBOSS_HOME%/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar 
wrapper.java.classpath.7=%JBOSS_HOME%/modules/org/apache/log4j/main/log4j-1.2.16.jar 
wrapper.java.classpath.8=%JBOSS_HOME%/jboss-modules.jar 


#wrapper.java.classpath.2=%JAVA_HOME%/lib/tools.jar 
#wrapper.java.classpath.3=%JBOSS_HOME%/bin/run.jar 

# used to avoid problems with quotes inside the PATH environment variable 
wrapper.java.library.path.append_system_path=TRUE 

# Java Library Path (location of Wrapper.DLL or libwrapper.so) 
wrapper.java.library.path.1=%OG_HOME%bin 
wrapper.java.library.path.2=%JBOSS_HOME%\lib 

# these are the JAVA_OPTS 
wrapper.java.additional.1=-XX:MaxPermSize=512m 
wrapper.java.additional.2=-Dorg.jboss.resolver.warning=true 
wrapper.java.additional.3=-Dsun.rmi.dgc.client.gcInterval=3600000 
wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000 
wrapper.java.additional.5=-Djboss.modules.system.pkgs=org.jboss.byteman 
wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false 
wrapper.java.additional.7=-Dlogging.configuration=file:%JBOSS_HOME%/standalone/configuration/logging.properties 
wrapper.java.additional.8=-Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl 
wrapper.java.additional.9-Djboss.server.default.config=standalone-full-ACE2.xml 

#wrapper.java.additional.1=-Dprogram.name=standalone.bat 

# Initial Java Heap Size (in MB) 
wrapper.java.initmemory=64 

# Maximum Java Heap Size (in MB) 
wrapper.java.maxmemory=512 

# Location of OG log folder 
wrapper.app.parameter.1=org.jboss.modules.Main 
wrapper.app.parameter.2=%JBOSS_HOME%\jboss-modules.jar 
wrapper.app.parameter.3=-mp 
wrapper.app.parameter.4=%JBOSS_HOME%\modules 
wrapper.app.parameter.5=-jaxpmodule 
wrapper.app.parameter.6=javax.xml.jaxp-provider 
wrapper.app.parameter.7=org.jboss.as.standalone 
wrapper.app.parameter.8=-Djboss.home.dir=%JBOSS_HOME% 
# Data source definitions are needed for the wait for DB Service 


#******************************************************************** 
# Wrapper Logging Properties 
#******************************************************************** 
# Format of output for the console. (See docs for formats) 
wrapper.console.format=PM 

# Log Level for console output. (See docs for log levels) 
wrapper.console.loglevel=DEBUG 

# wrapper log location 
wrapper.logfile=%OG_HOME%/log/ace2_wrapper.log 

# Format of output for the log file. (See docs for formats) 
wrapper.logfile.format=LPTM 

# Log Level for log file output. (See docs for log levels) 
wrapper.logfile.loglevel=DEBUG 

# Maximum size that the log file will be allowed to grow to before 
# the log is rolled. Size is specified in bytes. The default value 
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or 
# 'm' (mb) suffix. For example: 10m = 10 megabytes. 
wrapper.logfile.maxsize=10mb 

# Maximum number of rolled log files which will be allowed before old 
# files are deleted. The default value of 0 implies no limit. 
wrapper.logfile.maxfiles=10 

# Log Level for sys/event log output. (See docs for log levels) 
wrapper.syslog.loglevel=NONE 

#******************************************************************** 
# Wrapper Windows Properties 
#******************************************************************** 
# Title to use when running as a console 
wrapper.console.title=ACE2 on JBOSS Service Wrapper console 

#******************************************************************** 
# Wrapper Windows NT/2000/XP Service Properties 
#******************************************************************** 
# WARNING - Do not modify any of these properties when an application 
# using this configuration file has been installed as a service. 
# Please uninstall the service before modifying this section. The 
# service can then be reinstalled. 

# Name of the service 
wrapper.ntservice.name=JbossServiceForACE2 

# Display name of the service 
wrapper.ntservice.displayname=Oblicore - ACE2 on JBOSS Application Server 

# Description of the service 
wrapper.ntservice.description=JEE Application Server Running ACE2 Manager 

# Mode in which the service is installed. AUTO_START or DEMAND_START 
wrapper.ntservice.starttype=AUTO_START 

# Allow the service to interact with the desktop. 
wrapper.ntservice.interactive=false

但在運行它時我得到這個錯誤：

STATUS | wrapper | 2012/03/12 14:26:31 | --> Wrapper Started as Console 
DEBUG | wrapper | 2012/03/12 14:26:31 | Using tick timer. 
DEBUG | wrapperp | 2012/03/12 14:26:32 | server listening on port 32000. 
STATUS | wrapper | 2012/03/12 14:26:32 | Launching a JVM... 
DEBUG | wrapper | 2012/03/12 14:26:32 | command: "C:\Program Files\Java\jdk1.6.0_17\bin\java.exe" -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false -Dlogging.configuration=file:C:\jboss-as-7.1.0.Final/standalone/configuration/logging.properties -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -Xms64m -Xmx512m -Djava.library.path="C:\Program Files\CA\Cloud Insight\bin;C:\jboss-as-7.1.0.Final\lib;C:\Program Files\CA\SC\CAWIN\;C:\Program Files\Java\jdk1.6.0_17\bin;C:\oracle\product\11.1.0\db_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\CA\DSM\bin;C:\PROGRA~1\CA\SC\CAM\bin;C:\Program Files\CA\Cloud Insight\bin" -classpath "C:\Program Files\CA\Cloud Insight\/bin/wrapper-3.2.3.jar;C:/jboss-as-7.1.0.Final/modules/org/jboss/as/server/main/jboss-as-server-7.1.0.Final.jar;C:/jboss-as-7.1.0.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar;C:/jboss-as-7.1.0.Final/modules/org/jboss/stdio/main/jboss-stdio-1.0.1.GA.jar;C:/jboss-as-7.1.0.Final/modules/org/jboss/as/controller/main/jboss-as-controller-7.1.0.Final.jar;C:/jboss-as-7.1.0.Final/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar;C:/jboss-as-7.1.0.Final/modules/org/apache/log4j/main/log4j-1.2.16.jar;C:/jboss-as-7.1.0.Final/jboss-modules.jar" -Dwrapper.key="0wwz4AsNMPAgFGNc" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=3324 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.modules.Main C:\jboss-as-7.1.0.Final\jboss-modules.jar -mp C:\jboss-as-7.1.0.Final\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\jboss-as-7.1.0.Final 
DEBUG | wrapper | 2012/03/12 14:26:32 | JVM started (PID=5612) 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperManager class initialized by thread: main Using classloader: [email protected] 
INFO | jvm 1 | 2012/03/12 14:26:32 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 
INFO | jvm 1 | 2012/03/12 14:26:32 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 
INFO | jvm 1 | 2012/03/12 14:26:32 | 
INFO | jvm 1 | 2012/03/12 14:26:32 | Wrapper Manager: JVM #1 
INFO | jvm 1 | 2012/03/12 14:26:32 | Running a 32-bit JVM. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Wrapper Manager: Registering shutdown hook 
INFO | jvm 1 | 2012/03/12 14:26:32 | Wrapper Manager: Using wrapper 
INFO | jvm 1 | 2012/03/12 14:26:32 | Load native library. One or more attempts may fail if platform specific libraries do not exist. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Loading native library failed: wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path 
INFO | jvm 1 | 2012/03/12 14:26:32 | Loaded native library: wrapper.dll 
INFO | jvm 1 | 2012/03/12 14:26:32 | Calling native initialization method. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Initializing WrapperManager native library. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Java Executable: C:\Program Files\Java\jdk1.6.0_17\bin\java.exe 
INFO | jvm 1 | 2012/03/12 14:26:32 | Windows version: 6.0.6002 
INFO | jvm 1 | 2012/03/12 14:26:32 | Java Version : 1.6.0_17-b04 Java HotSpot(TM) Client VM 
INFO | jvm 1 | 2012/03/12 14:26:32 | Java VM Vendor : Sun Microsystems Inc. 
INFO | jvm 1 | 2012/03/12 14:26:32 | 
INFO | jvm 1 | 2012/03/12 14:26:32 | Control event monitor thread started. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Startup runner thread started. 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperManager.start([email protected], args["C:\jboss-as-7.1.0.Final\jboss-modules.jar", "-mp", "C:\jboss-as-7.1.0.Final\modules", "-jaxpmodule", "javax.xml.jaxp-provider", "org.jboss.as.standalone", "-Djboss.home.dir=C:\jboss-as-7.1.0.Final"]) called by thread: main 
INFO | jvm 1 | 2012/03/12 14:26:32 | Communications runner thread started. 
INFO | jvm 1 | 2012/03/12 14:26:32 | Open socket to wrapper...Wrapper-Connection 
INFO | jvm 1 | 2012/03/12 14:26:32 | Opened Socket from 31000 to 32000 
INFO | jvm 1 | 2012/03/12 14:26:32 | Send a packet KEY : 0wwz4AsNMPAgFGNc 
INFO | jvm 1 | 2012/03/12 14:26:32 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) 
DEBUG | wrapperp | 2012/03/12 14:26:32 | accepted a socket from 127.0.0.1 on port 31000 
DEBUG | wrapperp | 2012/03/12 14:26:32 | read a packet KEY : 0wwz4AsNMPAgFGNc 
DEBUG | wrapper | 2012/03/12 14:26:32 | Got key from JVM: 0wwz4AsNMPAgFGNc 
DEBUG | wrapperp | 2012/03/12 14:26:32 | send a packet LOW_LOG_LEVEL : 1 
DEBUG | wrapperp | 2012/03/12 14:26:32 | send a packet PING_TIMEOUT : 30 
DEBUG | wrapperp | 2012/03/12 14:26:32 | send a packet PROPERTIES : (Property Values) 
DEBUG | wrapper | 2012/03/12 14:26:32 | Start Application. 
DEBUG | wrapperp | 2012/03/12 14:26:32 | send a packet START : start 
INFO | jvm 1 | 2012/03/12 14:26:32 | Received a packet LOW_LOG_LEVEL : 1 
INFO | jvm 1 | 2012/03/12 14:26:32 | Wrapper Manager: LowLogLevel from Wrapper is 1 
INFO | jvm 1 | 2012/03/12 14:26:32 | Received a packet PING_TIMEOUT : 30 
INFO | jvm 1 | 2012/03/12 14:26:32 | PingTimeout from Wrapper is 30000 
INFO | jvm 1 | 2012/03/12 14:26:32 | Received a packet PROPERTIES : (Property Values) 
INFO | jvm 1 | 2012/03/12 14:26:32 | Received a packet START : start 
INFO | jvm 1 | 2012/03/12 14:26:32 | calling WrapperListener.start() 
INFO | jvm 1 | 2012/03/12 14:26:32 | Waiting for WrapperListener.start runner thread to complete. 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperListener.start runner thread started. 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperSimpleApp: invoking main method 
INFO | jvm 1 | 2012/03/12 14:26:32 | 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperSimpleApp: Encountered an error running main: java.lang.IllegalArgumentException: Slot has invalid characters or is empty 
INFO | jvm 1 | 2012/03/12 14:26:32 | java.lang.IllegalArgumentException: Slot has invalid characters or is empty 
INFO | jvm 1 | 2012/03/12 14:26:32 | at org.jboss.modules.ModuleIdentifier.fromString(ModuleIdentifier.java:180) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at org.jboss.modules.Main.main(Main.java:253) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at java.lang.reflect.Method.invoke(Method.java:597) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240) 
INFO | jvm 1 | 2012/03/12 14:26:32 | at java.lang.Thread.run(Thread.java:619) 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperSimpleApp: start(args) end. Main Completed=true, exitCode=1 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperListener.start runner thread stopped. 
INFO | jvm 1 | 2012/03/12 14:26:32 | returned from WrapperListener.start() 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperListener.start() returned an exit code of 1. 
INFO | jvm 1 | 2012/03/12 14:26:32 | WrapperManager.stop(1) called by thread: Wrapper-Connection 
INFO | jvm 1 | 2012/03/12 14:26:32 | Send a packet STOP : 1 
DEBUG | wrapperp | 2012/03/12 14:26:32 | read a packet STOP : 1 
DEBUG | wrapper | 2012/03/12 14:26:32 | JVM requested a shutdown. (1) 
DEBUG | wrapper | 2012/03/12 14:26:32 | wrapperStopProcess(1) called. 
DEBUG | wrapper | 2012/03/12 14:26:32 | Sending stop signal to JVM 
DEBUG | wrapperp | 2012/03/12 14:26:32 | send a packet STOP : NULL 
INFO | jvm 1 | 2012/03/12 14:26:33 | Thread, Wrapper-Connection, handling the shutdown process. 
INFO | jvm 1 | 2012/03/12 14:26:33 | shutdownJVM(1) Thread:Wrapper-Connection 
INFO | jvm 1 | 2012/03/12 14:26:33 | Send a packet STOPPED : 1 
DEBUG | wrapperp | 2012/03/12 14:26:33 | read a packet STOPPED : 1 
DEBUG | wrapper | 2012/03/12 14:26:33 | JVM signalled that it was stopped. 
INFO | jvm 1 | 2012/03/12 14:26:33 | Closing socket. 
DEBUG | wrapperp | 2012/03/12 14:26:33 | socket read no code (closed?). 
DEBUG | wrapperp | 2012/03/12 14:26:33 | server listening on port 32002. 
INFO | jvm 1 | 2012/03/12 14:26:34 | calling System.exit(1) 
DEBUG | wrapper | 2012/03/12 14:26:34 | JVM process exited with a code of 1, however the wrapper exit code was already 1. 
DEBUG | wrapper | 2012/03/12 14:26:34 | JVM exited normally. 
STATUS | wrapper | 2012/03/12 14:26:34 | <-- Wrapper Stopped

找不到網頁:(

UPDATE上的任何內容：多虧了回答下面我能解決這個問題，但現在我得到一個新的錯誤，我認爲，這與OCI-JDBC驅動程序有關：

INFO | jvm 1 | 2012/03/13 11:07:54 | 11:07:53,933 WARN 

[org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: javax.resource.ResourceException: Could not create connection 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:277) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:235) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:758) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.fillToMin(SemaphoreArrayListManagedConnectionPool.java:703) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/13 11:07:54 | at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17] 

INFO | jvm 1 | 2012/03/13 11:07:54 | Caused by: java.lang.UnsatisfiedLinkError: oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber(Native Method) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3552) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_17] 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CConnection.loadNativeLibrary(T2CConnection.java:3547) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:266) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:162) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) 
INFO | jvm 1 | 2012/03/13 11:07:54 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:249) 
INFO | jvm 1 | 2012/03/13 11:07:54 | ... 5 more 
INFO | jvm 1 | 2012/03/13 11:07:54 |

我在網上看到一些線程說可能驅動程序版本不是最新的，但我不知道他們是否指的是DLL或jar？

[更新]：

我使用「wrapper.java.library.path補充說：」 Oracle驅動程序路徑，它解決了這個錯誤，但當然我現在得到一個新問題：

INFO | jvm 1 | 2012/03/14 10:51:38 | 10:51:38,468 WARN 

[org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: javax.resource.ResourceException: Could not create connection 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:277) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:235) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:758) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.fillToMin(SemaphoreArrayListManagedConnectionPool.java:703) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97) [ironjacamar-core-impl-1.0.7.Final.jar:1.0.7.Final] 
INFO | jvm 1 | 2012/03/14 10:51:38 | at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17] 
INFO | jvm 1 | 2012/03/14 10:51:38 | Caused by: java.sql.SQLException: Internal Error: Fetch error message failed! 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:751) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:414) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:162) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) 
INFO | jvm 1 | 2012/03/14 10:51:38 | at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:249) 
INFO | jvm 1 | 2012/03/14 10:51:38 | ... 5 more 
INFO | jvm 1 | 2012/03/14 10:51:38 |

此外，在日誌的末尾我看到這一點：

DEBUG | wrapperp | 2012/03/14 10:51:42 | send a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:42 | Received a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:42 | Send a packet PING : ok 
DEBUG | wrapperp | 2012/03/14 10:51:42 | read a packet PING : ok 
DEBUG | wrapper | 2012/03/14 10:51:42 | Got ping response from JVM 
DEBUG | wrapperp | 2012/03/14 10:51:47 | send a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:47 | Received a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:47 | Send a packet PING : ok 
DEBUG | wrapperp | 2012/03/14 10:51:47 | read a packet PING : ok 
DEBUG | wrapper | 2012/03/14 10:51:47 | Got ping response from JVM 
DEBUG | wrapperp | 2012/03/14 10:51:51 | send a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:51 | Received a packet PING : ping 
INFO | jvm 1 | 2012/03/14 10:51:51 | Send a packet PING : ok 
DEBUG | wrapperp | 2012/03/14 10:51:51 | read a packet PING : ok 
DEBUG | wrapper | 2012/03/14 10:51:51 | Got ping response from JVM

，是它讓事情這樣的，直到我停止批...

來源

2012-03-12 Tomer

我不知道這張貼回答，因爲它被問3次，但我會做到這一點就這一個:-)

首先是類路徑的不看的權利。這些log4j庫都不應該在你的類路徑中。事實上，在將來的版本中，這些將會消失，並將指向jboss-modules中的不同庫。服務器類路徑應該由jboss-modules弄清楚。

而且不需要此位-Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl並可能導致出現問題。

你在哪裏想出這個配置BTW？

來源

2012-03-12 17:52:16

[從這裏來的：Problems using java service wrapper with jboss 7]

請看一看wrapper.app.parameter.2：

wrapper.app.parameter.2=%JBOSS_HOME%\jboss-modules.jar

我認爲這打亂了參數解析，導致一個IllegalArgumentException。因此，請刪除此行並重試。

此外，作爲詹姆斯·帕金斯已經指出，org.jboss.logging.Logger.pluginClass不應設置。你的類路徑也可能沒有必要，或者甚至是一個壞主意，將log4j庫設置到類路徑中（使用Jboss）。

最後，以下屬性也需要注意：

wrapper.java.additional.9-Djboss.server.default.config=standalone-full-ACE2.xml

請注意失蹤等號。

歡呼聲中，這個問題後

編輯被編輯：

這是造成的，因爲本機庫未發現異常。推測你的ocijdbc DLL。該文件位於何處？您可以配置位置，JVM將使用wrapper.java.library.path property查找本地（jni）庫。

目前，以下位置指定：

wrapper.java.library.path.1=%OG_HOME%bin wrapper.java.library.path.2=%JBOSS_HOME%\lib

path.1看起來有點可疑，因爲沒有文件分隔符（「\」），就像它是path.2或任何地方OG_HOME被用於conf文件...

希望這可以幫助你。

嗨，包裝是每5秒默認ping JVM，這是一個完全正常的操作。這也只會在調試模式下顯示在您的日誌文件中。一旦切換到另一個日誌級別，它不應該出現在日誌文件中。你沒有安裝什麼服務意義？一旦你的JBoss AS在控制檯上運行良好，你就可以利用安裝-App.bat文件或運行安裝它作爲服務：

.\wrapper.exe -i ..\conf\wrapper.conf

希望這可以幫助你。

歡呼聲，

來源

2012-03-13 06:22:06 Naytzyrhc

謝謝兩位非常多，不幸的是我不能標記2分的答案是正確的，因此第一個獲得信用:)。我用我得到的一個新錯誤更新了這個問題。 – Tomer 2012-03-13 09:45:34

再次感謝您的時間，％OG_HOME％是我們在應用程序中使用，其中包含所有類型的驅動程序和東西它的本地環境變量以「\」不小心被定義，這就是爲什麼我沒有把一個在定義（我會稍後改變它）。如你所說，它似乎工作，但當然，現在我得到一個新的錯誤（我編輯的問題）我已經添加了Oracle驅動程序路徑。 – Tomer 2012-03-14 08:57:34

嗨，我不確定內部錯誤，發生在您的jdbc驅動程序。但假設您的jdbc驅動程序版本與您的oracle數據庫版本不兼容....您可以嘗試另一個jdbc驅動程序嗎？ – Naytzyrhc 2012-03-15 02:06:34

錯誤在運行Java服務包裝器JBoss應用服務器7

回答

相關問題