Old plain JDBC connection managed by JEE container?

Hi,
I wonder, if there is an option to tell the JEE container to manage my old plain JDBC connection.
My current way
@Stateless
public class MyClass {
   @Resource(name = "jdbc/my-database")
   private DataSource dataSource;
   public void doSomething() {
      Connection conn = dataSource.getConnection();
      try {
          // Some stuff
      } finally {
         DatabaseUtils.closeSilent(conn);
   }Is there a way to get a connection instead of a data source?
Thanks a lot

Yes you're right.
What I mean, if there a way that the JEE container will open and close the connection I need.
If I use the datasource, I've to open a connection and I've to ensure that this connection will be "closed", so the pool manager can reuse this connection.
But I think, there is no way for something like this, or not:
@Resource
private Connection connection;

Similar Messages

  • Auto-Commit and Pooled JDBC Connections

    Forum Members,
    If I am using Oracle Pooled JDBC Connections in the OC4J container is auto-commit set to "true" by default?
    If I set auto-commit to "false" and then close the logical connection, when that connection is handed out again on a later call to getConnection(), is auto-commit automatically set back to "true"?
    Thanks,
    Richard

    Richard,
    Pardon me if I am stating the obvious, but you could test that in your code by invoking the getAutoCommit() method in interface java.sql.Connection.
    My experience (with OC4J stand-alone versions up to -- and including -- 10.1.2) is that the behaviour depends on which data source you have configured. For example, if you have defined an "ejb-location" attribute in your "data-sources.xml" file, and you use that as your JNDI lookup for your data source, then OC4J handles transactions and you shouldn't deal with "auto-commit" at all. See the following post for more details:
    Re: OC4J 10.1.3 Preview 4 - Global transaction active
    But if you have defined a "location" attribute and use that, then you do need to handle transactions explicitly.
    Hope this helps.
    Good Luck,
    Avi.

  • Configure JDBC connection ERROR: no ocijdbc9 in java.library.path

    ERROR: no ocijdbc9 in java.library.path
    step 6 is where I need help!? thanx.
    When configuring a database connection, I chose
    1. Oracle JDBC (connection type)
    2. Authentication (username/password of my D2K repository)
    3. Driver: oci8
    4. Hostname: pmurphy1 (my local machine where my db is)
    5. Port: 1521 default (odbc works on this)
    * 6. Enter custom JDBC url (? please help ?) left blank!!
    I really wanna get started with this cool toy!!!
    Cheers,
    Paully

    I am assuming you are using JDeveloper 3.2x
    Please see the online help for additional details.
    Search help for "JDBC Connection Properties" - With the
    quotations and you will find a page names "JDBC Connection
    Properties"
    This page contains the following info and additional links.
    -John
    ------------- COPIED FROM HELP ---------------
    Oracle JDBC-OCI8 Driver
    Use this type 2 driver when creating a Java application that
    runs against an Oracle8i server. This is a thick driver
    optimized for the Oracle8i database: it cannot be used with
    applets. This driver handles any database protocol (TCP, IPX,
    BEQ, and so on). It is required for applications which are run
    from the machine they are stored on. It can also be used against
    an Oracle7 database.
    This driver requires client software installation. The project
    must also include the correct version of the driver in a library
    and include no other Oracle JDBC library. This driver is
    included in the default Oracle JDBC library for all projects.
    The library is named Oracle 8.1.7 JDBC and it includes both the
    Thin JDBC and JDBC-OCI8 driver library components. For all OCI
    and type 2 JDBC drivers, see Connection Requirements for OCI and
    Type 2 JDBC Drivers.
    ------------- COPIED FROM HELP ---------------

  • Foreach Loop Container with a Data Flow Task looking for file from Connection Manager

    So I have a Data Flow Task within a Foreach Loop Container. The Foreach Loop Container has a Variable Mapping of User:FileName to pass to the Data Flow Task.
    The Data Flow Task has a Flat File Source since we're looking to process .csv Files. And the Flat File Source has a Flat File Connection Manager where I specified the File name when I created it. I thought you needed to do this even though it won't really
    use it since it should be getting its File name from the Foreach Loop Container. But when attempting to execute, it is blowing up because it seems to be looking for my test file name that I indicated in the Flat File Connection Manager rather than the file
    it should be trying to process in User:FileName from the Foreach Loop Container.
    What am I doing wrong here??? I thought you needed to indicate a File name within the Flat File Connection Manager even though it really won't be using it.
    Thanks for your review...I hope I've been clear...and am hopeful for a reply.
    PSULionRP

    The Flat File Connection manager's Connection String needs to be set to reference the variable used in the ForEach Loop:
    Arthur My Blog

  • JDBC connection pool getting killed in Managed Server

    I am running a managed server in a Windows2000 SP2,WebLogic 6.0 SP2, JDK 1.3.1_01
    environment
    When I start the managed server I get the following error:
    Attempting to create Connection Pool for the Pool Registry Entry : perfectFitPool
    <Nov 24, 2001 9:03:15 PM EST> <Error> <JDBC Connection Pool> <The pool 'perfectFitPool
    was created successfully. But it must be killed because of: creating Admin MBean
    on a managed server>
    weblogic.common.ResourceException: creating Admin MBean on a managed server
    at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:540)
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:766)
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:754)
    at ConnectionPoolStartupWl6.createDynamicConnectionPool(ConnectionPoolStartupWl6.java:64)
    at ConnectionPoolStartupWl6.startup(ConnectionPoolStartupWl6.java:45)
    at weblogic.t3.srvr.StartupClassRunner.invokeStartup(StartupClassRunner.java:112)
    at weblogic.t3.srvr.StartupClassRunner.invokeClass(StartupClassRunner.java:93)
    at weblogic.t3.srvr.StartupClassRunner.run(StartupClassRunner.java:61)
    at java.lang.Thread.run(Thread.java:484)
    <Nov 24, 2001 9:03:15 PM EST> <Critical> <WebLogicServer> <Failed to invoke startup
    class
    "ConnectionPoolStartupWl6", weblogic.common.ResourceException: creating Admin
    MBean on a managed server>
    <Nov 24, 2001 9:03:15 PM EST> <Notice> <WebLogicServer> <WebLogic Server started>
    Any idea on what could be wrong.
    Thanks in advance,
    Adarsh Ronald

    Hi Adarsh,
    You can not create Admin MBean on managed server. Managed server can
    have only cached copies of Admin MBeans with type ConfigMBean.
    Could you show us what you do @ ConnectionPoolStartupWl6?
    Regards,
    Slava Imeshev
    "Adarsh Ronald" <[email protected]> wrote in message
    news:3c0054eb$[email protected]..
    >
    I am running a managed server in a Windows2000 SP2,WebLogic 6.0 SP2, JDK1.3.1_01
    environment
    When I start the managed server I get the following error:
    Attempting to create Connection Pool for the Pool Registry Entry :perfectFitPool
    <Nov 24, 2001 9:03:15 PM EST> <Error> <JDBC Connection Pool> <The pool'perfectFitPool
    was created successfully. But it must be killed because of: creating AdminMBean
    on a managed server>
    weblogic.common.ResourceException: creating Admin MBean on a managedserver
    atweblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java
    :540)
    atweblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:
    766)
    atweblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:
    754)
    atConnectionPoolStartupWl6.createDynamicConnectionPool(ConnectionPoolStartupWl
    6.java:64)
    at ConnectionPoolStartupWl6.startup(ConnectionPoolStartupWl6.java:45)
    atweblogic.t3.srvr.StartupClassRunner.invokeStartup(StartupClassRunner.java:11
    2)
    atweblogic.t3.srvr.StartupClassRunner.invokeClass(StartupClassRunner.java:93)
    at weblogic.t3.srvr.StartupClassRunner.run(StartupClassRunner.java:61)
    at java.lang.Thread.run(Thread.java:484)
    <Nov 24, 2001 9:03:15 PM EST> <Critical> <WebLogicServer> <Failed toinvoke startup
    class
    "ConnectionPoolStartupWl6", weblogic.common.ResourceException: creatingAdmin
    MBean on a managed server>
    <Nov 24, 2001 9:03:15 PM EST> <Notice> <WebLogicServer> <WebLogic Serverstarted>
    >
    Any idea on what could be wrong.
    Thanks in advance,
    Adarsh Ronald

  • JDBC-Connection in SQL-Developer via Connection-Manager gives ORA-12529

    Hi !
    This is a followup of this Thread: https://community.oracle.com/thread/3568462
    I have the same problem but I have ConnectionManager 11g (11.2.0.1.0) , which doesn't know the setting for AUTHENTICATION_LEVEL=0
    And I have to use JDBC, so the OCI/Thick-driver is no option for me.
    The same error is raised when I use JDBC with Eclipse,...
    SQL-Plus over the Connection-Manager works without any problems.
    The ruleset of my cman.ora is:
    (rule_list=
        (rule=
           (src=*)(dst=*)(srv=*)(act=accept)
           (action_list=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))
    The error is:
    Listener refused the connection with the following error:
    ORA-12529, TNS:connect request rejected based on current filtering rules
    Anyone got jdbc-connections over ConnectionManager 11g+ running?
    Charly

    Using Windows XP/Vista...
    After testing in our environment, it appears that SQL Developer 1.5.1 (5440) does in fact ignore the TNS_ADMIN environment variable and ONLY looks in the Oracle Home directory (network/admin). We define a central network location for our tnsnames file and have the tns_admin setup to point there instead of locally for our users.
    When selecting to add a new connection (in 1.5.1, it works in previously releases... meaning 1.2.something) and selecting TNS, the drop-down remains empty. However, if I exit SQL Developer and then copy the tnsnames file to the local network/admin directory I can then re-launch SQL Developer and the drop-down is populated. Exiting SQL Developer again, deleting the local copy of tnsnames, and then launching SQL Developer yet again results in the drop-down being empty.
    All other Oracle-related applications function as expected (as they have for years) using the TNS_ADMIN environment variable.
    Any suggestions/ideas?

  • Connection Manager & JDBC

    I wrote an applet who connects to a database on a network where WebServer and Oracle Server were in the same host. Now I have to migrate the applet to a network where the Webserver and the database server are in diferent hosts. Because of security issues I can't make the connection to the database.
    I know that the solution is using a signed applet or with connection manager. The problem is that I have no permision to configure the WebServer neither time or money for an applet certificate.
    Is there any other way to access the database?

    applet security rules can be annoying.
    those are the only options.
    setting up Oracle's connection manager on your web server platform is easier and quicker to do than signing the applet.

  • Why no bluetooth in connection manager ?

    PC Suite 6.80.22 cannot connect to my phone (6021) via bluetooth.
    When I run the Nokia connection manager, I can only choose infrared, serial data cable and usb data cable.
    I do not have bluetooth !
    When I use the windows explorer, I can make a connection there and I can manage files (upload, remove, download).
    So I am sure my bluetooth device (Trust BT120) is installed and working correctly in my OS (Win2k SP4).
    In my device manager, the bluetooth device is reported as a lan device.
    I already re-installed the pc suite.
    My question is : why don't i have bluetooth in the connection manager ?

    Are you using a Mac?
    If yes the following is irellevant...just incase..
    Connecting the Phone to a USB Bluetooth Dongle. Using PC Suite.
    Yesterday, I stayed up all night to figure this out. I called nokia support to see what they can do, and apparently the new drivers from Sitecom (the BT adaptor that I use) creates a "Cloak" over the Microsoft ones. (This is only if you have SP2!!)
    Required for these steps:
    ~PC Running Windows XP on Service Pack 2. (how do I know if I have Service pack 1/2? Go to Start > Controll Panel > Classic View (on the top left corner, or if you already are then ignore this) > System. In system it will say which serivce pack you are running.
    ~PC Suite version 6.80.22 or later.
    ~Bluetooth Adaptor + Drivers for it
    ~Nokia Phone supporting a bluetooth In/Out connection.
    ~Patience (this may take half an hour depending on your PC Spec) (Took me 15 minutes)
    So here is what I did:
    First of all close all programs that you dont need running.
    Start > Controll Panel > Add Remove Programs > Sitecom drivers
    Remove ALL Sitecom (or which ever company's you use).
    Reboot Computer.
    Next put the CD/Floopy in the PC or folder that you downloaded have ready on your desktop, containing the drivers required for your adaptor.
    If a autorun comes up cancel it.
    Plug in your bluetooth adaptor to a permanent usb port! The port you plug it into will be the only and only port that you can run bluetooth from, dont ask me why. So use a good safe place. (I put mine in the back of my PC, not the front.)
    Windows will now say that it has found new hardware. It will ask you if it can search the internet for drivers, click > Yes This Time Only.
    It will search and wont find anything.
    Now it will ask you if it can search for drivers on the PC, click : Yes, and tell it where the drivers are located, CD/Floppy, Folder. eg: E:\Sitecom/drivers/XP
    Let it install. It will finish, then suddenly re-open.
    Run the same step as above again. (dont ask me why..it just installes some more drivers.)
    Finally it will finish and say that your software is ready to be used.
    DONT TRY TO USE IT! THE SOFTWARE REQUIRED ISNT RUNNING YET. DONT RUN PC SUITE EITHER! DONT QUIT PC SUITE, AND DONT TRY TO USE THE CONNECTION MANAGER.
    REBOT the PC.
    Now when you go into PC Suite > Connection Manager, you should find a new connection. In my case:
    Bluetooth (Sitecom)
    and the old bluetooth connection looks like this:
    Bluetooth (Microsoft)
    The connection is very fast and stable. You can browse the phone as if it is cable connected which is awsome. Transfer speed depends on your adaptor, but it averages between 1 - 3 Megabites Per Second.
    Hopefully this works for you too!
    Good Luck,
    Tal
    I own a 5210, 5140 and now..the new 3250. Symbian 60 Series OS 3.0 ..just the best.

  • Database Table Resource via Oracle RAC connection Manager

    Hello,
    Our current IDM 8.1 syncs off a HR Database Table using the Database Table connector.
    Our DBA's are moving the view into an Oracle RAC environment.
    Question: Is there a way for us to connect and sync off our DB table through an Oracle RAC connection manager.
    I understand that for the IDM repository, this is possible.
    jdbc:oracle:thin@(DESCRIPTION =
    (ADDRESS_LIST =
    (LOAD_BALANCE = ON)
    (FAILOVER = ON)
    (ADDRESS = (PROTOCOL = TCP)(HOST = server1.ser.com)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = server2.ser.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db.com)
    servers server1 and server2 are oracle connection managers
    Thank you for your input,
    -RC

    We moved the repository to Oracle RAC recently. The syntax to switch to the new databasecluster was something like this:
    lh setRepo -tOracle -ujdbc:oracle:thin:@//dbcluster1.domain:1521/service_idm.oradb.domain -Uwaveset -Pwachtwoord
    For the 'lh setRepo' command the old database had to be up, and we had to use the old ojdb5.jar. After that we switched to ojdb6.jar.
    One of our resources is a database table with HR data in the same database. The following Database Access Parameters work for us:
    Database Type:      Oracle
    JDBC Driver:      oracle.jdbc.driver.OracleDriver
    JDBC URL Template:      jdbc:oracle:thin:@//%h:%p/%d
    Host :     dbcluster1.domain
    Database: service_idm.oradb.domain
    Port: 1521
    Greetings,
    Marijke

  • JDBC Connection in ISA 7.0

    Hi,
    Where can we set JDBC connection for local SAP-J2EE DB for ISA 7.0.
    Please provide some information.
    Regards,
    Devender V

    The default connections are preconfigured for Web Channel applications.
    The actual resource references are made in web.xml
         <!-- security settings for administration area -->
         <resource-ref>
              <res-ref-name>SAP/CRM/b2b</res-ref-name>
              <res-type>javax.sql.DataSource</res-type>
              <res-auth>Container</res-auth>
         </resource-ref>
         <!--JDO connection factory lookup name, required-->
         <resource-ref>
              <res-ref-name>jdo/defaultPMF</res-ref-name>
              <res-type>javax.resource.cci.ConnectionFactory</res-type>
              <res-auth>Container</res-auth>
         </resource-ref>
    This res-ref-name> is the alias of the JDBC Datasource.
    You can find the JDBC connection / aliases either using Visual Admin or NWA Hope you know how to lausch them. I will explain this in Visual Admin.
    After launching Visual Admin, go to Server -> Services -> JDBC Connector of the Cluster in the navigator panel. After that in the working panel, expand Data Sources in Resources. You will find the default data source SAP<instance>DB . If you select this Data source, the details are shown.
    When you install the J2EE engine, the passwords of the JDBC data source SAP<instance>DB is requested  and stored in the and can be managed using the Config Tool. Here you can change the default user, password, connection-string (URL) and the driver.
    You can create a new alias if you want in the J2EE engine, but you have to diligently integrate it to your web application resource to use it in the application.
    Easwar Ram
    http://www.parxlns.com

  • Two jdbc connections in one transaction

    Hi<br>
              <br>
              In a method of a container managed ejb session bean I have two jdbc connections. I've expected, that they will be in the same transaction, so results of any actions performed with first connection will be visible for the second connection, but it is not. <br>
              I've checked, that there are two sessions at the database, so it seams that there are simply separate transactions. Is it a problem with a ejb-jar.xml (will paste it later), datasource (driver - Oracle Thin non-XA; 1PC selected) or such behaviour can not be achieved in WLS ? <BR>
              <BR>
              regards
              <br>
              <BR><?xml version="1.0" encoding="UTF-8"?>
              <BR>
              <BR><!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
              <BR>
              <BR><ejb-jar >
              <BR>
              <BR>     <description><![CDATA[No Description.]]></description>
              <BR>     <display-name>ConnectionTest1</display-name>
              <BR>     
              <BR>     <enterprise-beans>
              <BR>          <session >
              <BR>               <description><![CDATA[]]></description>
              <BR>               
              <BR>               <ejb-name>ConnectionTest1</ejb-name>
              <BR>               
              <BR>               <home>pl.axit.test.ConnectionTest1Home</home>
              <BR>               <remote>pl.axit.test.ConnectionTest1</remote>
              <BR>     <ejb-class>pl.axit.test.ConnectionTest1Bean</ejb-class>
              <BR>     <session-type>Stateless</session-type>
              <BR>     <transaction-type>Container</transaction-type>
              <BR>     
              <BR>     <resource-ref >
              <BR>          <res-ref-name>jdbc/wowrite</res-ref-name>
              <BR>          <res-type>javax.sql.DataSource</res-type>
              <BR>          <res-auth>Container</res-auth>
              <BR>     </resource-ref>
              <BR>     </session>
              <BR>     </enterprise-beans>     
              <BR>     
              <BR>     <assembly-descriptor>
              <BR>          <container-transaction>
              <BR>               <description/>
              <BR>               <method>
              <BR>                    <description/>
              <BR>                    <ejb-name>ConnectionTest1</ejb-name>
              <BR>                    <method-name>*</method-name>
              <BR>               </method>
              <BR>               <trans-attribute>Required</trans-attribute>
              <BR>          </container-transaction>          
              <BR>
              <BR>     </assembly-descriptor>
              <BR></ejb-jar>

    Hi,
              are you using XA transactions? Two separate JDBC Connections treated
              within one transactional context will require two phase commit (via
              Emulation or an XA database driver) Please check the connections
              settings within your datasources.
              Rgds,
              Axel van Lil (LMIS.de)
              Lukas Uruski schrieb:
              > I forgot to add, that in administration console in server_name > Monitoring > JTA parameter "Transactions Total Count" increases by one each time method from previous post is invoked.

  • Error retrieving JDBC connection from remote client (WLS 10.0)

    Hallo,
    I get an error when I try to retrieve a JDBC connection from a WLS datasource using a remote client. My Weblogic server version is: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184
    I use the following code to retrieve the JDBC connection:
    Hashtable<String,String> ctxEnv = null;
    InitialContext ctx = null;
    DataSource dataSource = null;
    Connection con = null;
    ctxEnv = new Hashtable<String,String>();
    ctxEnv.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    ctxEnv.put(InitialContext.PROVIDER_URL, "t3://localhost:7001");
    ctx = new InitialContext(ctxEnv);
    dataSource = (DataSource) ctx.lookup("datasources/XXX");
    con = dataSource.getConnection();
    When I execute this code with the weblogic.jar in the classpath everything works fine. However, when I put the wlfullclient.jar in the classpath which I created using the JAR Builder Tool I get the follwoing error:
    weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
    at weblogic.jdbc.common.internal.RmiDataSource_1001_WLStub.getConnection(Unknown Source)
    at net.schufa.enterprise.utilities.database.test.JDBCSupportTest.test_getConnection_manually(JDBCSupportTest.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
    weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
    ... 17 more
    Caused by: weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
    at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:938)
    at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1009)
    at weblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:452)
    at weblogic.rjvm.t3.MuxableSocketT3.hasException(MuxableSocketT3.java:373)
    at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:755)
    at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:708)
    at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:307)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused by: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
    at weblogic.diagnostics.instrumentation.rtsupport.InstrumentationSupportImpl.getMonitor(InstrumentationSupportImpl.java:54)
    at weblogic.diagnostics.instrumentation.InstrumentationSupport.getMonitor(InstrumentationSupport.java:201)
    at weblogic.jdbc.rmi.SerialConnection.<clinit>(SerialConnection.java)
    at sun.misc.Unsafe.ensureClassInitialized(Native Method)
    at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
    at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
    at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
    at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
    at java.lang.reflect.Field.getLong(Field.java:527)
    at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1586)
    at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52)
    at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:408)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400)
    at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
    at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:531)
    at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
    at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
    at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36)
    at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
    at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
    at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
    at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:223)
    at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:174)
    at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:435)
    at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
    at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:808)
    at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
    ... 4 more
    Can please anyone tell me what's going on there? What really astonishes me is that the class mentioned in the stacktrace is neither present in the wlfullclient.jar nor in the weblogic.jar, but using the weblogic.jar everything works fine. Any hint would be appreciated so much ...
    Here is the log written when is created the wlfullclient.jar:
    C:\Programme\bea\weblogic10.0\server\lib>java -jar ../../../modules/com.bea.core.jarbuilder_1.0.1.0.jar
    Setting Manifest:Class-Path = schema/weblogic-container-binding.jar schema/weblogic-domain-binding.jar schema/diagnostic
    s-binding.jar schema/diagnostics-image-binding.jar schema/kodo-conf-binding.jar wlcipher.jar xmlx.jar ojdbc14.jar jconn2
    .jar jConnect.jar EccpressoAsn1.jar EccpressoCore.jar EccpressoJcae.jar mysql-connector-java-commercial-5.0.3-bin.jar w
    lbase.jar wlutil.jar wlsqlserver.jar wldb2.jar wlsybase.jar wloracle.jar wlinformix.jar wlw-langx.jar ../../common/lib/p
    dev.jar debugging.jar wlw-system.jar ../../javelin/lib/javelinx.jar jcom.jar weblogic-L10N.jar
    Setting Manifest:Implementation-Vendor = BEA Systems
    Setting Manifest:Implementation-Title = Client jar for WebLogic Server 10.0 Thu Oct 18 20:17:44 EDT 2007 1005184
    Setting Manifest:Implementation-Version = 10.0.1.0
    Creating new jar file: wlfullclient.jar
    Integrating jar -->(0)/(0)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(0)/(31337)/(31337)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar -->(0)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
    Integrating jar <--(0)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
    Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
    Integrating jar <--(1)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
    Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ja_10.0.1.0.jar
    Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ko_10.0.1.0.jar
    Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.CN_10.0.1.0.jar
    Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.TW_10.0.1.0.jar
    Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
    Integrating jar <--(1)/(31410)/(73)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
    Integrating jar -->(1)/(31410)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(31487)/(77)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
    Integrating jar -->(1)/(31487)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
    Integrating jar <--(1)/(32047)/(560)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
    Integrating jar -->(1)/(32047)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
    Integrating jar <--(1)/(32265)/(218)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
    Integrating jar -->(1)/(32265)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
    Integrating jar <--(1)/(32277)/(12)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
    Integrating jar -->(1)/(32277)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
    Integrating jar <--(1)/(32294)/(17)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
    Integrating jar -->(1)/(32294)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
    Integrating jar <--(1)/(32321)/(27)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
    Integrating jar -->(1)/(32321)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
    Integrating jar <--(1)/(32446)/(125)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
    Integrating jar -->(1)/(32446)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
    Integrating jar <--(1)/(32895)/(449)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
    Integrating jar -->(1)/(32895)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
    Integrating jar <--(1)/(32908)/(13)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
    Integrating jar -->(1)/(32908)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
    Integrating jar <--(1)/(32963)/(55)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
    Integrating jar -->(1)/(32963)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
    Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger$LoggableMessageSpiImpl.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
    Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
    Integrating jar <--(1)/(33817)/(854)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
    Integrating jar -->(1)/(33817)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
    Integrating jar <--(1)/(33901)/(84)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
    Integrating jar -->(1)/(33901)/C:\Programme\bea\modules\javax.activation_1.1.jar
    Integrating jar <--(1)/(33945)/(44)/C:\Programme\bea\modules\javax.activation_1.1.jar
    Integrating jar -->(1)/(33945)/C:\Programme\bea\modules\javax.annotation_1.0.jar
    Integrating jar <--(1)/(33958)/(13)/C:\Programme\bea\modules\javax.annotation_1.0.jar
    Integrating jar -->(1)/(33958)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
    Integrating jar <--(1)/(33964)/(6)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
    Integrating jar -->(1)/(33964)/C:\Programme\bea\modules\javax.ejb_3.0.jar
    Integrating jar <--(1)/(34022)/(58)/C:\Programme\bea\modules\javax.ejb_3.0.jar
    Integrating jar -->(1)/(34022)/C:\Programme\bea\modules\javax.jdo_2.0.jar
    Integrating jar <--(1)/(34119)/(97)/C:\Programme\bea\modules\javax.jdo_2.0.jar
    Integrating jar -->(1)/(34119)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
    Integrating jar <--(1)/(34162)/(43)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
    Integrating jar -->(1)/(34162)/C:\Programme\bea\modules\javax.jms_1.1.jar
    Integrating jar <--(1)/(34221)/(59)/C:\Programme\bea\modules\javax.jms_1.1.jar
    Integrating jar -->(1)/(34221)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
    Integrating jar <--(1)/(34319)/(98)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
    Integrating jar -->(1)/(34319)/C:\Programme\bea\modules\javax.jws_2.0.jar
    Integrating jar <--(1)/(34335)/(16)/C:\Programme\bea\modules\javax.jws_2.0.jar
    Integrating jar -->(1)/(34335)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
    Integrating jar <--(1)/(34602)/(267)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
    Integrating jar -->(1)/(34602)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
    Integrating jar <--(1)/(34637)/(35)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
    Integrating jar -->(1)/(34637)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
    Integrating jar <--(1)/(34730)/(93)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
    Integrating jar -->(1)/(34730)/C:\Programme\bea\modules\javax.resource_1.5.jar
    Integrating jar <--(1)/(34799)/(69)/C:\Programme\bea\modules\javax.resource_1.5.jar
    Integrating jar -->(1)/(34799)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
    Integrating jar <--(1)/(34869)/(70)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
    Integrating jar -->(1)/(34869)/C:\Programme\bea\modules\javax.transaction_1.1.jar
    Integrating jar <--(1)/(34889)/(20)/C:\Programme\bea\modules\javax.transaction_1.1.jar
    Integrating jar -->(1)/(34889)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
    Integrating jar <--(1)/(34989)/(100)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
    Integrating jar -->(1)/(34989)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
    Integrating jar <--(1)/(35019)/(30)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
    Ignoring unresolved jarC:\Programme\bea\modules\jaxp-api.jar
    Ignoring unresolved jarC:\Programme\bea\modules\jax-qname.jar
    Ignoring unresolved jarC:\Programme\bea\modules\activation.jar
    Ignoring unresolved jarC:\Programme\bea\modules\servlet.jar
    Integrating jar -->(1)/(35019)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
    Integrating jar <--(1)/(35063)/(44)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
    Integrating jar -->(1)/(35063)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
    Integrating jar <--(1)/(35110)/(47)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
    Integrating jar -->(1)/(35110)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
    Ignoring Duplicate Entry javax/xml/namespace/QName.class also in C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
    Integrating jar <--(1)/(35167)/(57)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
    Integrating jar -->(1)/(35167)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
    Integrating jar <--(1)/(35423)/(256)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
    Integrating jar -->(1)/(35423)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
    Integrating jar <--(1)/(36825)/(1402)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
    Integrating jar -->(1)/(36825)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
    Integrating jar <--(1)/(36964)/(139)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
    Integrating jar -->(1)/(36964)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
    Integrating jar <--(1)/(36976)/(12)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
    Integrating jar -->(1)/(36976)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
    Ignoring Duplicate Entry utils/Schema.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry utils/dbping.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCConnectionPoolParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDriverParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertiesBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertyBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCXAParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(37133)/(157)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
    Integrating jar -->(1)/(37133)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/descriptor/SettableBean.class also in C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/descriptor/beangen/LegalChecks.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/descriptor/beangen/StringHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/descriptor/beangen/XMLHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
    Integrating jar <--(1)/(37226)/(93)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
    Integrating jar -->(1)/(37226)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/diagnostics/type/UnexpectedExceptionHandler.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(37264)/(38)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
    Integrating jar -->(1)/(37264)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
    Integrating jar <--(1)/(37289)/(25)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
    Integrating jar -->(1)/(37289)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
    Integrating jar <--(1)/(37335)/(46)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
    Integrating jar -->(1)/(37335)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
    Integrating jar <--(1)/(37343)/(8)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
    Integrating jar -->(1)/(37343)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Integrating jar <--(1)/(37389)/(46)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean$Helper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanBinder.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanImplBeanInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/BaseModelMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/Commo$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/Commo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoMBeanInstance.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanAttributeInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanConstructorInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanInfoSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanNotificationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanOperationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CommoOperationsException.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$1.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$VoidValue.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupportBase.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/RequiredModelMBeanWrapper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/SecurityMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/StandardInterface.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/TypedMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/ant/taskdefs/management/commo/antlib.xml also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/CustomMBeanImpl.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/DiabloCustomMBeanIntf.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/commo/commo.dtd also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/management/internal/mbean/SecurityReadOnlyMBean.template also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
    Integrating jar <--(1)/(37389)/(0)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
    Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(37548)/(159)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
    Integrating jar -->(1)/(37548)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(37583)/(35)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
    Integrating jar -->(1)/(37583)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
    Ignoring Duplicate Entry weblogic/rmi/extensions/server/_HeartbeatHelper_Stub.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(37612)/(29)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
    Integrating jar -->(1)/(37612)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
    Integrating jar <--(1)/(38016)/(404)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
    Integrating jar -->(1)/(38016)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
    Integrating jar <--(1)/(38217)/(201)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
    Integrating jar -->(1)/(38217)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
    Integrating jar <--(1)/(38543)/(326)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
    Integrating jar -->(1)/(38543)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
    Skipping native/aix/ppc64/libwlfileio2.so
    Skipping native/aix/ppc/libwlfileio2.so
    Skipping native/hpux11/IPF32/libwlfileio2.so
    Skipping native/hpux11/IPF64/libwlfileio2.so
    Skipping native/hpux11/PA_RISC64/libwlfileio2.sl
    Skipping native/hpux11/PA_RISC/libwlfileio2.sl
    Skipping native/linux/i686/libwlfileio2.so
    Skipping native/linux/ia64/libwlfileio2.so
    Skipping native/linux/x86_64/libwlfileio2.so
    Skipping native/solaris/sparc64/libwlfileio2.so
    Skipping native/solaris/sparc/libwlfileio2.so
    Skipping native/solaris/x64/libwlfileio2.so
    Skipping native/solaris/x86/libwlfileio2.so
    Skipping native/win/32/wlfileio2.dll
    Skipping native/win/64/wlfileio2.dll
    Skipping native/win/x64/wlfileio2.dll
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(38695)/(152)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
    Integrating jar -->(1)/(38695)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
    Integrating jar <--(1)/(38728)/(33)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
    Integrating jar -->(1)/(38728)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
    Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(38943)/(215)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
    Integrating jar -->(1)/(38943)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
    Skipping native/aix/ppc64/libterminalio.so
    Skipping native/aix/ppc/libterminalio.so
    Skipping native/hpux11/IPF32/libterminalio.so
    Skipping native/hpux11/IPF64/libterminalio.so
    Skipping native/hpux11/PA_RISC64/libterminalio.sl
    Skipping native/hpux11/PA_RISC/libterminalio.sl
    Skipping native/linux/i686/libterminalio.so
    Skipping native/linux/ia64/libterminalio.so
    Skipping native/linux/s3990/libterminalio.so
    Skipping native/linux/x86_64/libterminalio.so
    Skipping native/macosx/pps/libterminalio.jnilib
    Skipping native/solaris/sparc64/libterminalio.so
    Skipping native/solaris/sparc/libterminalio.so
    Skipping native/solaris/x64/libterminalio.so
    Skipping native/solaris/x86/libterminalio.so
    Skipping native/win/32/terminalio.dll
    Skipping native/win/64/terminalio.dll
    Skipping native/win/x64/terminalio.dll
    Ignoring Duplicate Entry weblogic/utils/StackTraceUtilsClient.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(39367)/(424)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
    Integrating jar -->(1)/(39367)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
    Integrating jar <--(1)/(39415)/(48)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
    Integrating jar -->(1)/(39415)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
    Integrating jar <--(1)/(39429)/(14)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
    Integrating jar -->(1)/(39429)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
    Integrating jar <--(1)/(39550)/(121)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
    Integrating jar -->(1)/(39550)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
    Ignoring Duplicate Entry commonj/timers/CancelTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/timers/StopTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/timers/Timer.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/timers/TimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/timers/TimerManager.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Integrating jar <--(1)/(39581)/(31)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
    Integrating jar -->(1)/(39581)/C:\Programme\bea\modules\com.bea.core.weblogic.workmanager_1.0.1.0.jar
    Ignoring Duplicate Entry commonj/work/RemoteWorkItem.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/work/Work.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/work/WorkCompletedException.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/work/WorkEvent.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
    Ignoring Duplicate Entry commonj/work/WorkExcep

    Dirk Ludwig wrote:
    Joe Weinstein wrote:[...]
    Hi. You should open an official support case,
    but it may be that we do not support
    external client JDBC with the client jar.Actually, I misspoke. I think we do supply a client
    jar, and that may be true
    what I said, but I see you're making your own. Can
    you find out what jar you're
    loading the InstrumentationSupport class from? That's
    the original location of
    the error, and that class doesn't exist in 10.0.Hi Joe, thanks for your reply.
    First of all, let me clarify what we did and why we did it: We have a stand-alone client application that needs to communicate with a Weblogic server using the t3 protocol (we don't want IIOP or HTTP tunneling). According to the official BEA documentation (see http://e-docs.bea.com/wls/docs100/client/basics.html and http://e-docs.bea.com/wls/docs100/client/t3.html) we needed to create the wlfullclient.jar file. We did this using the Weblogic JAR Builder Tool (see http://e-docs.bea.com/wls/docs100/client/jarbuilder.html). Unfortunatley we discovered the problem mentioned in my original post when we tried to run the client with that wlfullclient.jar.
    Regarding your classloading question: The InstrumentationSupportImpl class is located in the wlfullclient.jar, so it does exist in WLS 10.0 (it is also contained in the weblogic.jar). Unfortunately this JAR does not contain the required class "weblogic.diagnostics.instrumentation.InstrumentationDebug". I searched for this class and found it in the OSGI module "com.bea.core.diagnostics.instrumentor_1.0.1.0.jar" shipped with the Weblogic server. Obviously the JAR Builder Tool did not include the contents of this OSGI bundle into the wlfullclient.jar. I tried to include this OSGI bundle into the classpath of the client app manually (just for testing purposes), but this onyl resultet in another NoClassDefFoundError. This time the class "com.bea.objectweb.asm.Constants" could not be found.
    What astonishes me is the fact that the connection retrieval works fine when we only have the weblogic.jar in the client applications classpath, but fails when we have the wlfullclient.jar in the classpaht. It seems that the t3 communication is handled completely different, depending on what JARs I have in the classpath. Also, JMS communication works fine in both cases (i.e. for the weblogic.jar and the wlfullclient.jar). The only thing that causes problems (at least as far as we have discovered) is getting a JDBC connection from a datasource. I simply fail to see why this is the case.
    Best regards,
    DirkInteresting. I hope the official support case solves your problem.
    I would like to dig further, but it's too far afield for me with
    the workload I have at the moment.
    Joe

  • Jdbc connection in EJB using wsad 5.0

    Hi,
    I want to develop a small application using Ejbs by using oracle 9i as D/b, wsad 5.0 as app server . The problem is i am not able to connect to oracle database in WSAD. What i am doing is i have installed Oracle 9i in my system and has given the Global database name as "samp" while installation . I open my SQL plus with username scott and password tiger and i am able to do all my sql queries successfully.
    Now coming to WSAD,
    while creating a JDBC connection using Oracle 9i driver,
    i ve opened in Data perspective and in that go to DB Servers -> Right click -> New Connection
    There a window is opened for Database Connection.
    We need to fill the fields there.
    I have given samp as Global d/b name while installing Oracle 9i .
    In the window , the feilds are
    Connection Name : conn
    Database Name : samp
    user id : scott
    password : tiger
    D/b vendor type: Oracle 9i
    Jdbc Driver : Oracle Thin Driver
    Host : 127.0.0.1
    port No: 1521
    class location : c:\oracle\ora90\jdbc\lib\classes12.zip
    connection url : jdbc:oracle:thin:@127.0.0.1:1521:samp
    the class location and connection url are automatically coming.
    and please check whether all fields are correct or not
    Is this the correct way.
    Next in code if i want to connect to database should i use connection establish commands again or i can directly use create statement or prepare statement.
    Please reply.
    Thanks

    Create New Server and configure it properly
    It will work
    procedure is as follows:
    Pls visit the following link:
    http://www.webagesolutions.com/knowledgebase/waskb/waskb001/index.html
    Adding a Oracle9i DataSource from WSAD5
    Bibhas Bhattacharya, Web Age Solutions Inc.
    Before you begin, make sure that you have Oracle installed and a database is created. In this document we will use a database called MALL.
    Create a WAS V5 Server
    If you don't already have a WebSphere V5 server created, do so following these steps. Switch to the Server perspective. Right click in the Server Configuration view and select New->Server and Server Configuration.
    Name the server WASV5. Make sure that the Server type is set to WebSphere version 5.0->Test Environment. Click on Finish.
    Add the Database User
    In WSAD5, the default user ID and password to be used by a DataSource are first entered as a JAAS authentication entry.
    In the Server Configuration view, double click on WASV5 to open the configuration editor. Click on the Security tab. Next to the JAAS Authentication Entries list click on Add and add the user.
    Add the JDBC Driver
    Still in the server configuration GUI click on the DataSource tab. You can add the DataSource at the server level or at the node level. We will add it at the server level. Make sure that the Server Settings is expanded. Next to the JDBC providers list click on Add.
    Select the following options:
    Database type: Oracle
    JDBC provider type: Oracle JDBC Thin Driver or the XA version of it if you need two phase commit transaction.
    Click on Next.
    Set the name to Oracle Thin Driver.
    Notice that the location of the driver's class is automatically set to ${ORACLE_JDBC_DRIVER_PATH}/classes12.zip. Here, ORACLE_JDBC_DRIVER_PATH is a node level variable. We need to make sure that the variable is pointing to the correct directory where Oracle's JDBC driver is installed. In our case, we had installed Oracle in c:\oracle. This had installed the JDBC driver class in C:/oracle/ora81/jdbc/lib/classes12.zip.
    In the server configuration GUI click on the Variables tab. Under the Node settings select ORACLE_JDBC_DRIVER_PATH from the Defined variables list. Click on Edit and set the value to C:/oracle/ora81/jdbc/lib.
    Add the DataSource
    Click on the DataSource tab again. Select the Oracle Thin Driver you had created in the previous step. Click on Add next to the Data source defined in the JDBC provider selected above list.
    Select the following options:
    Select the type of JDBC Driver: Oracle JDBC Thin Driver.
    Select the data source type: Unless you will be testing your application with WAS V4, select Version 5.0. You can not use a V4 DataSource from a J2EE 1.3 EJB module running in WebSphere V5.
    Click on Next.
    Enter these key attributes in this screen:
    Name: My Oracle DataSource
    JNDI Name: jdbc/MyDataSource
    DataSource helper class name: com.ibm.websphere.rsadapter.OracleDataStoreHelper. Should be selected by default. The helper class is needed if you wish to access IBM extensions to JDBC. For more details search in WSAD help for "WSDataSource interface".
    Component-managed authentication alias: Set this if you wish to lookup the DataSource using its global JNDI name or using the java:comp/env/ name space and have set the authentication type of the resource reference to Application. Select the JAAS entry you had created. That is, Database user.
    Container-managed authentication alias: Set this if you intend to lookup the DataSource using the java:comp/env/ name space and have set the authentication type of the resource reference to Container. Select the JAAS entry you had created. That is, Database user.
    Use this data source in container managed persistence (CMP): Check on if you intend to use the DataSource from CMP EJBs.
    Click on Next.
    You need to set these properties:
    databaseName: MALL in our case.
    URL: jdbc:oracle:thin:@noble.webagesolutions.com:1521:MALL. In my case the server host name is noble.webagesolutions.com. The listener port number is 1521 (usually the default in most Oracle installations).
    Click on Finish.
    You have finished adding the DataSource. Save the server settings by clicking Control+S. Close the server configuration GUI.
    Testing the DataSource
    There is no out of the box way to test the DataSource. You can create a simple Servlet and add the following code:
    public void doGet(HttpServletRequest req, HttpServletResponse resp)
    javax.sql.DataSource ds = null;
    java.sql.Connection con = null;
    java.io.PrintWriter out = resp.getWriter();
    resp.setContentType("text/html");
    try {
    out.println("Looking up DataSource<br>");
    javax.naming.InitialContext ctx = new javax.naming.InitialContext();
    ds = (javax.sql.DataSource) ctx.lookup("jdbc/MyDataSource");
    out.println("Getting connection<br>");
    con = ds.getConnection();
    con.close();
    } catch (Exception e) {
    e.printStackTrace(out);
    out.println("Done<br>");
    Feedback
    Your e-mail:
    Rate this article:
    Very useful Somewhat useful Not bad Needs many corrections
    Comments:

  • ClassNotFoundException at JDBC connection

    Hi
    1)I have classpath:
    %CATALINA_HOME%\common\lib\servlet.jar;c:\jdk1.4.0_02\lib\tools.jar;c:\java;c:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;c:\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;c:\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar
    2) i have 3 java file on my c:\java2 folder.
    3) I test the following code, I got error at:
    ClassNotFoundException: com.microsoft.jdbc.sqlserver....
    Error Trace in getConnection() : com.microsoft.jdbc.sqlserver.SQLServ
    erDriver
    Error: No active Connection
    4) can I compile this code with regular way like
    java2>javac Connect.java
    java2>java Connect
    to compile and run the code?
    Thank you !
    import java.sql.*;
    public class Connect{
    private java.sql.Connection con = null;
    private final String url = "jdbc:microsoft:sqlserver://";
    private final String serverName= "localhost";
    private final String portNumber = "1433";
    private final String databaseName= "pubs";
    private final String userName = "sa";
    private final String password = "ProjectA11";
    // Informs the driver to use server a side-cursor,
    // which permits more than one active statement
    // on a connection.
    private final String selectMethod = "cursor";
    // Constructor
    public Connect(){}
    private String getConnectionUrl(){
    return url+serverName+":"+portNumber+";databaseName="+databaseName+";selectMethod="+selectMethod+";";
    private java.sql.Connection getConnection(){
    try{
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = java.sql.DriverManager.getConnection(getConnectionUrl(),userName,password);
    if(con!=null) System.out.println("Connection Successful!");
    }catch(Exception e){
    e.printStackTrace();
    System.out.println("Error Trace in getConnection() : " + e.getMessage());
    return con;
    Display the driver properties, database details
    public void displayDbProperties(){
    java.sql.DatabaseMetaData dm = null;
    java.sql.ResultSet rs = null;
    try{
    con= this.getConnection();
    if(con!=null){
    dm = con.getMetaData();
    System.out.println("Driver Information");
    System.out.println("\tDriver Name: "+ dm.getDriverName());
    System.out.println("\tDriver Version: "+ dm.getDriverVersion ());
    System.out.println("\nDatabase Information ");
    System.out.println("\tDatabase Name: "+ dm.getDatabaseProductName());
    System.out.println("\tDatabase Version: "+ dm.getDatabaseProductVersion());
    System.out.println("Avalilable Catalogs ");
    rs = dm.getCatalogs();
    while(rs.next()){
    System.out.println("\tcatalog: "+ rs.getString(1));
    rs.close();
    rs = null;
    closeConnection();
    }else System.out.println("Error: No active Connection");
    }catch(Exception e){
    e.printStackTrace();
    dm=null;
    private void closeConnection(){
    try{
    if(con!=null)
    con.close();
    con=null;
    }catch(Exception e){
    e.printStackTrace();
    public static void main(String[] args) throws Exception
    Connect myDbTest = new Connect();
    myDbTest.displayDbProperties();

    I use the driver available at:
    http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml
    no spacesin the above link. Once installed, read the following:
    If you still get the same error, this could be some security issue.
    No I dont need any special setup for sql server. Check to make sure your server is running. Also create a new user with password and give it all previleges. Use that user to login and make sure it works then read the below.
    Connecting Through the JDBC Driver Manager
    One way of connecting to a database is through the JDBC driver manager using the method DriverManager.getConnection. This method uses a string containing a URL. The following is an example of using the JDBC driver manager to connect to Microsoft SQL Server 2000 while passing the user name and password:
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    Connection conn = DriverManager.getConnection ("jdbc:microsoft:sqlserver://server1:1433;User=test;Password=secret");
    URL Examples
    The complete connection URL format used with the driver manager is:
    jdbc:microsoft:sqlserver://hostname:port[;property=value...]
    where:
    hostname is the TCP/IP address or TCP/IP host name of the server to which you are connecting.
    NOTE: Untrusted applets cannot open a socket to a machine other than the originating host.
    port is the number of the TCP/IP port.
    property=value specifies connection properties. See "Connection String Properties" for a list of connection properties and their values.
    The following example shows a typical connection URL:
    jdbc:microsoft:sqlserver://server1:1433;user=test;password=secret
    IF THE ABOVE STILL DOSENT WORK TRY CONNECTING THRU DATASOURCE.
    Connecting Through Data Sources
    A SQL Server 2000 Driver for JDBC data source is a DataSource object that provides the connection information needed to connect to an underlying database. The main advantage of using a data source is that it works with the Java Naming Directory Interface (JNDI) naming service, and it is created and managed outside of the applications that use it. Because the connection information is outside of applications, the time it takes to reconfigure your infrastructure when a change is made is minimal. For example, if the underlying database is moved to another server and uses another port number, the administrator must change only the relevant properties of the SQL Server 2000 Driver for JDBC data source (a DataSource object). The applications using the underlying database do not need to change because they only refer to the logical name of the SQL Server 2000 Driver for JDBC data source.
    How SQL Server 2000 Driver for JDBC Data Sources Are Implemented
    Microsoft ships a data source class for the SQL Server 2000 Driver for JDBC. See "SQL Server 2000 Driver for JDBC" for the name of the class.
    The SQL Server 2000 Driver for JDBC data source class provided implements the following interfaces defined in the JDBC 2.0 Optional Package:
    javax.sql.DataSource
    javax.sql.ConnectionPoolDataSource, which enables you to implement connection pooling
    NOTE: You must include the javax.sql.* and javax.naming.* classes to create and use SQL Server 2000 Driver for JDBC data sources. The SQL Server 2000 Driver for JDBC provides all the necessary JAR files that contain the required classes and interfaces.
    Calling a Data Source in an Application
    Applications can call a SQL Server 2000 Driver for JDBC data source using a logical name to retrieve the javax.sql.DataSource object. This object loads the SQL Server 2000 Driver for JDBC and can be used to establish a connection to the underlying database.
    Once a SQL Server 2000 Driver for JDBC data source has been registered with JNDI, it can be used by your JDBC application as shown in the following example:
    Context ctx = new InitialContext();
    DataSource ds = (DataSource)ctx.lookup("jdbc/EmployeeDB");
    Connection con = ds.getConnection("matt", "wwf");
    In this example, the JNDI environment is first initialized. Next, the initial naming context is used to find the logical name of the SQL Server 2000 Driver for JDBC data source (EmployeeDB). The Context.lookup() method returns a reference to a Java object, which is narrowed to a javax.sql.DataSource object. Finally, the DataSource.getConnection() method is called to establish a connection with the underlying database.
    Using Connection Pooling
    Connection pooling allows you to reuse connections rather than create a new one every time the SQL Server 2000 Driver for JDBC needs to establish a connection to the underlying database. Connection pooling manages connection sharing across different user requests to maintain performance and reduce the number of new connections that must be created. For example, compare the following transaction sequences.
    Example A: Without Connection Pooling
    The client application creates a connection.
    The client application sends a data access query.
    The client application obtains the result set of the query.
    The client application displays the result set to the end user.
    The client application ends the connection.
    Example B: With Connection Pooling
    The client checks the connection pool for an unused connection.
    If an unused connection exists, it is returned by the pool implementation; otherwise, it creates a new connection.
    The client application sends a data access query.
    The client application obtains the result set of the query.
    The client application displays the result set to the end user.
    The client application returns the connection to the pool.
    NOTE: The client application still calls "close()", but the connection remains open and the pool is notified of the close request.
    The pool implementation creates "real" database connections using the getPooledConnection() method of ConnectionPoolDataSource. Then, the pool implementation registers itself as a listener to the PooledConnection. When a client application requests a connection, the pool implementation (Pool Manager) assigns one of its available connections. If there is no connection available, the Pool Manager establishes a new connection and assigns it to that application. When the client application closes the connection, the Pool Manager is notified by the driver through the ConnectionEventListener interface that the connection is free and available for reuse. The pool implementation is also notified by the ConnectionEventListener interface when the client somehow corrupts the database connection, so that the pool implementation can remove that connection from the pool.
    Once a SQL Server 2000 Driver for JDBC data source has been registered with JNDI, it can be used by your JDBC application as shown in the following example, typically through a third-party connection pool tool:
    Context ctx = new InitialContext();
    ConnectionPoolDataSource ds =
    (ConnectionPoolDataSource)ctx.lookup("jdbc/EmployeeDB");
    pooledConnection pcon = ds.getPooledConnection("matt", "wwf");
    In this example, the JNDI environment is first initialized. Next, the initial naming context is used to find the logical name of the JDBC data source (EmployeeDB). The Context.lookup() method returns a reference to a Java object, which is narrowed to a javax.sql.ConnectionPoolDataSource object. Finally, the ConnectionPoolDataSource.getPooledConnection() method is called to establish a connection with the underlying database.
    NOTE: JDBC drivers do not manage connection pooling. You must use an external connection pool manager.

  • Jdbc connection to teradata db

    Hi,
    need your help with the Teradata connection.I have no past experience on jdbc connection. I have placed both Teradata jdbc driver jar files "tdgssconfig" and "terajdbc4" under \tomcat\6.0\lib directory.
    This is a default configuration on windows 7 with tomcat and postgresql.
    Here is the connection details :
    Attached is the error:

    couple of times I got connected to see the table connection view:
    and, next step it fails with the following error and
    Client version: 12.1.3.0.0 (727)
    Apr 20, 2015 4:58:11 PM
    com.datanomic.utils.blueprints.BlueprintException: Could not connect to database: [Teradata JDBC Driver] [TeraJDBC 14.10.00.39] [Error 1277] [SQLState 08S01] Login timeout for Connection to TDXDW Mon Apr 20 16:58:11 CDT 2015 socket orig=TDXDW cid=70b471ba sess=0 java.net.SocketTimeoutException: connect timed out   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)   at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)   at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)   at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)   at java.net.AbstractPlainSocketImpl.connect(Unknown Source)   at java.net.PlainSocketImpl.connect(Unknown Source)   at java.net.SocksSocketImpl.connect(Unknown Source)   at java.net.Socket.connect(Unknown Source)   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:1216) (Code: 2,010) (Code: 205,615)
    at com.datanomic.director.datasource.client.gui.ColumnListPanel.initialiseColumns(ColumnListPanel.java:257)
    at com.datanomic.director.snapshot.client.wizards.ColumnSelectorWizardPage$1.construct(ColumnSelectorWizardPage.java:100)
    at com.datanomic.director.snapshot.client.wizards.ColumnSelectorWizardPage$1.construct(ColumnSelectorWizardPage.java:94)
    at com.datanomic.director.guihelper.MultiSwingChore$WorkerRunner.run(MultiSwingChore.java:186)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    Caused by: com.datanomic.utils.databasespecies.DatabaseException: Could not connect to database: [Teradata JDBC Driver] [TeraJDBC 14.10.00.39] [Error 1277] [SQLState 08S01] Login timeout for Connection to TDXDW Mon Apr 20 16:58:11 CDT 2015 socket orig=TDXDW cid=70b471ba sess=0 java.net.SocketTimeoutException: connect timed out   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)   at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)   at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)   at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)   at java.net.AbstractPlainSocketImpl.connect(Unknown Source)   at java.net.PlainSocketImpl.connect(Unknown Source)   at java.net.SocksSocketImpl.connect(Unknown Source)   at java.net.Socket.connect(Unknown Source)   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:1216) (Code: 2,010)
    at com.datanomic.utils.databasespecies.species.Database.getConnection(Database.java:201)
    at com.datanomic.utils.databasespecies.species.Database.getConnection(Database.java:169)
    at com.datanomic.utils.databasespecies.species.Database.getTables(Database.java:432)
    at com.datanomic.utils.databasespecies.species.Database.getTable(Database.java:397)
    at com.datanomic.utils.databasespecies.species.Database.getTable(Database.java:365)
    at com.datanomic.utils.databasespecies.manager.DatabaseSpeciesManager.getTable(DatabaseSpeciesManager.java:743)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.datanomic.utils.transport.server.ServerTransport.invoke(ServerTransport.java:120)
    at com.datanomic.utils.transport.server.ServerTransport.invoke(ServerTransport.java:60)
    at com.datanomic.utils.transport.http.server.TransportServlet.doPost(TransportServlet.java:132)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at com.datanomic.userauth.server.http.AuthFilter.doFilter(AuthFilter.java:129)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1023)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    and, then application error to maintain the integrity of the application:
    Client version: 12.1.3.0.0 (727)
    Apr 20, 2015 4:49:19 PM
    java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@4da8bb5d rejected from java.util.concurrent.ThreadPoolExecutor@a4fe80[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
    at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)
    at java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
    at com.datanomic.director.guihelper.MultiSwingChore.addWorker(MultiSwingChore.java:98)
    at com.datanomic.director.snapshot.client.wizards.ColumnSelectorWizardPage.pageSelected(ColumnSelectorWizardPage.java:121)
    at com.datanomic.director.guicomponents.wizard.Wizard.updateWizardPage(Wizard.java:327)
    at com.datanomic.director.guicomponents.wizard.Wizard.access$000(Wizard.java:46)
    at com.datanomic.director.guicomponents.wizard.Wizard$1.wizardPageChanged(Wizard.java:272)
    at com.datanomic.director.guicomponents.wizard.AbstractWizardModel.fireWizardPageChanged(AbstractWizardModel.java:29)
    at com.datanomic.director.snapshot.client.wizards.SnapshotWizardModel.next(SnapshotWizardModel.java:181)
    at com.datanomic.director.guicomponents.wizard.Wizard.doOK(Wizard.java:451)
    at com.datanomic.director.guicomponents.wizard.Wizard.actionPerformed(Wizard.java:426)
    at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
    at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
    at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
    at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
    at java.awt.Component.processMouseEvent(Unknown Source)
    at javax.swing.JComponent.processMouseEvent(Unknown Source)
    at java.awt.Component.processEvent(Unknown Source)
    at java.awt.Container.processEvent(Unknown Source)
    at java.awt.Component.dispatchEventImpl(Unknown Source)
    at java.awt.Container.dispatchEventImpl(Unknown Source)
    at java.awt.Component.dispatchEvent(Unknown Source)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
    at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
    at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
    at java.awt.Container.dispatchEventImpl(Unknown Source)
    at java.awt.Window.dispatchEventImpl(Unknown Source)
    at java.awt.Component.dispatchEvent(Unknown Source)
    at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
    at java.awt.EventQueue.access$200(Unknown Source)
    at java.awt.EventQueue$3.run(Unknown Source)
    at java.awt.EventQueue$3.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
    at java.awt.EventQueue$4.run(Unknown Source)
    at java.awt.EventQueue$4.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
    at java.awt.WaitDispatchSupport$2.run(Unknown Source)
    at java.awt.WaitDispatchSupport$4.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.awt.WaitDispatchSupport.enter(Unknown Source)
    at java.awt.Dialog.show(Unknown Source)
    at java.awt.Component.show(Unknown Source)
    at java.awt.Component.setVisible(Unknown Source)
    at java.awt.Window.setVisible(Unknown Source)
    at java.awt.Dialog.setVisible(Unknown Source)
    at com.datanomic.director.snapshot.client.actions.NewSnapshotAction.showSnapshotWizard(NewSnapshotAction.java:88)
    at com.datanomic.director.snapshot.client.actions.NewSnapshotAction.showSnapshotWizard(NewSnapshotAction.java:53)
    at com.datanomic.director.snapshot.handler.chore.edit.LaunchWizardChore.finished(LaunchWizardChore.java:73)
    at com.datanomic.director.guihelper.SwingChore$1.run(SwingChore.java:89)
    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
    at com.datanomic.utils.blueprints.ui.chores.ChoreMaster$InvokeQueue$Invoker.run(ChoreMaster.java:600)
    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
    at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

