[JBoss JIRA] (ISPN-9841) HotRod server AUTH requests can block
by William Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9841?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9841:
--------------------------------
Description: The AUTH request can perform remote blocking operations to an external source, such as LDAP. This can cause a backup of netty event loop threads if the authentication takes a while and there are enough incoming concurrent connections. (was: The AUTH request can perform remote blocking operations to an external source, such as LDAP. This can cause a backup of netty event loop threadss if the authentication takes a while and there are enough incoming concurrent connections.)
> HotRod server AUTH requests can block
> -------------------------------------
>
> Key: ISPN-9841
> URL: https://issues.jboss.org/browse/ISPN-9841
> Project: Infinispan
> Issue Type: Bug
> Reporter: William Burns
> Priority: Major
>
> The AUTH request can perform remote blocking operations to an external source, such as LDAP. This can cause a backup of netty event loop threads if the authentication takes a while and there are enough incoming concurrent connections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (ISPN-9841) HotRod server AUTH requests can block
by William Burns (Jira)
William Burns created ISPN-9841:
-----------------------------------
Summary: HotRod server AUTH requests can block
Key: ISPN-9841
URL: https://issues.jboss.org/browse/ISPN-9841
Project: Infinispan
Issue Type: Bug
Reporter: William Burns
The AUTH request can perform remote blocking operations to an external source, such as LDAP. This can cause a backup of netty event loop threadss if the authentication takes a while and there are enough incoming concurrent connections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (ISPN-9840) RemoteCacheManager shouldn't attempt to start a second time
by William Burns (Jira)
William Burns created ISPN-9840:
-----------------------------------
Summary: RemoteCacheManager shouldn't attempt to start a second time
Key: ISPN-9840
URL: https://issues.jboss.org/browse/ISPN-9840
Project: Infinispan
Issue Type: Bug
Components: Hot Rod
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Beta1
The RemoteCacheManager doesn't check the start boolean before performing start. This means if a user invokes {code}new RemoteCacheManager().start(){code} this would attempt to start it twice.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (ISPN-6041) Remote Listeners: Client event reader thread reports EOF as error
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6041?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6041:
----------------------------------
Fix Version/s: 9.4.6.Final
(was: 9.4.5.Final)
> Remote Listeners: Client event reader thread reports EOF as error
> -----------------------------------------------------------------
>
> Key: ISPN-6041
> URL: https://issues.jboss.org/browse/ISPN-6041
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.1.0.Final
> Reporter: Dan Berindei
> Priority: Minor
> Fix For: 9.4.6.Final
>
>
> {noformat}
> 14:02:14,904 ERROR (Client-Listener-87aa07aee56d43e1) [ClientListenerNotifier] ISPN004043: Unrecoverable error reading event from server /127.0.0.1:15530, exiting event reader thread
> org.infinispan.client.hotrod.exceptions.TransportException: End of stream reached!
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:198)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:305)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:147)
> at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:252)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6162:
----------------------------------
Fix Version/s: 9.4.6.Final
(was: 9.4.5.Final)
> Drop Query.getResultSize() method
> ---------------------------------
>
> Key: ISPN-6162
> URL: https://issues.jboss.org/browse/ISPN-6162
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 9.4.6.Final
>
>
> Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6094:
----------------------------------
Fix Version/s: 9.4.6.Final
(was: 9.4.5.Final)
> Use security actions to read system properties for configuration
> ----------------------------------------------------------------
>
> Key: ISPN-6094
> URL: https://issues.jboss.org/browse/ISPN-6094
> Project: Infinispan
> Issue Type: Task
> Components: Core, Embedded Querying
> Affects Versions: 8.1.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.6.Final
>
>
> Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute:
> * infinispan.arrays.debug
> * infinispan.unsafe.force_multicast
> * infinispan.compat (obsolete?)
> * infinispan.debugDependencies
> * infinispan.stagger.delay (introduced with ISPN-825)
> * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE
> We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years