[JBoss JIRA] (ISPN-12131) HR Creating Caches on First Access shouldn't throw CacheNotFoundException
by Gustavo Lira Silva (Jira)
Gustavo Lira Silva created ISPN-12131:
-----------------------------------------
Summary: HR Creating Caches on First Access shouldn't throw CacheNotFoundException
Key: ISPN-12131
URL: https://issues.redhat.com/browse/ISPN-12131
Project: Infinispan
Issue Type: Bug
Components: Hot Rod
Reporter: Gustavo Lira Silva
When using {{builder.remoteCache("my-cache").templateName}} to create cache for the first time is throwing a WARN message with CacheNotFoundException
{noformat}
WARN: ISPN004005: Error received from the server: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'my-cache' not found amongst the configured caches
{noformat}
The message could be more friendly or just omitted
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (ISPN-12109) TcpConnection.Receiver.run() blocking call
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12109?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12109:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> TcpConnection.Receiver.run() blocking call
> ------------------------------------------
>
> Key: ISPN-12109
> URL: https://issues.redhat.com/browse/ISPN-12109
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite
> Affects Versions: 11.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.2.Final
>
>
> {noformat}
> [TestSuiteProgress] Test failed: org.infinispan.distribution.rehash.WorkDuringJoinTest[DIST_SYNC, tx=false].BlockingChecker
> 22:28:37.967 [Connection.Receiver [127.0.0.1:34169 - 127.0.0.1:8001]-8,WorkDuringJoinTest-NodeC] ERROR org.infinispan.commons.test.TestSuiteProgress - Test failed: org.infinispan.distribution.rehash.WorkDuringJoinTest[DIST_SYNC, tx=false].BlockingChecker
> java.lang.AssertionError: Blocking call! java.net.SocketInputStream#socketRead0 on thread Thread[Connection.Receiver [127.0.0.1:34169 - 127.0.0.1:8001]-8,WorkDuringJoinTest-NodeC,5,ISPN-non-blocking-thread-group]
> at org.infinispan.util.CoreTestBlockHoundIntegration.lambda$applyTo$0(CoreTestBlockHoundIntegration.java:45) ~[test-classes/:?]
> at reactor.blockhound.BlockHound$Builder.lambda$install$8(BlockHound.java:383) ~[blockhound-1.0.3.RELEASE.jar:?]
> at reactor.blockhound.BlockHoundRuntime.checkBlocking(BlockHoundRuntime.java:89) [?:?]
> at java.net.SocketInputStream.socketRead0(SocketInputStream.java) [?:?]
> at java.net.SocketInputStream.socketRead(SocketInputStream.java:115) [?:?]
> at java.net.SocketInputStream.read(SocketInputStream.java:168) [?:?]
> at java.net.SocketInputStream.read(SocketInputStream.java:140) [?:?]
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:252) [?:?]
> at java.io.BufferedInputStream.read(BufferedInputStream.java:271) [?:?]
> at java.io.DataInputStream.readInt(DataInputStream.java:392) [?:?]
> at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:301) [jgroups-4.2.1.Final.jar:4.2.1.Final]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {noformat}
> The blocking call doesn't always happen, but it appears to be more common in the unstable CI builds:
> https://ci.infinispan.org/job/InfinispanAlternateBuilds/job/InfinispanUns...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (ISPN-12029) Replace Blocking Executor with an EnhancedQueueExecutor
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12029?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12029:
------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8494
> Replace Blocking Executor with an EnhancedQueueExecutor
> -------------------------------------------------------
>
> Key: ISPN-12029
> URL: https://issues.redhat.com/browse/ISPN-12029
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.2.Final
>
>
> The blocking executor today uses a simple ThreadPoolExecutor. Unfortunately, this means that we will eventually start all configured threads (since core = max and we require a queue). Setting core size to less than max is not desirable as well as it will enqueue additional tasks rather than spawn a thread.
>
> The EnhancedQueueExecutor does exactly what we want and also has some additional features. We should utilize this which will keep our blocking thread pool size down during times of less activity.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months