October 2009 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-242) MarshalledValue leaked to event listener implementations when lazy deserialization is on

by Galder Zamarreno (JIRA)

MarshalledValue leaked to event listener implementations when lazy deserialization is on ---------------------------------------------------------------------------------------- Key: ISPN-242 URL: https://jira.jboss.org/jira/browse/ISPN-242 Project: Infinispan Issue Type: Bug Components: Listeners Affects Versions: 4.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR2 I've noticed that when lazy deserialization is on and you use a user defined key, notification callbacks receive MarshalledValue instances within event.getKey() rather than instances of the user defined class. This forces listener code to be aware whether lazy deserialization is enabled or not, hence we're leaking an implementation detail to the client code. I think these callbacks should provide user defined class instances regardless of whether lazy deserialization is on or not. Manik: The event instance should be able to detect a MarshalledValue and return the actual key. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-104) Update release script

by Manik Surtani (JIRA)

Update release script --------------------- Key: ISPN-104 URL: https://jira.jboss.org/jira/browse/ISPN-104 Project: Infinispan Issue Type: Task Reporter: Manik Surtani Assignee: Navin Surtani Priority: Minor Fix For: 4.0.0.BETA1 The release script (written in Python) needs to be updated to: 1. Include JMX docs 2. Include config guide (ISPN-89) 3. Update docs with Google Analytics tags (currently done by running bin/updateTracker.sh manually before uploading docs) 4. Upload javadocs to SourceForge 5. Upload release files to SourceForge (SourceForge has an API for this) 6. Upload XSD schema to www.infinispan.org (need to check with the JBoss.org team on how to do this programmatically. Currently done via the CMS interface) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-167) Ensure the mvn deploy process handles all ancillary tasks such as generating documentation, schema and parsers

by Manik Surtani (JIRA)

Ensure the mvn deploy process handles all ancillary tasks such as generating documentation, schema and parsers -------------------------------------------------------------------------------------------------------------- Key: ISPN-167 URL: https://jira.jboss.org/jira/browse/ISPN-167 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA6 Reporter: Manik Surtani Assignee: Manik Surtani Priority: Blocker Fix For: 4.0.0.BETA1 Currently doing $ mvn deploy -Dmaven.test.skip.exec=true -Pdistribution does not generate JMX or Config docs, or the XSD schemas. JMX and config docs can be generated separately using scripts in bin/ but this is a pain. Ideally, running mvn deploy -Dmaven.test.skip.exec=true -Pdistribution should: 1. Generate schema - make sure this schema is packaged in the core JAR as well as made available in /etc/schema in the -ALL jar 2. Generate parsers - make sure this parser is packaged in the core JAR 3. Generate Javadoc, JMX docs and config docs - all in the /doc directory of the -ALL jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
5
0 / 0

[JBoss JIRA] Resolved: (ISPN-185) Need to provide a mechanism in which a JGroups channel can be passed in.

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-185?page=com.atlassian.jira.plugi... ] Manik Surtani resolved ISPN-185. -------------------------------- Resolution: Done > Need to provide a mechanism in which a JGroups channel can be passed in. > ------------------------------------------------------------------------ > > Key: ISPN-185 > URL: https://jira.jboss.org/jira/browse/ISPN-185 > Project: Infinispan > Issue Type: Task > Affects Versions: 4.0.0.BETA1 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.0.0.CR2, 4.0.0.GA > > > Analogous to the old JBoss Cache RuntimeConfig bean. Necessary for systems where a channel is already created and existing, and needs to be reused. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-185) Need to provide a mechanism in which a JGroups channel can be passed in.

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-185?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-185: ------------------------------------ Implemented using org.infinispan.remoting.transport.jgroups.JGroupsChannelLookup In your Infinispan config, you can specify this lookup by: <transport ....> <properties> <property name="channelLookup" value="com.blah.MyJGroupsChannelLookup" /> </properties> </transport> > Need to provide a mechanism in which a JGroups channel can be passed in. > ------------------------------------------------------------------------ > > Key: ISPN-185 > URL: https://jira.jboss.org/jira/browse/ISPN-185 > Project: Infinispan > Issue Type: Task > Affects Versions: 4.0.0.BETA1 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.0.0.CR2, 4.0.0.GA > > > Analogous to the old JBoss Cache RuntimeConfig bean. Necessary for systems where a channel is already created and existing, and needs to be reused. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-142) More JMX information to be exposed

by Manik Surtani (JIRA)

More JMX information to be exposed ---------------------------------- Key: ISPN-142 URL: https://jira.jboss.org/jira/browse/ISPN-142 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.CR1, 4.0.0.GA This is a wish-list of what folks want to see exposed via JMX (and JOPR). Please add to the comments with what you would like to see. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Updated: (ISPN-188) Benchmark Infinispan cache provider

by Galder Zamarreno (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-188?page=com.atlassian.jira.plugi... ] Galder Zamarreno updated ISPN-188: ---------------------------------- Fix Version/s: 5.0.0.BETA1 (was: 4.0.0.GA) > Benchmark Infinispan cache provider > ----------------------------------- > > Key: ISPN-188 > URL: https://jira.jboss.org/jira/browse/ISPN-188 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreno > Assignee: Galder Zamarreno > Fix For: 5.0.0.BETA1 > > > We have an EJB3 app that stresses 2nd level cache: http://anonsvn.jboss.org/repos/qa/ejb3demo/ > More work will go in the near future into this app, and so it's worth waiting for the outcome of that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-188) Benchmark Infinispan cache provider

by Galder Zamarreno (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-188?page=com.atlassian.jira.plugi... ] Galder Zamarreno updated ISPN-188: ---------------------------------- Priority: Minor (was: Major) > Benchmark Infinispan cache provider > ----------------------------------- > > Key: ISPN-188 > URL: https://jira.jboss.org/jira/browse/ISPN-188 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreno > Assignee: Galder Zamarreno > Priority: Minor > Fix For: 5.0.0.BETA1 > > > We have an EJB3 app that stresses 2nd level cache: http://anonsvn.jboss.org/repos/qa/ejb3demo/ > More work will go in the near future into this app, and so it's worth waiting for the outcome of that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-100) test Infinispan binding to JNDI

by Mircea Markus (JIRA)

test Infinispan binding to JNDI ------------------------------- Key: ISPN-100 URL: https://jira.jboss.org/jira/browse/ISPN-100 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA This is related to a forum post(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235108#423.... a serialization exception appeared when trying to bind JBossCache instance in JNDI; same should hapend for Infinispan. Though I wouldn't expect the CacheDelegate to be serialized, this JIRA is for checking that binding a Infinispan instance can be placed in JNDI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Resolved: (ISPN-30) DIST - distributed cache

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-30?page=com.atlassian.jira.plugin... ] Manik Surtani resolved ISPN-30. ------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.CR2) Resolution: Done > DIST - distributed cache > ------------------------ > > Key: ISPN-30 > URL: https://jira.jboss.org/jira/browse/ISPN-30 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.0.0.GA, 4.0.0.CR1 > > Time Spent: 4 hours > > - Detailed designs should be on a wiki somewhere for review > - Consistent hash algo should be pluggable > - A new cache mode ("d" or "distributed", in addition to "r", "replicated", "i", "invalidated") > - Should include code for rebalancing > - A front-end L1 cache for fast reads > - Multicast invalidation to flush L1's -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2009