Cheers,
Wai Meng
Peter Johnson wrote:Most likely you are including in WEB-INF/lib some JAR files that are already present in JBoss AS, and this is causing classloader issues. But this is just a guess because you did not provide the stack traces showing the errors.
Cheers,
Wai Meng
Peter Johnson wrote:Please post the list of JAR files, and the stack trace you are seeing. That might give us some clue. Other than that we would juts be guessing.
Cheers,
Wai Meng
Actually, I have resolved the issue by putting the jars in the "%JBOSS_HOME%server\default\lib" folder. Whether the jars are included in the WAR's "WEB-INF\lib" or not does not cause the stack trace error. Only when the jars are not included in the "%JBOSS_HOME%server\default\lib" folder does the errors come up. So based on this, I reckon that JBoss only looks up and references jar files not from the WEB-INF/lib in my War file but rather solely on the jars found in "%JBOSS_HOME%server\default\lib".
However, if i exclude the ojdbc14.jar file, the errors in the stack trace appears
Peter Johnson wrote:And you also need to correct the connection URL:
You need to replace <IPADDR> and <TNSNAME> with the values for your system.
Cheers,
Wai Meng
Jaikiran Pai wrote:
Actually, I have resolved the issue by putting the jars in the "%JBOSS_HOME%server\default\lib" folder. Whether the jars are included in the WAR's "WEB-INF\lib" or not does not cause the stack trace error. Only when the jars are not included in the "%JBOSS_HOME%server\default\lib" folder does the errors come up. So based on this, I reckon that JBoss only looks up and references jar files not from the WEB-INF/lib in my War file but rather solely on the jars found in "%JBOSS_HOME%server\default\lib".
However, if i exclude the ojdbc14.jar file, the errors in the stack trace appears
As suspected this jar is a JDBC driver jar. And a JDBC driver jar must be placed in the %JBOSS_HOME%/server/< serverName>/lib folder. See this for details.
Cheers,
Wai Meng
Peter Johnson wrote:You still need to correct the URL:
The Oracle driver does not like the URL you gave it.
Cheers,
Wai Meng
Peter Johnson wrote:Sorry, I though the you had already provided the ojdbc14.jar file and were getting the error, in which case the error means that the Oracle driver didn't like the URL.
Cheers,
Wai Meng
How do they get the deer to cross at the signs? Or to read this tiny ad?
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
|