December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3296) Total Order: timeout exceptions are not throw correctly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3296?page=com.atlassian.jira.plugin.... ] Work on ISPN-3296 started by Pedro Ruivo. > Total Order: timeout exceptions are not throw correctly > ------------------------------------------------------- > > Key: ISPN-3296 > URL: https://issues.jboss.org/browse/ISPN-3296 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 6.1.0.Final > > > Issues found in Cloud-TM. Check if they happen here and create a JIRA for each of them > * IgnoreExtraResponseFilter is not needed anymore. > * missing argument log message > * TimeoutException, when happens, it is ignored and the transaction is processed normally > * TimeoutException can block the total order chain (all system is blocked!) > * port the testTimeoutCleanup from cloudtm to master -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3296) Total Order: timeout exceptions are not throw correctly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3296?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3296: ------------------------------ Summary: Total Order: timeout exceptions are not throw correctly (was: Total Order check list) > Total Order: timeout exceptions are not throw correctly > ------------------------------------------------------- > > Key: ISPN-3296 > URL: https://issues.jboss.org/browse/ISPN-3296 > Project: Infinispan > Issue Type: Task > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 6.1.0.Final > > > Issues found in Cloud-TM. Check if they happen here and create a JIRA for each of them > * IgnoreExtraResponseFilter is not needed anymore. > * missing argument log message > * TimeoutException, when happens, it is ignored and the transaction is processed normally > * TimeoutException can block the total order chain (all system is blocked!) > * port the testTimeoutCleanup from cloudtm to master -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3755) Add more detailed description of the filtering operators supported by the new query DSL

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3755?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3755: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.1.0.Final Resolution: Done > Add more detailed description of the filtering operators supported by the new query DSL > --------------------------------------------------------------------------------------- > > Key: ISPN-3755 > URL: https://issues.jboss.org/browse/ISPN-3755 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 620 > Fix For: 6.1.0.Final > > > The documentation exists (http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_filtering_op...), but is a bit scarce. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2285) Allow embedding of JGroups configuration in Infinispan XML

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2285?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2285: ---------------------------------- Assignee: Galder Zamarreño (was: Tristan Tarrant) > Allow embedding of JGroups configuration in Infinispan XML > ---------------------------------------------------------- > > Key: ISPN-2285 > URL: https://issues.jboss.org/browse/ISPN-2285 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: NadirX > Assignee: Galder Zamarreño > Priority: Minor > > When specifying a transport we should allow "embedding" the JGroups XML configuration. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2309) Support parsing of the AS7 threads configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2309?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2309: ---------------------------------- Assignee: Galder Zamarreño (was: Tristan Tarrant) > Support parsing of the AS7 threads configuration > ------------------------------------------------ > > Key: ISPN-2309 > URL: https://issues.jboss.org/browse/ISPN-2309 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: NadirX > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3731) Multicast messages can be replayed to new node

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3731?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3731: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2296 > Multicast messages can be replayed to new node > ---------------------------------------------- > > Key: ISPN-3731 > URL: https://issues.jboss.org/browse/ISPN-3731 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > > Messages that target all current members are sent as multicast messages. > However, these retransmissions can be replayed on new nodes that have just joined the cluster. > This can result for example in execution of already completed transaction on the new node, causing possible data inconsistency for those entries which are owned by the new node in backup way - the replayed transaction sequence authoritatively overwrites them. > The node should remember the first topologyId it has seen and do not execute any commands that have lower topologyId. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3731) Multicast messages can be replayed to new node

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3731?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3731: ------------------------------------ I've created ISPN-3843 for the broadcast optimization, we need to run some performance tests to see whether we should remove it only for asynchronous RPCs or for synchronous/OOB RPCs as well. > Multicast messages can be replayed to new node > ---------------------------------------------- > > Key: ISPN-3731 > URL: https://issues.jboss.org/browse/ISPN-3731 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > > Messages that target all current members are sent as multicast messages. > However, these retransmissions can be replayed on new nodes that have just joined the cluster. > This can result for example in execution of already completed transaction on the new node, causing possible data inconsistency for those entries which are owned by the new node in backup way - the replayed transaction sequence authoritatively overwrites them. > The node should remember the first topologyId it has seen and do not execute any commands that have lower topologyId. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3843: ---------------------------------- Summary: Remove broadcast/unicast optimization in JGroupsTransport Key: ISPN-3843 URL: https://issues.jboss.org/browse/ISPN-3843 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 6.0.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 6.1.0.Final The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3770) Incorrect Content-Type header when putting object via REST and get with different Accept

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3770?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-3770: ---------------------------------------- Actually, I had misread this. I thought the test was failing in compatibility mode, but this is disabled in the test actually. Martin's answer is correct, closing. > Incorrect Content-Type header when putting object via REST and get with different Accept > ---------------------------------------------------------------------------------------- > > Key: ISPN-3770 > URL: https://issues.jboss.org/browse/ISPN-3770 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Jiří Holuša > Assignee: Galder Zamarreño > Fix For: 6.1.0.Final > > > When putting serialized object via REST post and then getting it back with different Accept header (for example application/json), the retrieved data has still the "creation-time" Content-Type and data doesn't change in any way. > I would expect retrieving nice json structure for instace. > Code snippet: > {code} > public void testCustomObjectGetAcceptJSONAndXML() throws Exception{ > String fullPathKeyA = fullPathKey(KEY_A); > TestSerializable object = new TestSerializable("CONTENT"); > ByteArrayOutputStream bout = new ByteArrayOutputStream(); > ObjectOutputStream oo = new ObjectOutputStream(bout); > oo.writeObject(object); > oo.flush(); > oo.close(); > byte[] byteData = bout.toByteArray(); > post(fullPathKeyA, byteData, "application/x-java-serialized-object"); > HttpResponse getJson = get(fullPathKeyA, null, HttpServletResponse.SC_OK, true, "Accept", "application/json"); > assertTrue(getJson.getHeaders("Content-type")[0].getValue().contains("application/json")); //this assertion fails > HttpResponse getXml = get(fullPathKeyA, null, HttpServletResponse.SC_OK, true, "Accept", "application/xml"); > assertTrue(getXml.getHeaders("Content-type")[0].getValue().contains("application/xml")); //this assertion fails > } > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3770) Incorrect Content-Type header when putting object via REST and get with different Accept

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3770?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-3770. ------------------------------------ Fix Version/s: (was: 6.1.0.Final) Resolution: Rejected > Incorrect Content-Type header when putting object via REST and get with different Accept > ---------------------------------------------------------------------------------------- > > Key: ISPN-3770 > URL: https://issues.jboss.org/browse/ISPN-3770 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Jiří Holuša > Assignee: Galder Zamarreño > > When putting serialized object via REST post and then getting it back with different Accept header (for example application/json), the retrieved data has still the "creation-time" Content-Type and data doesn't change in any way. > I would expect retrieving nice json structure for instace. > Code snippet: > {code} > public void testCustomObjectGetAcceptJSONAndXML() throws Exception{ > String fullPathKeyA = fullPathKey(KEY_A); > TestSerializable object = new TestSerializable("CONTENT"); > ByteArrayOutputStream bout = new ByteArrayOutputStream(); > ObjectOutputStream oo = new ObjectOutputStream(bout); > oo.writeObject(object); > oo.flush(); > oo.close(); > byte[] byteData = bout.toByteArray(); > post(fullPathKeyA, byteData, "application/x-java-serialized-object"); > HttpResponse getJson = get(fullPathKeyA, null, HttpServletResponse.SC_OK, true, "Accept", "application/json"); > assertTrue(getJson.getHeaders("Content-type")[0].getValue().contains("application/json")); //this assertion fails > HttpResponse getXml = get(fullPathKeyA, null, HttpServletResponse.SC_OK, true, "Accept", "application/xml"); > assertTrue(getXml.getHeaders("Content-type")[0].getValue().contains("application/xml")); //this assertion fails > } > {code} -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013