[JBoss JIRA] (JGRP-2210) EOFException[JGRP000030] : failed handling incoming message
by Dharam Thacker (JIRA)
[ https://issues.jboss.org/browse/JGRP-2210?page=com.atlassian.jira.plugin.... ]
Dharam Thacker updated JGRP-2210:
---------------------------------
Description:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
[error 2017/07/28 00:13:30.521 EDT EventServer <unicast receiver,hostXXX> tid=0x45]
JGRP000030: hostXXX<v2>:1025: failed handling incoming message: java.io.EOFException
java.io.EOFException
at org.jgroups.util.ByteArrayDataInputStream.readShort(ByteArrayDataInputStream.java:138)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1705)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Within our company, there is some cyber security server which keeps hitting our process & I get below warning as well,
[warning 2017/08/16 22:05:51.334 EDT EventServer <unicast receiver,hostXXX> tid=0x46] JGRP000010: packet from *hostYYY*:45482 has different version (0.0.2) than ours (3.6.10); packet is discarded
*hostYYY* is not a part of my cluster process [Neither client not server] but some cyber security scanner which knows about all hosts and have its own way to check for security violations
Response from Geode community:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
was:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
[error 2017/07/28 00:13:30.521 EDT EventServer <unicast receiver,hostXXX> tid=0x45]
JGRP000030: hostXXX<v2>:1025: failed handling incoming message: java.io.EOFException
java.io.EOFException
at org.jgroups.util.ByteArrayDataInputStream.readShort(ByteArrayDataInputStream.java:138)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1705)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Within our company, there is some cyber security server which keeps hitting our process & I get below warning as well,
[warning 2017/08/16 22:05:51.334 EDT EventServer <unicast receiver,hostXXX> tid=0x46] JGRP000010: packet from *hostYYY*:45482 has different version (0.0.2) than ours (3.6.10); packet is discarded
>> *hostYYY *is not a part of my cluster process [Neither client not server] but some cyber security scanner which knows about all hosts and have its own way to check for security violations
Response from Geode community:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
> EOFException[JGRP000030] : failed handling incoming message
> -----------------------------------------------------------
>
> Key: JGRP-2210
> URL: https://issues.jboss.org/browse/JGRP-2210
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Dharam Thacker
> Assignee: Bela Ban
>
> Hi Team,
> I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
> I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
> I confirm that both of my client and server processes are using same version as 3.6.10.Final.
> I would request you to look into the same.
> *+Exception Stack Trace:+*
> [error 2017/07/28 00:13:30.521 EDT EventServer <unicast receiver,hostXXX> tid=0x45]
> JGRP000030: hostXXX<v2>:1025: failed handling incoming message: java.io.EOFException
> java.io.EOFException
> at org.jgroups.util.ByteArrayDataInputStream.readShort(ByteArrayDataInputStream.java:138)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1705)
> at org.jgroups.protocols.TP.receive(TP.java:1654)
> at org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:745)
> Within our company, there is some cyber security server which keeps hitting our process & I get below warning as well,
> [warning 2017/08/16 22:05:51.334 EDT EventServer <unicast receiver,hostXXX> tid=0x46] JGRP000010: packet from *hostYYY*:45482 has different version (0.0.2) than ours (3.6.10); packet is discarded
> *hostYYY* is not a part of my cluster process [Neither client not server] but some cyber security scanner which knows about all hosts and have its own way to check for security violations
> Response from Geode community:
> https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JGRP-2210) EOFException[JGRP000030] : failed handling incoming message
by Dharam Thacker (JIRA)
[ https://issues.jboss.org/browse/JGRP-2210?page=com.atlassian.jira.plugin.... ]
Dharam Thacker updated JGRP-2210:
---------------------------------
Description:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
[error 2017/07/28 00:13:30.521 EDT EventServer <unicast receiver,hostXXX> tid=0x45]
JGRP000030: hostXXX<v2>:1025: failed handling incoming message: java.io.EOFException
java.io.EOFException
at org.jgroups.util.ByteArrayDataInputStream.readShort(ByteArrayDataInputStream.java:138)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1705)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Response from Geode community:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
was:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
error 2017/08/16 23:28:46.396 EDT EventServer <unicast receiver,dharam-host-1> tid=0x45] JGRP000030: dharam-host-1.svr.us.domain.net<v2>:1025: failed handling incoming message: java.io.EOFException"
Response from Geode community:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
> EOFException[JGRP000030] : failed handling incoming message
> -----------------------------------------------------------
>
> Key: JGRP-2210
> URL: https://issues.jboss.org/browse/JGRP-2210
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Dharam Thacker
> Assignee: Bela Ban
>
> Hi Team,
> I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
> I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
> I confirm that both of my client and server processes are using same version as 3.6.10.Final.
> I would request you to look into the same.
> *+Exception Stack Trace:+*
> [error 2017/07/28 00:13:30.521 EDT EventServer <unicast receiver,hostXXX> tid=0x45]
> JGRP000030: hostXXX<v2>:1025: failed handling incoming message: java.io.EOFException
> java.io.EOFException
> at org.jgroups.util.ByteArrayDataInputStream.readShort(ByteArrayDataInputStream.java:138)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1705)
> at org.jgroups.protocols.TP.receive(TP.java:1654)
> at org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:745)
> Response from Geode community:
> https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JGRP-2210) EOFException[JGRP000030] : failed handling incoming message
by Dharam Thacker (JIRA)
[ https://issues.jboss.org/browse/JGRP-2210?page=com.atlassian.jira.plugin.... ]
Dharam Thacker updated JGRP-2210:
---------------------------------
Description:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
error 2017/08/16 23:28:46.396 EDT EventServer <unicast receiver,dharam-host-1> tid=0x45] JGRP000030: dharam-host-1.svr.us.domain.net<v2>:1025: failed handling incoming message: java.io.EOFException"
Response from Geode community:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
was:
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
error 2017/08/16 23:28:46.396 EDT EventServer <unicast receiver,dharam-host-1> tid=0x45] JGRP000030: dharam-host-1.svr.us.domain.net<v2>:1025: failed handling incoming message: java.io.EOFException"
> EOFException[JGRP000030] : failed handling incoming message
> -----------------------------------------------------------
>
> Key: JGRP-2210
> URL: https://issues.jboss.org/browse/JGRP-2210
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Dharam Thacker
> Assignee: Bela Ban
>
> Hi Team,
> I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
> I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
> I confirm that both of my client and server processes are using same version as 3.6.10.Final.
> I would request you to look into the same.
> *+Exception Stack Trace:+*
> error 2017/08/16 23:28:46.396 EDT EventServer <unicast receiver,dharam-host-1> tid=0x45] JGRP000030: dharam-host-1.svr.us.domain.net<v2>:1025: failed handling incoming message: java.io.EOFException"
> Response from Geode community:
> https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JGRP-2210) EOFException[JGRP000030] : failed handling incoming message
by Dharam Thacker (JIRA)
Dharam Thacker created JGRP-2210:
------------------------------------
Summary: EOFException[JGRP000030] : failed handling incoming message
Key: JGRP-2210
URL: https://issues.jboss.org/browse/JGRP-2210
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.10
Reporter: Dharam Thacker
Assignee: Bela Ban
Hi Team,
I am using Apache geode as our distributed caching solution which internally using JGroups 3.6.10.Final version.
I see this exception almost daily 5-6 times but we don't know the root cause for that. I tried reaching with Apache Geode community as well. As per their suggestion, it could be due to empty datagrams being sent to process.
I confirm that both of my client and server processes are using same version as 3.6.10.Final.
I would request you to look into the same.
*+Exception Stack Trace:+*
error 2017/08/16 23:28:46.396 EDT EventServer <unicast receiver,dharam-host-1> tid=0x45] JGRP000030: dharam-host-1.svr.us.domain.net<v2>:1025: failed handling incoming message: java.io.EOFException"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9233) [GSS](7.1.0) Add optional support for RFC6265 compliant cookie validation
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9233?page=com.atlassian.jira.plugin.... ]
Stuart Douglas moved JBEAP-12758 to WFLY-9233:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9233 (was: JBEAP-12758)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Affects Version/s: (was: 7.0.5.GA)
> [GSS](7.1.0) Add optional support for RFC6265 compliant cookie validation
> -------------------------------------------------------------------------
>
> Key: WFLY-9233
> URL: https://issues.jboss.org/browse/WFLY-9233
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Priority: Blocker
> Labels: downstream_dependency
>
> Undertow does not conform to Set-Cookie syntax defined in the cookie specification.
> [RFC6265 (Section 4.1 Set-Cookie)|http://httpwg.org/specs/rfc6265.html#rfc.section.4.1] states that Servers SHOULD NOT send Set-Cookie headers that fail to conform the defined grammer. For example, cookie value should be US-ASCII characters excluding CTLs, whitespace, double quote, comma, semicolon, and backslash.
> However, undertow does not restrict the invalid characters. For example, when accessing the following JSP which add one of invalid characters (whitespace) to cookie value:
> {code}
> <%
> Cookie c = new Cookie("example","example cookie");
> response.addCookie(c);
> %>
> {code}
> undertow responds with the following Set-Cookie format but this is not correct {{Set-Cookie}} header in RFC6265:
> {code}
> Set-Cookie: example=example cookie
> {code}
> Note: The previous cookie specifications ([RFC2109|https://tools.ietf.org/html/rfc2109#section-4.1] and [RFC2965|https://tools.ietf.org/html/rfc2965#section-3.1]) allow some characters in cookie value when the cookie value are quoted. (i.e. {{Set-Cookie: example="example cookie"}} was allowed in the old specifications.) EAP 6/JBossWeb (and Tomcat 6.0/7.0/8.0) conform to this old specification and it will automatically quotes a cookie value (also path and domain) when the value contains any seprarator characters which should be quoted.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (LOGMGR-160) Fix JavaDoc for the SizeRotatingFileHander.setSuffix()
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-160?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-160:
---------------------------------
Fix Version/s: 2.0.8.Final
> Fix JavaDoc for the SizeRotatingFileHander.setSuffix()
> ------------------------------------------------------
>
> Key: LOGMGR-160
> URL: https://issues.jboss.org/browse/LOGMGR-160
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 2.0.8.Final, 2.1.0.Alpha3
>
>
> The JavaDoc for the {{SizeRotatingFileHandler.setSuffix()}} indicates that files will not be deleted when deleted. However there are multiple rotations for the same date they will be purged.
> For example if the suffix is {{.yyyy-DD-mm}}, the size was reached 20 times on the same day and the {{maxBackupIndex}} was set to 10 there will only be 10 files kept.What won't be purged is files from a previous day.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months