[JBoss JIRA] (ISPN-7933) Investigate moving the request id from a message header to the buffer
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7933:
----------------------------------
Summary: Investigate moving the request id from a message header to the buffer
Key: ISPN-7933
URL: https://issues.jboss.org/browse/ISPN-7933
Project: Infinispan
Issue Type: Task
Components: Core
Affects Versions: 9.1.0.Alpha1
Reporter: Dan Berindei
Assignee: Dan Berindei
The ISPN-6971 pull request removes the usage of JGroups' {{MessageDispatcher}}, but keeps using {{RequestCorrelator.Header}} to put the request id in the message. We could eliminate the header allocation and put the request id in the buffer.
OTOH having a separate header means the request id is visible in the logs of various JGroups protocols, so we may want to only replace {{RequestCorrelator.Header}} with our own header class.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7933) Investigate moving the request id from a message header to the buffer
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7933?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-7933:
-------------------------------
Status: Open (was: New)
> Investigate moving the request id from a message header to the buffer
> ---------------------------------------------------------------------
>
> Key: ISPN-7933
> URL: https://issues.jboss.org/browse/ISPN-7933
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 9.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
>
> The ISPN-6971 pull request removes the usage of JGroups' {{MessageDispatcher}}, but keeps using {{RequestCorrelator.Header}} to put the request id in the message. We could eliminate the header allocation and put the request id in the buffer.
> OTOH having a separate header means the request id is visible in the logs of various JGroups protocols, so we may want to only replace {{RequestCorrelator.Header}} with our own header class.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7710) CompatibilityProtoStreamMarshaller can't be set in server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7710?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7710:
----------------------------------------
[~anistor] I've sent a PR to apply the workaround. If you have any other changes in mind, let me know.
> CompatibilityProtoStreamMarshaller can't be set in server
> ---------------------------------------------------------
>
> Key: ISPN-7710
> URL: https://issues.jboss.org/browse/ISPN-7710
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Final
> Reporter: Galder Zamarreño
> Assignee: Adrian Nistor
> Fix For: 9.1.0.Final, 9.0.2.Final
>
>
> Out of the box, it's impossible to set compatibility marshaller to {{org.infinispan.query.remote.CompatibilityProtoStreamMarshaller}} in server because {{org.infinispan.main}} classloader can't access that class.
> As [~dan.berindei] suggested in the mailing list, one way to avoid these kind of issues would be to allow class definitions to have {{slot:module:class}} format so that using the ModularClassResolver any class can be found.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7710) CompatibilityProtoStreamMarshaller can't be set in server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7710?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7710:
-----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5205
> CompatibilityProtoStreamMarshaller can't be set in server
> ---------------------------------------------------------
>
> Key: ISPN-7710
> URL: https://issues.jboss.org/browse/ISPN-7710
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Final
> Reporter: Galder Zamarreño
> Assignee: Adrian Nistor
> Fix For: 9.1.0.Final, 9.0.2.Final
>
>
> Out of the box, it's impossible to set compatibility marshaller to {{org.infinispan.query.remote.CompatibilityProtoStreamMarshaller}} in server because {{org.infinispan.main}} classloader can't access that class.
> As [~dan.berindei] suggested in the mailing list, one way to avoid these kind of issues would be to allow class definitions to have {{slot:module:class}} format so that using the ModularClassResolver any class can be found.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months