[JBoss JIRA] (ISPN-9451) When fail-silently is false, the system will behave based on persistence configuration
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9451?page=com.atlassian.jira.plugin.... ]
Ryan Emerson reassigned ISPN-9451:
----------------------------------
Assignee: Ryan Emerson
> When fail-silently is false, the system will behave based on persistence configuration
> --------------------------------------------------------------------------------------
>
> Key: ISPN-9451
> URL: https://issues.jboss.org/browse/ISPN-9451
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Ryan Emerson
> Priority: Critical
>
> Using the configuration below when the store is not available, the system won't fail at the first time.
> {code:xml}
> <?xml version="1.0" ?>
> <infinispan>
> <jgroups>
> <stack-file name="external-file" path="default-jgroups-tcp.xml"/>
> </jgroups>
> <cache-container name="myCacheContainer" default-cache="myCache" statistics="true">
> <transport cluster="WeatherApp" stack="external-file" />
> <distributed-cache owners="2" mode="SYNC" remote-timeout="15000" name="myCache">
> <transaction mode="NONE"/>
> <persistence connection-attempts="5" connection-interval="2000">
> <string-keyed-jdbc-store fetch-state="false" purge="false" read-only="false" shared="true">
> <write-behind fail-silently="false" />
> <string-keyed-table prefix="ISPN_STRING_TABLE" create-on-start="true">
> <id-column name="ID_COLUMN" type="VARCHAR(255)"/>
> <data-column name="DATA_COLUMN" type="BINARY"/>
> <timestamp-column name="TIMESTAMP_COLUMN" type="BIGINT"/>
> </string-keyed-table>
> <connection-pool
> connection-url="jdbc:h2:~/test;FILE_LOCK=SOCKET"
> driver="org.h2.Driver" username="sa"/>
> </string-keyed-jdbc-store>
> </persistence>
> </distributed-cache>
> </cache-container>
> </infinispan>
> {code}
> To reproduce the issue, you should start the application twice.
> The first application will work fine. The second one will fail 5 times before stops working.
> The fail-silently is "false" so it should fail at the first time.
> {code:java}
> public class ConfigurationFileCacheExample {
> public static void main(String[] args) throws InterruptedException, IOException {
> EmbeddedCacheManager cacheManager = new DefaultCacheManager("cache-jdbc-store.xml");
> try {
> Cache<String, LocationWeather> cache = cacheManager.getCache("weather");
> System.out.println(cache.size());
> while (true) {
> String location = UUID.randomUUID().toString();
> cache.put(location, new LocationWeather(37, location));
> TimeUnit.SECONDS.sleep(1);
> }
> } finally {
> cacheManager.stop();
> }
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9451) When fail-silently is false, the system will behave based on persistence configuration
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9451?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-9451:
------------------------------------
[~dlovison] I am struggling to reproduce this. I'm not sure I completely follow the scenario you're trying to describe. At what point is the underlying db made unavailable? and how do you make the h2 database unavailable?
> When fail-silently is false, the system will behave based on persistence configuration
> --------------------------------------------------------------------------------------
>
> Key: ISPN-9451
> URL: https://issues.jboss.org/browse/ISPN-9451
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Priority: Critical
>
> Using the configuration below when the store is not available, the system won't fail at the first time.
> {code:xml}
> <?xml version="1.0" ?>
> <infinispan>
> <jgroups>
> <stack-file name="external-file" path="default-jgroups-tcp.xml"/>
> </jgroups>
> <cache-container name="myCacheContainer" default-cache="myCache" statistics="true">
> <transport cluster="WeatherApp" stack="external-file" />
> <distributed-cache owners="2" mode="SYNC" remote-timeout="15000" name="myCache">
> <transaction mode="NONE"/>
> <persistence connection-attempts="5" connection-interval="2000">
> <string-keyed-jdbc-store fetch-state="false" purge="false" read-only="false" shared="true">
> <write-behind fail-silently="false" />
> <string-keyed-table prefix="ISPN_STRING_TABLE" create-on-start="true">
> <id-column name="ID_COLUMN" type="VARCHAR(255)"/>
> <data-column name="DATA_COLUMN" type="BINARY"/>
> <timestamp-column name="TIMESTAMP_COLUMN" type="BIGINT"/>
> </string-keyed-table>
> <connection-pool
> connection-url="jdbc:h2:~/test;FILE_LOCK=SOCKET"
> driver="org.h2.Driver" username="sa"/>
> </string-keyed-jdbc-store>
> </persistence>
> </distributed-cache>
> </cache-container>
> </infinispan>
> {code}
> To reproduce the issue, you should start the application twice.
> The first application will work fine. The second one will fail 5 times before stops working.
> The fail-silently is "false" so it should fail at the first time.
> {code:java}
> public class ConfigurationFileCacheExample {
> public static void main(String[] args) throws InterruptedException, IOException {
> EmbeddedCacheManager cacheManager = new DefaultCacheManager("cache-jdbc-store.xml");
> try {
> Cache<String, LocationWeather> cache = cacheManager.getCache("weather");
> System.out.println(cache.size());
> while (true) {
> String location = UUID.randomUUID().toString();
> cache.put(location, new LocationWeather(37, location));
> TimeUnit.SECONDS.sleep(1);
> }
> } finally {
> cacheManager.stop();
> }
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9580) Avoid parsing the MediaType when the client sends an Id directly
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-9580:
---------------------------------------
Summary: Avoid parsing the MediaType when the client sends an Id directly
Key: ISPN-9580
URL: https://issues.jboss.org/browse/ISPN-9580
Project: Infinispan
Issue Type: Enhancement
Components: Server
Affects Versions: 9.4.0.CR3
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The Hot Rod client can send pre-defined ids representing common media types, and the server should avoid parsing those MediaType again.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9579) The server does too many ConcurrentHashMap lookups to get the cache
by Dan Berindei (Jira)
Dan Berindei created ISPN-9579:
----------------------------------
Summary: The server does too many ConcurrentHashMap lookups to get the cache
Key: ISPN-9579
URL: https://issues.jboss.org/browse/ISPN-9579
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 9.4.0.CR3
Reporter: Dan Berindei
Assignee: Gustavo Fernandes
Fix For: 10.0.0.Final
Got a profiler snapshot while investigating ISPN-9198, and there are a lot of map lookups just to find the cache with the right flags and make sure it's not ignored.
||Stack Trace||Sample Count||Percentage(%)||
|org.infinispan.server.hotrod.CacheRequestProcessor.get(HotRodHeader, Subject, byte[])|6,554|41.615|
|+org.infinispan.server.hotrod.CacheRequestProcessor.handleGet(HotRodHeader, CacheEntry, Throwable)|2,659|16.884|
|+org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.getCacheEntry(Object)|2,569|16.312|
|+org.infinispan.server.hotrod.HotRodServer.cache(HotRodHeader, Subject)|793|5.035|
|+org.infinispan.server.hotrod.HotRodServer.cache(HotRodHeader, Subject, String)|793|5.035|
|++java.util.concurrent.ConcurrentHashMap.get(Object)|349|2.216|
|++org.infinispan.server.hotrod.HotRodServer.getCacheConfiguration(String)|203|1.289|
|++org.infinispan.server.hotrod.HotRodHeader.getOptimizedCache(AdvancedCache, Configuration)|152|0.965|
|++org.infinispan.server.core.AbstractCacheIgnoreAware.isCacheIgnored(String)|88|0.559|
|+org.infinispan.server.hotrod.HotRodServer.getCacheInfo(AdvancedCache, HotRodHeader)|516|3.276|
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9578) Move HR wire docs to contributing guide
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-9578:
-------------------------------------
Summary: Move HR wire docs to contributing guide
Key: ISPN-9578
URL: https://issues.jboss.org/browse/ISPN-9578
Project: Infinispan
Issue Type: Task
Components: Documentation-Core
Affects Versions: 9.4.0.CR3
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.4.0.Final
The Hot Rod wire protocol has no place in the user guide. It should be moved to the contributing guide.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months