Exception in DriverManager.getConnection
Hello, i am using most recent version of GWT. I want to connect via RPC to hibernate- mysql. I encounter the same error messages as the mentioned in thread http://www.mail-archive.com/google-web-toolkit@googlegroups.com/msg15320.html I have solved the problem the same way as in the thread (i.e. by unchecking of Project-Properties-Google-Use Google App Engine), but now I am unable to run, debug application in hosted mode. How should it be started? Please help me, i am stuck! Thanks Arne -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Exception in DriverManager.getConnection
Hello, i am using most recent version of GWT. I want to connect via RPC to hibernate- mysql. I encounter the same error messages as the mentioned in thread http://www.mail-archive.com/google-web-toolkit@googlegroups.com/msg15320.html I have solved the problem the same way as in the thread (i.e. by unchecking of Project-Properties-Google-Use Google App Engine), but now I am unable to run, debug application in hosted mode. How should it be started? Please help me, i am stuck! Thanks Arne -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Additional information for those who have this same problem and find this post like I did. Using Eclipse 3.4.2, Google Eclipse Plugin 1.0.1.v200905131143, GWT 1.6.4, App Engine Java SDK 1.2.1 I faced two issues when trying to develop my JSP web application (which uses JDBC and is not intended to be deployed on Google App Engine; it just uses GWT) - With App Engine enabled for the project it would compile my JSPs correctly but give the security errors noted above - With App Engine disabled (only gwt enabled) the JSP files would not compile with the error org.apache.jasper.JasperException: Unable to compile class for JSP and referencing me to the Compile Error Output which does not seem to be available anywhere I can find... My work around hack: Extract appengine-java-sdk-1.2.1\libappengine-tools-api.jar Use JBE (Java Bytecode Editor) to edit com\google\appengine\tools \development\DevAppServerFactory$CustomSecurityManager.class Empty out the check* functions so they only contain a 'return' Jar back up and replace the original libappengine jar I can now leave App Engine enabled and have no more security errors AND my JSP files compile correctly! Huzzah!! Note that of course this app could NOT be deployed to google app engine. The App engine is just enabled since it allows my JSPs to compile correctly. Regards On Jun 16, 12:35 pm, Khoa khoa.cof...@gmail.com wrote: Another soul is saved -- thank you On Jun 7, 8:34 am, aydogdu aydo...@gmail.com wrote: god bless you On Apr 13, 2:46 pm, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Hi, When you say that the JSP files would not compile, how were you trying to compile them? Were you hitting the JSP in a browser? Rajeev On Tue, Jul 7, 2009 at 10:37 PM, puddlesofjoy jcrowe.u...@gmail.com wrote: Additional information for those who have this same problem and find this post like I did. Using Eclipse 3.4.2, Google Eclipse Plugin 1.0.1.v200905131143, GWT 1.6.4, App Engine Java SDK 1.2.1 I faced two issues when trying to develop my JSP web application (which uses JDBC and is not intended to be deployed on Google App Engine; it just uses GWT) - With App Engine enabled for the project it would compile my JSPs correctly but give the security errors noted above - With App Engine disabled (only gwt enabled) the JSP files would not compile with the error org.apache.jasper.JasperException: Unable to compile class for JSP and referencing me to the Compile Error Output which does not seem to be available anywhere I can find... My work around hack: Extract appengine-java-sdk-1.2.1\libappengine-tools-api.jar Use JBE (Java Bytecode Editor) to edit com\google\appengine\tools \development\DevAppServerFactory$CustomSecurityManager.class Empty out the check* functions so they only contain a 'return' Jar back up and replace the original libappengine jar I can now leave App Engine enabled and have no more security errors AND my JSP files compile correctly! Huzzah!! Note that of course this app could NOT be deployed to google app engine. The App engine is just enabled since it allows my JSPs to compile correctly. Regards On Jun 16, 12:35 pm, Khoa khoa.cof...@gmail.com wrote: Another soul is saved -- thank you On Jun 7, 8:34 am, aydogdu aydo...@gmail.com wrote: god bless you On Apr 13, 2:46 pm, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Another soul is saved -- thank you On Jun 7, 8:34 am, aydogdu aydo...@gmail.com wrote: god bless you On Apr 13, 2:46 pm, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
god bless you On Apr 13, 2:46 pm, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
This post is a gold mine. On Jun 2, 1:17 am, MM mmea...@gmail.com wrote: Nice! This com.mysql.jdbc.ConnectionImpl exception error was driving me crazy also. Thanks! On Apr 13, 6:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, themysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due toJettyand security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody gotMysqlworking with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due toJettyand security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Nice! This com.mysql.jdbc.ConnectionImpl exception error was driving me crazy also. Thanks! On Apr 13, 6:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
You saved my life, the weeks I'm trying to solve this problem. On 13 abr, 08:46, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin.- Ocultar texto das mensagens anteriores - - Mostrar texto das mensagens anteriores - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
This is indeed a great finding. I have a similar problem when I tried the slicr GWT tutorial from IBM. At last, I managed to reduce the problem to putting a statement new org.apache.derby.jdbc.EmbeddedDriver(); inside the GreetingServiceImpl.java file generated by webAppCreator. I did some tracing and found that the objects inside the servlet are loaded by different classloaders. It seems that there are non-trivial classloadings done by Eclipse and Google App Engine that cause the problem. It's great that you found the solution : uncheck the Use Google App Engine checkbox. Thanks, david On Apr 13, 6:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Thanks a lot Martin. :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
I am having a similar problem. It's very weird. The test code I wrote works fine when I execute it directly, but when run from within the GWT framework I get a weird NullPointer exception thrown all seemingly caused by the exception below. Have you had any lucky solving your problem? Thanks. Jeff The server is running at http://localhost:8080/ Apr 28, 2009 3:20:42 PM com.google.appengine.tools.development.ApiProxyLocalImpl log SEVERE: [1240946442913000] javax.servlet.ServletContext log: Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract java.lang.String com.onenine.products.timekeeper.client.GreetingService.greetServer (java.lang.String)' threw an unexpected exception: java.lang.ExceptionInInitializerError at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure (RPC.java:360) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse (RPC.java:546) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall (RemoteServiceServlet.java:166) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost (RemoteServiceServlet.java:86) at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter (ServletHandler.java:1093) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter (TransactionCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter (ServletHandler.java:1084) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:360) at org.mortbay.jetty.security.SecurityHandler.handle (SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle (SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle (ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle (DevAppEngineWebAppContext.java:54) at org.mortbay.jetty.handler.HandlerWrapper.handle (HandlerWrapper.java:139) at com.google.appengine.tools.development.JettyContainerService $ApiProxyHandler.handle(JettyContainerService.java:306) at org.mortbay.jetty.handler.HandlerWrapper.handle (HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 506) at org.mortbay.jetty.HttpConnection$RequestHandler.content (HttpConnection.java:844) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run (SelectChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.run (BoundedThreadPool.java:442) Caused by: java.lang.ExceptionInInitializerError at com.mysql.jdbc.NonRegisteringDriver.connect (NonRegisteringDriver.java:282) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at com.onenine.products.timekeeper.server.GreetingServiceImpl.testLogin (GreetingServiceImpl.java:54) at com.onenine.products.timekeeper.server.GreetingServiceImpl.greetServer (GreetingServiceImpl.java:22) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse (RPC.java:527) ... 25 more Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup) at java.security.AccessControlContext.checkPermission(Unknown Source) at java.security.AccessController.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPermission(Unknown Source) at com.google.appengine.tools.development.DevAppServerFactory $CustomSecurityManager.checkPermission(DevAppServerFactory.java:76) at com.google.appengine.tools.development.DevAppServerFactory $CustomSecurityManager.checkAccess(DevAppServerFactory.java:98) at java.lang.ThreadGroup.checkAccess(Unknown Source) at java.lang.Thread.init(Unknown Source) at java.lang.Thread.init(Unknown Source) at java.util.TimerThread.init(Unknown Source) at java.util.Timer.init(Unknown Source) at java.util.Timer.init(Unknown Source) at
Re: GWT 1.6.4: Exception in DriverManager.getConnection
If you unselect Google App Enginee. Does that me you disable the google Gears Options? I have google app 1.2.0 which correspond to the same version as the gwt-gear that I have installed. Please verify because I do need the use of gears. and If I need to disable gears in order to fix the my mysql problem. Then it is not a solution. Thank you. Churk On Apr 17, 11:18 pm, Seattle_Dave davidco...@gmail.com wrote: Thanks a million. How on earth did you figure that out? I was going crazy. My app worked fine on the server, but failed with a permissions error on my dev box, connecting to localhost. On Apr 13, 4:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Removing App Engine just means that you don't plan on running the project on appengine. That should not impact Gears at all. On Wed, Apr 22, 2009 at 2:36 PM, Churky chu...@gmail.com wrote: If you unselect Google App Enginee. Does that me you disable the google Gears Options? I have google app 1.2.0 which correspond to the same version as the gwt-gear that I have installed. Please verify because I do need the use of gears. and If I need to disable gears in order to fix the my mysql problem. Then it is not a solution. Thank you. Churk On Apr 17, 11:18 pm, Seattle_Dave davidco...@gmail.com wrote: Thanks a million. How on earth did you figure that out? I was going crazy. My app worked fine on the server, but failed with a permissions error on my dev box, connecting to localhost. On Apr 13, 4:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. -- Miguel --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Thanks a million. How on earth did you figure that out? I was going crazy. My app worked fine on the server, but failed with a permissions error on my dev box, connecting to localhost. On Apr 13, 4:46 am, martin hotston...@googlemail.com wrote: Ok, I solved the problem ;-) Go to the project's properties and uncheck Use Google App Engine. Additionally, as vitali mentioned, the mysql-connector jar has to be in the war/WEB-INF/lib directory. Cheers, Martin. On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Yes, I am using the google eclipse plugin. The project was freshly generated by the plugin, I just added the database connection stuff. @Vitali: I did also try to put the mysql-connecter jar file into the war/WEB-INF/lib directory, that did not change anything (with or without changing the reference to the WEB-INF/lib directory). So, any expert who can help us out? On Apr 12, 3:16 pm, IvanRdz ivan.rd...@gmail.com wrote: I have the same problem and I am sure it´s due to Jetty and security settings as you have mentioned. Are you using google plugin? On Apr 11, 7:59 pm, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6.4: Exception in DriverManager.getConnection
I don't think so. It worked fine for me. Don't see how GWT has anything to do with the server side code that does the mysql call. Just drop that file into war/WEB-INF/lib. On Sat, Apr 11, 2009 at 1:59 PM, martin hotston...@googlemail.com wrote: Ok, I am still stuck :-( Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT 1.5 for me, but something seems to have changed with GWT 1.6.4. Maybe it is due to Jetty and security settings, since I get a java.security.AccessControlException... All I did was to add the / usr/share/java/mysql-connector-java-5.1.6.jar to the referenced libraries. Please help me out! Thanks, Martin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
GWT 1.6.4: Exception in DriverManager.getConnection
Hi!
I created a very simple test application with the Eclipse PlugIn from
a freshly installed GWT 1.6.4. When trying to connect to the database,
I get a java.lang.ExceptionInInitializerError calling getConnection:
public ServiceImplementation()
{
try
{
Class.forName(com.mysql.jdbc.Driver);
} catch (Exception e)
{
e.printStackTrace();
System.exit(1);
}
try
{
connection =
DriverManager.getConnection(jdbc:mysql://localhost/
testdatabase, root, pwd);
} catch (SQLException e)
{
e.printStackTrace();
System.exit(1);
}
}
I am able to connect to the database using the MySQL Query Browser.
Also, the same server code worked with previous GWT versions. I use
Ubuntu 8.10, Eclipse 3.4.2.
Any help is appreciated!
Thanks,
Martin.
The server is running at http://localhost:8080/
Apr 9, 2009 1:27:20 PM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: Nested in javax.servlet.ServletException: init:
java.lang.ExceptionInInitializerError
at com.mysql.jdbc.NonRegisteringDriver.connect
(NonRegisteringDriver.java:282)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:185)
at com.testproject.server.ServiceImplementation.init
(ServiceImplementation.java:41)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance
(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
at org.mortbay.jetty.servlet.ServletHolder.getServlet
(ServletHolder.java:339)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
463)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1093)
at
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter
(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle
(ServletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle
(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle
(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle
(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
405)
at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle
(DevAppEngineWebAppContext.java:54)
at org.mortbay.jetty.handler.HandlerWrapper.handle
(HandlerWrapper.java:139)
at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:306)
at org.mortbay.jetty.handler.HandlerWrapper.handle
(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
506)
at org.mortbay.jetty.HttpConnection$RequestHandler.content
(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool.java:442)
Caused by: java.security.AccessControlException: access denied
(java.lang.RuntimePermission modifyThreadGroup)
at java.security.AccessControlContext.checkPermission
(AccessControlContext.java:323)
at java.security.AccessController.checkPermission
(AccessController.java:546)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:
532)
at com.google.appengine.tools.development.DevAppServerFactory
$CustomSecurityManager.checkPermission(DevAppServerFactory.java:76)
at com.google.appengine.tools.development.DevAppServerFactory
$CustomSecurityManager.checkAccess(DevAppServerFactory.java:98)
at java.lang.ThreadGroup.checkAccess(ThreadGroup.java:288)
at java.lang.Thread.init(Thread.java:332)
at java.lang.Thread.init(Thread.java:377)
at java.util.TimerThread.init(Timer.java:456)
at java.util.Timer.init(Timer.java:71)
at java.util.Timer.init(Timer.java:122)
at
