[ 
https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945634&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945634
 ]

ASF GitHub Bot logged work on ARTEMIS-5174:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Nov/24 07:56
            Start Date: 26/Nov/24 07:56
    Worklog Time Spent: 10m 
      Work Description: AntonRoskvist commented on PR #5366:
URL: 
https://github.com/apache/activemq-artemis/pull/5366#issuecomment-2499911037

   I have tried with some variations in the stack to try and get around this 
problem but without success. The stack I posted yesterday is using TCP as the 
transport, typically I use TCP_NIO. 
   
   Similar stack using that transport:
   `2024-11-06 12:30:48,947 ERROR [org.jgroups.protocols.TCP_NIO2] JGRP000030: 
$HOSTNAME-26050: failed handling incoming message 
   java.io.EOFException: null 
           at 
org.jgroups.util.ByteArrayDataInputStream.readFully(ByteArrayDataInputStream.java:118)
 ~[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.BytesMessage.readPayload(BytesMessage.java:265) 
~[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.BaseMessage.readFrom(BaseMessage.java:317) 
~[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1327) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.protocols.TP.receive(TP.java:1283) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.util.Util.bufferToArray(Util.java:1221) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.blocks.cs.Receiver.receive(Receiver.java:36) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.blocks.cs.NioConnection._read(NioConnection.java:226) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at org.jgroups.blocks.cs.NioConnection.read(NioConnection.java:201) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at 
org.jgroups.blocks.cs.NioBaseServer$Acceptor.run(NioBaseServer.java:145) 
[jgroups-5.3.9.Final.jar:5.3.9.Final] 
           at java.base/java.lang.Thread.run(Thread.java:833) [?:?] `
   
   This is the basic config I use:
   `<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
              xmlns="urn:org:jgroups"
              xsi:schemaLocation="urn:org:jgroups 
http://www.jgroups.org/schema/jgroups.xsd";>
   
      <TCP_NIO2 bind_port="7800" bind_addr="match-interface:$IF" 
diag.enable_tcp="true" diag.port="7801"/>
      <TCPPING 
initial_hosts="$HOST1[7800],$HOST2[7800],$HOST3[7800],$HOST4[7800],$HOST5[7800]"
 port_range="0"/>
   
      <MERGE3 min_interval="5000" max_interval="10000" check_interval="15000"/>
      <RED/>
      <FD_ALL3 timeout="10000" interval="1000"/>
      <VERIFY_SUSPECT2 timeout="1500"/>
      <BARRIER/>
      <pbcast.NAKACK2 use_mcast_xmit="false"/>
      <UNICAST3/>
      <pbcast.STABLE desired_avg_gossip="50000" max_bytes="4M"/>
      <pbcast.GMS print_local_addr="true" join_timeout="2000"/>
      <UFC max_credits="2M" min_threshold="0.4"/>
      <FRAG2 frag_size="60K"/>
      <pbcast.STATE_TRANSFER/>
   </config>`




Issue Time Tracking
-------------------

    Worklog Id:     (was: 945634)
    Time Spent: 1h  (was: 50m)

> Have dependabot ignore jgroups until JGRP-2794 is resolved
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-5174
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5174
>             Project: ActiveMQ Artemis
>          Issue Type: Dependency upgrade
>            Reporter: Anton Roskvist
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Before [JGRP-2794|https://issues.redhat.com/projects/JGRP/issues/JGRP-2794] 
> is resolved, jgroups provides compatibility between versions on a 
> "best-effort" basis. Since moving to upgrade jGroups through dependabot I 
> have seen multiple cases where "rolling upgrades" between broker versions in 
> a clustered setting does not work as intended.
> I therefore think dependency updates to jgroups should be made manually on a 
> case by case basis until the aforementioned jgroups Jira ticket is resolved.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact


Reply via email to