[JBoss JIRA] (ISPN-9492) Unknown type: 130
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9492?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-9492:
-----------------------------------------
The stack trace indicates that the server was expecting data from a different type than provided. Please provide the server cache configuration, the client marshalled used, and the operation attempted.
> Unknown type: 130
> -----------------
>
> Key: ISPN-9492
> URL: https://issues.jboss.org/browse/ISPN-9492
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.1.Final
> Reporter: Sergey Chernolyas
> Priority: Blocker
>
> I take exception:
> _____________
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=22 returned server error (status=0x85): java.io.IOException: Unknown type: 130
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:333)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:179)
> at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138)
> at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
> at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:806)
> at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304)
> at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ____________
> Main problem of the exception is cache became to unmanagable. I can't clear cache!
> After get the exception I need to stop cluster and remove files of external storage.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9492) Unknown type: 130
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9492?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-9492 at 9/10/18 1:50 AM:
------------------------------------------------------------------
The stack trace indicates that the server was expecting data from a different type than provided. Please provide the server cache configuration, the client marshaller used, and the operation executed.
was (Author: gustavonalle):
The stack trace indicates that the server was expecting data from a different type than provided. Please provide the server cache configuration, the client marshalled used, and the operation attempted.
> Unknown type: 130
> -----------------
>
> Key: ISPN-9492
> URL: https://issues.jboss.org/browse/ISPN-9492
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.3.1.Final
> Reporter: Sergey Chernolyas
> Priority: Blocker
>
> I take exception:
> _____________
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=22 returned server error (status=0x85): java.io.IOException: Unknown type: 130
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:333)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:179)
> at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138)
> at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
> at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:806)
> at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304)
> at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ____________
> Main problem of the exception is cache became to unmanagable. I can't clear cache!
> After get the exception I need to stop cluster and remove files of external storage.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9403) Investigate slow CI builds
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9403?page=com.atlassian.jira.plugin.... ]
Dan Berindei resolved ISPN-9403.
--------------------------------
Fix Version/s: (was: 9.4.0.Final)
Resolution: Done
The slowdown was caused by a kernel bug on the Central CI hosts, and was fixed when the infra team rolled back the kernel.
> Investigate slow CI builds
> --------------------------
>
> Key: ISPN-9403
> URL: https://issues.jboss.org/browse/ISPN-9403
> Project: Infinispan
> Issue Type: Task
> Components: Build, Test Suite - Core
> Affects Versions: 9.4.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
>
> Some CI builds are really slow and eventually time out after 3 hours. Both the tests and the compilation are affected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9485) RoundRobinBalancingStrategy always starts from server 0
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9485?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9485:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> RoundRobinBalancingStrategy always starts from server 0
> -------------------------------------------------------
>
> Key: ISPN-9485
> URL: https://issues.jboss.org/browse/ISPN-9485
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 9.4.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final
>
>
> {{RoundRobinBalancingStrategy}} always starts from server 0, and resets back to 0 if a server topology update has less servers. This means if N clients start and immediately add a listener (e.g. for near cache), all N client listeners will be attached to the same server.
> We should pick a random server on every server topology update instead, so that near cache listeners are attached to random servers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9494) Ickl full-text queries with wildcards are affected by upper/lower case
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-9494?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-9494:
--------------------------------
Status: Open (was: New)
> Ickl full-text queries with wildcards are affected by upper/lower case
> ----------------------------------------------------------------------
>
> Key: ISPN-9494
> URL: https://issues.jboss.org/browse/ISPN-9494
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 7.2.2.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Adrian Nistor
>
> If an attribute is annotated with
> @Field(index = Index.YES,store = Store.YES, analyze = Analyze.YES)
> a full-text search with wildcards can be used like this
> from proto.Person p where p.firstName : 'wolf*ng'
> It is expected that the query will ignore capitalisation. So a search 'Wolf*' 'Wolf*ng' 'wolf*' should find the attribute value "Wolfgang" and "wolfgang".
> But only if the query is written in lower-case it will match the expectation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9494) Ickl full-text queries with wildcards are affected by upper/lower case
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/ISPN-9494?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink reassigned ISPN-9494:
--------------------------------------
Assignee: Adrian Nistor
> Ickl full-text queries with wildcards are affected by upper/lower case
> ----------------------------------------------------------------------
>
> Key: ISPN-9494
> URL: https://issues.jboss.org/browse/ISPN-9494
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 7.2.2.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Adrian Nistor
>
> If an attribute is annotated with
> @Field(index = Index.YES,store = Store.YES, analyze = Analyze.YES)
> a full-text search with wildcards can be used like this
> from proto.Person p where p.firstName : 'wolf*ng'
> It is expected that the query will ignore capitalisation. So a search 'Wolf*' 'Wolf*ng' 'wolf*' should find the attribute value "Wolfgang" and "wolfgang".
> But only if the query is written in lower-case it will match the expectation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9495) Ickl full-text queries with wildcards are affected by upper/lower case
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-9495:
--------------------------------------
Summary: Ickl full-text queries with wildcards are affected by upper/lower case
Key: ISPN-9495
URL: https://issues.jboss.org/browse/ISPN-9495
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying, Remote Querying
Affects Versions: 7.2.2.Final
Reporter: Wolf-Dieter Fink
If an attribute is annotated with
@Field(index = Index.YES,store = Store.YES, analyze = Analyze.YES)
a full-text search with wildcards can be used like this
from proto.Person p where p.firstName : 'wolf*ng'
It is expected that the query will ignore capitalisation. So a search 'Wolf*' 'Wolf*ng' 'wolf*' should find the attribute value "Wolfgang" and "wolfgang".
But only if the query is written in lower-case it will match the expectation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9494) Ickl full-text queries with wildcards are affected by upper/lower case
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-9494:
--------------------------------------
Summary: Ickl full-text queries with wildcards are affected by upper/lower case
Key: ISPN-9494
URL: https://issues.jboss.org/browse/ISPN-9494
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying, Remote Querying
Affects Versions: 7.2.2.Final
Reporter: Wolf-Dieter Fink
If an attribute is annotated with
@Field(index = Index.YES,store = Store.YES, analyze = Analyze.YES)
a full-text search with wildcards can be used like this
from proto.Person p where p.firstName : 'wolf*ng'
It is expected that the query will ignore capitalisation. So a search 'Wolf*' 'Wolf*ng' 'wolf*' should find the attribute value "Wolfgang" and "wolfgang".
But only if the query is written in lower-case it will match the expectation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months