Google Patents Secure gateway interconnection in an e-commerce based environmentĭownload PDF Info Publication number US6704873B1 US6704873B1 US09/364,490 US36449099A US6704873B1 US 6704873 B1 US6704873 B1 US 6704873B1 US 36449099 A US36449099 A US 36449099A US 6704873 B1 US6704873 B1 US 6704873B1 Authority US United States Prior art keywords component wide area activity area network business Prior art date Legal status (The legal status is an assumption and is not a legal conclusion.
Google Patents US6704873B1 - Secure gateway interconnection in an e-commerce based environment These versions are running in JVM 8 and therefore support newer versions of ojdbc8.jar, which will make use of the new JDBC 4 features resulting in better performance and stability.US6704873B1 - Secure gateway interconnection in an e-commerce based environment See JDBC Adapter users guide for how to migrate the services to match the new services templates (there is a migration service inside the updated Adapter package).įurthermore you should consider upgrading to wM 9.12/wM 10.x, which provide newer versions of the JDBC Adapter (9.10, 10.1 and 10.3). Ojdbc14.jar has some issues with LOB handling when driver is running in thin mode which is needed by the JDBC Adapter as long as you are not adding the native oci library for the driver.Īdditionally check if it is possible for you to update the JDBC Adapter to version 9.0. Update ojdbc7.jar to Oracle client version 12.1.0.2 (the last one which has an ojdbc7.jar available). Please remove the ojdbc14.jar completely (it was built with Java 1.4) and use (replace it with) ojdbc7.jar (which was built with JVM 7). And if it turns out to be the driver specifically I’d be very interested in learning the details of how such a problem would result in “connection refused.”
It is likely a very simple issue that does not have to do with the driver version. If the driver was the issue, I would think the error message would be different and likely indicate a version/impedence mismatch.Ĭheck connectivity from SQL Developer or TOAD or other tool to confirm the DB. So either the DB changed from using the default port on the same server, or the updated DB is on a different server. It is saying that nothing is listening on port 1521. As we’ve all experienced over the years – trust the error message. Given the update of the DB server, this seems like a good opportunity to update the driver since testing will likely be performed due to the DB update.īut IMO, this is not likely the root cause of the error. I agree that using a newer driver is preferable.
0 kommentar(er)
