January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1749) log4j.configuration system property cannot be set

by David van Balen (JIRA)

David van Balen created ISPN-1749: ------------------------------------- Summary: log4j.configuration system property cannot be set Key: ISPN-1749 URL: https://issues.jboss.org/browse/ISPN-1749 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR4 Environment: Unix Reporter: David van Balen Assignee: Manik Surtani Although the startServer.sh script provides a way to specify custom system properties, via the JVM_PARAMS environment variable, it is not possible to specify a different log4j configuration file through the log4j.configuration system property because it will be overridden in functions.sh (see script snippet below, starting at line 154 of functions.sh). I think the portion of functions.sh that sets the location of the log4j configuration file should only execute if the user hasn't provided their own location. # Log4J config path needs path conversion in Cygwin if $CYGWIN; then LOG4J_CONFIG=`cygpath -w "${ISPN_HOME}/etc/log4j.xml"` else LOG4J_CONFIG=${ISPN_HOME}/etc/log4j.xml fi START_ARGS=( "${START_ARGS[@]}" "-Dlog4j.configuration=file:///$LOG4J_CONFIG" ) -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] (ISPN-1772) Entry iterators should initialize currentTime lazily

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1772: ------------------------------------- Summary: Entry iterators should initialize currentTime lazily Key: ISPN-1772 URL: https://issues.jboss.org/browse/ISPN-1772 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.FINAL Initializing the value of System#currentTimeMillis is so expensive that should not be done if not needed, for example if all involved entries are immortal. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1773) Some time intervals still using System.currentTimeMillis

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1773: ------------------------------------- Summary: Some time intervals still using System.currentTimeMillis Key: ISPN-1773 URL: https://issues.jboss.org/browse/ISPN-1773 Project: Infinispan Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.1.0.FINAL -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1774) Avoid duplicate invocation to currentTime in entry constructors

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1774: ------------------------------------- Summary: Avoid duplicate invocation to currentTime in entry constructors Key: ISPN-1774 URL: https://issues.jboss.org/browse/ISPN-1774 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.1.0.FINAL -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1771) CommandAwareRpcDispatcher should not invoke currentTime at all - does twice

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1771: ------------------------------------- Summary: CommandAwareRpcDispatcher should not invoke currentTime at all - does twice Key: ISPN-1771 URL: https://issues.jboss.org/browse/ISPN-1771 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.FINAL -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1765) InterruptedException during cluster shutdown in state transfer

by Michal Linhard (JIRA)

Michal Linhard created ISPN-1765: ------------------------------------ Summary: InterruptedException during cluster shutdown in state transfer Key: ISPN-1765 URL: https://issues.jboss.org/browse/ISPN-1765 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.0.CR4 Reporter: Michal Linhard Assignee: Manik Surtani I'm getting lots of these during shutdown phase of 4 node test {code} 2012-01-19 14:18:58,635 ERROR [InvocationContextInterceptor] (HotRodServerWorker-1-124) ISPN000136: Execution error java.lang.InterruptedException at java.lang.Object.wait(Native Method) at org.infinispan.statetransfer.StateTransferLockImpl.acquireLockForWriteCommand(StateTransferLockImpl.java:304) at org.infinispan.statetransfer.StateTransferLockImpl.acquireForCommand(StateTransferLockImpl.java:126) at org.infinispan.interceptors.StateTransferLockInterceptor.visitPutKeyValueCommand(StateTransferLockInterceptor.java:127) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.infinispan.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:124) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:116) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76) at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:61) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:345) at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:941) at org.infinispan.CacheImpl.put(CacheImpl.java:654) at org.infinispan.DecoratedCache.put(DecoratedCache.java:179) at org.infinispan.server.core.AbstractProtocolDecoder.put(AbstractProtocolDecoder.scala:187) at org.infinispan.server.core.AbstractProtocolDecoder.decodeValue(AbstractProtocolDecoder.scala:141) at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:71) at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:44) at org.jboss.netty.handler.codec.replay.CustomReplayingDecoder.callDecode(CustomReplayingDecoder.java:250) at org.jboss.netty.handler.codec.replay.CustomReplayingDecoder.messageReceived(CustomReplayingDecoder.java:223) at org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:351) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:351) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:202) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {code} I'm guessig for all PUTs waiting on state transfer lock. so this happens when shutting down during state transfer. full log: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-experi... I thought I'll report this since we're tidying technical exceptions during shutdown phase as in ISPN-1754. -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1759) Throw an exception when using <hash > and <l1 > configurations in replicated, invalidated or local mode.

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1759: ----------------------------------- Summary: Throw an exception when using <hash > and <l1 > configurations in replicated, invalidated or local mode. Key: ISPN-1759 URL: https://issues.jboss.org/browse/ISPN-1759 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 5.1.0.CR4 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.FINAL Makes for more sane configurations. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] (ISPN-1732) Upgrade to JGroups 3.0.3

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1732: ------------------------------------- Summary: Upgrade to JGroups 3.0.3 Key: ISPN-1732 URL: https://issues.jboss.org/browse/ISPN-1732 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Blocker Fix For: 5.1.0.FINAL This is critical to solve some spotted performance issues which are being solved in JGroups. -- 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, 4 months

5
11
0 / 0

[JBoss JIRA] (ISPN-1770) Upgrade to JGroups 3.0.3.FINAL

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1770: -------------------------------------- Summary: Upgrade to JGroups 3.0.3.FINAL Key: ISPN-1770 URL: https://issues.jboss.org/browse/ISPN-1770 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 5.1.0.CR4 Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.1.0.FINAL Upgrade to JGroups 3.0.3.FINAL. It includes some performance improvements around the message dispatcher. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1325) Config reference for 5.0 is broken

by Galder Zamarreño (JIRA)

Config reference for 5.0 is broken ---------------------------------- Key: ISPN-1325 URL: https://issues.jboss.org/browse/ISPN-1325 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.ALPHA1 http://docs.jboss.org/infinispan/5.0/apidocs/config.html is broken. Fix it and generate a new version that can be uploaded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012