Question about eclipse plugin for Geronimo with jetty
Hi, I find the jetty option cannot be selected when installing Geronimo 1.1 plugin in eclipse, and it fails to deploy servlet in the container. Is this still a limitation of the current plugin distribution? Or something wrong with my code. Cheers, Dong
Re: PLEASE: where does one specify additional libraries?
Are you trying to use the version of Axis bundled with Geronimo, or a separate version that you supply yourself? Thanks, Aaron On 11/28/06, Michael Moser <[EMAIL PROTECTED]> wrote: I am trying since days to get an application running on Geronimo. This application - big deal one would think - is using the axis library. When I try to start it I always get the following error: - org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The type org.apache.axis.AxisFault cannot be resolved. It is indirectly referenced from required .class files org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409) org.apache.jasper.compiler.Compiler.compile(Compiler.java:297) org.apache.jasper.compiler.Compiler.compile(Compiler.java:276) org.apache.jasper.compiler.Compiler.compile(Compiler.java:264) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) - So - apparently - the axis.jar (the one that contains the class org.apache.axis.AxisFault) is not on the classpath when the JSPs are compiled. Where does one specify these libraries so that compilation succeeds? The geronimo docs are suspiciously silent on this? Is this such an obvious thing? Not for me, I have to admit... Michael
PLEASE: where does one specify additional libraries?
I am trying since days to get an application running on Geronimo. This application - big deal one would think - is using the axis library. When I try to start it I always get the following error: - org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The type org.apache.axis.AxisFault cannot be resolved. It is indirectly referenced from required .class files org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409) org.apache.jasper.compiler.Compiler.compile(Compiler.java:297) org.apache.jasper.compiler.Compiler.compile(Compiler.java:276) org.apache.jasper.compiler.Compiler.compile(Compiler.java:264) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) - So - apparently - the axis.jar (the one that contains the class org.apache.axis.AxisFault) is not on the classpath when the JSPs are compiled. Where does one specify these libraries so that compilation succeeds? The geronimo docs are suspiciously silent on this? Is this such an obvious thing? Not for me, I have to admit... Michael
Re: Rollbacks at database level throws exception in Geronimo
Hi, I am using the provided TranQL connectors for the datasource and the problem I faced seemed to be connected with the TranQL connector which seems to be setting auto commit to true. I was asked to file a JIRA on this ( http://issues.apache.org/jira/browse/GERONIMO-2576). There have been not any responses to that and I also could not make any headway into the issue so far. Thanks and regards, Vimalan On 11/28/06, Meenakshi <[EMAIL PROTECTED]> wrote: Hi Arunanthisivam, Were you able to debug the problem? I am also facing a similar error wherein I have set autocommit to false in the application and I am using DB2 9.1 universal JDBC drivers...and I get the same error..as below: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. at com.ibm.db2.jcc.c.p.rollback(p.java:752) at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions (WSRdbManagedConnectionImpl.java:3663) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup (WSRdbManagedConnectionImpl.java:3143) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:475) at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java :2237) at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion (LocalTransactionWrapper.java:1228) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations (LocalTranCoordImpl.java:1488) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup (LocalTranCoordImpl.java:1196) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end (LocalTranCoordImpl.java:1301) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:343) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke (TransactionControlImpl.java:581) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3876) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3698) at com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1 . start(Unknown Source) at com.ibm.websphere.startupservice._AppStartUp_Stub.start (_AppStartUp_Stub.java:252) at com.ibm.ws.startupservice.StartBeanInfo.start (StartBeanInfo.java:287) at com.ibm.ws.startupservice.StartUpModule.appStart (StartUpModule.java:152) at com.ibm.ws.startupservice.StartUpApplication.start (StartUpApplication.java:105) at com.ibm.ws.startupservice.StartUpService.stateChanged (StartUpService.java:461) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1247) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent (DeployedApplicationImpl.java:1112) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:232) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:227) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start (DeployedApplicationImpl.java:826) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication (ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run (ApplicationMgrImpl.java:2114) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run (WsComponentImpl.java:340) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) Please let me know if you got the solution to the problem. Thanks, Meenakshi
Re: Rollbacks at database level throws exception in Geronimo
Hi Arunanthisivam, Were you able to debug the problem? I am also facing a similar error wherein I have set autocommit to false in the application and I am using DB2 9.1 universal JDBC drivers...and I get the same error..as below: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. at com.ibm.db2.jcc.c.p.rollback(p.java:752) at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions (WSRdbManagedConnectionImpl.java:3663) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup (WSRdbManagedConnectionImpl.java:3143) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:475) at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:2237) at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion (LocalTransactionWrapper.java:1228) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations (LocalTranCoordImpl.java:1488) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup (LocalTranCoordImpl.java:1196) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end (LocalTranCoordImpl.java:1301) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:343) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke (TransactionControlImpl.java:581) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3876) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3698) at com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1. start(Unknown Source) at com.ibm.websphere.startupservice._AppStartUp_Stub.start (_AppStartUp_Stub.java:252) at com.ibm.ws.startupservice.StartBeanInfo.start (StartBeanInfo.java:287) at com.ibm.ws.startupservice.StartUpModule.appStart (StartUpModule.java:152) at com.ibm.ws.startupservice.StartUpApplication.start (StartUpApplication.java:105) at com.ibm.ws.startupservice.StartUpService.stateChanged (StartUpService.java:461) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1247) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent (DeployedApplicationImpl.java:1112) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:232) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:227) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start (DeployedApplicationImpl.java:826) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication (ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run (ApplicationMgrImpl.java:2114) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run (WsComponentImpl.java:340) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) Please let me know if you got the solution to the problem. Thanks, Meenakshi