org.apache.derby.client.am.SqlException: Java exception: 'FWK005 parse may not be called while parsing.: org.xml.sax.SAXException'.

Apache's JIRA Issue Tracker | Royi Ronen | 8 years ago
  1. 0

    [DERBY-2549] ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE - ASF JIRA

    apache.org | 12 months ago
    java.sql.SQLException: The exception 'java.lang.ArrayIndexOutOfBoundsException: 100' was thrown while evaluating an expression. SQLSTATE: XJ001: Java exception: '100: java.lang.ArrayIndexOutOfBoundsException'.
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    The issue arrives when multiple XA transactions are done in parallel and there is either a lock timeout or a lock deadlock detected. When this happens the connection is leaked in the Glassfish connection pool and the client thread hangs in "org.apache.derby.client.netReply.fill(Reply.java:172)". Shutting down the app server fails because the thread has a lock in "org.apache.derby.client.net.NetConnection40" and another task is calling "org.apache.derby.client.ClientPooledConnection.close(ClientPooledConnection.java:214)" which is waiting for the lock. Killing the appsever using "kill" and then attempting to shutdown Derby network server causes the Network Server to hang. One of the threads hangs waiting for a lock at "org.apache.derby.impl.drda.NeworkServerControlImpl.removeFromSessionTable(NetworkServerControlImpl.java:1525)" and the "main" thread has this locked at "org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(NetworkServerControlImpl.java:2242)" and it itself is waiting for a lock which belongs to a thread that is stuck at "org.apache.derby.impl.services.locks.ActiveLock.waitForGrant(ActiveLock.java:118) which is in the TIMED_WAITING state. Only by killing the Network Server using "kill" is possible at this point. There are transactions left even though all clients have been removed.

    Apache's JIRA Issue Tracker | 5 years ago | Brett Bergquist
    java.sql.SQLNonTransientConnectionException: A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific conditio n for which there was no architected message (additional information may be available in the derby.log file on the serve r)
  4. 0

    Derby out of memory

    Stack Overflow | 3 years ago | user3001676
    java.sql.SQLNonTransientConnectionException: A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message (additional information may be available in the derby.log file on the server)

    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. org.apache.derby.client.am.SqlException

      Java exception: 'FWK005 parse may not be called while parsing.: org.xml.sax.SAXException'.

      at org.apache.derby.client.am.SqlException.<init>()
    2. Apache Derby Client JDBC Driver
      SqlException.<init>
      1. org.apache.derby.client.am.SqlException.<init>(Unknown Source)
      2. org.apache.derby.client.am.SqlException.<init>(Unknown Source)
      2 frames