[JBoss JIRA] (ISPN-2278) Implicit transaction enabling during configuration fails
by Thomas Fromm (JIRA)
Thomas Fromm created ISPN-2278:
----------------------------------
Summary: Implicit transaction enabling during configuration fails
Key: ISPN-2278
URL: https://issues.jboss.org/browse/ISPN-2278
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 5.1.6.FINAL
Reporter: Thomas Fromm
Assignee: Mircea Markus
The implicit enabling of transaction support does not work in all cases described in TransactionMode Javadoc inside the current configuration API.
- transactionManagerLookup is explicit configured
This works not in programmatic.
- enabled batching
When using XML configuration, this will not work, when only <invocationBatching> element and no <transaction> element is used.
At ConfigurationBuilderHolder.newConfigurationBuilder(...) the default cache config is used as base for the new named cache. Since build() is called, the TransactionConfiguration is set to NON_TRANSACTIONAL in the Configuration template used for the new ConfigurationBuilder. Later then any if(transactionMode == null)-related conditions in TransactionConfigurationBuilder will fail.
ISPN-2276 _maybe_ also points to this problem, did not spent further investigation on it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (ISPN-2082) JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes
by Ryan Scharer (JIRA)
Ryan Scharer created ISPN-2082:
----------------------------------
Summary: JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Manik Surtani
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything works fine. If the value is greater, the cache store fails with ORA-24816. This occurs because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore implementation and write my own insert/update SQL in storeLockSafe(). This works fine, but obviously isn't ideal from an upgrade point of view. Simply overriding storeLockSafe() isn't an option due to all the private fields.
--
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
10 years, 4 months
[JBoss JIRA] (ISPN-2344) StateTransferReplicationQueueTest.testStateTransferWithNodeRestartedAndBusy
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2344:
--------------------------------------
Summary: StateTransferReplicationQueueTest.testStateTransferWithNodeRestartedAndBusy
Key: ISPN-2344
URL: https://issues.jboss.org/browse/ISPN-2344
Project: Infinispan
Issue Type: Bug
Components: State transfer
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.CR1
{code}java.lang.AssertionError
at org.infinispan.statetransfer.StateTransferReplicationQueueTest.thirdWritingCacheTest(StateTransferReplicationQueueTest.java:146)
at org.infinispan.statetransfer.StateTransferReplicationQueueTest.testStateTransferWithNodeRestartedAndBusy(StateTransferReplicationQueueTest.java:108){code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] Created: (ISPN-1403) Optimise sending Hot Rod topology updates for distributed caches
by Galder Zamarreño (JIRA)
Optimise sending Hot Rod topology updates for distributed caches
----------------------------------------------------------------
Key: ISPN-1403
URL: https://issues.jboss.org/browse/ISPN-1403
Project: Infinispan
Issue Type: Enhancement
Components: Cache Server, Distributed Cache
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
Right now, whenever a Hot Rod client sends a request with a view id which is different to the one on the server, it'd get a brand new view in the response to the request. This could be optimised nicely by only sending back a new view id when the server discovers that the client is using an inefficient view. For example, in distributed caches, the moment it gets a request for a key which lands on a node that does not own the key, it could decide to send back the view.
This would reduce the number of times the view is returned, hence improving the performance of requests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months