[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-8900:
--------------------------------------
Summary: Sockets might be left open if server unreachable on creation
Key: ISPN-8900
URL: https://issues.jboss.org/browse/ISPN-8900
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 9.2.0.Final, 9.1.6.Final
Reporter: Galder Zamarreño
Fix For: 9.2.1.Final, 9.1.7.Final
Seems to …
[View More]affect pre-netty client but not sure yet whether it affects netty version:
In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8898:
------------------------------------
Workaround Description:
Currently Infinispan only creates the correct wrapper around data for server mode, but it's possible to manually force with:
DefaultCacheManager cacheManager = new DefaultCacheManager("distlayer-distributed-config.xml");
{code}
AdvancedCache<?, ?> advancedCache = ...
advancedCache.…
[View More]getValueDataConversion().overrideWrapper(ProtostreamWrapper.class, advancedCache.getComponentRegistry());
{code}
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: Bug
> Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Fix For: 9.2.1.Final
>
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8898:
------------------------------------
Fix Version/s: 9.2.1.Final
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: Bug
…
[View More]> Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Fix For: 9.2.1.Final
>
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8898:
------------------------------------
Status: Open (was: New)
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: Bug
> …
[View More] Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-8898:
-----------------------------------------
Hi Adam, thanks for sharing the reproducer!
You can workaround the issue until it's fixed by changing the wrapper for the indexed cache manually:
{code:java}
DefaultCacheManager cacheManager = new DefaultCacheManager("distlayer-distributed-config.xml");
AdvancedCache<?, ?> pokemonCache = cacheManager.getCache("pokemon").…
[View More]getAdvancedCache();
pokemonCache.getValueDataConversion().overrideWrapper(ProtostreamWrapper.class, pokemonCache.getComponentRegistry());
{code}
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: Bug
> Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Priority: Critical
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8898:
------------------------------------
Priority: Major (was: Critical)
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: …
[View More]Bug
> Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8898?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-8898:
---------------------------------------
Assignee: Gustavo Fernandes
> Indexing not working using REST with embedded cache manager
> -----------------------------------------------------------
>
> Key: ISPN-8898
> URL: https://issues.jboss.org/browse/ISPN-8898
> Project: Infinispan
> Issue Type: …
[View More]Bug
> Components: Indexing, Remote Querying, REST
> Affects Versions: 9.2.0.Final
> Environment: sample application attached
> Reporter: Adam Melkus
> Assignee: Gustavo Fernandes
> Priority: Critical
> Attachments: ispn_broken.zip
>
>
> JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
> Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8897) Indexes from different caches are mixed-up in server mode
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8897?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8897:
------------------------------------
Description:
When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index.
This can cause issues with two caches having the same key stepping in each other's toes. Example, when …
[View More]doing:
{code:java}
remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)
{code}
The second call will replace the first indexed entry since the key is identical and the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.
was:
When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index.
This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
{code:java}
remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)
{code}
The second call will replace the first indexed entry since the key is identical ans the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.
> Indexes from different caches are mixed-up in server mode
> ---------------------------------------------------------
>
> Key: ISPN-8897
> URL: https://issues.jboss.org/browse/ISPN-8897
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 9.1.6.Final, 9.2.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index.
> This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
> {code:java}
> remoteCache1.put(1, entity1)
> remoteCache2.put(1, entity2)
> {code}
> The second call will replace the first indexed entry since the key is identical and the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8897) Indexes from different caches are mixed-up in server mode
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-8897:
---------------------------------------
Summary: Indexes from different caches are mixed-up in server mode
Key: ISPN-8897
URL: https://issues.jboss.org/browse/ISPN-8897
Project: Infinispan
Issue Type: Bug
Components: Remote Querying
Affects Versions: 9.2.0.Final, 9.1.6.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
When configuring …
[View More]multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index.
This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
{code:java}
remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)
{code}
The second call will replace the first indexed entry since the key is identical ans the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years