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.
Related
class java.lang.RuntimeException in glassfish when i try to create new JDBC Resources.
This is the exception. Following is the snapshot:
I've been having same issues with the latest Glassfish 4.1. I couldn't find any solution on how to resolve RuntimeException when using web interface to add new resources. From what I understand it is a major bug that hasn't been resolved yet (GLASSFISH-21437). Meanwhile, I manually add JDBC Connection Pool and JDBC Resource entries by modifying domain.xml file located in the domain's config folder:
glassfish4/glassfish/domains/domain1/config/domain.xml
Just make sure that you make a backup copy just in case you make a mistake. You will need to restart Glassfish.
You can also use asadmin CLI commands to add resources. I have not done this myself but instructions on how to do that can be found in Glassfish administration guide (chapter 5).
I hope this helps.
I had the same issue. I found the only solution to replace glassfish 4.1.1 with version 4.1.0. This fixed my problem.
I have found that BUG is fixed (https://java.net/jira/browse/GLASSFISH-21314). I created JDBC resurce without exception
Update to 4.1.2 .
I had the same issue with Glassfish 4.1.1 , until now I set up all with asadmin commands , but the bug has been fixed with version 4.1.2 , no more exception thrown while creating new JDBC ressources .
I have to download another version of glassfish, in my case "GlassFish 5.0 - Web Profile" https://javaee.github.io/glassfish/download , after in netbeans i removed the old GlassFish setting up the new version and everything was fine.
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
We're using Worklight 6.1.0.0 / WebSphere 8.0.0.2 (ND/aix).
This seemed pretty close to my question too, but for version 6.0.
I've successfully done uninstall/install to our worklight console war package. However, there is some extra work on re-deploying adapters and such. I was looking for a way to just update the console. Among the ant tasks there is a target 'minimal-update', which sounds like what I'm looking for (is it?). However when all other pieces fell into place, I have an error for mapping the datasources:
ADMA0007E: A validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for resource reference jdbc/WorklightDS in module Worklight with EJB name .
Contents of the 'minimal-update' task is pretty much the same as for 'install'.
I tried that as update from websphere admin console (but i should use the ant task - right?), that gave me a wizard screen to map jdbc/WorklightDS from package to jdbc/WorklightDS on server. This left me wondering how could I tell this using the ant task.
The ant target minimal-update of the sample configuration files documented at http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.deploy.doc/devref/c_ant_tasks_sample_config_files.html is meant to update a WAR file already deployed (and not uninstalled). In particular, on WAS, it assumes that the JNDI datasources are in place.
If you have uninstalled the WAR file, you should use the target install instead, provided that your databases were created for Worklight 6.1.
If they were created for a previous version of worklight you must upgrade their schema as well running the target 'databases' (and if it's a production installation, you might want to read all the steps in detail at http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_in_production_env.html )
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.
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.