July 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1235) Per class(es) logging settings in testsuite

by Galder Zamarreño (JIRA)

Per class(es) logging settings in testsuite ------------------------------------------- Key: ISPN-1235 URL: https://issues.jboss.org/browse/ISPN-1235 Project: Infinispan Issue Type: Enhancement Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.Final Just brainstorming: It'd be very useful to have a way to run the testsuite with normal logging settings but have the ability to define one or more test classes as having TRACE on x.y.z. This could be useful for those elusive failures that only happen when the testsuite runs! Clearly, it'd need some programmatic magic to enable/disable the logging at runtime, but there's some benefit to all this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-1015) Optimize HotRod client to match Memcached performance

by Dan Berindei (JIRA)

Optimize HotRod client to match Memcached performance ----------------------------------------------------- Key: ISPN-1015 URL: https://issues.jboss.org/browse/ISPN-1015 Project: Infinispan Issue Type: Task Reporter: Dan Berindei Assignee: Dan Berindei Load tests show the HotRod protocol performing worse than the Memcached client. Since the HotRod protocol should be easier to parse and we also have the extra topology information, this is quite surprising. We have analyzed the servers and seem to perform about the same, so we need to optimize the client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
20
0 / 0

[JBoss JIRA] Created: (ISPN-303) Follow up Jopr demo ideas

by Galder Zamarreno (JIRA)

Follow up Jopr demo ideas ------------------------- Key: ISPN-303 URL: https://jira.jboss.org/jira/browse/ISPN-303 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Ideas for a follow up Jopr demo: - Show ISPN-302 in action. - Heiko: About the monitoring schedules : in Administration->System Configuration->Templates you can also "predefine" this, so it gets applied to every new instance (and if wanted also to all existing instances). - Heiko: mention that 30 seconds is too too short for production -- 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

12 years, 7 months

3
5
0 / 0

[JBoss JIRA] (ISPN-2170) Size inaccuracy after emptying a populated cache

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2170: -------------------------------------- Summary: Size inaccuracy after emptying a populated cache Key: ISPN-2170 URL: https://issues.jboss.org/browse/ISPN-2170 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.2.0.ALPHA2, 5.1.5.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL Container size inaccuracy after populating and emptying the cache. See: https://gist.github.com/3168674 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2167) TestObjectStreamMarshaller doesn't use offset and size arguments

by William Burns (JIRA)

William Burns created ISPN-2167: ----------------------------------- Summary: TestObjectStreamMarshaller doesn't use offset and size arguments Key: ISPN-2167 URL: https://issues.jboss.org/browse/ISPN-2167 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.0.ALPHA1 Reporter: William Burns Assignee: Manik Surtani The TestObjectStreamMarshaller.objectFromByteBuffer(byte[], int, int) method does not actually pass the array with offsets. The code made a copy using the offset and size, but then passes the wrong byte array in. This is causing some issues with some tests I am writing for a CacheStore that I had to work around for now. I personally don't see why it creates a copy of the array when it could just pass in the offset and size directly and not incur the cost of copying the byte array again. I have a fix that just passes the offset and index directly to the ByteArrayInputStream instead of doing the copy. If you feel that the copy is still needed obviously then just change it to pass in newBytes as the change instead. I will attach a pull request soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
4
0 / 0

[JBoss JIRA] (ISPN-2168) To disable REALY for selected named caches within one cache manager

by dex chen (JIRA)

dex chen created ISPN-2168: ------------------------------ Summary: To disable REALY for selected named caches within one cache manager Key: ISPN-2168 URL: https://issues.jboss.org/browse/ISPN-2168 Project: Infinispan Issue Type: Enhancement Components: Core API Affects Versions: 5.1.5.FINAL Environment: ISPN 5.1.5.Final Reporter: dex chen Assignee: Manik Surtani As I understood, Infinispan supports to use JGROUPS RELAY to bridge 2 clusters across data centers for all configured named caches. However, there are cases that we just want to relay certain configured named caches, not others. For example, I have the following configurations: I have 2 named caches: relayCache, and noRelayCache. As name indicates, I just need to relay one of the caches across 2 sites/clusters. Right now, I do not have a way to configure this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (ISPN-2163) LowMemoryEvent in case of internal OoM Exceptions

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2163: ---------------------------------- Summary: LowMemoryEvent in case of internal OoM Exceptions Key: ISPN-2163 URL: https://issues.jboss.org/browse/ISPN-2163 Project: Infinispan Issue Type: Feature Request Reporter: Thomas Fromm Assignee: Manik Surtani -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
6
0 / 0

[JBoss JIRA] (ISPN-2153) Distributed ejb cache container on AS7 - Server hangs when invoking an SFSB

by Heinz Wilming (JIRA)

