[JBoss JIRA] Created: (ISPN-745) In Memcached, unix time expiry before now is considered as immortal
by Galder Zamarreño (JIRA)
In Memcached, unix time expiry before now is considered as immortal
-------------------------------------------------------------------
Key: ISPN-745
URL: https://jira.jboss.org/browse/ISPN-745
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1, 4.2.0.Final
In memcached, if lifespan is bigger than seconds in a month, it is considered unix time, but if this time is smaller than current time, a negative number is produced and passed to Infinispan cache which results in entry not being removed. Instead, Memcached server should spot this and since the time is in the past, pass 0 to remove it immediately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-743) memcached server incr/decr doesn't work in unsigned 64bit integer mode
by Galder Zamarreño (JIRA)
memcached server incr/decr doesn't work in unsigned 64bit integer mode
----------------------------------------------------------------------
Key: ISPN-743
URL: https://jira.jboss.org/browse/ISPN-743
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1, 4.2.0.Final
[mlinhard@michal-linhard ~]$ telnet localhost 11211
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
set a 0 0 19
9223372036854775808
STORED
incr a 1
SERVER_ERROR org.infinispan.server.core.ServerException: java.lang.NumberFormatException: For input string: "9223372036854775808"
when I run original memcached server on port 11212 it works:
[mlinhard@michal-linhard ~]$ telnet localhost 11212
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
set a 0 0 1
A
STORED
set a 0 0 19
9223372036854775808
STORED
incr a 1
9223372036854775809
----------------
Other issue here is overflow:
set a 0 0 19
9223372036854775807
incr a 1
-9223372036854775808
whereas original memcached server overflows in "unsigned mode":
set b 0 0 20
18446744073709551615
incr b 1
0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-740) TypedProperties.toTypedProperties should do system property substitution
by Galder Zamarreño (JIRA)
TypedProperties.toTypedProperties should do system property substitution
------------------------------------------------------------------------
Key: ISPN-740
URL: https://jira.jboss.org/browse/ISPN-740
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1
Infinispan Servers should do system property substitution in any of the values present in the properties passed.
The easiest thing would be to as part of the call to TypedProperties.toTypedProperties(properties), we take the value parts and do system property substitution.
Without this, you won't be able to define things like this:
infinispan.server.host = ${jboss.infinispan.hotrod.server.host:127.0.0.1}
infinispan.server.port = ${jboss.infinispan.hotrod.server.port:11222}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (ISPN-688) Data preloaded from a CacheStore is immediately stored in the CacheStore again
by Sanne Grinovero (JIRA)
Data preloaded from a CacheStore is immediately stored in the CacheStore again
------------------------------------------------------------------------------
Key: ISPN-688
URL: https://jira.jboss.org/browse/ISPN-688
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final, 4.0.0.Final
Reporter: Sanne Grinovero
Assignee: Mircea Markus
Priority: Minor
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
When enabling logging on the CacheStore, which is being used with preload=true, I can clearly see that during the preload operation each value is read from the store and immediately after that stored again.
This is quite a performance hit in application loading, as the whole store is written again without this being needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (ISPN-704) Make cache events generic where possible
by Paul Ferraro (JIRA)
Make cache events generic where possible
----------------------------------------
Key: ISPN-704
URL: https://jira.jboss.org/browse/ISPN-704
Project: Infinispan
Issue Type: Feature Request
Components: Listeners
Affects Versions: 4.2.0.ALPHA3
Reporter: Paul Ferraro
Assignee: Manik Surtani
Priority: Minor
It would be nice if the Cache events were generic, and save the user from needless casting. e.g. CacheEntryActivatedEvent<K, V>
This would also further discourage users from fetching values from their own generic Cache<K, V> rather than having to cast the values from the event or DataContainer (a potential gotcha, see ISPN-703).
Type erasure should ensure that any current unparameterized usage is fully compatible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (ISPN-700) Query integration fails to stop integrated Hibernate Search
by Sanne Grinovero (JIRA)
Query integration fails to stop integrated Hibernate Search
-----------------------------------------------------------
Key: ISPN-700
URL: https://jira.jboss.org/browse/ISPN-700
Project: Infinispan
Issue Type: Sub-task
Components: Querying
Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final, 4.0.0.Final
Reporter: Sanne Grinovero
Assignee: Navin Surtani
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
For a test application, see the attachment of parent issue (ISPN-697).
Hibernate Search needs to be stopped or background threads will prevent the JVM from closing properly.
In the integration with Hibernate, org.hibernate.search.event.FullTextIndexEventListener is invoked during SessionFactory close as it implements org.hibernate.event.Destructible
The listener then calls into org.hibernate.search.impl.ImmutableSearchFactory.close() which actually stops all additional threads.
It seems that org.infinispan.query.impl.LifecycleManager should be completed; it's work was blocked by HSEARCH-397 but this was solved, so the Search/Infinispan integration should be updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (ISPN-733) Lock down ports and use AS friendly system properties in JGroups config files
by Galder Zamarreño (JIRA)
Lock down ports and use AS friendly system properties in JGroups config files
-----------------------------------------------------------------------------
Key: ISPN-733
URL: https://jira.jboss.org/browse/ISPN-733
Project: Infinispan
Issue Type: Task
Components: RPC
Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final, 4.0.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1, 4.2.0.Final
Lock down FD_SOCK start port in shipped configuration and use AS ServiceBindingManager friendly properties:
<FD_SOCK start_port="${jboss.jgroups.udp.fd_sock_port:54200}"/>
and
- diagnostics when it is enabled
enable_diagnostics="${jboss.jgroups.enable_diagnostics:true}"
diagnostics_addr="${jboss.jgroups.diagnostics_addr:224.0.75.75}"
diagnostics_port="${jboss.jgroups.diagnostics_port:7500}"
- the UDP unicast bind port
bind_port="${jboss.jgroups.udp.bind_port:55200}"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months