Google Cloud SQL doesnt work when deployed to appspot - sql

I have a GWT project, using google sql cloud database. Everything works fine when developing locally ( development mode ). But when I deploy it to appspot it can't connect to to the database.
Doesn't anyone have an idea why this is? Should I change permissions somewhere ? I'm pretty much lost.
I must say there is another deployed project using this database.
Thanks in advance :)
UPDATE:
2012-11-02 16:14:59.888
Uncaught exception from servlet
java.lang.UnsupportedClassVersionError:
com/layout/server/EntityServiceImpl :
Unsupported major.minor version 51.0
My App Engine log gave the following error, which is not database related. I've been using JRE 7 which appearantly is not compatible with GAE. ( appengine.google.com -> log ).
I'm trying to use JDK6 now and see what happens :)
This was the problem, changed to JDK 6 and everything is solved now. Had nothing to do with my database. Just the Java Version.

Related

couldnt create db schema "ACT_RU_IDENTITYLINK" in flowable engine

I have Spring Boot (2.3.4) app runs on Tomcat (9). When i try to build the project, flowable(6.6.0) engine gives this error. Schema is already created but it tries to create again. My problem is, i cannot deploy war code to the server because of it.
I upgraded flowable-engine version 6.6.0 to 6.7.0, and its solved.

com.ibm.worklight.admin.common.util.exceptions.TimeoutException

MobileFirst 6.3.0.00 Studio Plugin. Working in development server for Maximo Anywhere. Unable to deploy Adapter.
I am presented with "Adapter deployment failed: UndeclaredThrowableException" in the MobileFirstConsole.
I look at the MobielFirst Development Server and I see "CWWKX0204E: Unable to parse Throwable from server error stream".
Further down I see "java.lang.ClassNotFoundException: com.ibm.worklight.admin.common.util.exceptions.TimeoutException"
I have rebuilt the MobielFirstServerConfigFolder multiple times at the direction of others and this does not seem to solve this particular problem. I have searched my system and I in fact cannot locate this file.
Where should it be? and what is normal procedure for shoving it into its little home?
Thanks in advance.
Perhaps using the latest available v6.3 iFix will help.
As an IBM customer you can connect to IBM Fix Central, search for "mobilefirst platform", select 6.3 as your release version and download the latest available Studio fix.
Install it in fresh Eclipse that uses a new workspace and import your project into it. Start the server and deploy the adapter.

"Failed to Deploy Artefact error" in Eclipse Mule ESB project

I'm trying to run a trivial http echo app against the 3.50 CE runtime and I get the following stack trace(s) when I try to run
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Failed to deploy artifact 'default', see below +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
java.lang.NullPointerException
at org.mule.module.launcher.DefaultArchiveDeployer.guardedDeploy(DefaultArchiveDeployer.java:274)
...
Exception in thread "main" java.lang.NullPointerException
at org.mule.module.launcher.DefaultArchiveDeployer.addZombieApp(DefaultArchiveDeployer.java:325)
Additional context:
I've just started working with Mule (using the Eclipse Plugin). I initially had the trial package which is configured for Enterprise edition and I had that working with some of the trivial examples - hello world and echo.
I then downloaded the community runtimes and changed the targets on the projects, at that point I had been getting No Application Name errors, and I tried rebuilding them as new projects with CE targets from the start.
I also had been running them as mule applications, but this page
https://developer.mulesoft.com/docs/display/current/Studio+in+Eclipse
seems to indicate I must use maven ( I've set that up - although the automatic POM management doesn't seem to be working) but I still get the above failure.
There's no indication of why it's failing, as far as I can tell my projects output is valid.
Any suggestions welcome.
For what it's worth this is working now (fixed it shortly after posting the question even though it's been a blocker since yesterday).
If anyone else runs aground of the same issue..
I wasn't using the latest Community Edition runtime so I upgraded using the eclipse plugin install from (http://studio.mulesoft.org/r4/studio-runtimes).
I think this might have had something to do with it as I had previously been using the r4 plugin (http://studio.mulesoft.org/r4/plugin) with the Eclipse hosted 3.5 CE. Possibly the plugin is not backward compatible with the Runtimes.
basically once I completed the install and restarted I upgraded my project to use the new CE (changing the project setting and the flow xml). It worked first time.
Oddly all my Mule-Maven options have disappeared, but that's a separate question.

How to Fix No MBean found for Worklight project?

I have a problem when deploying my Worklight project on the server . It shows the following Error Message :
FWLSE3041E: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans.
and when I tried to preview my application it showed this message :
SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:420'
I had the same issue using Worklight 6.2 CLI, but recreating the project did not work.
One issue that I had was that worklight did not build a .war-file properly, so I copied the .war-file from a backup.
Edit: This happens regularly in our project now, and we have no idea why. We fix it by invoking any procedure, which makes it work until you restart the server. Worklight must be building something when invoking a procedure that it does not do when building.
I Solved The problem by creating a new Worklight Project and copied all my files , it works just fine :) I used Worklight 6.1 instead of 6.2
I solved this by fixing a recently created security test in
server/conf/authenticationConfig.xml
The problem was I mispelled the Realm name I previously defined.
I solved this problem by deleting the application from the worklight server and rebuild it.
Delete WorklightServerConfig folder in workspace and rebuild your application.
I was able to fix this in MobileFirst 7.0 (Fka Worklight) by opening the Servers view, Window -> Show View -> Servers. Then expanding the MobileFirst Development Server and right click on the project in question, chose delete.
Once you do that go back to the applications' directory in the "apps" directory and right click -> Run As -> Run On MobileFirst Development Server
This should rebuild and deploy the project on the server.
I solved the problem by using ibm jdk not open jdk. My solution is to make sure the env parameters are correct
export JAVA_HOME = $your_ibm_jdk
export PATH + $your_ibm_jdk/bin:$PATH
run java -version to make sure the setting work

HSQLDB is working on Windows but throws exceptions on Linux

This is really annoying: my java web-application deployed on Windows Tomcat runs perfectly. When application is deployed to Linux HSQLDB starts throwing exeptions about bad SQL grammar and syntax of elementary SQL statements. Like "DROP TABLE Test IF EXISTS" "IF EXISTS" is an error or "double" type is not supported. I tested with hsql 2.1.0 and hsql 1.8.1 - same errors.
My brain is in real stackoverflow. Am I struggling with a known issue?
P.S.
After further investigation it shows that my web-application of Linux suddenly switches to DBCP of Tomcat instead of using DBCP in the WEB-INF/lib
HSQLDB does not run differently in Linux. It is possible that an earlier version Jar is in Tomcat's classpath in Linux. In this situation, classes from the early jar may be picked up.
It is possible to add a test to your app to detect the existence of early version Jars.
For example DatabaseMetaData#getDriverVersion() will report the version of the jar.
I appologize for the question. The cause of the problem had nothing to do with HSQL database. The datasource was created using Spring and I was using th same name for teh datasource bean in two different places.