[
https://issues.apache.org/jira/browse/DERBY-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216254#comment-14216254
]
Myrna van Lunteren commented on DERBY-6771:
-------------------------------------------
In addition, because this issue is logged against Derby 10.4...
I am assuming this is an existing application.
What JVM (and version & build) is used?
Again assuming you have a test environment where this happens, do you see the
same behavior with derby jar files from a more recent release eg. 10.10.2 or
10.11 (only do soft upgrade, i.e. only use the new jars, don't specify upgrade
on the connection urls)? I don't expect it to be fixed, but it is an extra data
point.
> Derby is crashing and writing
> org.apache.derby.impl.drda.DRDAProtocolException: Execution failed because of
> a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error
> Code Value = 3. Plaintext connection attempt from an SSL enabled client?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6771
> URL: https://issues.apache.org/jira/browse/DERBY-6771
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.2.0
> Environment: Linux 2.6.18-348.3.1.el5xen x86_64
> Reporter: Sidhant Behura
> Labels: Crash, DRDAProtocolException, Derby
>
> The derby db crashes and writes the following log into derby.out
> Execution failed because of a Distributed Protocol Error:
> DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error Code Value = 3. Plaintext
> connection attempt from an SSL enabled client?
> org.apache.derby.impl.drda.DRDAProtocolException: Execution failed because of
> a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error
> Code Value = 3. Plaintext connection attempt from an SSL enabled client?
> at
> org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(DRDAConnThread.java:513)
> at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown Source)
> at
> org.apache.derby.impl.drda.DRDAConnThread.exchangeServerAttributes(DRDAConnThread.java:1109)
> at
> org.apache.derby.impl.drda.DRDAConnThread.sessionInitialState(DRDAConnThread.java:663)
> at
> org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:279)
> I have observed the PS Perm Generation used space is > 99%.
> Please provide some information what is triggering this and how to resolve
> this.
> Thanks in advance...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
