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
Expand all | Collapse all

WebSphere DB errors-Application is working

  • 1.  WebSphere DB errors-Application is working

    Posted Mon August 26, 2013 04:25 AM
    Hi All,

    I have seen the below communication error in logs, application is working.

    please help me, what is causing the problem.

    00001205 ConnectionEve A   J2CA0056I: The Connec
    tion Manager received a fatal connection error from the Resource Adapter for res
    ource jdbc/appname. The exception is: com.ibm.db2.jcc.b.DisconnectException: [ib
    m][db2][jcc][t4][2030][11211] A communication error has been detected. Communica
    tion protocol being used: TCP/IP.
    Communication API being used: SOCKETS.  Location where the error was detected: R
    eply.fill().

    communication function detecting the error: InputStream.read().  Protocol specific error codes Insufficient data, * , 0.  Message: null


    Thanks,
    Chinna.



  • 2.  WebSphere DB errors-Application is working

    Posted Mon August 26, 2013 06:20 AM
    Hi Chinna,

      Could you put the complete exception, what is following to "Protocol specific error codes Insufficient data, * , 0.  Message: null"
     
      In what platform is DB2?

      Thanks in advanced.

    Regards


  • 3.  WebSphere DB errors-Application is working

    Posted Mon August 26, 2013 09:37 AM
    . The exception is: com.ibm.db2.jcc.b.DisconnectException: [ib m][db2][jcc][t4][2030][11211] A communication error has been detected.


    The firewall port between WAS and DB is not opened. or the DB which you defined in the datasource is not exists in the backend Database.

    Thanks
    Venkata


  • 4.  WebSphere DB errors-Application is working

    Posted Fri August 30, 2013 07:44 AM
    Hi All,

    Thanks for your inputs.

    Application is working fine with the datasource, port are listening properly. Still i am getting the fatal error in logs, not frequently.

    I am not aware is there any commucation is failed at that perticular time or not.

    Thanks,

    Chinna.


  • 5.  WebSphere DB errors-Application is working

    Posted Mon September 02, 2013 05:01 AM

     


    Hi All,


    We are using WAS 8.0 fix 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


    www-01.ibm.com/support/docview.wss?uid=s...

    How can i check  multithreaded access detection option.

    Thanks,
    Chinna.
     



  • 6.  WebSphere DB errors-Application is working

    Posted Mon September 02, 2013 05:30 AM
    Hi chinna,

      I had requested the following information:
     
        1.- Could you put the complete exception, what is following to "Protocol specific error codes Insufficient data, * , 0.  Message: null"
     
        2.- In what platform is DB2?
        
      Could you answer please?  
     
      About your questions to check multithreaded access detection option, you need to review if in your datasource properties you have checked the option::
     
      Resources > JDBC > Data sources > data_source > WebSphere Application Server data source properties
     
      Thanks in advance.
     
    Regards 


  • 7.  WebSphere DB errors-Application is working

    Posted Tue September 03, 2013 04:09 AM
    Hi Gabriel,

    Thanks for your inputs.

    9/3/13 3:32:49:012 GMT+05:30] 00000143 WSJccConnecti W   DSRA8650W: Error closing a JDBC child wrapper, com.ibm.ws.rsadapter.jdbc.WSJccPreparedStatement@e23053c0
    com.ibm.db2.jcc.b.SqlException: [ibm][db2][jcc][10120][10943] Invalid operation: statement is closed.
            at com.ibm.db2.jcc.b.rh.z(rh.java:2471)
            at com.ibm.db2.jcc.b.rh.a(rh.java:932)
            at com.ibm.db2.jcc.b.rh.getMoreResults(rh.java:775)
            at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(WSJdbcPreparedStatement.java:482)
            at com.ibm.ws.rsadapter.jdbc.WSJccPreparedStatement.closeWrapper(WSJccPreparedStatement.java:294)
            at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:241)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.mapException(WSJdbcUtil.java:1185)
            at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:726)
            at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:286)
            at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeQuery(LoggingConnectionDecorator.java:1181)
            at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:284)
            at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeQuery(JDBCStoreManager.java:1787)
            at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:274)
            at org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:318)
            at org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:221)
            at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1005)
            at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
            at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
            at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
            at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:315)
            at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:331)
            at org.apache.openjpa.persistence.QueryImpl.getSingleResult(QueryImpl.java:359)
            at com.ibm.daksh.econvey.dao.UserMgtImpl.getUserByID(UserMgtImpl.java:751)
            at com.ibm.daksh.econvey.service.eConveyFacadeJDBCImpl.getUserByID(eConveyFacadeJDBCImpl.java:265)
            at com.ibm.daksh.econvey.action.UserLogin.execute(UserLogin.java:102)
            at sun.reflect.GeneratedMethodAccessor1533.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    9/3/13 3:32:49:014 GMT+05:30] 00000143 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/3/13 3:32:49:015 GMT+05:30] 00000143 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
    [9/3/13 3:32:49:022 GMT+05:30] 00000143 Form          W org.apache.struts2.components.Form evaluateExtraParamsServletRequest No configuration found for the specified action: 'lo
    gin.action' in namespace: '/'. Form action defaulting to 'action' attribute's literal value.
    [9/3/13 3:32:49:025 GMT+05:30] 00000143 Form          W org.apache.struts2.components.Form evaluateExtraParamsServletRequest No configuration found for the specified action: 'lo
    gin.action' in namespace: '/'. Form action defaulting to 'action' attribute's literal value.
    [9/3/13 3:40:21:545 GMT+05:30] 00000132 Form          W org.apache.struts2.components.Form evaluateExtraParamsServletRequest No configuration found for the specified action: 'lo
    gin.action' in namespace: ''. Form action defaulting to 'action' attribute's literal value.


    DB is on AIX.

    multithreaded access detection is disabled.


    We have three more applications deployed and working fine.


    Is there any fix for this.

    Thanks,
    Chinna.



  • 8.  WebSphere DB errors-Application is working

    Posted Tue September 03, 2013 05:04 AM
    Chinna,

      Seems like the error arise when someone try to do a login in the application a
     
        at com.ibm.daksh.econvey.dao.UserMgtImpl.getUserByID(UserMgtImpl.java:751)
        at com.ibm.daksh.econvey.service.eConveyFacadeJDBCImpl.getUserByID(eConveyFacadeJDBCImpl.java:265)
        at com.ibm.daksh.econvey.action.UserLogin.execute(UserLogin.java:102)
        
        [9/3/13 3:32:49:022 GMT+05:30] 00000143 Form          W org.apache.struts2.components.Form evaluateExtraParamsServletRequest No configuration found for the specified action: 'login.action' in namespace: '/'. Form action defaulting to 'action' attribute's literal value.
        
      and take a connection from the pool
     
        9/3/13 3:32:49:012 GMT+05:30] 00000143 WSJccConnecti W   DSRA8650W: Error closing a JDBC child wrapper,com.ibm.ws.rsadapter.jdbc.WSJccPreparedStatement@e23053c0 com.ibm.db2.jcc.b.SqlException: [ibm][db2][jcc][10120][10943] Invalid operation:statement is closed.
     
     
      what is your datasource configuration?

       Min
       Reap Time =
       Unused timeout =
       Aged timeout =   
        
    regards


  • 9.  WebSphere DB errors-Application is working

    Posted Tue September 03, 2013 09:36 AM
    Hi Gabriel,

    Please find the below for DB configuration.

    what is your datasource configuration?

       Min = 2
       Reap Time = 180 
       Unused timeout = 1800
       Aged timeout =0


    Thanks,
    Chinna.


  • 10.  WebSphere DB errors-Application is working

    Posted Tue September 03, 2013 11:27 AM
    Chinna,

      You have default values in timeouts. I think that your problem if with one of the to connections that still alive in your pool.  Maybe you have in DB some timeout for your connections and this connections are closed
     
      I suggest one of this two options or put Min=0 or put and Aged timeout= greater than 0.

      When the Unused timeout reach, all the connections are deleted until the Min value.  With Aged timeout, min connections are deleted too. An example:

      Reap Time=180
      Unused timeout=180
      Aged timeout=300   

      Hope this helps.
     
    Regards