[JBoss JIRA] (ISPN-4014) remote-query quickstart app fails with NPE when run without a console
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-4014:
-----------------------------------
Summary: remote-query quickstart app fails with NPE when run without a console
Key: ISPN-4014
URL: https://issues.jboss.org/browse/ISPN-4014
Project: Infinispan
Issue Type: Bug
Components: Remote Querying
Affects Versions: 6.0.0.Final
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Priority: Minor
Fix For: 7.0.0.Alpha1, 7.0.0.Final
The app depends on System.console() not being null which is not always true. While in 99% cases the app works for the intended purpose it should also be possible to launch it from an IDE (were console support is missing).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-4013) Improve MapReduceTask timeout exception messages
by Vladimir Blagojevic (JIRA)
Vladimir Blagojevic created ISPN-4013:
-----------------------------------------
Summary: Improve MapReduceTask timeout exception messages
Key: ISPN-4013
URL: https://issues.jboss.org/browse/ISPN-4013
Project: Infinispan
Issue Type: Enhancement
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Currently we just let TimoutException from RPC call propagate up the stack which confuses users as they do not understand why timeout even occurred.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-3296) Total Order: timeout exceptions are not throw correctly
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3296?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3296:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Total Order: timeout exceptions are not throw correctly
> -------------------------------------------------------
>
> Key: ISPN-3296
> URL: https://issues.jboss.org/browse/ISPN-3296
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Critical
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>
> Issues found in Cloud-TM. Check if they happen here and create a JIRA for each of them
> * IgnoreExtraResponseFilter is not needed anymore.
> * missing argument log message
> * TimeoutException, when happens, it is ignored and the transaction is processed normally
> * TimeoutException can block the total order chain (all system is blocked!)
> * port the testTimeoutCleanup from cloudtm to master
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-4012) Timeout errors in the mass indexing tests
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4012:
----------------------------------
Summary: Timeout errors in the mass indexing tests
Key: ISPN-4012
URL: https://issues.jboss.org/browse/ISPN-4012
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Query
Affects Versions: 6.0.1.Final
Reporter: Dan Berindei
Assignee: Sanne Grinovero
Fix For: 7.0.0.Alpha1
Both DistProgrammaticMassIndexTest and TopologyAwareDistMassIndexingTest failed in CI today: http://ci.infinispan.org/viewLog.html?buildId=6578&tab=buildResultsDiv&bu...
{noformat}
org.infinispan.util.concurrent.TimeoutException: Node DistProgrammaticMassIndexTest-NodeC-7069 timed out
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:174)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:521)
at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:280)
at org.infinispan.query.indexmanager.InfinispanCommandsBackend.sendCommand(InfinispanCommandsBackend.java:87)
at org.infinispan.query.indexmanager.InfinispanCommandsBackend.applyWork(InfinispanCommandsBackend.java:81)
at org.infinispan.query.indexmanager.MasterSwitchDelegatingQueueProcessor.applyWork(MasterSwitchDelegatingQueueProcessor.java:53)
at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.performOperations(DirectoryBasedIndexManager.java:126)
at org.hibernate.search.backend.impl.WorkQueuePerIndexSplitter.commitOperations(WorkQueuePerIndexSplitter.java:63)
at org.hibernate.search.backend.impl.BatchedQueueingProcessor.performWorks(BatchedQueueingProcessor.java:99)
at org.hibernate.search.backend.impl.TransactionalWorker.performWork(TransactionalWorker.java:105)
at org.infinispan.query.backend.QueryInterceptor.performSearchWorks(QueryInterceptor.java:232)
at org.infinispan.query.backend.QueryInterceptor.purgeAllIndexes(QueryInterceptor.java:207)
at org.infinispan.query.backend.QueryInterceptor.purgeAllIndexes(QueryInterceptor.java:199)
at org.infinispan.query.impl.massindex.MapReduceMassIndexer.wipeExistingIndexes(MapReduceMassIndexer.java:33)
at org.infinispan.query.impl.massindex.MapReduceMassIndexer.start(MapReduceMassIndexer.java:24)
at org.infinispan.query.distributed.DistributedMassIndexingTest.rebuildIndexes(DistributedMassIndexingTest.java:75)
at org.infinispan.query.distributed.DistributedMassIndexingTest.testReindexing(DistributedMassIndexingTest.java:63)
Caused by: org.jgroups.TimeoutException: timeout sending message to DistProgrammaticMassIndexTest-NodeC-7069
at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:419)
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:349)
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:167)
... 37 more
{noformat}
Full logs: http://ci.infinispan.org/repository/download/bt2/6578:id/logs-638.zip
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month