Heinz Wilming created ISPN-2153: ----------------------------------- Summary: Distributed ejb cache container on AS7 - Server hangs when invoking an SFSB Key: ISPN-2153 URL: https://issues.jboss.org/browse/ISPN-2153 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.1.5.FINAL Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT, EAP6 Reporter: Heinz Wilming Assignee: Manik Surtani Priority: Critical I'm working on scalable ha-clusters and I have a domain-mode cluster in mind which uses Infinispan-distribution to be scalable. So I started to make the cache-containers use distributed-caches instead of replicated ones. It starts up well and seems like everything is ok. But when I try to access a stateful-session-bean the server hangs. It only hangs when I try to use a distributed cache for the container ejb. If I use a replicated cache for ejb but still use distributed caches for cluster and web everything works fine. The problem does appear independent from the number of cluster nodes. By hanging I mean that the server won't complete the request. It will start to shutdown on CTRL+C but will not finish to. The only way to kill the server is kill -9. Attached to this post there is a file containing the stdout of the server with a thread-dump (kill -3) appended at the point where I requested a SFSB and nothing happened. Threaddump: [Server:server-one] "ajp-/192.168.122.165:8009-2" daemon prio=10 tid=0x08708800 nid=0x2583 runnable [0xb0882000] [Server:server-one] java.lang.Thread.State: RUNNABLE [Server:server-one] at java.util.HashMap.containsKey(HashMap.java:352) [Server:server-one] at java.util.HashSet.contains(HashSet.java:201) [Server:server-one] at org.infinispan.affinity.KeyAffinityServiceImpl.isNodeInConsistentHash(KeyAffinityServiceImpl.java:351) [Server:server-one] at org.infinispan.affinity.KeyAffinityServiceImpl.getKeyForAddress(KeyAffinityServiceImpl.java:145) [Server:server-one] at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.createIdentifier(InfinispanBackingCacheEntryStore.java:123) [Server:server-one] at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.createIdentifier(InfinispanBackingCacheEntryStore.java:71) [Server:server-one] at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.createIdentifier(SerializationGroupMemberContainer.java:83) [Server:server-one] at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.createIdentifier(SerializationGroupMemberContainer.java:51) [Server:server-one] at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.createIdentifier(PassivatingBackingCacheImpl.java:96) [Server:server-one] at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.createIdentifier(PassivatingBackingCacheImpl.java:60) [Server:server-one] at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.createIdentifier(AbstractCache.java:48) [Server:server-one] at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.createIdentifier(AbstractCache.java:39) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponentInstance.<init>(StatefulSessionComponentInstance.java:70) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.instantiateComponentInstance(StatefulSessionComponent.java:259) [Server:server-one] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:150) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:145) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:76) [Server:server-one] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:135) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:76) [Server:server-one] at org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.createInstance(TransactionAwareObjectFactory.java:53) [Server:server-one] at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.create(PassivatingBackingCacheImpl.java:121) [Server:server-one] at org.jboss.as.ejb3.cache.impl.GroupAwareCache.create(GroupAwareCache.java:67) [Server:server-one] at org.jboss.as.ejb3.cache.impl.GroupAwareCache.create(GroupAwareCache.java:41) [Server:server-one] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:241) [Server:server-one] at org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl.<init>(StatefulSessionObjectReferenceImpl.java:72) [Server:server-one] at org.jboss.as.weld.services.bootstrap.WeldEjbServices.resolveEjb(WeldEjbServices.java:60) [Server:server-one] at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:412) [Server:server-one] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:69) [Server:server-one] at org.jboss.weld.bean.SessionBean.create(SessionBean.java:297) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
8
0 / 0

[JBoss JIRA] (ISPN-2166) Missing source jars in stopping closing release in Nexus

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2166: -------------------------------------- Summary: Missing source jars in stopping closing release in Nexus Key: ISPN-2166 URL: https://issues.jboss.org/browse/ISPN-2166 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.ALPHA2 Nexus not allowing closing 5.2.0.ALPHA2 release with the following error: {code}Staging ruleset evaluation on repository 'JBoss Releases Staging Profile-048 (u:galder.zamarreno@jboss.com, a:10.33.144.144)' has failed. Staging Sources Validation -Missing: no sources jar found in folder '/org/infinispan/infinispan-rhq-plugin/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-gui-demo/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-ec2-demo/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-distexec-demo/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-directory-demo/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-lucene-demo/5.2.0.ALPHA2' -Missing: no sources jar found in folder '/org/infinispan/infinispan-nearcache-demo/5.2.0.ALPHA2'{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
3
0 / 0

[JBoss JIRA] (ISPN-2165) Release script is broken

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2165: -------------------------------------- Summary: Release script is broken Key: ISPN-2165 URL: https://issues.jboss.org/browse/ISPN-2165 Project: Infinispan Issue Type: Bug Components: Build process Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.ALPHA2 ... inflating: infinispan-5.2.0.ALPHA2-all/doc/configdocs/urn_infinispan_config_5.2/simpleType/transactionMode.html [INFO] Step 4: Update Google Analytics tracker Traceback (most recent call last): File "./bin/release.py", line 366, in <module> release() File "./bin/release.py", line 322, in release update_javadoc_tracker(base_dir, version) File "./bin/release.py", line 215, in update_javadoc_tracker os.chdir("%s/target/distribution/infinispan-%s/doc" % (base_dir, version)) OSError: [Errno 2] No such file or directory: '/Users/g/Go/releases/infinispan-5.2.0.ALPHA2/target/distribution/infinispan-5.2.0.ALPHA2/doc' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2012