WebLogic Upgrade Causes JDBC DataSource to fail - java

My company uses a commercial web tool that we host on-site. It uses a Java backend and runs out of WebLogic. We recently did an upgrade to the tool and part of it was an upgrade from WebLogic 12.1.1 to 12.1.3. After the upgrade we noticed that we started getting consistent errors when it tried to do certain things.
From WebLogic's log file:
java.sql.SqlException: [FMWGEN][SQLServer JDBC Driver]Object has been closed.
The database is SQL Server 2012 Enterprise Edition (SP3) and running on a Windows Server 2012 box. It appears to only happen when the tool does a SELECT statement against a synonym to another SQL box. If I make that synonym point to something locally, it works. I have verified that Enable XA Transactions is still enabled (as it was before the upgrade).
Sadly, I am unable to turn to the company of the tool since our use of synonyms is not supported with there system. Nothing changed with the database server - what could the issue be?

Related

disable java security alerts from oracle 11g forms application

I have developed one application in oracle forms 11g and it has been published on oracle middleware 11g (oracle Weblogic server 11g). In this application I am using Webutility tool as well.
whenever I am trying to run the application it gives me 3 to 4 alerts as "Do you want to run this application?". Each time we have to check "I accept the risk and want to run this application." then click on Run button. actually it is irritating for the end users. Is there any way to avoid these kinds of alerts while opening the application.
Create and deploy a Deployment Rule Set (DRS).
https://docs.oracle.com/javase/8/docs/technotes/guides/deploy/deployment_rules.html

Error connecting to memsql with mysql J connector

I have memsql server version 6.7. I am able to connect to it using mysql java connector version 5.1.47 from my spring boot application.
But when i upgrade connector version to 8.0.16 I get below error -
Caused by: java.sql.SQLException: Unknown system variable 'performance_schema'
Ran query SHOW VARIABLES; on my memsql instance and I do not see system variable 'performance_schema'.
Can i change datasource.url string to ignore this variable? Any other latest version of driver is supported?
If your concern is the security issue in the 8.0.15 mysql driver you could use the mariaDb drivers instead. We generally recommend folks use them with MemSQL:
https://docs.memsql.com/client-downloads/
MySQL 8 made a number of breaking changes (i.e., you will have issues with MySQL 8 drivers connecting to older versions of MySQL as well : https://bugs.mysql.com/bug.php?id=90994)
From https://github.com/spring-projects/spring-boot/issues/17090:
A relevant change in Spring Boot 2.1.5 would appear to be that it upgraded MySQL's Java connector from 8.0.15 to 8.0.16. The 8.0.x driver should be compatible with MySQL 5.6, 5.7, and 8.0 so this would either appear to be a problem with your configuration or, probably more likely, a regression in the driver. If you would like to pursue this, I would recommend asking for some help on the MySQL forums and providing sufficient information to allow someone to reproduce the problem.
Try version 8.0.15 to see if that works better.

Laravel Application on Oracle WebLogic Server

please i need someone to highlight firstly how i could execute php 5.x on Oracle Weblogic J2EE server and the settings required if any...
its a java based environment and i'm wondering how i could get this up and running seamlessly.
if you could provide in details the process required to get Apache working, alongside PHP, my intentions is to use it as the base for a Laravel application i'm currently working on and utilize Oracle as the backend database model...
any ideas ?

Not able to connect to Teradata using jdbc

I am trying to connect to Teradata using jdbc. My application is running in JDK 1.4.
The url i am using is "jdbc:teradata:///TMODE=ANSI,CHARSET=UTF8";
I get "No suitable driver error" when i try to run using JDK 1.4.
However, I am able to run my app using JDK 1.7 with the same url.
I have both terajdbc4.jar and tdgssconfig.jar in my Netbeans libraries.
You probably use the wrong version of either Java, Teradata JDBC or Teradata Utilities (TTU).
Take a look here, what is compatible with what: Compatibility
The matrix is part of this reference which holds information how to use JDBC with different Application Server like JBoss, Tomcat, WebSphere, ColdFusion, WebLogic, SAP etc.

Deployed Tomcat 6 webapp can't connect to Amazon RDS Oracle instance

We are building a Java Spring-based web application that accesses an Oracle backend via Hibernate.
Here is our stack/tools:
Tomcat 6
Maven 3
Spring (mvc, web, orm) 3.2.0
Hibernate 4.1.9
Oracle 11g Release 2
Intellij IDEA.
To access the RDS from our local machines, we are port forwarding localhost:2521 to our-rds-instance-name.wercytsdzeszx.us-east-1.rds.amazonaws.com:1521
We are running embedded Tomcat using the tomcat6-maven-plugin. Our Maven configuration for testing is clean package tomcat6:run-war-only. This will deploy the WAR file to http://app.local:8080/our-app-name/ and allow us to test the site through this link.
Using Hibernate, we can connect successfully to the RDS instance when we are running the web app from our local embedded Tomcat instances.
HOWEVER - this is where it gets stupid - when we deploy the WAR file to our EC2 instance (which is part of a security group that has access to the RDS instance), the application can no longer access the database. We receive this error:
org.hibernate.exception.GenericJDBCException: Could not open connection
This is boggling my mind. We have installed SQLPlus on our EC2 instance running Tomcat and we can connect to the RDS instance, so the EC2 instance does have access to connect to the RDS instance.
Our local connection string would look something like this:
*jdbc:oracle:thin:USER_NAME/password#localhost:2521/sid*
Our EC2 (staging) instance connection string would look like this:
*jdbc:oracle:thin:USER_NAME/password#our-rds-instance-name.wercytsdzeszx.us-east-1.rds.amazonaws.com:1521/sid*
I can provide more details, but I first wanted to get the main problem out there so I don't muddy the waters with useless information.
I appreciate all feedback.
Tony
I have solved this problem.
It turns out there was an Oracle timezone error (ORA-01882: timezone region not found) that was the culprit. The Ubuntu server we are using for our EC2 AMI had a default timezone set that I guess was not recognized by Java or Oracle. I had seen that error, but ignorantly thought it could not be related to a database connectivity error.
We used the dpkg-reconfigure tzdata command to set the timezone to the correct one and restarted Tomcat. This allowed us to connect successfully to the Oracle database.
Tony

Categories