java.sql.SQLException: Fail to convert to internal representation). In a debug window, I'm seeing a LazyInitializationException, which is likely related. I'm completely stumped, and hope somewhere out there, someone can help. All I can think of is that I have a mapping issue. I have these classes: Here is the EquipmentItem class: Finally, here is (most of) the ViewHelper that attempts to get the equipment list (not the most efficient implementation yet...) Need help with Hibernate? Read this first: 500 Internal Server Error Exception: [.LookupUtil] Error looking up property "equipmentList" in object type "mine.equipmenttracker.web.helpers.EquipmentAccountViewHelper". Cause: null

hibernate.org | 2 months ago
  1. 0

    Hibernate Community • View topic - java.sql.SQLException: Fail to convert to internal represent

    hibernate.org | 2 months ago
    java.sql.SQLException: Fail to convert to internal representation). In a debug window, I'm seeing a LazyInitializationException, which is likely related. I'm completely stumped, and hope somewhere out there, someone can help. All I can think of is that I have a mapping issue. I have these classes: Here is the EquipmentItem class: Finally, here is (most of) the ViewHelper that attempts to get the equipment list (not the most efficient implementation yet...) Need help with Hibernate? Read this first: 500 Internal Server Error Exception: [.LookupUtil] Error looking up property "equipmentList" in object type "mine.equipmenttracker.web.helpers.EquipmentAccountViewHelper". Cause: null
  2. 0

    Hibernate Community • View topic - Fail to Convert to Internal Representation

    hibernate.org | 8 months ago
    java.sql.SQLException: Fail to convert to internal representation). In a debug window, I'm seeing a LazyInitializationException, which is likely related. I'm completely stumped, and hope somewhere out there, someone can help. All I can think of is that I have a mapping issue. I have these classes: Here is the EquipmentItem class: Finally, here is (most of) the ViewHelper that attempts to get the equipment list (not the most efficient implementation yet...) Need help with Hibernate? Read this first: Hibernate version:3.2.4.sp1 (Annotations 3.3.0.GA) Mapping documents: Code between sessionFactory.openSession() and session.close(): Full stack trace of any exception that occurs: 500 Internal Server Error Exception: [.LookupUtil] Error looking up property "equipmentList" in object type "mine.equipmenttracker.web.helpers.EquipmentAccountViewHelper". Cause: null
  3. 0

    Stuck Thread problem with XA Connections

    Oracle Community | 10 years ago | 666705
    java.sql.SQLException: [BEA][Oracle JDBC Driver]Internal error: Net8 protocol > error..> Hi. What version of the Oracle DBMS are you running? Is it a supported version? Something is going wrong between the driver and the DBMS. Is there any info in the DBMS error log to indicate that/why it may have killed some running sessions? We may want you to reproduce this in a single-server case (easier to debug), with the driver spy logging turned on. Joe > When this happens, that thread seems to lock pretty much for good. The web user never gets a response, > and if we run a thread dump, we can see that the thread is stuck. (see below). > DBAs have confirmed that the connection is no longer active, so the thread seems to be stuck somewhere in the driver. > 2) We do not get the Net8 error. Instead, the transaction continues inexplicably (it should have timed out) to the next piece of SQL, which it then attempts to run. I am not as clear as to what is going on in this case, but it appears that it makes another request on the same connection, but now the database responds unbelievably slowly (if at all.) Sometimes the Net8 error occurs at a later time. > System is Weblogic 9.2. We are using the BEA XA driver for Oracle. This problem exists both in a clustered environment as well as on local single-server environments. > This is a stack trace we get in the log: > <May 9, 2007 11:16:28 AM EDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '84' for queue: 'w > eblogic.kernel.Default (self-tuning)' has been busy for "622" seconds working on the request "Http Request: /c > sds/esignature/esigPopup.faces", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. > Stack trace: > weblogic.jdbcx.base.BaseXAConnection.getXAResource(Unknown Source) > weblogic.jdbc.wrapper.XAConnection.getXAResource(XAConnection.java:455) > weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:693) > weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:460) > weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1455) > weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1372) > weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1362) > weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:329) > weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294) > weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:284) > weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:466) > weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:357) > weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83) > weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1476) > weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1274) > weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:195) > weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:70) > weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:250) > weblogic.jdbc.wrapper.Statement.doClose(Statement.java:342) > weblogic.jdbc.wrapper.Statement.close(Statement.java:329) > com.pfizer.disco.fw.DaoBase.queryMultipleRows(DaoBase.java:1303) > Here is a snippet from the thread dump: > "[ACTIVE] ExecuteThread: '397' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x005340a8 nid=0x20f waiting for monitor entry [0x812ff000..0x812ffb10]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Getting java.sql.SQLException: ORA-02291 for a nullable foreign key

    Stack Overflow | 2 years ago
    java.sql.SQLException: ORA-02291 when I try to insert a NULL value to a column which has a foreign key constraint to another table. By definition this column is NULLABLE in the child table and the column it is referencing in the parent is the PK of that table. I am confused, why I am getting this exception. Any help with this will be greatly appreciated. Here is the exception and DDL Exception org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; violated - parent key not found
  6. 0

    Stuck Thread problem with XA Connections

    Oracle Community | 10 years ago | 666705
    java.sql.SQLException: [BEA][Oracle JDBC Driver]Internal error: Net8 protocol error..> When this happens, that thread seems to lock pretty much for good. The web user never gets a response, and if we run a thread dump, we can see that the thread is stuck. (see below). DBAs have confirmed that the connection is no longer active, so the thread seems to be stuck somewhere in the driver. 2) We do not get the Net8 error. Instead, the transaction continues inexplicably (it should have timed out) to the next piece of SQL, which it then attempts to run. I am not as clear as to what is going on in this case, but it appears that it makes another request on the same connection, but now the database responds unbelievably slowly (if at all.) Sometimes the Net8 error occurs at a later time. System is Weblogic 9.2. We are using the BEA XA driver for Oracle. This problem exists both in a clustered environment as well as on local single-server environments. This is a stack trace we get in the log: <May 9, 2007 11:16:28 AM EDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '84' for queue: 'w eblogic.kernel.Default (self-tuning)' has been busy for "622" seconds working on the request "Http Request: /c sds/esignature/esigPopup.faces", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: weblogic.jdbcx.base.BaseXAConnection.getXAResource(Unknown Source) weblogic.jdbc.wrapper.XAConnection.getXAResource(XAConnection.java:455) weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:693) weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:460) weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1455) weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1372) weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1362) weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:329) weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294) weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:284) weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:466) weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:357) weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83) weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1476) weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1274) weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:195) weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:70) weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:250) weblogic.jdbc.wrapper.Statement.doClose(Statement.java:342) weblogic.jdbc.wrapper.Statement.close(Statement.java:329) com.pfizer.disco.fw.DaoBase.queryMultipleRows(DaoBase.java:1303) Here is a snippet from the thread dump: "[ACTIVE] ExecuteThread: '397' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x005340a8 nid=0x20f waiting for monitor entry [0x812ff000..0x812ffb10]

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLException

      Fail to convert to internal representation). In a debug window, I'm seeing a LazyInitializationException, which is likely related. I'm completely stumped, and hope somewhere out there, someone can help. All I can think of is that I have a mapping issue. I have these classes: Here is the EquipmentItem class: Finally, here is (most of) the ViewHelper that attempts to get the equipment list (not the most efficient implementation yet...) Need help with Hibernate? Read this first: 500 Internal Server Error Exception: [.LookupUtil] Error looking up property "equipmentList" in object type "mine.equipmenttracker.web.helpers.EquipmentAccountViewHelper". Cause: null

      at org.displaytag.util.LookupUtil.getBeanProperty()
    2. Display tag library
      TableTag.doStartTag
      1. org.displaytag.util.LookupUtil.getBeanProperty(LookupUtil.java:137)
      2. org.displaytag.util.LookupUtil.getBeanValue(LookupUtil.java:90)
      3. org.displaytag.tags.TemplateTag.evaluateExpression(TemplateTag.java:84)
      4. org.displaytag.tags.TableTag.initParameters(TableTag.java:847)
      5. org.displaytag.tags.TableTag.doStartTag(TableTag.java:722)
      5 frames
    3. _web_2d_inf._jsp
      _viewAccountProfile._jspService
      1. _web_2d_inf._jsp._viewAccountProfile._jspService(_viewAccountProfile.java:386)[SRC:/WEB-INF/jsp/viewAccountProfile.jsp:67]
      1 frame