We are using Grails 4 framework for our web application with oracle database. Everything work fine when we host the application locally. However, when we migrated the application to production environment, application is getting disconnected with database server intermittently. On checking the tomcat logs we are getting " SQLexception Failed to validate newly established connection" error.
SQL error
Application.yml
Related
I have spring boot application which starts H2 db with below URL
jdbc:h2:~/data/test;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE;TRACE_LEVEL_SYSTEM_OUT=3;AUTO_SERVER_PORT=52002;AUTO_RECONNECT=TRUE
After this i run a test suit which also connects to same H2 instance but at this time i get. At this application is still running and I can access the H2 console
Connection is broken: "java.io.EOFException: 192.168.1.178:52002" [90067-200]
If an error occurs during startup, e.g. wrong database password, the server will not start. But if you use spring actuator, the server could return DOWN on the health interface, instead of not starting the server.
Is it possible to start the server despite errors and then display the error via /health?
Setup:
2 HTTP Servers
1 Load Balancer between 2 HTTP server and 2 MobileFirst servers
2 MobileFirst server 8.0 s on Liberty Farm 8.5.5
IBM DB2
i am facing an issue with session affinity during mobilefirst server failover. when it failed over to other server, the console says the session has expired.
i followed the below link to configure the session persistence for Liberty but the procedure is not clear. i created sessions database but it doesn't create any table under that.
http://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.wlp.doc/ae/twlp_admin_session_persistence.html
the web plugin config.xml files is configured to point so it's like HTTP server > LB > mobilefirst servers.
I have running H2 database locally in server mode.
TCP server running at tcp://192.168.159.1:9092 (others can connect)
When I connect to H2 instance via Playframework aplication using this configuration
db.default.url="jdbc:h2:tcp://192.168.159.1:9092/~/test3"
db.default.driver=org.h2.Driver
db.default.username="sa"
db.default.password="sa"
Everything is fine database is created, evolution scripts are triggered but I cannot connect to that database using for example SQuirell. I keep getting
this error:
java.util.concurrent.ExecutionException: java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: Wrong user name or password [28000-192]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.engine.Engine.validateUserAndPassword(Engine.java:336)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:162)
at org.h2.engine.Engine.createSession(Engine.java:137)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:148)
at java.lang.Thread.run(Thread.java:745)
Same is happenig when database is created outside Play, then in Play i'm getting same error. Is this some bug in 2.3.10 ( version of Play)
The Play 2.3.x JDBC datasource is managed by BoneCP
Correctly define User name
db.default.user=sa
So I used settings from more recent version
Play framework 2.5.x is using HikaryCP where this would be correct
db.default.username=sa
<sql:setDataSource var="TCIT" scope="application"
driver="${driver}"
url="${url}"
user="${username}"
password="${password}" />
The above code is used in a legacy application deployed in OC4J that is being migrated to WebSphere 8.5. The properties in {} above are fetched from a property file. Ensured the values are coming correctly form there. However, when the database connection is created the application is encountering the following exception: Unable to get connection, DataSource invalid: "java.sql.SQLException: No suitable driver" . I have the ojdbc14.jar in the WEB-INF/lib folder, still facing the issue.
Finally the issue got resolved creating a JDBC connection pool at Application server level. Turns out Websphere does not allow the connection to be created using the above method. Below is the modified tag that is using JNDI lookup for accessing the JDBC connection pool at application level.
<sql:setDataSource var="connPool" scope="application" dataSource="${jndi.devPool}"/>