[
https://issues.apache.org/jira/browse/PHOENIX-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752474#comment-17752474
]
ASF GitHub Bot commented on PHOENIX-6945:
-----------------------------------------
stoty commented on PR #106:
URL:
https://github.com/apache/phoenix-connectors/pull/106#issuecomment-1671766612
I messed up and applied the wrong patch.
I have pushed an addenum to fix the problem you have found.
> Update Surefire plugin to 3.0.0 and switch to TCP forkNode implementation
> -------------------------------------------------------------------------
>
> Key: PHOENIX-6945
> URL: https://issues.apache.org/jira/browse/PHOENIX-6945
> Project: Phoenix
> Issue Type: Bug
> Components: connectors, core, queryserver
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: connectors-6.0.0, 5.2.0, 5.1.4
>
>
> Surefire 3.0.0 has been released.
> It has the option of using a different proticol for communicating with the
> test executors, which may or may not fix some of the sporadical "[WARNING]
> Corrupted channel by directly writing to native stream in forked JVM" events
> we see.
> https://maven.apache.org/surefire/maven-surefire-plugin/examples/process-communication.html#the-tcp-ip-communication-channel
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
