[JBoss JIRA] (ISPN-7838) JBoss Modules NPE in Domain mode
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7838?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7838:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5146
> JBoss Modules NPE in Domain mode
> --------------------------------
>
> Key: ISPN-7838
> URL: https://issues.jboss.org/browse/ISPN-7838
> Project: Infinispan
> Issue Type: Bug
> Components: Server, WildFly modules
> Affects Versions: 9.0.1.Final, 9.1.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Tristan Tarrant
> Priority: Blocker
>
> When starting the server in domain mode, the bellow errors are present on the server nodes. This seems to have been introduced by this [commit|https://github.com/infinispan/infinispan/commit/8401553ea9a64d5445...] for ISPN-7652.
> {code:java}
> 10:31:40,010 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> 10:31:40,092 INFO [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
> [Host Controller] 10:31:40,397 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> [Host Controller] 10:31:40,512 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> [Host Controller] 10:31:40,544 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: Infinispan Server 9.1.0-SNAPSHOT (WildFly Core 2.2.0.Final) starting
> [Host Controller] 10:31:40,926 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 10:31:40,927 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 10:31:40,950 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 10:31:40,953 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.4.0.Final
> [Host Controller] 10:31:40,960 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.4.0.Final
> [Host Controller] 10:31:40,988 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.21.Final
> [Host Controller] 10:31:41,017 INFO [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on 127.0.0.1:9999
> [Host Controller] 10:31:41,377 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=clustered/subsystem=datagrid-jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 10:31:41,473 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
> [Host Controller] 10:31:41,474 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: default
> 10:31:41,522 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
> [Host Controller] 10:31:41,565 WARN [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: default
> [Server:server-one] 10:31:41,824 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> [Server:server-one] java.lang.NullPointerException
> [Server:server-one] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:116)
> [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [Server:server-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [Server:server-one] at java.lang.reflect.Method.invoke(Method.java:498)
> [Server:server-one] at org.jboss.modules.Module.run(Module.java:330)
> [Server:server-one] at org.jboss.modules.Main.main(Main.java:505)
> [Server:server-one] 10:31:41,901 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
> [Server:server-one]
> 10:31:41,917 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'Server:server-one' finished with an exit status of 1
> [Host Controller] 10:31:41,960 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-one
> [Host Controller] 10:31:41,961 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
> [Host Controller] 10:31:41,961 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: default
> 10:31:42,045 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
> [Host Controller] 10:31:42,088 WARN [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: default
> [Server:server-two] 10:31:42,365 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> [Server:server-two] java.lang.NullPointerException
> [Server:server-two] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:116)
> [Server:server-two] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [Server:server-two] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [Server:server-two] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [Server:server-two] at java.lang.reflect.Method.invoke(Method.java:498)
> [Server:server-two] at org.jboss.modules.Module.run(Module.java:330)
> [Server:server-two] at org.jboss.modules.Main.main(Main.java:505)
> [Server:server-two] 10:31:42,444 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
> [Server:server-two]
> 10:31:42,463 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'Server:server-two' finished with an exit status of 1
> [Host Controller] 10:31:42,505 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-two
> [Host Controller] 10:31:42,512 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> [Host Controller] 10:31:42,513 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> [Host Controller] 10:31:42,513 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Infinispan Server 9.1.0-SNAPSHOT (WildFly Core 2.2.0.Final) (Host Controller) started in 2356ms - Started 53 of 55 services (17 services are lazy, passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-7802) Use chunked reads/writes in TcpTransport
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-7802?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-7802:
-----------------------------------------------
Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1448366|https://bugzilla.redhat.com/show_bug.cgi?id=1448366] from ON_QA to VERIFIED
> Use chunked reads/writes in TcpTransport
> ----------------------------------------
>
> Key: ISPN-7802
> URL: https://issues.jboss.org/browse/ISPN-7802
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Tristan Tarrant
>
> The buffering implementation of {{TcpTransport.socketInputStream}} needs to use fixed size input buffer, rather than growing as {{BufferedInputStream}} does. Growing buffer can lead to excessive memory consumption on heap, and more importantly, by direct memory allocated in JDK classes and pooled in thread-local caches.
> EDIT: As Tristan pointed out, the {{BufferedInputStream}} does not grow in our use case, but if {{TcpTransport}} passes a big {{byte[]}} buffer, the implementation works as read through/write through. Therefore we need to chunk all calls.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-7841) Add stream operations that can operate upon data exclusively
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7841?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7841:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5148
> Add stream operations that can operate upon data exclusively
> ------------------------------------------------------------
>
> Key: ISPN-7841
> URL: https://issues.jboss.org/browse/ISPN-7841
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.1.0.Final
>
>
> It would be nice to have a way to perform a stream operation where the data performed upon is done in an exclusive way. That is that the data cannot change while it is being processed upon. This is only at the level of per key. For example non tx cache could temporarily lock the entry to prevent a write. The same could occur with pessimistic transactions. Optimistic transactions are a bit special and in this case we could just allow for some retry logic to allow for the stream to reread a given key and try the stream operation again if a WriteSkewException was thrown.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-6869) Deadlock during stopping CacheManager
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6869?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6869:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Deadlock during stopping CacheManager
> -------------------------------------
>
> Key: ISPN-6869
> URL: https://issues.jboss.org/browse/ISPN-6869
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha3
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Attachments: server.log.gz
>
>
> When new cache is started during ISPN shutdown, it can result into a deadlock.
> When new cache is created, first {{DefaultCacheManager.CacheWrapper}} is created with a latch. This latch is release once cache is fully started. If in meantime {{DefaultCacheManager#stop}} is called, it will first stop and lock {{GlobalComponentRegistry}} and after that will try to access and stop all caches. However, if there is present half-created cache (one with latch in {{DefaultCacheManager.CacheWrapper}} not released yet), if will result into a deadlock, as {{cache#start}} tries to access and lock {{GlobalComponentRegistry}}, already lock by {{DefaultCacheManager}}.
> Relevant pieces of stack traces are bellow, whole stack trace is attached.
> Locking of {{GlobalComponentRegistry}} by {{DefaultCacheManager#stop}}:
> {noformat}
> at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:569)
> - locked <0x00000000e1606fc0> (a org.infinispan.factories.GlobalComponentRegistry)
> at org.infinispan.factories.GlobalComponentRegistry.stop(GlobalComponentRegistry.java:282)
> - locked <0x00000000e1606fc0> (a org.infinispan.factories.GlobalComponentRegistry)
> at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:699)
> - locked <0x00000000e1606bb0> (a org.infinispan.manager.DefaultCacheManager)
> at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.stop(AbstractDelegatingEmbeddedCacheManager.java:173)
> {noformat}
> and later of waiting for cache latch:
> {noformat}
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000fd59db80> (a java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at org.infinispan.manager.DefaultCacheManager$CacheWrapper.getCache(DefaultCacheManager.java:968)
> {noformat}
> Waiting for a lock for {{GlobalComponentRegistry}} when cache is created:
> {noformat}
> at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277)
> - waiting to lock <0x00000000e1606fc0> (a org.infinispan.factories.GlobalComponentRegistry)
> at org.infinispan.factories.GlobalComponentRegistry.getTimeService(GlobalComponentRegistry.java:167)
> at org.infinispan.factories.ComponentRegistry.getTimeService(ComponentRegistry.java:271)
> at org.infinispan.distexec.DefaultExecutorService.<init>(DefaultExecutorService.java:190)
> [...]
> org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:636)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:587)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:452)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:438)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-7850) JDBC Migrator 9.x Marshaller Incorrectly Loaded
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7850?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7850.
--------------------------------
Resolution: Done
> JDBC Migrator 9.x Marshaller Incorrectly Loaded
> -----------------------------------------------
>
> Key: ISPN-7850
> URL: https://issues.jboss.org/browse/ISPN-7850
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.0.1.Final, 9.1.0.Alpha1
>
>
> When loading the CURRENT marshaller we extract it from an existing CacheManager and place it in the config for the target cache manager. This is wrong, because it results in the GlobalMarshaller having another instance of a GlobalMarshaller as the `external` marshaller, resulting in an infinite loop occurring when attempting to extract externalizers from the SerializeWith annotation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-7768) Average stats should be expressed in Nanoseconds
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7768?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7768:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Average stats should be expressed in Nanoseconds
> ------------------------------------------------
>
> Key: ISPN-7768
> URL: https://issues.jboss.org/browse/ISPN-7768
> Project: Infinispan
> Issue Type: Enhancement
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.1.0.Alpha1
>
>
> Currently the cache stats average-read-time, average-write-time and average-remove-time are measured in milliseconds, however it is often the case that these operations are less than one milliseconds and so these averages regularly return 0. We should change measurement format to Nanoseconds so this information is not lost.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ISPN-7745) clusterwide-hit-ratio returns NAN
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7745?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7745:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> clusterwide-hit-ratio returns NAN
> ---------------------------------
>
> Key: ISPN-7745
> URL: https://issues.jboss.org/browse/ISPN-7745
> Project: Infinispan
> Issue Type: Bug
> Components: Console, JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.0.1.Final, 9.1.0.Alpha1
>
>
> "clusterwide-hit-ratio" statistic returns NaN in the DMR when a put operation occurs without any get operations, this causes the console to fail as it is unable to validate the NaN property in the subsequent JSON.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months