[
https://issues.apache.org/jira/browse/DERBY-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903731#action_12903731
]
Kathey Marsden commented on DERBY-4784:
---------------------------------------
Please let us know as you find out more. Usually a severe protocol error like
this occurs upon some very serious error on the server side has occurred, so
getting the derby.log and full nested exception stack traces is the first
place to look.
If that does not show anything revealing, try to understand what is going on
with the database at the time of the failure.
If it is an actual protocol bug then the query being performed, the amount
and type of data retrieved may be relevant.
See http://wiki.apache.org/db-derby/ProtocolDebuggingTips for more information
on debugging protocol issues.
Your customer may also wish to upgrade at least to 10.4.2.0 to get the latest
release on that branch after backing up their database.
> derby in network mode sporadically drops connections
> ----------------------------------------------------
>
> Key: DERBY-4784
> URL: https://issues.apache.org/jira/browse/DERBY-4784
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.4.1.3
> Environment: WIndows Server 2003 SP2 with 32 bit JVM
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode)
> Reporter: Trung Tran
> Priority: Critical
>
> We are sporadically getting "Cause:
> 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" and we will have to restart the server. We
> also have received "Cause: java.sql.SQLNonTransientConnectionException:
> Network protocol exception: actual code point, 4,692, does not match expected
> code point, 9,224. The connection has been terminated.; nested exception is
> com.ibatis.common.jdbc.exception.NestedSQLException: " which also required a
> restart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
