[
https://issues.apache.org/jira/browse/GEODE-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Blum updated GEODE-7201:
-----------------------------
Description:
For testing, it is valid that I might register interests on a client Region
where the server-side Region is a PARTITION Region, yet I am not using either
mcast-port or Locators since I only need a single server for my tests!
Therefore this Exception is not helpful in anyway and only adds confusion to
the user...
{code}
at
org.apache.geode.internal.cache.tier.sockets.command.RegisterInterest61.cmdExecute(RegisterInterest61.java:257)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:851)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:75)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1227)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:616)
at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
... 1 common frames omitted
{code}
So, I "should" not...
> "_Should not register interest for a partitioned region when mcast-port is 0
> and no locator is present_"
Why not?
And, why does this message need to be logged at ERROR? WARN would suffice,
especially since "_should_" implies a "_recommendation_" and not a strict, hard
rule or requirement, which would be appropriate states as "_Must not register
interest..._".
was:
In tests is valid that I might register interests on a client Region where the
server-side Region is a PARTITION Region, yet I am not using either mcast-port
or Locators since I only need a single server for my tests!
Therefore this Exception is not helpful in anyway and only adds confusion to
the user...
{code}
at
org.apache.geode.internal.cache.tier.sockets.command.RegisterInterest61.cmdExecute(RegisterInterest61.java:257)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:851)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:75)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1227)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:616)
at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
... 1 common frames omitted
{code}
So, I "should" not...
> "_Should not register interest for a partitioned region when mcast-port is 0
> and no locator is present_"
Why not?
And, why does this message need to be logged at ERROR? WARN would suffice,
especially since "_should_" implies a "_recommendation_" and not a strict, hard
rule or requirement, which would be appropriate states as "_Must not register
interest..._".
> Useless and unhelpful Exception inappropriately logged at ERROR
> ---------------------------------------------------------------
>
> Key: GEODE-7201
> URL: https://issues.apache.org/jira/browse/GEODE-7201
> Project: Geode
> Issue Type: Bug
> Reporter: John Blum
> Priority: Major
> Labels: affects-spring
>
> For testing, it is valid that I might register interests on a client Region
> where the server-side Region is a PARTITION Region, yet I am not using either
> mcast-port or Locators since I only need a single server for my tests!
> Therefore this Exception is not helpful in anyway and only adds confusion to
> the user...
> {code}
> at
> org.apache.geode.internal.cache.tier.sockets.command.RegisterInterest61.cmdExecute(RegisterInterest61.java:257)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:851)
> at
> org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:75)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1227)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:616)
> at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> ... 1 common frames omitted
> {code}
> So, I "should" not...
> > "_Should not register interest for a partitioned region when mcast-port is
> > 0 and no locator is present_"
> Why not?
> And, why does this message need to be logged at ERROR? WARN would suffice,
> especially since "_should_" implies a "_recommendation_" and not a strict,
> hard rule or requirement, which would be appropriate states as "_Must not
> register interest..._".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