Maybe you are looking for

  • Can a Mini DisplayPort to Dual-Link DVI Adapter do the same job as the Mini DisplayPort to DVI Adapter?

    Can a Mini DisplayPort to Dual-Link DVI Adapter do the same job as the Mini DisplayPort to DVI Adapter?  Meaning, can I connect a DVI screen less than 30 inches?  Why would I buy the expensive product?  Simply because I might have to sometimes work w

  • Regarding web analysis database connections

    Hi All, I have couple of web analysis reports and the issue is i have copied this web analysis server to another server where i have the same application. Now iam trying to append those database connection properties of the file to point to the new s

  • Idoc with Status 56

    Hi Friends, I am processing an inbound idoc file using MBGMCR. It is creating an idoc in status 56. I am not able to figure what is wrong. Please suggest. Here is the error. EDI: Receiver port in control record is invalid Message no. EA602 Diagnosis

  • Dequeue Condition in BPEL

    I want to place a Dequeue Condition on my AQ ProcessType = STANDARD My payload is something like that: <OutboundPaymentInstruction> <PaymentInstructionInfo> <InstructionReferenceNumber>190933</InstructionReferenceNumber> <FormatProgramRequestID>65778

  • Flash plug in crashing in Gmail/everytime I want to upload a photo to a website?

    Updated to 3.6.10 and newest flash version, got rid of time out, tried in safe mode with add ons disabled and also reinstalled flash & firefox. Also tried older FF version. Still having the problem. FF crashes every time I try uploading photos in a w