I have Installed weblogic 10.3.5 with jrocket 1.6.0_33. Oracle Fusion Middleware 11.1.1 on Windows Environment. On database side I have Oracle database 11gR2 RAC environment with Two instance on Linux Environment. I have created
GRIDLINK DataSource with NON-XA DRIVERS.
NAME: test
JNDI: jdbc/testDS
NOTE: I have used SCAN IP for this DataSource configuration.
FAN ENABLED checked.
ONS HOST : scan-ip:6200
Not using "ONS Wallet".
The DataSource created successfully and Application also run but after few minutes or hours there some error accord in Managed Server console when Connection for pool "test" is getting closed it through error <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "test": SQLRecoverableException: Closed Coonection.>
what should I do to solve this problem?
Related
I am facing below error while connecting to the SQL Server on another server from a .NET application.
An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. The underlying provider failed on Open. A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
SQL Server is running on Windows Server 2016 and the application is on Windows Server 2012.
Everything was fine before those security updates but after updates were installed and servers were restarted, I started getting those errors.
Any suggestions on how to resolve this?
You might want look to look at the following article at Microsoft: Applications experience "forcibly closed" TLS connection errors when connecting SQL Servers in Windows
I am running into the same issue and I applied the work around, I am still waiting for the results to confirm the solution. It started happening recently in our production environment, as this happens very randomly while connecting to hundreds of servers it is difficult to spot the issue. First we were reviewing network side for lost packets as we work between different data centers. As nothing strange came back from this investigation I stumbled upon the above article.
Update
I applied the workaround, the Group Policy on the local computer, basically followed the instructions of this Group Policy, enabled the policy, copied all cipher suits, removed the TLS_DHE* and applied it. After that restarted the server. The issue has been resolved.
We recently migrated an application database to a new version from winserv2008/sql2008 to winserv2012R2/Sql2014. A service that pulls on this DB needs to be redesigned to accommodate some minor table/view definition changes.
Running the service code through tests under my personal security context works fine. However, installing and starting the service under .\LocalSystem is problematic. Looking at the service logs in event viewer I see that the service tries to connect to the sql server but gets a ERROR[28000] Login failed for user 'Domain\LocalSystemName$'.
The connection is via ODBC, SQL Server Native Client 11.0. Connection string is like:
"dsn=dsn_name;Driver={SQL Server Native Client 11.0};Database=database_name;Integrated Security=False;uid=accountname;pwd=accountpassword;Connect Timeout=15;ApplicationIntent=ReadOnly;"
Also, through the course of troubleshooting I've discovered/confirmed several things.
The sql server credentials I am using are correct, they are also being used to connect from a SQL2016 instance to the SQL14 server as a linked server.
The original service install on a utility server appears to be hitting the new database fine after the ODBC connection settings were switched.
My questions are:
Have you run into anything like this before?
Am I missing something simple in my connection string?
Are there per machine security settings in sql14 that I'm missing?
I have Installed weblogic 10.3.5 with jrocket 1.6.0_33. Oracle Fusion Middleware 11.1.1 on Windows Environment. On database side I have Oracle database 11gR2 RAC environment with Two instance on Linux Environment. I have created
GRIDLINK DataSource with XA DRIVERS.
NAME: test
JNDI: jdbc/testDS
NOTE: I have used SCAN IP for this DataSource configuration.
FAN ENABLED checked.
ONS HOST : scan-ip:6200
Not using "ONS Wallet".
DataSource was created successfully. Testing is done. Now when I start Application for 1st time and Click on any TAB, The Managed Server through some error on its console screen.
<error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "test": SQLRecoverableException: Closed Coonection.>
What should I do to resolve this error.
You should discover what's really happening when you enable debug on the weblogic instance in question. Here are the flags you can setup on server start as arguments.
-Dweblogic.debug.DebugJDBCRAC=true
-Dweblogic.debug.DebugJDBCONS=true
-Dweblogic.debug.DebugJDBCUCP=true
I am working with mobile first application and I have set it locally. I left server idle for about 15 minutes and then it is gives me configuration error.
When then I deploy adapter below error get started coming and not getting stop and adapter is not getting deploy.
Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
I tried clean the server, projects, restart studio every thing.
I have changed the workspace three time.
1) Eclipse - Version: Luna Service Release 2 (4.4.2) Build id: 20150219-0600
2) Mobile first : 7.0.0.00-20160307 - 1716
3) OS : Windows 8
Try killing the Java process or restarting the computer. You should then be able to successfully start the server and deploy the adapter.
Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
This is a common error or warning while server is downloading the artifacts(wlapp, adapter etc.) from database.
My actual problem was with database. WebSphere liberty with mobilefirst is giving derby as default database and My server was not working properly with it.
I changed it to MySQL database and it is working fine.
I had built an application to connect to MySQL DB and SyBase - SQL Anywhere DB using VB.NET and appropriate ODBC connections. This was working fine until we had to make this application a service which keeps running in the background irrespective of any users logged in.
I built the application into a service and after installation, the service was able to successfully connect to MySQL DB, but I am getting the following error when connecting to SyBase (please note the connection string is exactly same as used in the application)
ERROR [08001] [Sybase][ODBC Driver][SQL Anywhere]Database server not found
The project installer - service process installer 1 is configured as localsystem.
The creepiest thing here is, mysql connection is successful, when the same application was not a service, connecting to sybase was successful. Once it was made into a service it started failing. I have a Windows 7 64-bit workstation and VS 2010.
I have been trying to do every single thing for the last one week to fix it but nothing seems to be working. Any advice would be highly appreciated.
Looks like you are using a DSN to connect to SQL Anywhere.
First, make sure that you have configured it as a System DSN. Then, verify that you are using a TCP/IP connection protocol (ODBC Admin -> Select System DSN tab -> Select DSN in list -> Click Configure -> Goto Network tab) and NOT Shared Memory.
Using Shared Memory will NOT work from a Win Service that tries to connect to a SQL Anywhere DB Server.
I suspect that is the issue since you are able to connect from a desktop app using the same connection string.
One way to make this work is to start your SQL Anywhere db as a network server (Start -> All Programs -> Sql Anywhere 12 (or 11, depending on your setup) -> SQL Anywhere -> Network Server.
That should run the dbsvr12.exe, which will start listening for connections on a TCP port.
Then, add a Links=tcpip, or a Host=localhost to your Win Service connection string and give that a try!
Take notice that simple win app is running with credentials from logged user, while windows service is running on system account (in your case). You have two options, change connection string to connect with specific user (if you are now using trusted connection) or change windows service logon user to your user.