[JBoss JIRA] (ISPN-10968) Invalidation sync clustered cache throws IllegalStateException on remote server as it starts up
by Tom Dearman (Jira)
Tom Dearman created ISPN-10968:
----------------------------------
Summary: Invalidation sync clustered cache throws IllegalStateException on remote server as it starts up
Key: ISPN-10968
URL: https://issues.jboss.org/browse/ISPN-10968
Project: Infinispan
Issue Type: Bug
Components: Transactions
Affects Versions: 10.0.1.Final
Environment: Java(TM) SE Runtime Environment (build 1.8.0_152-b16), macos and linux production, arjuna transaction manager
Reporter: Tom Dearman
Attachments: invalidationsync.tar.gz
If we bring up one server and let it start to write to an invalidation_sync cache with putForExternalRead within a transaction, on bringing up another server which doesn't write to the cache we will get exceptions thrown on the commit of the transaction as the second server is coming up. If we use a 'put' it does not cause the issue and if it is a DISTRIBUTED_SYNC it doesn't cause the issue.
I have tried to write this test as an infinispan test but this doesn't show the issue, on trying the EmbeddedTransactionManager in my own test it also did not show the issue so I assume it has something to do with the limited nature of the EmbeddedTransactionManager.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10967) CORS rules for localhost don't take offset into account
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10967?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10967:
-------------------------------------
Description: Starting the server with {{-Dinfinispan.socket.binding.port-offset}} will not automatically configure the localhost CORS rule to match the offset port
> CORS rules for localhost don't take offset into account
> -------------------------------------------------------
>
> Key: ISPN-10967
> URL: https://issues.jboss.org/browse/ISPN-10967
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Starting the server with {{-Dinfinispan.socket.binding.port-offset}} will not automatically configure the localhost CORS rule to match the offset port
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10966) StateTransferLockImpl.topologyFuture should complete exceptionally after stop
by dan.berindei (Jira)
dan.berindei created ISPN-10966:
-----------------------------------
Summary: StateTransferLockImpl.topologyFuture should complete exceptionally after stop
Key: ISPN-10966
URL: https://issues.jboss.org/browse/ISPN-10966
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 10.1.0.Beta1
Reporter: dan.berindei
Assignee: dan.berindei
Fix For: 10.1.0.CR1
When a cache is shutting down, the topology id is increased to {{Integer.MAX_VALUE}}.
If a component uses {{StateTransferLock.topologyUpdate()}} to retry in the next topology and doesn't explicitly check if the cache is running, it could retry 2^^31 times before giving up.
This causes {{StreamDistPartitionHandlingTest.clearContent}} to hang randomly:
{noformat}
11:58:14,655 TRACE (testng-Test:[]) [StateTransferLockImpl] Signalling topology 2147483647 is installed
11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying
11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046
...
12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying
12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046
...
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month