You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Hernan Cunico (JIRA)" <ji...@apache.org> on 2007/03/30 21:20:25 UTC
[jira] Created: (GERONIMO-3051) DB Viewer portlet error
DB Viewer portlet error
-----------------------
Key: GERONIMO-3051
URL: https://issues.apache.org/jira/browse/GERONIMO-3051
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console, databases
Affects Versions: 2.0-M4
Environment: embedded Derby databases
Reporter: Hernan Cunico
There is a problem when trying to view an embedded Derby database.
I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
When I check the logs I get this:
09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
...
09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
javax.servlet.ServletException
...
09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
javax.portlet.PortletException
...
With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486670 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
Well, my attempt to run with the jstl dependency in both jee-specs and in the default environment of the app didn't go very well. I was unable to initialize the gbean after deploying the app because of a strange NPE in the JspModuleBuilderExtension trying to add the GBean.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486156 ]
David Jencks commented on GERONIMO-3051:
----------------------------------------
Before any changes get committed can we verify that system-database is a parent of the app we're having problems with? the derby classes should be coming from system-database, not from including the jars directly. In any case we've seen similar problems in the past when a second copy of derby classes is loaded: this definitely is a problem with the embedded driver and possibly with the network driver.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486548 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
I had a similar problem with some other JSTL apps so I tried to apply the GERONIMO-3051-new.patch. After I applied the patch I could no longer build the config for webconsole-tomcat (and I presume webonsole-jetty though the build didn't get that far). It seems like building this car requires jstl to be at a higher level in the classpath than just in the TCCL.
Here's the build exception:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org/apache/taglibs/standard/tag/common/core/ChooseTag
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/taglibs/standard/tag/common/core/ChooseTag
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
at java.lang.Class.getDeclaredMethods(Class.java:1763)
at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:162)
at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createWebAppClassFinder(AbstractWebModuleBuilder.java:780)
at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:790)
at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:303)
at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder$$FastClassByCGLIB$$6f85ec2c.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$166ace5e.addGBeans(<generated>)
at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$166ace5e.addGBeans(<generated>)
at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:607)
at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$4d984873.buildConfiguration(<generated>)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302)
at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:668)
at org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:487)
at org.apache.geronimo.mavenplugins.car.PackageMojo.doExecute(PackageMojo.java:300)
at org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:122)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn updated GERONIMO-3051:
-------------------------------
Comment: was deleted
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487013 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
Just to make sure I wasn't going crazy I did this again this morning with the same results. I guess we need a third person to break the tie. :-)
I'm building on mac. Here are the steps I followed:
1. fresh checkout of geronimo to clean directory (not just an svn up)
2. build geronimo to ensure it builds prior to any changes ... it did
3. applied patch GERONIMO-3051-new.patch from configs directory (patch -p0 -u < GERONIMO-3051-new.patch)
4. "mvn clean install" from geronimo root (not just from within configs)
5. Build error in configs/ webconsole-tomcat
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Frank G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486937 ]
Frank G commented on GERONIMO-3051:
-----------------------------------
Hi Joe,
That's unfortunately to have these problems on your building. :-(
I did the following steps today:
1. Check out the source codes from the trunk
2. Apply GERONIMO-3051-new.patch
3. mvn clean install -Dtest=false
4. Create a database named "MyDB" and view the tables in the console
Seems everything works fine. Can you have a try with these steps or someone else can try this patch?
Hope it helps.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492126 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
I had mixed results. One test that I thought was failing earlier did work after I applied the patch (sans the tld code). However when I attempted to run all of the jstl tests I had several failures like that below. I also didn't get to change the URLs for the console yet to see if it would work properly with the new driver. I'll try that later tonight.
Here's the error on the other jstl tests:
04-26-2007 17:44:23: ERROR: [WebValidatorBase] Unexpected '500' received from target server!
Error response recieved from server:
------------------------------------------------
<html><head><title>Apache Tomcat/6.0-snapshot - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:whi
te;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-s
ize:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahom
a,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525
D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : blac
k;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Except
ion report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented i
t from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Unable to get connection, DataSo
urce invalid: "java.sql.SQLException: Could not look up datasource"
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:855)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:784)
org.apache.jsp.positiveDateParamQueryTimestampTest_jsp._jspService(positiveDateParamQueryTimestampTest_jsp.java:268)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:379)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
com.sun.ts.tests.jstl.common.filters.JstlDbFilter.doFilter(JstlDbFilter.java:109)
</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><
HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0-snapshot</h3></body></html>
04-26-2007 17:44:23: ERROR: Exception at:
04-26-2007 17:44:23: ERROR: com.sun.ts.tests.common.webclient.TestFailureException: Test FAILED!
at com.sun.ts.tests.common.webclient.WebTestCase.execute(WebTestCase.java:164)
at com.sun.ts.tests.common.webclient.BaseUrlClient.invoke(BaseUrlClient.java:389)
at com.sun.ts.tests.jstl.compat.onedotzero.JSTLClient.positiveDateParamQueryTimestampTest(JSTLClient.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.ts.lib.harness.EETest.run(EETest.java:495)
at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392)
at com.sun.ts.lib.harness.EETest.run(EETest.java:252)
at com.sun.ts.tests.jstl.compat.onedotzero.JSTLClient.run(JSTLClient.java:54)
at com.sun.ts.tests.jstl.compat.onedotzero.JSTLClient.main(JSTLClient.java:40)
04-26-2007 17:44:23: [BaseUrlClient] Test cleanup OK
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486689 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
Ok, I had something else messed up that was preventing the application from deploying. However, with the patch applied and keeping jstl included in jee-specs (for the build issue I mentioned) I still had the same "no suitable driver" issue that I was hoping this might resolve for me.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492101 ]
Paul McMahan commented on GERONIMO-3051:
----------------------------------------
I reverted rev 532106 locally and applied David Jencks' patch (minus the GeronimoTldLocationsCache portion, which I believe was included accidentally). The JSF test case works again. Thanks David.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul McMahan reopened GERONIMO-3051:
------------------------------------
Regression: [Regression, Unit Test Broken] (was: [Regression])
The changes made in #532106 causes the myfaces testcase to fail with a java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
To recreate the testcase failure go to testsuite/web-testsuite/test-myfaces and type "mvn -P child"
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486199 ]
Paul McMahan commented on GERONIMO-3051:
----------------------------------------
According to the Application EARs portlet, the system-database config is a parent of the app we're having problems with (i.e. the console). But based on the way that java.sql.DriverManager#getConnection() works I don't see any way that system-database in the lineage would have an effect unless it was made a parent of jee-specs. The underlying problem is that as long as JSTL is loaded from jee-specs the DriverManager will also try to load the database driver from jee-specs' classloader.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486654 ]
Joe Bohn commented on GERONIMO-3051:
------------------------------------
I noticed that you created the patch from configs. The patch was applied correclty. The difference in our results might be because I'm doing a top level clean build. I think if you try that (using mvn clean install) you will see the problem. We can get past the build problem by keeping the dependency on jstl in jee-specs while still adding it to the defaultEnvironment in JspModuleBuilderExtension, but I'm not sure if that will continue to cause the runtime issues. I'll try it out a little later and see.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492362 ]
Paul McMahan commented on GERONIMO-3051:
----------------------------------------
verified that the JSF test case runs properly at rev 533182 where the previous change is reverted and David's patch is applied. Thanks David and Joe!
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc-2.patch, GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn reassigned GERONIMO-3051:
----------------------------------
Assignee: Joe Bohn
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486145 ]
Paul McMahan commented on GERONIMO-3051:
----------------------------------------
JSTL is not the culprit, at least not directly. It uses the TCCL to load the driver classes. The setDataSource tag completes successfully. Its the subsequent calls that try to run queries on the db that fail.
The problem is that JSTL relies on java.sql.DriverManager#getConnection() to set up its connections to the database. That method does *not* use the TCCL to load drivers. Instead it determines the classloader of whoever called it and uses that classloader to try to load the driver. In this case the caller is JSTL and its classloader is the jee specs config classloader, which obviously does not have the derby classes.
The javadoc for this getConnection() method says:
{quote}
When the method getConnection is called, the DriverManager will attempt to locate a suitable driver from amongst those loaded at initialization and those loaded explicitly using the same classloader as the current applet or application.
{quote}
I don't understand the rationale for this design (security?) but I think it forces Geronimo to move the JSTL classes to the default env for webapps since that is where the database drivers will most likely be loaded from. From that perspective the patch looks right, except I would also like to understand why the JSTL deps are added to the deployers.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3051) DB Viewer portlet error
Posted by "Frank G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank G updated GERONIMO-3051:
------------------------------
Attachment: GERONIMO-3051-new.patch
Thank you Divid for your advice. I've changed the patch to add the JSTL dependency to the JspModuleBuilderExtension default environment. I tested the patch on Tomcat and Jetty. Please ignore GERONIMO-3051.patch and review the new patch.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3051) DB Viewer portlet error
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-3051:
-----------------------------------
Attachment: GERONIMO-3051-jdbc.patch
Possible way to get around the retarded classloading problems from jstl/jdbc. It compiles but is untested. This would require undoing the other patches so jstl is once again in the jee-specs module.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3051) DB Viewer portlet error
Posted by "Frank G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank G updated GERONIMO-3051:
------------------------------
Attachment: GERONIMO-3051.patch
This is a general problem for any web application which uses standard tag in the jsp file like this:
<sql:setDataSource
var="ds"
driver="org.apache.derby.jdbc.EmbeddedDriver"
url="jdbc:derby:${db};create=true"
user=""
password=""
/>
The classloader hierarchy of any web application is something like bellow:
classloader(configuration org.apache.geronimo.configs/jee-specs/2.0/car)
^
/|\
|
classloader(configuration org.apache.geronimo.configs/rmi-naming/2.0/car)
^
/|\
|
.....
^
/|\
|
classloader(configuration org.apache.geronimo.application/any-web-application/1.0/car)
jstl-1.2.jar is included in classloader of configuration org.apache.geronimo.configs/jee-specs/2.0/car and the JDBC driver jar files are included in classloader of configuration org.apache.geronimo.application/any-web-application/1.0/car. So the classloader of configuration org.apache.geronimo.configs/jee-specs/2.0/car can not find the JDBC driver class defined in tag setDataSource.
Because the problem affects not only our web admin console, but also any web application which will use the above tag, my patch moved down jstl-1.2.jar from classloader of configuration org.apache.geronimo.configs/jee-specs/2.0/car to classloader of configuration org.apache.geronimo.application/any-web-application/1.0/car. One site effect of this solution is jstl-1.2.jar will be loaded many times in different web applications which use the standard tag lib, so I don't know if this is the best solution for this problem. What's your thought?
The patch was tested on Tomcat and Jetty.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3051) DB Viewer portlet error
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn resolved GERONIMO-3051.
--------------------------------
Resolution: Fixed
I integrated the new patch in trunk rev. 532106 along with a change in the JspModuleBuilderExtension which was required to get things to build successfully. Thanks Frank, David and Paul.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "Frank G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486568 ]
Frank G commented on GERONIMO-3051:
-----------------------------------
Hi, Joe, I retried to build the webconsole-tomcat and webconsole-jetty6 using the patch and didn't see the error you encountered. GERONIMO-3051-new.patch was made based on GeroninoSource_home\configs, not GeroninoSource_home, I'm not sure if this caused the error. Can you try it again, if it still fails, I need more deep investigation :-).
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486041 ]
David Jencks commented on GERONIMO-3051:
----------------------------------------
I think this is a bug in jstl, it should be using the TCCL. However unless someone wants to write geronimo-jstl we probably have to live with it.
Could I ask what bad things happen if you leave the jstl dependency out of jetty-deployer and tomcat-deployer? Also, isn't jstl a jsp feature? If so I would think that the JspModuleBuilderExtension default environment would be an even better place for the dependency, and it would only have to go in one place.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Attachments: GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3051) DB Viewer portlet error
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-3051:
-----------------------------------
Attachment: GERONIMO-3051-jdbc-2.patch
Another cheating driver impl :-)
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc-2.patch, GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3051) DB Viewer portlet error
Posted by "Paul McMahan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul McMahan resolved GERONIMO-3051.
------------------------------------
Resolution: Fixed
Regression: [Regression, Unit Test Broken] (was: [Unit Test Broken, Regression])
verified that the DB manager portlet is functioning OK, which means the jstl:sql tag can load the drivers from DriverManager using the new approach David implemented.
> DB Viewer portlet error
> -----------------------
>
> Key: GERONIMO-3051
> URL: https://issues.apache.org/jira/browse/GERONIMO-3051
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M4
> Environment: embedded Derby databases
> Reporter: Hernan Cunico
> Assigned To: Joe Bohn
> Attachments: GERONIMO-3051-jdbc-2.patch, GERONIMO-3051-jdbc.patch, GERONIMO-3051-new.patch, GERONIMO-3051.patch
>
>
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet.
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded Derby are also unaccessible from other applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.