[JBoss JIRA] (ISPN-7230) XSite view should be logged at INFO
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7230?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7230:
-----------------------------------
Fix Version/s: 9.0.0.Beta2
> XSite view should be logged at INFO
> -----------------------------------
>
> Key: ISPN-7230
> URL: https://issues.jboss.org/browse/ISPN-7230
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cross-Site Replication
> Affects Versions: 9.0.0.Alpha4, 8.2.5.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 9.0.0.Beta2, 9.0.0.Final
>
>
> XSite view should be printed as INFO message. Currently, the only log messages printed are:
> Site A:
> {code}
> 11:19:00,398 INFO [org.jgroups.protocols.relay.RELAY2]
> (Timer-2,gs-macbook-pro-3) _gs-macbook-pro-3:LON:
> joined bridge cluster 'xsite'
> {code}
> Site B:
> {code}
> 11:19:31,329 INFO [org.jgroups.protocols.relay.RELAY2]
> (Timer-3,gs-macbook-pro-3) _gs-macbook-pro-3:NYC:
> joined bridge cluster 'xsite'
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months
[JBoss JIRA] (ISPN-7358) Hot Rod server not dealing with pipe requests properly
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7358?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7358:
-----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4767
> Hot Rod server not dealing with pipe requests properly
> ------------------------------------------------------
>
> Key: ISPN-7358
> URL: https://issues.jboss.org/browse/ISPN-7358
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.0.0.Beta1, 8.2.5.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Blocker
> Fix For: 9.0.0.Beta2, 9.0.0.Final
>
>
> This might not become so apparent with the current synchronous Java client, but with fully asynchronous clients such as the Javascript one, multiple requests can be piped one after the other.
> Hot Rod server does not often deal with those well, showing exceptions such as:
> {code}
> org.infinispan.server.hotrod.InvalidMagicIdException:
> Error reading magic byte or message id: 119
> {code}
> {code}
> org.infinispan.server.hotrod.UnknownVersionException:
> Unknown version:-96
> {code}
> This exceptions appear when applying considerable load with the Javascript client (see HRJS-24), but the same effect can be replicated with a Netty based, fully asynchronous client, such as the simplified version used [here|https://gist.github.com/galderz/94705dd73d5339b1ab5aa0a5157a9803].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months