[JBoss JIRA] (ISPN-7247) Administration console - changing any cache configuration adds security tag to the configuration
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-7247?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-7247:
------------------------------
Priority: Blocker (was: Major)
> Administration console - changing any cache configuration adds security tag to the configuration
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-7247
> URL: https://issues.jboss.org/browse/ISPN-7247
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> Steps to reproduce:
> click on cache container -> cache -> configuration -> change a value (e.g. number of owner 2 -> 1) -> click apply changes -> click restart later
> Check the configuration file - domain.xml, the modified cache now has security tag:
> <security>
> <authorization roles=""/>
> </security>
> This result in error when we stop the server and start it again:
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.default.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:745)
> [Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled.
> ...
> 09:57:05,492 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("memcached-connector" => "memcached-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("hotrod-connector" => "hotrod-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,494 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("rest-connector" => "rest-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,495 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("websocket-connector" => "websocket-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("configurations" => "CONFIGURATIONS"),
> [Server:server-one] ("distributed-cache-configuration" => "default")
> [Server:server-one] ]) - failure description: {
> [Server:server-one] "WFLYCTL0080: Failed services" => {"jboss.datagrid-infinispan.clustered.default.config" => "org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
> [Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled."},
> [Server:server-one] "WFLYCTL0412: Required services that are not installed:" => ["jboss.datagrid-infinispan.clustered.default.config"],
> [Server:server-one] "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> [Server:server-one] }
> [Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("distributed-cache" => "default")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7247) Administration console - changing any cache configuration adds security tag to the configuration
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-7247?page=com.atlassian.jira.plugin.... ]
Roman Macor reopened ISPN-7247:
-------------------------------
This is still present, but now it only happens when security is enabled in cache container.
To enable security, add security element under cache-container element
e.g.
<cache-container name="clustered" default-cache="default" statistics="true">
<transport lock-timeout="60000"/>
<security>
<authorization>
<identity-role-mapper/>
<role name="reader" permissions="READ"/>
<role name="admin" permissions="ALL BULK_READ WRITE"/>
</authorization>
</security>
> Administration console - changing any cache configuration adds security tag to the configuration
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-7247
> URL: https://issues.jboss.org/browse/ISPN-7247
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Fix For: 9.0.0.Beta1
>
>
> Steps to reproduce:
> click on cache container -> cache -> configuration -> change a value (e.g. number of owner 2 -> 1) -> click apply changes -> click restart later
> Check the configuration file - domain.xml, the modified cache now has security tag:
> <security>
> <authorization roles=""/>
> </security>
> This result in error when we stop the server and start it again:
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.default.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:745)
> [Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled.
> ...
> 09:57:05,492 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("memcached-connector" => "memcached-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("hotrod-connector" => "hotrod-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,494 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("rest-connector" => "rest-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,495 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
> [Server:server-one] ("websocket-connector" => "websocket-connector")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
> [Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("configurations" => "CONFIGURATIONS"),
> [Server:server-one] ("distributed-cache-configuration" => "default")
> [Server:server-one] ]) - failure description: {
> [Server:server-one] "WFLYCTL0080: Failed services" => {"jboss.datagrid-infinispan.clustered.default.config" => "org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
> [Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled."},
> [Server:server-one] "WFLYCTL0412: Required services that are not installed:" => ["jboss.datagrid-infinispan.clustered.default.config"],
> [Server:server-one] "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> [Server:server-one] }
> [Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("distributed-cache" => "default")
> [Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-29) Security related error messages vary between Node versions
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-29?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-29:
---------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/js-client/pull/11
> Security related error messages vary between Node versions
> ----------------------------------------------------------
>
> Key: HRJS-29
> URL: https://issues.jboss.org/browse/HRJS-29
> Project: Infinispan Javascript client
> Issue Type: Bug
> Reporter: Galder Zamarreño
> Fix For: 0.4.0
>
>
> Currently testsuite works fine with Node 0.10. When running for example with Node 4.x, you get errors like this:
> {code}
> 2) Infinispan TLS/SSL client can operate on data via crypto store trusted encrypted transport
> Message:
> Error: self signed certificate in certificate chain
> Stacktrace:
> Error: self signed certificate in certificate chain
> at Error (native)
> at TLSSocket.<anonymous> (_tls_wrap.js:1016:38)
> at emitNone (events.js:67:13)
> at TLSSocket.emit (events.js:166:7)
> at TLSSocket._finishInit (_tls_wrap.js:585:8)
> 3) Infinispan TLS/SSL client fails to operate if default server name (SNI) does not match default server realm
> Message:
> Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> Stacktrace:
> Error: Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> 4) Infinispan TLS/SSL client fails to operate if server name (SNI) and trusted certificate are incorrect
> Message:
> Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> Stacktrace:
> Error: Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> {code}
> So, the error message comparisons need to be adjusted to support other Node versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-29) Security related error messages vary between Node versions
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-29?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-29:
---------------------------------
Fix Version/s: 0.4.0
> Security related error messages vary between Node versions
> ----------------------------------------------------------
>
> Key: HRJS-29
> URL: https://issues.jboss.org/browse/HRJS-29
> Project: Infinispan Javascript client
> Issue Type: Bug
> Reporter: Galder Zamarreño
> Fix For: 0.4.0
>
>
> Currently testsuite works fine with Node 0.10. When running for example with Node 4.x, you get errors like this:
> {code}
> 2) Infinispan TLS/SSL client can operate on data via crypto store trusted encrypted transport
> Message:
> Error: self signed certificate in certificate chain
> Stacktrace:
> Error: self signed certificate in certificate chain
> at Error (native)
> at TLSSocket.<anonymous> (_tls_wrap.js:1016:38)
> at emitNone (events.js:67:13)
> at TLSSocket.emit (events.js:166:7)
> at TLSSocket._finishInit (_tls_wrap.js:585:8)
> 3) Infinispan TLS/SSL client fails to operate if default server name (SNI) does not match default server realm
> Message:
> Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> Stacktrace:
> Error: Expected 'Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: untrusted.acme"' to be 'Hostname/IP doesn't match certificate's altnames'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> 4) Infinispan TLS/SSL client fails to operate if server name (SNI) and trusted certificate are incorrect
> Message:
> Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> Stacktrace:
> Error: Expected 'certificate signature failure' to be 'CERT_SIGNATURE_FAILURE'.
> at /home/wburns/RedHat/jdg-js-client/spec/infinispan_ssl_spec.js:139:27
> at tryCallOne (/home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:37:12)
> at /home/wburns/RedHat/jdg-js-client/node_modules/promise/lib/core.js:123:15
> at flush (/home/wburns/RedHat/jdg-js-client/node_modules/asap/raw.js:50:29)
> at nextTickCallbackWith0Args (node.js:419:9)
> at process._tickCallback (node.js:348:13)
> {code}
> So, the error message comparisons need to be adjusted to support other Node versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-25) Test pkill command might be killing itself
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-25?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-25:
---------------------------------
Status: Open (was: New)
> Test pkill command might be killing itself
> ------------------------------------------
>
> Key: HRJS-25
> URL: https://issues.jboss.org/browse/HRJS-25
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Fix For: 0.4.0
>
>
> In some environments (e.g. ubuntu), failover and xsite tests fail with errors like this:
> {code}
> 1) Infinispan cluster client can failover when nodes crash
> Message:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> Stacktrace:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> at ChildProcess.exithandler (child_process.js:213:12)
> at emitTwo (events.js:87:13)
> at ChildProcess.emit (events.js:172:7)
> at maybeClose (internal/child_process.js:854:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
> {code}
> After adding more info the error, we've found that the error contains:
> {code}
> exec error (JS): {"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh -c pkill -9 -f '.*java.*node4 .*'"}
> {code}
> The node.js documentation says:
> {code}
> If the process terminated normally, code is the final exit code of
> the process, otherwise null. If the process terminated due to
> receipt of a signal, signal is the string name of the signal,
> otherwise null.
> {code}
> So, it might imply that the {{pkill}} command is killing itself...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-25) Test pkill command might be killing itself
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-25?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño reassigned HRJS-25:
------------------------------------
Assignee: Galder Zamarreño
> Test pkill command might be killing itself
> ------------------------------------------
>
> Key: HRJS-25
> URL: https://issues.jboss.org/browse/HRJS-25
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 0.4.0
>
>
> In some environments (e.g. ubuntu), failover and xsite tests fail with errors like this:
> {code}
> 1) Infinispan cluster client can failover when nodes crash
> Message:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> Stacktrace:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> at ChildProcess.exithandler (child_process.js:213:12)
> at emitTwo (events.js:87:13)
> at ChildProcess.emit (events.js:172:7)
> at maybeClose (internal/child_process.js:854:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
> {code}
> After adding more info the error, we've found that the error contains:
> {code}
> exec error (JS): {"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh -c pkill -9 -f '.*java.*node4 .*'"}
> {code}
> The node.js documentation says:
> {code}
> If the process terminated normally, code is the final exit code of
> the process, otherwise null. If the process terminated due to
> receipt of a signal, signal is the string name of the signal,
> otherwise null.
> {code}
> So, it might imply that the {{pkill}} command is killing itself...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-25) Test pkill command might be killing itself
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-25?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-25:
---------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/js-client/pull/10
> Test pkill command might be killing itself
> ------------------------------------------
>
> Key: HRJS-25
> URL: https://issues.jboss.org/browse/HRJS-25
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 0.4.0
>
>
> In some environments (e.g. ubuntu), failover and xsite tests fail with errors like this:
> {code}
> 1) Infinispan cluster client can failover when nodes crash
> Message:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> Stacktrace:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> at ChildProcess.exithandler (child_process.js:213:12)
> at emitTwo (events.js:87:13)
> at ChildProcess.emit (events.js:172:7)
> at maybeClose (internal/child_process.js:854:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
> {code}
> After adding more info the error, we've found that the error contains:
> {code}
> exec error (JS): {"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh -c pkill -9 -f '.*java.*node4 .*'"}
> {code}
> The node.js documentation says:
> {code}
> If the process terminated normally, code is the final exit code of
> the process, otherwise null. If the process terminated due to
> receipt of a signal, signal is the string name of the signal,
> otherwise null.
> {code}
> So, it might imply that the {{pkill}} command is killing itself...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7207) Cache creation requires specific permissions when using security manager
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/ISPN-7207?page=com.atlassian.jira.plugin.... ]
Ingo Weiss updated ISPN-7207:
-----------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4678
> Cache creation requires specific permissions when using security manager
> ------------------------------------------------------------------------
>
> Key: ISPN-7207
> URL: https://issues.jboss.org/browse/ISPN-7207
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Paul Ferraro
> Assignee: Ingo Weiss
>
> *org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase#test*
> {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase -Dsecurity.manager}}
> {code}
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/infinispan-resource-ref.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.infinispan-resource-ref.war:main" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1528)
> at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1442)
> at org.infinispan.commons.util.Util.getClassLoaders(Util.java:127)
> at org.infinispan.commons.util.Util.loadClassStrict(Util.java:163)
> at org.infinispan.commons.util.ReflectionUtil.getClassForName(ReflectionUtil.java:319)
> at org.infinispan.commons.util.ReflectionUtil.toClassArray(ReflectionUtil.java:313)
> at org.infinispan.factories.AbstractComponentRegistry$Component.buildInjectionMethodsList(AbstractComponentRegistry.java:810)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:213)
> at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:193)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:171)
> at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:163)
> at org.infinispan.factories.ComponentRegistry.<init>(ComponentRegistry.java:79)
> ... 210 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7160:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> RemoteSpringSessionTest random failures
> ---------------------------------------
>
> Key: ISPN-7160
> URL: https://issues.jboss.org/browse/ISPN-7160
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Reporter: Dan Berindei
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta2
>
>
> {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager:
> {noformat}
> org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147)
> at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29)
> {noformat}
> If the cache manager was not created, teardown also fails with a NPE:
> {noformat}
> java.lang.NullPointerException
> at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41)
> {noformat}
> The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months