WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  JDBC error

    Posted Wed May 22, 2013 06:09 PM
    HI ALL

    I am getting the below information when I tried to login to Application. the login is failing first time and its successfull for next logins.

    [5/22/13 14:31:19:012 EDT] 00000025 ConnectionEve W   J2CA0206W: A connection error occurred.  To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option.
    [5/22/13 14:31:19:012 EDT] 00000025 ConnectionEve A   J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource OracledataDS. The exception is: java.sql.SQLRecoverableException: IO Error: Socket read timed out:oracle.net.ns.NetException: Socket read timed out

    WebSphere version is 7.0.0.27
    Oracle version is ..oracle 11g.

    Thanks in advance....



  • 2.  JDBC error

    Posted Thu May 23, 2013 02:07 AM
    Do you look in the WAS v7 InfoCenter:

    Enable multithreaded access detection




    If checked, the following warning message is entered in the WebSphere Application Server system out log if multiple threads attempt to concurrently use the same connection handle. You can use this property to debug connection problems if you think the problems might be caused by multiple threads trying to use the same connection handle. Having multiple threads concurrently using the same connection handle is a programming model violation.


    J2CA0167W: An attempt to concurrently use the same connection handle by multiple threads has been detected. The connection handle is: {0}.




  • 3.  JDBC error

    Posted Thu May 23, 2013 08:40 AM
    If only the first connection is failing ...

    it could be due to 'stale connection' or your netwrok is talking longer time to get the first response.

    for stale connection:
    make the minimum no of connection '0'. restart JVM and see
    By making min connections '0' you are instructing the pool to not to keep any connections.

    ping the database server host from you websphere host . Check how the long the first PING request is taking.
    If this is the reason.. increase the readtimeout


  • 4.  JDBC error

    Posted Mon September 02, 2013 04:55 AM
    Hi All,

    I am also facing same problem in my application. We are using WAS 8.0 finx pack 6.

    We are able to login into application, some times we are not able to login, its not giving error message on login page, its again redicet to login page(page refreshing again). This is not happening prequently.

    Error:

    9/2/13 11:01:18:815 GMT+05:30] 0000002c ConnectionEve W   J2CA0206W: A connection error occurred.  To help determine the problem, enable the Diagnose Connection Usage option on
     the Connection Factory or Data Source.
    [9/2/13 11:01:18:815 GMT+05:30] 0000002c ConnectionEve A   J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jdbc/appname. The exception is: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
    Communication API being used: SOCKETS.  Location where the error was detected: Reply.fill().
    Communication function detecting the error: InputStream.read().  Protocol specific error codes Insufficient data, * , 0.  Message: null



     Thanks,
    Chinna.



Related Content