[JBoss JIRA] Created: (ISPN-375) Enable Hot Rod clients to start transactions
by Galder Zamarreno (JIRA)
Enable Hot Rod clients to start transactions
--------------------------------------------
Key: ISPN-375
URL: https://jira.jboss.org/jira/browse/ISPN-375
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 5.1.0.BETA1, 5.1.0.Final
It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only.
This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction.
Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky.
--
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, 5 months
[JBoss JIRA] (ISPN-2080) Cache Listener is not notified on cache replace
by William Burns (JIRA)
William Burns created ISPN-2080:
-----------------------------------
Summary: Cache Listener is not notified on cache replace
Key: ISPN-2080
URL: https://issues.jboss.org/browse/ISPN-2080
Project: Infinispan
Issue Type: Bug
Components: Listeners
Affects Versions: 5.1.5.FINAL
Reporter: William Burns
Assignee: Manik Surtani
Previously I have been using put with cache listeners to get remote updates. This works fine, however I changed over to using the concurrent map replace method due to my new value being a composite value and I wanted to make sure to work with asynchronous updates across jvm in a loop. The changes work fine however I am no longer getting CacheModification listener events.
I have attached a test case that tests this and changes that allow for the cache listeners to be notified.
--
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, 5 months
[JBoss JIRA] Created: (ISPN-1336) Infinispan core fails to build with JDK 7
by Radoslav Husar (JIRA)
Infinispan core fails to build with JDK 7
-----------------------------------------
Key: ISPN-1336
URL: https://issues.jboss.org/browse/ISPN-1336
Project: Infinispan
Issue Type: Bug
Components: Build process
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Java version: 1.7.0, vendor: Oracle Corporation
Reporter: Radoslav Husar
Assignee: Manik Surtani
"Or is it just me?"
{code}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project infinispan-core: Compilation failure
[ERROR] error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project infinispan-core: Compilation failure
error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
{code}
Trying on master, last commit was
commit e81e8a63fd68b85bc20b3304d62cc5fdcd75f327
Author: Galder Zamarreño
Date: Fri Aug 12 13:35:50 2011 +0200
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (ISPN-1794) change default minIdle attribute for hot rod client
by Michal Linhard (JIRA)
Michal Linhard created ISPN-1794:
------------------------------------
Summary: change default minIdle attribute for hot rod client
Key: ISPN-1794
URL: https://issues.jboss.org/browse/ISPN-1794
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 5.1.0.FINAL
Reporter: Michal Linhard
Assignee: Mircea Markus
Priority: Minor
This is just a proposal, feel free to reject.
Default behaviour in PropsKeyedObjectPoolFactory is
minIdle = 1
timeBetweenEvictionRunsMillis = 2min
i.e. after 2minutes of idle RemoteCacheManager will try to ensure at least one connection and will try to create one.
This might be a surprise for user to get this WARNING without doing anything:
{code}
2012-01-26 15:05:00,816 138699 WARN [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport] (Timer-1:) ISPN004008: Could not connect to server: test1/192.168.11.101:11222
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567)
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:100)
at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:80)
at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:57)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:1668)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.ensureMinIdle(GenericKeyedObjectPool.java:2038)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.ensureMinIdle(GenericKeyedObjectPool.java:2003)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.access$1600(GenericKeyedObjectPool.java:203)
at org.apache.commons.pool.impl.GenericKeyedObjectPool$Evictor.run(GenericKeyedObjectPool.java:2282)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
of course it's easy to change this via "minIdle" property, I just think this is a strange default and IMHO it should be 0 instead of 1.
WDYT?
--
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, 5 months
[JBoss JIRA] (ISPN-2007) Performance improvements for Infinispan servers
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2007:
--------------------------------------
Summary: Performance improvements for Infinispan servers
Key: ISPN-2007
URL: https://issues.jboss.org/browse/ISPN-2007
Project: Infinispan
Issue Type: Enhancement
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
Future improvements for Memcached/HotRod servers:
- Get rid of tuples, they're costly. This would require parameters/header objects to be made mutable.
- In Memcached, Get rid of any String construction and deal directly with byte[]. This would require converting adding validation to String-represented numbers, booleans...etc. This is by far biggest hotspot in our implementation.
- Get rid of any collection (ListBuffer) for parameter parsing in Memcached.
--
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, 5 months