October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3587) Add remote query support in ispn server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3587?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3587: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1015412|https://bugzilla.redhat.com/show_bug.cgi?id=1015412] from ON_QA to ASSIGNED > Add remote query support in ispn server > --------------------------------------- > > Key: ISPN-3587 > URL: https://issues.jboss.org/browse/ISPN-3587 > Project: Infinispan > Issue Type: Feature Request > Components: Querying, Server > Reporter: William Burns > Assignee: William Burns > Labels: jdg62GAblocker > Fix For: 6.0.0.CR1 > > > Infinispan Server querying over HotRod doesn't currently work. There appears to be a CL hell that we need to go through first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3582: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1015412|https://bugzilla.redhat.com/show_bug.cgi?id=1015412] from ON_QA to ASSIGNED > Server does not expose MBean for registering server-side serialization context > ------------------------------------------------------------------------------ > > Key: ISPN-3582 > URL: https://issues.jboss.org/browse/ISPN-3582 > Project: Infinispan > Issue Type: Bug > Components: Querying, Server > Affects Versions: 6.0.0.Beta2 > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62GAblocker > Fix For: 6.0.0.CR1 > > > There should be the following MBean available when starting ISPN server: > {code} > jboss.infinispan:type=RemoteQuery,name="{cacheManagerName}",component=ProtobufMetadataManager > {code} > However, this MBean is not exposed and so the server-side serialization context cannot be configured. > More information about the MBean and its usage can be found in HotRodQueryTest . In infinispan itself (non-server) the JMX domain would be different but in the server it should be jboss.infinispan > I'll attach a test for server-side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3582: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> made a comment on [bug 1015412|https://bugzilla.redhat.com/show_bug.cgi?id=1015412] The server contains wrong version of hibernate-search so the existing tests fail and remote querying is not working. Setting back to ASSIGNED. > Server does not expose MBean for registering server-side serialization context > ------------------------------------------------------------------------------ > > Key: ISPN-3582 > URL: https://issues.jboss.org/browse/ISPN-3582 > Project: Infinispan > Issue Type: Bug > Components: Querying, Server > Affects Versions: 6.0.0.Beta2 > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62GAblocker > Fix For: 6.0.0.CR1 > > > There should be the following MBean available when starting ISPN server: > {code} > jboss.infinispan:type=RemoteQuery,name="{cacheManagerName}",component=ProtobufMetadataManager > {code} > However, this MBean is not exposed and so the server-side serialization context cannot be configured. > More information about the MBean and its usage can be found in HotRodQueryTest . In infinispan itself (non-server) the JMX domain would be different but in the server it should be jboss.infinispan > I'll attach a test for server-side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3587) Add remote query support in ispn server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3587?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3587: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> made a comment on [bug 1015412|https://bugzilla.redhat.com/show_bug.cgi?id=1015412] The server contains wrong version of hibernate-search so the existing tests fail and remote querying is not working. Setting back to ASSIGNED. > Add remote query support in ispn server > --------------------------------------- > > Key: ISPN-3587 > URL: https://issues.jboss.org/browse/ISPN-3587 > Project: Infinispan > Issue Type: Feature Request > Components: Querying, Server > Reporter: William Burns > Assignee: William Burns > Labels: jdg62GAblocker > Fix For: 6.0.0.CR1 > > > Infinispan Server querying over HotRod doesn't currently work. There appears to be a CL hell that we need to go through first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3603) Conditional command is committed when it fails on primary owner

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3603?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3603: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1016499 > Conditional command is committed when it fails on primary owner > --------------------------------------------------------------- > > Key: ISPN-3603 > URL: https://issues.jboss.org/browse/ISPN-3603 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > In non-tx cache, when conditional command (e.g. ReplaceCommand) fails on primary owner because the old value is not equal to current value, the NonTxDistributionInterceptor.visitReplaceCommand returns false but the entry is committed in EntryWrappingInterceptor anyway. > Speaking about EntryWrappingInterceptor.invokeNextAndApplyChanges: NonTxDistributionInterceptor does not mark the command as unsuccessful if it fails on the primary owner, therefore, checking for command.isSuccessful() in order to retry the command upon topology change may seem insufficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3603) Conditional command is committed when it fails on primary owner

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3603?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3603: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> made a comment on [bug 1016499|https://bugzilla.redhat.com/show_bug.cgi?id=1016499] In non-tx cache, when conditional command (e.g. ReplaceCommand) fails on primary owner because the old value is not equal to current value, the NonTxDistributionInterceptor.visitReplaceCommand returns false but the entry is committed in EntryWrappingInterceptor anyway. Speaking about EntryWrappingInterceptor.invokeNextAndApplyChanges: NonTxDistributionInterceptor does not mark the command as unsuccessful if it fails on the primary owner, therefore, checking for command.isSuccessful() in order to retry the command upon topology change may seem insufficient. > Conditional command is committed when it fails on primary owner > --------------------------------------------------------------- > > Key: ISPN-3603 > URL: https://issues.jboss.org/browse/ISPN-3603 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > In non-tx cache, when conditional command (e.g. ReplaceCommand) fails on primary owner because the old value is not equal to current value, the NonTxDistributionInterceptor.visitReplaceCommand returns false but the entry is committed in EntryWrappingInterceptor anyway. > Speaking about EntryWrappingInterceptor.invokeNextAndApplyChanges: NonTxDistributionInterceptor does not mark the command as unsuccessful if it fails on the primary owner, therefore, checking for command.isSuccessful() in order to retry the command upon topology change may seem insufficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3603) Conditional command is committed when it fails on primary owner

by Radim Vansa (JIRA)

Radim Vansa created ISPN-3603: --------------------------------- Summary: Conditional command is committed when it fails on primary owner Key: ISPN-3603 URL: https://issues.jboss.org/browse/ISPN-3603 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Radim Vansa Assignee: Mircea Markus Priority: Critical In non-tx cache, when conditional command (e.g. ReplaceCommand) fails on primary owner because the old value is not equal to current value, the NonTxDistributionInterceptor.visitReplaceCommand returns false but the entry is committed in EntryWrappingInterceptor anyway. Speaking about EntryWrappingInterceptor.invokeNextAndApplyChanges: NonTxDistributionInterceptor does not mark the command as unsuccessful if it fails on the primary owner, therefore, checking for command.isSuccessful() in order to retry the command upon topology change may seem insufficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3183) HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3183: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> made a comment on [bug 986307|https://bugzilla.redhat.com/show_bug.cgi?id=986307] I'm pretty sure that this should be ON_QA. Setting ON_QA + target milestone back to ER2, and immediately setting as VERIFIED (in for 6.2 ER2 build) because this seems to be no longer an issue since this build. > HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS > ----------------------------------------------------------------------------------- > > Key: ISPN-3183 > URL: https://issues.jboss.org/browse/ISPN-3183 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2 > > Attachments: 52to52sourceTrace, 52to52targetTrace, 52to53sourceTrace, 52to53targetTrace > > > Scenario (typical for rollups): > Start source node, put entries. > Start target node which is pointing to source (source is his RemoteCacheStore now) and try to get entries. > For 5.2 to 5.2 working perfectly. > For 5.2 source and 5.3 target -- we have problems here. > Sorry that I can't provide any valuable info beside TRACEs. > 4 TRACE logs -- rollups from 5.2 to 5.2 source log and target log + rollups from 5.2 to 5.3 source log and target log. > Very quick summary: > 5.2 to 5.2 on target: Entry exists in loader? true > 5.2 to 5.3 on targer: > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Exists in context? null > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Retrieved from container null > What changed in RemoteCacheStore. What changed in HotRod? Any idea? Let me know, thank you! > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3183) HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3183: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 986307|https://bugzilla.redhat.com/show_bug.cgi?id=986307] from ASSIGNED to ON_QA > HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS > ----------------------------------------------------------------------------------- > > Key: ISPN-3183 > URL: https://issues.jboss.org/browse/ISPN-3183 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2 > > Attachments: 52to52sourceTrace, 52to52targetTrace, 52to53sourceTrace, 52to53targetTrace > > > Scenario (typical for rollups): > Start source node, put entries. > Start target node which is pointing to source (source is his RemoteCacheStore now) and try to get entries. > For 5.2 to 5.2 working perfectly. > For 5.2 source and 5.3 target -- we have problems here. > Sorry that I can't provide any valuable info beside TRACEs. > 4 TRACE logs -- rollups from 5.2 to 5.2 source log and target log + rollups from 5.2 to 5.3 source log and target log. > Very quick summary: > 5.2 to 5.2 on target: Entry exists in loader? true > 5.2 to 5.3 on targer: > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Exists in context? null > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Retrieved from container null > What changed in RemoteCacheStore. What changed in HotRod? Any idea? Let me know, thank you! > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3183) HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3183: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 986307|https://bugzilla.redhat.com/show_bug.cgi?id=986307] from ON_QA to VERIFIED > HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS > ----------------------------------------------------------------------------------- > > Key: ISPN-3183 > URL: https://issues.jboss.org/browse/ISPN-3183 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2 > > Attachments: 52to52sourceTrace, 52to52targetTrace, 52to53sourceTrace, 52to53targetTrace > > > Scenario (typical for rollups): > Start source node, put entries. > Start target node which is pointing to source (source is his RemoteCacheStore now) and try to get entries. > For 5.2 to 5.2 working perfectly. > For 5.2 source and 5.3 target -- we have problems here. > Sorry that I can't provide any valuable info beside TRACEs. > 4 TRACE logs -- rollups from 5.2 to 5.2 source log and target log + rollups from 5.2 to 5.3 source log and target log. > Very quick summary: > 5.2 to 5.2 on target: Entry exists in loader? true > 5.2 to 5.3 on targer: > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Exists in context? null > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Retrieved from container null > What changed in RemoteCacheStore. What changed in HotRod? Any idea? Let me know, thank you! > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2013