CLASSPATH problem with Application Server 8.2

Hi!

Creator's application uses driveradapter.jar for work with DB and therefore You should add it to classpath of remote application server. You can just copy $Creator_Dir\SunAppServer8\lib\driveradapter.jar to lib directory of remote application server (SunAppServer_Dir\lib\). If it won't help try to copy driveradapter.jar and add it to classpath suffix with Admin Console.

Thanks,

Roman.

Grif at 2007-7-7 3:41:16 >

just for more info:

i did everything i found in any tutorial. there was one post somewhere that i found that said the driveradapter files and classpath links should be in the <install_dir>/lib/JDBCRESOURCES....i did that too.

this is what i have in JVM settings:

Server Classpath:

--

${com.sun.aas.installRoot}/lib/install/applications/jmsra/imqjmsra.jar

${com.sun.aas.imqLib}/jaxm-api.jar

${com.sun.aas.imqLib}/fscontext.jar

${com.sun.aas.antLib}/ant.jar

Classpath Prefix:

--

${com.sun.aas.installRoot}/lib/driveradapter.jar

${com.sun.aas.installRoot}/lib/jdbcdrivers/driveradapter.jar

Classpath Suffix:

--

${com.sun.aas.installRoot}/lib/driveradapter.jar

${com.sun.aas.installRoot}/lib/jdbcdrivers/driveradapter.jar

PLEASE HELP!!

InfoSysExperts at 2007-7-7 3:41:16 >

i did what you suggested and now i get a different error: Connection could not be allocated because: com.sun.sql.jdbc.oracle.OracleDriver

see page below:

================================================

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

com.sun.rave.web.ui.appbase.ApplicationException: javax.servlet.ServletException: java.lang.RuntimeException: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: com.sun.sql.jdbc.oracle.OracleDriver

com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.destroy(ViewHandlerImpl.java: 601)

com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.ja va:316)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87 )

com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)

com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)

javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

java.lang.reflect.Method.invoke(Method.java:585)

org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)

java.security.AccessController.doPrivileged(Native Method)

javax.security.auth.Subject.doAsPrivileged(Subject.java:517)

org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)

org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)

java.security.AccessController.doPrivileged(Native Method)

com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)

================================================

thank you so much for all your help thus far!!

InfoSysExperts at 2007-7-7 3:41:16 >

Hi,

your last stack trace looks like the app server found the driveradapter.jar, that's good.

But now it tries to use the automatically configured datasource information. But that works for Oracle only for appservers which have the license to use the Sun JDBC drivers:-( (The properties are different for the normal Oracle driver:-()

Now you have a couple of choices, I don't like any of them much:-(

* Use the normal Oracle drivers and configure your datasources by hand. Then you can give the JNDI name to Creator for the remote deployment. But, there are some bugs/limitations in the Oracle drivers which you might hit:-(

* Buy the Oracle drivers from DataDirect or i-net software. We test with the DataDirect drivers and they work as far as we know. I did some tests with the i-net drivers and I did not see any problem. But both drivers cost money and you still have to configure your datasources by hand.

* Install a complete JS Creator 2.1 on your remote system and use the bundled appserver. That bundle is licensed to use the Sun JDBC drivers. So all the automatic configuration should just work.

* Install a Sun Application Server 8.1 EE/SE (with the latest patches!!) on your remote system. Again, you get the license for the Sun JDBC drivers but you'll have to copy the driveradapter.jar.

I hope that helps.

Thanks,

-- Marco

mw46 at 2007-7-7 3:41:16 >

Thanks mw46 for the comprehensive reply.

i will try installing JSC2 on the server PC and use its bundled application server. I will also try the DataDirect driver..

could you describe what i need to do use either the JSC2 bundled server or the DataDirect driver?

but all this seems too complicated for the simple task of deploying the web applications. none of these issues are mentioned in any of the tutorials about deployment.

InfoSysExperts at 2007-7-7 3:41:16 >