[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ 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] JGRP30: $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: `http://www.w3.org/2001/XMLSchema-instance"; xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd";> ` 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
[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945534&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945534 ] ASF GitHub Bot logged work on ARTEMIS-5174: --- Author: ASF GitHub Bot Created on: 25/Nov/24 18:26 Start Date: 25/Nov/24 18:26 Worklog Time Spent: 10m Work Description: jbertram commented on PR #5366: URL: https://github.com/apache/activemq-artemis/pull/5366#issuecomment-2498745675 What JGroups configuration were you using here? Issue Time Tracking --- Worklog Id: (was: 945534) Time Spent: 50m (was: 40m) > 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: 50m > 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
[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945419&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945419 ] ASF GitHub Bot logged work on ARTEMIS-5174: --- Author: ASF GitHub Bot Created on: 25/Nov/24 08:30 Start Date: 25/Nov/24 08:30 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #5366: URL: https://github.com/apache/activemq-artemis/pull/5366#issuecomment-2497240791 @jbertram I've actually seen slightly different issues between different versions but this is a stack trace I had saved that occurs when "rolling in" a version 2.36.0 broker to a cluster of 2.35.0 brokers: `2024-11-06 12:48:21,198 ERROR [org.jgroups.protocols.TCP] JGRP30: $HOSTNAME-23534: failed handling incoming message java.net.SocketException: Socket closed at java.base/sun.nio.ch.NioSocketImpl.endRead(NioSocketImpl.java:248) ~[?:?] at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:327) ~[?:?] at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350) ~[?:?] at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803) ~[?:?] at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966) ~[?:?] at java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:244) ~[?:?] at java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:284) ~[?:?] at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:343) ~[?:?] at java.base/java.io.DataInputStream.readFully(DataInputStream.java:201) ~[?:?] 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:1302) [jgroups-5.3.9.Final.jar:5.3.9.Final] at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:213) [jgroups-5.3.9.Final.jar:5.3.9.Final] at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:304) [jgroups-5.3.9.Final.jar:5.3.9.Final] at java.base/java.lang.Thread.run(Thread.java:833) [?:?] ` I've seen some variation in the effect of this as well, like two clusters forming alongside each other or the new brokers simply not forming a cluster at all until all the old ones are stopped, then restarting some or all of the new ones. Issue Time Tracking --- Worklog Id: (was: 945419) Time Spent: 40m (was: 0.5h) > 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: 40m > 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
[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945200&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945200 ] ASF GitHub Bot logged work on ARTEMIS-5174: --- Author: ASF GitHub Bot Created on: 22/Nov/24 16:01 Start Date: 22/Nov/24 16:01 Worklog Time Spent: 10m Work Description: jbertram commented on PR #5366: URL: https://github.com/apache/activemq-artemis/pull/5366#issuecomment-2494099055 @AntonRoskvist, can you elaborate on what compatibility issues you saw when upgrading? Issue Time Tracking --- Worklog Id: (was: 945200) Time Spent: 0.5h (was: 20m) > 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: 0.5h > 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
[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945161&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945161 ] ASF GitHub Bot logged work on ARTEMIS-5174: --- Author: ASF GitHub Bot Created on: 22/Nov/24 13:56 Start Date: 22/Nov/24 13:56 Worklog Time Spent: 10m Work Description: jbertram merged PR #5366: URL: https://github.com/apache/activemq-artemis/pull/5366 Issue Time Tracking --- Worklog Id: (was: 945161) Time Spent: 20m (was: 10m) > 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: 20m > 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
[jira] [Work logged] (ARTEMIS-5174) Have dependabot ignore jgroups until JGRP-2794 is resolved
[ https://issues.apache.org/jira/browse/ARTEMIS-5174?focusedWorklogId=945058&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945058 ] ASF GitHub Bot logged work on ARTEMIS-5174: --- Author: ASF GitHub Bot Created on: 22/Nov/24 07:31 Start Date: 22/Nov/24 07:31 Worklog Time Spent: 10m Work Description: AntonRoskvist opened a new pull request, #5366: URL: https://github.com/apache/activemq-artemis/pull/5366 This replaces #5360 Issue Time Tracking --- Worklog Id: (was: 945058) Remaining Estimate: 0h Time Spent: 10m > 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 > Time Spent: 10m > 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
