Unable to stablish connection using JDBC
I can not stablish a connection using JDBC.
Oracle Server (8.1.7) SuSE Linux 7.1 kernel 2.4 AMD 650 with 750MB of memory.
Client: Win2000 (JDBC driver thin (The last one that you can download from OTN)
I can connect using ODBC or the JDBC-ODBC bridge without any problem, but when I try to connect using JDBC I got an exception:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection. If I restart the listener then the connection can be stablished, after the connection is closed, and before any other connection can be made the listener must be stoped and restarted.
any suggestions :)
Thank you very much, seeing that document it was much easier to solve the problem.
Now I am facing other problem:
When I try to execute a query(for example : select * from
) I get this error:
Error occurred while executing init statements
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: SQL statement(s) cannot be executed over DataSource "TEST". If you are using an Open SQL DataSource, you must register your tables using JDDI before you request them. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.microsoft.sqlserver.jdbc.SQLServerException: La conexión a la instancia con nombre ha fallado. Error: java.net.SocketTimeoutException: Receive timed out.
Do you have any idea how to solve this?
thanks again
Bye!
Similar Messages
-
Problem with Progress DB while using to connect using JDBC Adapter
Hi,
I am facing Problem with Progress DB while using to connect using JDBC Adapter. I am getting the following error in auditlog file like,
Error during database connection to the database URL jdbc:JdbcProgress:T:156.5.31.65:2545:/mfgprodev/devbadb
/devsche/i_apoext.db using the JDBC driver "com.progress.sql.jdbc.JdbcProgressDriver" : com.sap.aii.adapter.jdbc.sql.DriverManagerException: Unable to locate a suitable JDBC driver to establish a connection to URL " jdbc:JdbcProgress:T:156.5.31.65:2545:/mfgprodev/devbadb
/devsche/i_apoext.db "
I tried using the following all URLs,
1. jdbc:JdbcProgress:T:156.5.31.65:2545:i_apoext.
2. jdbc:JdbcProgress:T:156.5.31.65:2545:i_apoext.db
3.
jdbc:JdbcProgress:T:156.5.31.65:2545:/mfgprodev/devbadb
/devsche/i_apoext.
4.
jdbc:JdbcProgress:T:156.5.31.65:2545:/mfgprodev/devbadb
/devsche/i_apoext.db.
Can anyone please help me out in solving this issue.
May be the cause for this is :
1) The Wrong URL format
2) CLASSPATH is not setted properly..
Can you look more into this stuff.
Thanks,
Soorya.Hi,
To access any database fromm XI, using the JDBC adapter, the corresponding drivers have to be installed on the XI server.
Just check this note 831162.
Also, check this PDF to install Drivers in XI,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10 -
Getting socket error while trying to get oracle connection using JDBC
hi,
I am getting following socket read error while trying to get database connection using JDBC. This happening with jdk1.5.0_12 version with Oracle 9i
following is the stacktrace...
Thread t@92: (state = IN_NATIVE)
- java.net.SocketInputStream.socketRead0(java.io.FileDescriptor, byte[], int, int, int) @bci=0 (Compiled frame; information may be imprecise)
- java.net.SocketInputStream.read(byte[], int, int) @bci=84, line=129 (Compiled frame)
- oracle.net.ns.Packet.receive() @bci=31 (Compiled frame)
- oracle.net.ns.DataPacket.receive() @bci=1 (Interpreted frame)
- oracle.net.ns.NetInputStream.getNextPacket() @bci=48 (Compiled frame)
- oracle.jdbc.driver.T4CMAREngine.unmarshalSB1() @bci=1, line=1070 (Compiled frame)
- oracle.jdbc.driver.T4CStatement.doOall8(boolean, boolean, boolean, boolean) @bci=617, line=207 (Compiled frame)
- oracle.jdbc.driver.T4CStatement.executeForDescribe() @bci=39, line=790 (Compiled frame)
- oracle.jdbc.driver.OracleStatement.executeMaybeDescribe() @bci=106, line=1039 (Interpreted frame)
- oracle.jdbc.driver.T4CStatement.executeMaybeDescribe() @bci=11, line=830 (Interpreted frame)
- oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout() @bci=128, line=1132 (Interpreted frame)
- oracle.jdbc.driver.OracleStatement.executeQuery(java.lang.String) @bci=76, line=1272 (Interpreted frame)
any help would appreciated. thanks in advanceI do not have exact exception message.
additionally, i have got following the tomcat log file:
INFO - Resource pool cleanup thread just woke up.
Nov 1, 2008 3:41:52 AM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (100) are currently busy, waiting. Increase maxThreads (100) or check the servlet status
INFO - Resource pool cleanup thread just woke up.
thanks in advance -
Getting Multiple Recordsets using A Single Connection using jdbc-odbc
I have a java application which uses sql 7.0 database server. I want to have multiple recordsets created using a single connection using jdbc-odbc bridge. Kindly let me know the procedure.
Well, you create a recordset, then you create another one, and so on. Are you actually having a problem or you just don't know where to start?
-
OS_USER not correct when connecting using JDBC Thin Client on 10G
Hi Folks,
We are migrating an application from a 9i database to 10g and have a problem that someone might have come across before.
The application is a Java applet based application that connects to the database using JDBC Thin client. on 9i the OS_USER comes up as the user running the applet but in 10G it is coming up as the user account that installed 10G on the DB server.
We tried using a 9i client to identify if it was a client or DB issue but its the same problem with the 9i client connecting to the 10G DB.
If anyone can help it would be much appreciated.
Thanks,
John.What is the return of this command?
SELECT sys_context ('USERENV', 'OS_USER') FROM dual;
Is it the DB user or the OS user? -
Unable to stablish a connection using JDBC Drivers and Datasources
Hi all,
I am using SQL Server 2005,
I configured the driver(name:SQL2005) and added sqljdbc.jar
Also created a datasource with this information:
Application name: TEST
Name: TEST
Desc: TEST
I gave TEST as Alias.
I selected the driver I've created before(SQL2005), with JDBC Version 1.x(No AX Support)
As Driver Class I put com.microsoft.sqlserver.jdbc.SQLServerDriver
As DatabaseURL I put jdbc:sqlserver://<ServerName>:<port>;database=<dbName>
User: Admin, Password: pass
In SQL Engine I put "VENDOR SQL"
when I save it and try to Start Selected StandAlone Application I get this Error:
Error occurred while starting application 'sap.com/TEST'
these are the details:
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
Loader Info -
ClassLoader name: [library:SQL2005]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\ext\SQL2005\sqljdbc.jar
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
Can Anyone please help me?
Thanks in advance!
GuillermoThank you very much, seeing that document it was much easier to solve the problem.
Now I am facing other problem:
When I try to execute a query(for example : select * from
) I get this error:
Error occurred while executing init statements
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: SQL statement(s) cannot be executed over DataSource "TEST". If you are using an Open SQL DataSource, you must register your tables using JDDI before you request them. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.microsoft.sqlserver.jdbc.SQLServerException: La conexión a la instancia con nombre ha fallado. Error: java.net.SocketTimeoutException: Receive timed out.
Do you have any idea how to solve this?
thanks again
Bye! -
Connection using JDBC is to slow on windows xp
Hi all!
I'm trying to connect to Microsoft SQL Server 2000 using the microsoft jdbc driver. I tested this in linux Fedora and the connection is very fast, but in windows xp it takes about 5 seconds.
The drivers are 3 jar files witch I include in the classpath variable : msbase.jar , mssqlserver.jar and msutil.jar
To get the connection i use the following code:
DriverManager.registerDriver(new com.microsoft.jdbc.sqlserver.SQLServerDriver()); _con=DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:18345;databasename=DBNAME","MYUSER","MYPASS");
Note that the connection is made sucessful, but it takes 5 seconds witch I think it's not a normal time and in linux with the same drivers the connection is made in miliseconds.
I searched a lot about this, but found nothing.
I hope someone can help me.
Thanks in advance.
In forget to say that I am using jdk1.6 and jre 1.6
Edited by: GrEg on Apr 21, 2009 10:59 PMGrEg wrote:
Hi!
Thanks very much for your answer. In fact I tested connection pooling but the the first connection is also to slow. This is important because I am using threads and wich one needs a connection object.
Now I am using the sqlserver 2005 jdbc driver to connect to sql server 2000 and surprisly is so much faster, it takes about a second to establish the connection.
You mean for the first test you were using the MS 2000 driver?
Simple then - don't use it. That driver was very problematic as reported on this site. Use either the MS driver or the jtds driver instead. -
Infinite wait for connection using JDBC thin driver.
Hi,
I am using an OracleDataSource and an OracleConnectionCacheManager to manage my connection pool from my stand alone Java application. I am using ojdbc14.jar for my Oracle drivers. The database is Oracle 10g RAC. Java version is 1.5. I am using thin client.
The problem I have experienced is that upon calling the getConnection() method on the OracleDataSource object, my application waits infinitely for a connection. As my application is not checking how long it takes to retrieve a connection, the application effectively hangs.
Has anyone else witnessed this behaviour?? I have observed this behaviour in two seperate stand alone Java applications that are both talking to Oracle RAC databases.
When I create the OracleDataSource, I am considering calling the setLoginTimeout() method to specify a timeout when trying to connect to the database. Does anyone know if this will throw an SQLException if the infinite wait occurs again??
Thanks, Kenny.OK, I have the JVM stack trace at last!!! Here it is. This actually uses the following code every single time a database connection is required.
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
conn = (OracleConnection)DriverManager.getConnection(url, username, password);Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_15-b04 mixed mode):
"pool-2-thread-3" prio=10 tid=0x0000000100fd2500 nid=0x68 waiting for monitor entry [0xffffffff1cdfe000..0xffffffff1cdff628]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-2-thread-2" prio=10 tid=0x0000000100ecfb00 nid=0x67 waiting for monitor entry [0xffffffff1d0fe000..0xffffffff1d0ff7a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-21" prio=10 tid=0x0000000100fa9180 nid=0x66 waiting for monitor entry [0xffffffff1e4fe000..0xffffffff1e4ff728]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-20" prio=10 tid=0x0000000100f832b0 nid=0x65 waiting for monitor entry [0xffffffff1e6fe000..0xffffffff1e6ff8a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-19" prio=10 tid=0x0000000100f82240 nid=0x64 runnable [0xffffffff1e8fe000..0xffffffff1e8ff828]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at oracle.net.ns.Packet.receive(Unknown Source)
at oracle.net.ns.NSProtocol.connect(Unknown Source)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:707)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:218)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:343)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:147)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
- locked <0xffffffff2045e108> (a java.lang.Class)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
- locked <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-18" prio=10 tid=0x0000000100f905a0 nid=0x63 waiting for monitor entry [0xffffffff1ebfe000..0xffffffff1ebff9a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-17" prio=10 tid=0x0000000101a531b0 nid=0x62 waiting for monitor entry [0xffffffff1edfe000..0xffffffff1edff928]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-16" prio=10 tid=0x000000010171ced0 nid=0x61 waiting for monitor entry [0xffffffff1f0fe000..0xffffffff1f0ff6a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-15" prio=10 tid=0x0000000100ea6a70 nid=0x60 waiting for monitor entry [0xffffffff1f2fe000..0xffffffff1f2ff628]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-14" prio=10 tid=0x0000000101a520b0 nid=0x5f waiting for monitor entry [0xffffffff1f4fe000..0xffffffff1f4ff7a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-13" prio=10 tid=0x0000000100e7a870 nid=0x5e waiting for monitor entry [0xffffffff1f6fe000..0xffffffff1f6ff728]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-12" prio=10 tid=0x0000000100ea7430 nid=0x5d waiting for monitor entry [0xffffffff1f8fe000..0xffffffff1f8ff8a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-11" prio=10 tid=0x0000000101262330 nid=0x5c waiting for monitor entry [0xffffffff1fafe000..0xffffffff1faff828]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-10" prio=10 tid=0x0000000100b66160 nid=0x5b waiting for monitor entry [0xffffffff1fcfe000..0xffffffff1fcff9a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-9" prio=10 tid=0x0000000100b47ff0 nid=0x5a waiting for monitor entry [0xffffffff1fefe000..0xffffffff1feff928]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-8" prio=10 tid=0x0000000101a7ac70 nid=0x59 waiting for monitor entry [0xffffffff65afe000..0xffffffff65aff6a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-7" prio=10 tid=0x0000000101212460 nid=0x58 waiting for monitor entry [0xffffffff65cfe000..0xffffffff65cff628]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-6" prio=10 tid=0x0000000100f8f6f0 nid=0x57 waiting for monitor entry [0xffffffff65efe000..0xffffffff65eff7a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-5" prio=10 tid=0x0000000100c7c420 nid=0x56 waiting for monitor entry [0xffffffff660fe000..0xffffffff660ff728]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-2-thread-1" prio=10 tid=0x0000000101a41370 nid=0x55 waiting for monitor entry [0xffffffff662fe000..0xffffffff662ff8a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-4" prio=10 tid=0x0000000101a28ef0 nid=0x54 waiting for monitor entry [0xffffffff664fe000..0xffffffff664ff828]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-3" prio=10 tid=0x00000001009a1850 nid=0x53 waiting for monitor entry [0xffffffff666fe000..0xffffffff666ff9a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-2" prio=10 tid=0x0000000100f8e980 nid=0x52 waiting for monitor entry [0xffffffff668fe000..0xffffffff668ff928]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"pool-1-thread-1" prio=10 tid=0x0000000100bd86f0 nid=0x51 waiting for monitor entry [0xffffffff67afe000..0xffffffff67aff6a8]
at java.sql.DriverManager.registerDriver(DriverManager.java:259)
- waiting to lock <0xffffffff2045e108> (a java.lang.Class)
at com.jpm.mra.common.DBUtil.getDBConnection(Unknown Source)
at com.jpm.mra.bulking.BaseBulker.openConnection(Unknown Source)
at com.jpm.mra.bulking.GenericBulker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
"Thread-5" prio=10 tid=0x0000000100b66b90 nid=0x50 waiting on condition [0xffffffff67cff000..0xffffffff67cff628]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.IntervalBulker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Thread-3" prio=10 tid=0x0000000100f36860 nid=0x4f waiting on condition [0xffffffff67eff000..0xffffffff67eff7a8]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.ClockBulker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Thread-1" prio=10 tid=0x0000000100a4b300 nid=0x4e waiting on condition [0xffffffff680ff000..0xffffffff680ff728]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.DepthBulker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Thread-4" prio=10 tid=0x0000000100a4c380 nid=0x4d waiting on condition [0xffffffff682ff000..0xffffffff682ff8a8]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.IntervalBulkerStaticDataPoller.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Thread-2" prio=10 tid=0x0000000100bcf260 nid=0x4c waiting on condition [0xffffffff684ff000..0xffffffff684ff828]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.ClockBulkerStaticDataPoller.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Thread-0" prio=10 tid=0x0000000100a1b2d0 nid=0x4b waiting on condition [0xffffffff689ff000..0xffffffff689ff9a8]
at java.lang.Thread.sleep(Native Method)
at com.jpm.mra.bulking.MRABulking.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Low Memory Detector" daemon prio=10 tid=0x00000001006db880 nid=0x49 runnable [0x0000000000000000..0x0000000000000000]
"CompilerThread1" daemon prio=10 tid=0x00000001006da9e0 nid=0x48 waiting on condition [0x0000000000000000..0xffffffff6b6fdcc8]
"CompilerThread0" daemon prio=10 tid=0x00000001006d72a0 nid=0x47 waiting on condition [0x0000000000000000..0xffffffff6b8fde58]
"AdapterThread" daemon prio=10 tid=0x00000001006d6370 nid=0x46 waiting on condition [0x0000000000000000..0x0000000000000000]
"Signal Dispatcher" daemon prio=10 tid=0x00000001006d5440 nid=0x45 waiting on condition [0x0000000000000000..0x0000000000000000]
"Finalizer" daemon prio=10 tid=0x00000001006bf6b0 nid=0x44 in Object.wait() [0xffffffff6beff000..0xffffffff6beff828]
at java.lang.Object.wait(Native Method)
- waiting on <0xffffffff2544e010> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:120)
- locked <0xffffffff2544e010> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:136)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00000001006bd500 nid=0x43 in Object.wait() [0xffffffff6c0ff000..0xffffffff6c0ff9a8]
at java.lang.Object.wait(Native Method)
- waiting on <0xffffffff2544e000> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0xffffffff2544e000> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=0x000000010011ed20 nid=0x1 in Object.wait() [0xffffffff7fff5000..0xffffffff7fff56e0]
at java.lang.Object.wait(Native Method)
- waiting on <0xffffffff25456218> (a java.lang.Thread)
at java.lang.Thread.join(Thread.java:1095)
- locked <0xffffffff25456218> (a java.lang.Thread)
at java.lang.Thread.join(Thread.java:1148)
at com.jpm.mra.bulking.MRABulking.main(Unknown Source)
"VM Thread" prio=10 tid=0x00000001006b9790 nid=0x42 runnable
"GC task thread#0 (ParallelGC)" prio=10 tid=0x00000001001d47d0 nid=0x2 runnable
"GC task thread#1 (ParallelGC)" prio=10 tid=0x00000001001d5270 nid=0x3 runnable
"GC task thread#2 (ParallelGC)" prio=10 tid=0x00000001001d5d70 nid=0x4 runnable
"GC task thread#3 (ParallelGC)" prio=10 tid=0x00000001001d6870 nid=0x5 runnable
"GC task thread#4 (ParallelGC)" prio=10 tid=0x00000001001d7370 nid=0x6 runnable
"GC task thread#5 (ParallelGC)" prio=10 tid=0x00000001001d7e70 nid=0x7 runnable
"GC task thread#6 (ParallelGC)" prio=10 tid=0x00000001001d8970 nid=0x8 runnable
"GC task thread#7 (ParallelGC)" prio=10 tid=0x00000001001d9470 nid=0x9 runnable
"GC task thread#8 (ParallelGC)" prio=10 tid=0x00000001001d9f70 nid=0xa runnable
"GC task thread#9 (ParallelGC)" prio=10 tid=0x00000001001daa70 nid=0xb runnable
"GC task thread#10 (ParallelGC)" prio=10 tid=0x00000001001db570 nid=0xc runnable
"GC task thread#11 (ParallelGC)" prio=10 tid=0x00000001001dc070 nid=0xd runnable
"GC task thread#12 (ParallelGC)" prio=10 tid=0x00000001001dcb70 nid=0xe runnable
"GC task thread#13 (ParallelGC)" prio=10 tid=0x00000001001dd670 nid=0xf runnable
"GC task thread#14 (ParallelGC)" prio=10 tid=0x00000001001de170 nid=0x10 runnable
"GC task thread#15 (ParallelGC)" prio=10 tid=0x00000001001dec70 nid=0x11 runnable
"GC task thread#16 (ParallelGC)" prio=10 tid=0x00000001001df7b0 nid=0x12 runnable
"GC task thread#17 (ParallelGC)" prio=10 tid=0x00000001001e02b0 nid=0x13 runnable
"GC task thread#18 (ParallelGC)" prio=10 tid=0x00000001001e0db0 nid=0x14 runnable
"GC task thread#19 (ParallelGC)" prio=10 tid=0x00000001001e18b0 nid=0x15 runnable
"GC task thread#20 (ParallelGC)" prio=10 tid=0x00000001001e23b0 nid=0x16 runnable
"GC task thread#21 (ParallelGC)" prio=10 tid=0x00000001001e2eb0 nid=0x17 runnable
"GC task thread#22 (ParallelGC)" prio=10 tid=0x00000001001e39b0 nid=0x18 runnable
"GC task thread#23 (ParallelGC)" prio=10 tid=0x00000001001e44b0 nid=0x19 runnable
"GC task thread#24 (ParallelGC)" prio=10 tid=0x00000001001e4fb0 nid=0x1a runnable
"GC task thread#25 (ParallelGC)" prio=10 tid=0x00000001001e5ab0 nid=0x1b runnable
"GC task thread#26 (ParallelGC)" prio=10 tid=0x00000001001e65b0 nid=0x1c runnable
"GC task thread#27 (ParallelGC)" prio=10 tid=0x00000001001e70b0 nid=0x1d runnable
"GC task thread#28 (ParallelGC)" prio=10 tid=0x00000001001e7bb0 nid=0x1e runnable
"GC task thread#29 (ParallelGC)" prio=10 tid=0x00000001001e86b0 nid=0x1f runnable
"GC task thread#30 (ParallelGC)" prio=10 tid=0x00000001001e91b0 nid=0x20 runnable
"GC task thread#31 (ParallelGC)" prio=10 tid=0x00000001001e9cb0 nid=0x21 runnable
"GC task thread#32 (ParallelGC)" prio=10 tid=0x00000001001ea7b0 nid=0x22 runnable
"GC task thread#33 (ParallelGC)" prio=10 tid=0x00000001001eb2b0 nid=0x23 runnable
"GC task thread#34 (ParallelGC)" prio=10 tid=0x00000001001ebdb0 nid=0x24 runnable
"GC task thread#35 (ParallelGC)" prio=10 tid=0x00000001001ec8b0 nid=0x25 runnable
"GC task thread#36 (ParallelGC)" prio=10 tid=0x00000001001ed3b0 nid=0x26 runnable
"GC task thread#37 (ParallelGC)" prio=10 tid=0x00000001001edeb0 nid=0x27 runnable
"GC task thread#38 (ParallelGC)" prio=10 tid=0x00000001001f09c0 nid=0x28 runnable
"GC task thread#39 (ParallelGC)" prio=10 tid=0x00000001001f14c0 nid=0x29 runnable
"GC task thread#40 (ParallelGC)" prio=10 tid=0x00000001001f1fc0 nid=0x2a runnable
"GC task thread#41 (ParallelGC)" prio=10 tid=0x00000001001f2ac0 nid=0x2b runnable
"GC task thread#42 (ParallelGC)" prio=10 tid=0x00000001001f35c0 nid=0x2c runnable
"GC task thread#43 (ParallelGC)" prio=10 tid=0x00000001001f40c0 nid=0x2d runnable
"GC task thread#44 (ParallelGC)" prio=10 tid=0x00000001001f4bc0 nid=0x2e runnable
"GC task thread#45 (ParallelGC)" prio=10 tid=0x00000001001f56c0 nid=0x2f runnable
"GC task thread#46 (ParallelGC)" prio=10 tid=0x00000001001f61c0 nid=0x30 runnable
"GC task thread#47 (ParallelGC)" prio=10 tid=0x00000001001f6cc0 nid=0x31 runnable
"GC task thread#48 (ParallelGC)" prio=10 tid=0x00000001001f7810 nid=0x32 runnable
"GC task thread#49 (ParallelGC)" prio=10 tid=0x00000001001f8310 nid=0x33 runnable
"GC task thread#50 (ParallelGC)" prio=10 tid=0x00000001001f8e10 nid=0x34 runnable
"GC task thread#51 (ParallelGC)" prio=10 tid=0x00000001001f9910 nid=0x35 runnable
"GC task thread#52 (ParallelGC)" prio=10 tid=0x00000001001fa410 nid=0x36 runnable
"GC task thread#53 (ParallelGC)" prio=10 tid=0x00000001001faf10 nid=0x37 runnable
"GC task thread#54 (ParallelGC)" prio=10 tid=0x00000001001fba10 nid=0x38 runnable
"GC task thread#55 (ParallelGC)" prio=10 tid=0x00000001001fc510 nid=0x39 runnable
"GC task thread#56 (ParallelGC)" prio=10 tid=0x00000001001fd010 nid=0x3a runnable
"GC task thread#57 (ParallelGC)" prio=10 tid=0x00000001001fdb10 nid=0x3b runnable
"GC task thread#58 (ParallelGC)" prio=10 tid=0x00000001001fe610 nid=0x3c runnable
"GC task thread#59 (ParallelGC)" prio=10 tid=0x00000001001ff110 nid=0x3d runnable
"GC task thread#60 (ParallelGC)" prio=10 tid=0x00000001001ffc10 nid=0x3e runnable
"GC task thread#61 (ParallelGC)" prio=10 tid=0x0000000100200710 nid=0x3f runnable
"GC task thread#62 (ParallelGC)" prio=10 tid=0x0000000100201210 nid=0x40 runnable
"GC task thread#63 (ParallelGC)" prio=10 tid=0x0000000100201d10 nid=0x41 runnable
"VM Periodic Task Thread" prio=10 tid=0x00000001001c93f0 nid=0x4a waiting on condition
Edited by: krodman on 08-Jan-2010 04:03 -
[Solved] rtorrent unable to stablish connection with trackers
# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.
# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
max_peers = 34
# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
max_peers_seed = 34
# Maximum number of simultanious uploads per torrent.
max_uploads = 5
# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 100
upload_rate = 26
# Default directory to save the downloaded torrents.
directory = /home/chariabidis/downloads
# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /home/chariabidis/.session
# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/home/chariabidis/downloads/*.torrent
#schedule = untied_directory,5,5,stop_untied=
# Close torrents when diskspace is low.
#schedule = low_diskspace,5,60,close_low_diskspace=100M
# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,"stop_on_ratio=200,200M,2000"
# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no
# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no
# Port range to use for listening.
port_range = 49999-49999
# Start opening ports at a random position within the port range.
#port_random = no
# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no
# Set whetever the client should try to connect to UDP trackers.
#use_udp_trackers = yes
# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa
# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
encryption = allow_incoming,enable_retry,prefer_plaintext
# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
# dht = auto
# UDP port to use for DHT.
# dht_port = 6881
# Enable peer exchange (for torrents not marked private)
# peer_exchange = yes
# Do not modify the following parameters unless you know what you're doing.
# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10
# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100
# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10
The proper message I recieve is:
Tracker: [Couldn't connect to server]
I've tried several torrents from several trackers, and other torrent downloading programs too. rTorrent seems to be the only one with this problem.
Is there something I'm passing by in my network configuration?
I
Last edited by JMO (2011-03-08 00:35:44)Well I don't really know an answer, but what I can say is that I get these messages all the time, but rtorrent downloads the stuff nonetheless.
-
NT Adapter unable to make connection
Hi,
I am trying to create a java application using the
Data Form component. I keep getting the error message
TN adapter unable to make connection when I use the data form
wizard. Can I use JDeveloper 2.0 Beta with Oracle 8.0.4?
TIA,
Phil
nullHi,
I still can't get a JDeveloper 2.0 Beta to access a local
database.
Here is my configuration:
Oracle 8.0.5 Enterprise Edition for Windows NT 4.0 (SP3)
JDeveloper 2.0 Beta (Build 184)
Oracle Developer 2.1 and Oracle Designer 2.1.1 (installed
in the same Oracle home directory as the RDBMS)
All of the above are installed on a STAND ALONE machine with
NO network card installed. I am NOT connected to a network
either.
I have tried using the Oracle Thin driver, the OCI-8 driver, and
the Sun JDBC driver and still unable to make a connection to
the local RDBMS 8.0.5. I have tried every combination in the
Data Form Wizard. I even tried to access the RDBMS with the
Microsoft Loopback adapter. Does JDeveloper use SQL*Net or Net8?
Thanks in advance for your help.
Phil
JDeveloper Team (guest) wrote:
: Hi Phil,
: I posted some DB connect info a few weeks back, but it looks
: like it's faded off of the list. Here it is again (basically,
: to connect to an 8.0.4 DB, you need to use the 8.0.5 drivers):
: There have been quite a few postings on problems with
connections
: using JDBC in the JDeveloper 2.0 Beta release. This may help
: answer some of the common questions that arise. Please note
that
: the connection issues listed here are specific to the Beta
: release of JDeveloper. The production release of JDeveloper
will
: include Oracle 815 JDBC drivers, which should fix some of the
: limitations listed below.
: If this message does not help you fix your connection problem,
: please be sure to provide the following information in your
: posting to help us troubleshoot your problem:
: * version of the database you are trying to connect to
: * platform the database is installed on
: * is the database local or remote
: * what driver(s) you have tried connecting with
: The JDBC 8.1.4 THIN driver is provided as the default driver
with
: JDeveloper 2.0Beta. This driver can connect to 8.1.4 and
: 8.0.5 databases.
: If you are connecting to an 8.1.4 database and want to use the
: thin driver, you should be OK.
: If you are connecting to an 8.1.4 database and want to use the
: OCI driver, see
: the instructions below for switching your driver version. No
: 8.1.4 OCI
: drivers were available at the time of our Beta release. If you
: want to use
: OCI, you need to use the 8.0.5 drivers.
: If you are connecting to an 8.0.5 database and want to use the
: thin driver, you should be OK.
: If you are connecting to an 8.0.5 database and want to use the
: OCI driver, see the instructions below for switching driver
: versions.
: If you are connecting to an 8.0.5 database on Linux, there is a
: bug which does not currently allow this connection.
: If you are connecting to an 8.0.4 or earlier database (back to
: 7.2) and want to use the JDBC thin or OCI drivers, see the
: instructions below for switching driver versions.
: If you are connecting to a Personal Oracle database, use the
OCI
: bequeath method to connect.
: If you are connecting to an Oracle Lite 3.5 database, you will
: need to upgrade the drivers that came with JDeveloper 2.0
Beta.
: See the instructions below.
: Instructions for Switching Driver Versions (regular Oracle):
: 1. Exit from JDeveloper.
: 2. Open the jdeveloper.ini file in a text editor. This file is
: located in the JDeveloper bin directory.
: 3. Edit the IDE Classpath so one of the following appears
before
: ..\aurora\classes111.zip:
: ..\jdbc\lib\oci8\classes111.zip (to use the 8.0.5 thin or
OCI8
: driver)
: ..\jdbc\lib\oci7\classes111.zip (to use the OCI7 driver)
: 4. Save and close the jdeveloper.ini file.
: 5. Restart JDeveloper
: Optional steps to use the right driver at runtime within the
IDE
: - must be performed for each project that you will use the
: non-814 JDBC driver with:
: 1. Select Project Properties from the Project menu for the
: project you are working on.
: 2. Make sure the library for the non-814 JDBC driver you want
to
: use appears in the
: libraries list (if not, click Add to add it).
: 3. Select the non-814 JDBC driver you want to use and drag it
to
: the top of the list. It must appear BEFORE BOTH of the
following
: libraries:
: a. Oracle 814 JDBC
: b. Enterprise Java Beans (this library also pulls in the 814
: JDBC driver)
: Notes on using the 8.0.5 drivers:
: 1. If you are using the 8.0.5 thin driver to connect to a local
: database, type the name of your host, or the IP address. Do
not
: use 'localhost' for the host name.
: Instructions for upgrading to Oracle Lite 3.5 drivers:
: 1.Install Oracle Lite 3.5
: 2.Find the following files in <ORACLE_HOME>:
: olad2035.dll
: olite35.msb
: oljac35.dll
: oljdbc35.dll
: olobj35.dll
: olod2035.dll
: olodmg35.dll
: olrep835.dll
: olsql35.dll
: (these files will be refered as olite35-dlls from now on)
: 3.Copy olite35-dlls into <JDeveloper_Home>\bin
: 4.Create directory <JDeveloper_Home>\jdbc\lib\olite35
: 5.Copy <ORACLE_HOME>\Lite\Classes\olite35.jar into
: <JDeveloper_Home>\jdbc\lib\olite35
: 6.Open <JDeveloper_Home>\bin\JDeveloper.ini, replace
: "olite30\olite.jar" with "olite35\olite35.jar" in the
: IDE_CLASSPATH.
: 7.Launch JDeveloper 2.0
: 8.Create a Oracle Lite 3.5 Library:
: a. Select Tools | Default Project Properties from the menu.
: b. Click the Libraries button.
: c. Click the New button to create a new library.
: d. Name: Oracle Lite 3.5 JDBC
: e. Classpath:<JDeveloper_Home>\jdbc\lib\olite35\Olite35.jar
: f. Click OKto create the library
: 9.Select the Oracle Lite 3.0 JDBC library in the Library list
: and
: click the Remove button.
: 10. Click Add and select your newly created Oracle Lite 3.5
JDBC
: library from the list. Click OK to add it.
: If you already have a project defined and opened in the IDE,
: select Project Properties from the Project menu, and make sure
: your new Oracle Lite 3.5 library is listed in the libraries
: list.
: If not, use steps 9 and 10 above to add it to your project.
: phil (guest) wrote:
: : Hi,
: : I am trying to create a java application using the
: : Data Form component. I keep getting the error message
: : TN adapter unable to make connection when I use the data form
: : wizard. Can I use JDeveloper 2.0 Beta with Oracle 8.0.4?
: : TIA,
: : Phil
null -
Getting Sql Exception while using JDBC/ODBC to Excel 2007 through Java
Iam getting the SQLexception by trying to connect using JDBC/ODBC to Excel 2007 through Java. Any Guys can tell abt this problem. java.sql.SQLException: [Microsoft][ODBC Excel Driver] External table is not in the expected format.
at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcConnection.initialize(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at InteractWithExcel.main(InteractWithExcel.java:13)From [Google Groups|http://groups.google.co.uk/group/sybase.public.powerbuilder.general/browse_frm/thread/97fbab02a5e6d45b]
To use Excel as a datasource, you need to defined a named range in the spreadsheet, with the first row containing the column names. -
Get a tns connection through JDBC.
Hi
I am trying to get tns connection using jdbc to the dabatase. The following code returns an exception "SQLException: IO Error: Unknown host specified ". Most likely becuase the string is missing a host address. Does a tns connection require a host to be included? I am under the assumption, there are only 3 tns properties - username, password and a Net Service Name (e.g. ORCL) . Thanks.
string url = jdbc:oracle:thin:@//username/password/service_name";
try {
Class.forName("oracle.jdbc.OracleDriver");
} catch (java.lang.ClassNotFoundException e) {
System.err.print("ClassNotFoundException: ");
e.printStackTrace();
try {
Connection connection = DriverManager.getConnection(url);
new ConnectionInfo(connection);
} catch (SQLException ex) {
System.err.println("SQLException: " + ex.getMessage());
Edited by: 875864 on 10-Jan-2012 16:53The thin driver needs the host; it doesn't use the tnsnames.ora file
Here is a simple set of code to get a connection
String driver = "oracle.jdbc.OracleDriver";
String url = "jdbc:oracle:thin:@host:port:sid";
String username = "SCOTT";
String password = "tiger";
try {
Class.forName(driver);
Connection con = DriverManager.getConnection(url, username, password);
...This link shows how to use the thin or the OCI (thick) drivers. The OCI driver needs an Oracle client and will use tnsnames.ora
http://www.orafaq.com/wiki/JDBC -
Can not deploy a report using JDBC connection on CR2008 Server
Hi Group,
I have a report created with JDBC connection. When I tried to add it to CR2008 server, it gives an error - "An unexpected error has occurred ". Basically I want to add a report to a public folder via CMC. I am using adminstrator account.
Then I thought I need to add JDBC driver into CR2008 server. so I put oracle jdbc jar into CR2008 server classpath and add JDBC connection info into CRConfig.xml. but I still got the same error.
I also tried:
- Change the report to use native Oracle driver rather than JDBC. The deployment succeeded (but this is not what I want)
- Add a data source connection via Business View Manager, but no luck.
I know how to use/change jdbc connection with programtic way, but I just want to know if I want to use built-in components in CR2008 server without any coding the reports can be deployed and managed.
Thanks in advance.
DennisHello Will,
Crystal Reports supports connections to JDBC/JNDI out of the box, and have done so for a while, whether stand-alone or published to Enterprise.
To specify where the server would search for the JDBC driver jar files, you'd change the classpath tag found in the CRConfig.xml file found on the machine where the Crystal Reports Page or Job Server is running.
For early Crystal Enterprise 10 and before, it used Java Native Interface (JNI) to start the Java process to retrieve the data from the JDBC connection.
For later Crystal Enterprise 10 and later, it starts off a "Java Server" process, and communicates to the Crystal Reports process via CORBA TCP/IP connection.
Commonissues that may arise: (1) CRConfig.xml not configured properly, (2) unable to start or communicate to the "Java Server" because of permissions or firewall.
Note that this is a separate connectivity map from using ADO or ADO.NET.
Sincerely,
Ted Ueda -
Problem using JDBC to connect to WBEM ODBC driver
Hello,
I've got a problem to connect to WBEM ODBC driver using JDBC. The error is:
exception due a la requetejava.sql.SQLException: [Microsoft][WBEM ODBC Driver]Unable to connect
When I try to connect to a MS access database, replacing only the ODBC source name, it's working. I can access to the MS access db. But when I put the WMI ODBC source name, WMI, I've got this error.
Does anybody know what could happened? Is it possible to access to WMI through JDBC? With MS access, accessing WMI ODBC is working !
Thanks very much for your help.
Here is the part of the source code :
import java.sql.*;
import java.io.*;
public class Main_1 {
/** Creates a new instance of Main_1 */
public Main_1() {
* @param args the command line arguments
public static void main(String[] args) {
try {
String url = "jdbc:odbc:WMI";
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con = DriverManager.getConnection(url);
String query = "Select * from Win32_Processor";
//String query = "Select * from test;";
ResultSet results;
Statement stmt = con.createStatement();
results = stmt.executeQuery(query);
//System.out.println (results);
catch(Exception e){
System.out.println("exception due a la requete" + e);
e.printStackTrace();
}you have to first start the network listener before you can run the program
start TNSLSNR before running the jdbc program -
Trouble connecting to the Microsoft SQL Server 2005 using JDBC Connection
Hi,
I am unable to connect to the Microsoft SQL Server 2005 using JDBC Connection. Kindly tell me steps to connect to the SQL Server using JDBC. The error message that I am getting while creating a data source is :
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/JDBCConnector_KedDS.xml". [id = StartupError]
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 33 more
at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at javax.management.MBeanException.writeObject(MBeanException.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)i'm using jcreator pro
jdk i.6
mssql server 2005
and downloaded the jdbc driver( i noticed that the msutil.jar and msbase.jar are not in the folder avalable on microsoft site Microsoft SQL Server 2005 JDBC Driver so i installed
Microsoft SQL Server 2000 Driver for JDBC 1st and just changed the jqljdb.jar file with the one available in Microsoft SQL Server 2005 JDBC Driver )
and set the path of the CLASSPATH to a folder which name has no spaces
and tried Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
and Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
and tried compiling and running with command prompt
and still have the same exception which occurs at runtime
"An exception has occured: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver"
i really need help
Maybe you are looking for
-
Can't Drag and Drop songs onto Shuffle. Autofill Doesn't work either
I know that many people have been having this same problem. The Shuffle is recognized by the computer AND even iTunes. It shows up in the playlist, but when you try to Autofill or even Drag and Drop the songs individual, the songs, for lack of a bett
-
How to Increase width of heading in search help list?
Hi..all.. I have created a search help exit with 7 fields in the output list. When I view the search help in the webdynpro screen, iam not able to view the result fully.,ie. the results are crumbled. the headings and data are not displayed fully. For
-
Hi Friends, Please clarify me the difference between Payment terms and Inco terms (PO-Header data). I have gone thru SAP help, but I am not clear. Please help. Best regards, Raman.
-
How to send a new ringtone to my Nokia 1600 ? From my PC or from anybody else more capable Mobile... I have the midi; what is the maximum size ? I didn't find lot of info about OTA SMS format :-( ! Philippe
-
Hello everyone, I'm using an httpservice with a php script and resultformat "e4x". When I call my script directly in my browser, I receive a well formatted XML file (I think so as I can even see the closing tag </elements>). But, in my application, t