[JBoss JIRA] (WFLY-5434) HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
by Mark Wardell (JIRA)
[ https://issues.jboss.org/browse/WFLY-5434?page=com.atlassian.jira.plugin.... ]
Mark Wardell updated WFLY-5434:
-------------------------------
Description:
Running standalone HA configuration with single sign on enabled in undertow configuration
Two wars deployed each marked as distributable
If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
{code}
08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction {xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
...
at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
{code}
(full stack trace attached)
was:
Running standalone HA configuration with single sign on enabled in undertow configuration
Two wars deployed each marked as distributable
If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
...
at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
(full stack trace attached)
> HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-5434
> URL: https://issues.jboss.org/browse/WFLY-5434
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR2
> Reporter: Mark Wardell
> Assignee: Jason Greene
> Attachments: exception.txt
>
>
> Running standalone HA configuration with single sign on enabled in undertow configuration
> Two wars deployed each marked as distributable
> If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
> {code}
> 08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction {xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
> at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
> at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
> at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> ...
> at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
> at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
> {code}
> (full stack trace attached)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5434) HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
by Mark Wardell (JIRA)
[ https://issues.jboss.org/browse/WFLY-5434?page=com.atlassian.jira.plugin.... ]
Mark Wardell updated WFLY-5434:
-------------------------------
Steps to Reproduce:
Reproduced in a project here:
* https://github.com/mbw-ahc/wf10issue
* servlet-security copied from the quick starts but with <distributable/> added to the configuration
* logoutwar has a simple servlet that executes the session invalidate on get
* standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
* run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
* setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
* deploy the wars
* open a browser,
** To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
** To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
** The stack trace should be visible in the console log.
was:
Reproduced in a project here:
* https://github.com/mbw-ahc/wf10issue
* servlet-security copied from the quick starts but with <distributable/> added to the configuration
* logoutwar has a simple servlet that executes the session invalidate on get
* standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
* run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
* setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
* deploy the wars
* open a browser,
To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
The stack trace should be visible in the console log.
> HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-5434
> URL: https://issues.jboss.org/browse/WFLY-5434
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR2
> Reporter: Mark Wardell
> Assignee: Jason Greene
> Attachments: exception.txt
>
>
> Running standalone HA configuration with single sign on enabled in undertow configuration
> Two wars deployed each marked as distributable
> If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
> 08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
> at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
> at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
> at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> ...
> at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
> at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
> (full stack trace attached)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5434) HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
by Mark Wardell (JIRA)
[ https://issues.jboss.org/browse/WFLY-5434?page=com.atlassian.jira.plugin.... ]
Mark Wardell updated WFLY-5434:
-------------------------------
Steps to Reproduce:
Reproduced in a project here:
* https://github.com/mbw-ahc/wf10issue
* servlet-security copied from the quick starts but with <distributable/> added to the configuration
* logoutwar has a simple servlet that executes the session invalidate on get
* standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
deploy the wars
open a browser,
To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
The stack trace should be visible in the console log.
was:
Reproduced in a project here:
https://github.com/mbw-ahc/wf10issue
servlet-security copied from the quick starts but with <distributable/> added to the configuration
logoutwar has a simple servlet that executes the session invalidate on get
standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
deploy the wars
open a browser,
To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
The stack trace should be visible in the console log.
> HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-5434
> URL: https://issues.jboss.org/browse/WFLY-5434
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR2
> Reporter: Mark Wardell
> Assignee: Jason Greene
> Attachments: exception.txt
>
>
> Running standalone HA configuration with single sign on enabled in undertow configuration
> Two wars deployed each marked as distributable
> If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
> 08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
> at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
> at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
> at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> ...
> at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
> at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
> (full stack trace attached)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5434) HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
by Mark Wardell (JIRA)
[ https://issues.jboss.org/browse/WFLY-5434?page=com.atlassian.jira.plugin.... ]
Mark Wardell updated WFLY-5434:
-------------------------------
Steps to Reproduce:
Reproduced in a project here:
* https://github.com/mbw-ahc/wf10issue
* servlet-security copied from the quick starts but with <distributable/> added to the configuration
* logoutwar has a simple servlet that executes the session invalidate on get
* standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
* run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
* setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
* deploy the wars
* open a browser,
To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
The stack trace should be visible in the console log.
was:
Reproduced in a project here:
* https://github.com/mbw-ahc/wf10issue
* servlet-security copied from the quick starts but with <distributable/> added to the configuration
* logoutwar has a simple servlet that executes the session invalidate on get
* standalone-ha-sso.xml is the configuration file used, it is just standalone-ha with sso configured, plus some security domain added from the quick start.
Steps
run wildfly 10.0.0.CR2 with the standalone-ha-sso.xml configuration
setup the quickstart as per the instructions on the quickstart https://github.com/wildfly/quickstart/tree/10.x/servlet-security
deploy the wars
open a browser,
To login from one war, open the URL to http://localhost:8080/wildfly-servlet-security/SecuredServlet
To invalidate the session from the other war, open http://localhost:8080/logoutwar/logout
The stack trace should be visible in the console log.
> HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-5434
> URL: https://issues.jboss.org/browse/WFLY-5434
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR2
> Reporter: Mark Wardell
> Assignee: Jason Greene
> Attachments: exception.txt
>
>
> Running standalone HA configuration with single sign on enabled in undertow configuration
> Two wars deployed each marked as distributable
> If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
> 08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
> at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
> at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
> at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> ...
> at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
> at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
> (full stack trace attached)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5434) HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
by Mark Wardell (JIRA)
Mark Wardell created WFLY-5434:
----------------------------------
Summary: HttpSession invalidate() throws IllegalStateException: Transaction is not in a valid state
Key: WFLY-5434
URL: https://issues.jboss.org/browse/WFLY-5434
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.CR2
Reporter: Mark Wardell
Assignee: Jason Greene
Attachments: exception.txt
Running standalone HA configuration with single sign on enabled in undertow configuration
Two wars deployed each marked as distributable
If you login thought one war, then execute sesssion.invalidate() on the other you get the following exception during the invalidate call:
08:55:46,441 ERROR [io.undertow.request] (default task-35) UT005023: Exception handling request to /logoutwar/logout: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=96}, status=3} is not in a valid state to be invoking cache operations on.
at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:388)
at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:357)
at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
...
at org.wildfly.clustering.web.infinispan.session.coarse.CoarseSessionFactory.remove(CoarseSessionFactory.java:66)
at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:68)
at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:438)
at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:176)
at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199)
at wf10issue.logoutwar.LogoutServlet.doGet(LogoutServlet.java:27)
(full stack trace attached)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1022) AliasEntry needs more information than just the PathAddress
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-1022:
----------------------------------
Summary: AliasEntry needs more information than just the PathAddress
Key: WFCORE-1022
URL: https://issues.jboss.org/browse/WFCORE-1022
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Priority: Critical
Fix For: 2.0.0.CR6
As mentioned on https://issues.jboss.org/browse/WFLY-5290
[17:58] Kabir Khan: @PaulFerraro For https://issues.jboss.org/browse/WFLY-5290, what should the transport=TRANSPORT alias become?
[17:59] Paul Ferraro: @KabirKhan it becomes transport=*
[18:00] Kabir Khan: @PaulFerraro That can't map properly, it needs to map onto one resource
[18:00] Paul Ferraro: e.g. transport=TRANSPORT,type=UDP becomes transport=UDP
[18:00] Kabir Khan: ok, I see
in that case I can try to take a look
[18:01] Paul Ferraro: so - it needs more context than just the address
[18:01] Kabir Khan: and let me guess, that is not available at the moment from AliasEntry
[18:01] Paul Ferraro: right
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5180) InfinispanResourceRefTestCase causes NameNotFoundException with security manager
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5180?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-5180:
------------------------------------
I see - internally, we should be using a privileged action during construction of the cache components that require reflection.
> InfinispanResourceRefTestCase causes NameNotFoundException with security manager
> --------------------------------------------------------------------------------
>
> Key: WFLY-5180
> URL: https://issues.jboss.org/browse/WFLY-5180
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Paul Ferraro
>
> *Description of problem:*
> InfinispanResourceRefTestCase causes NameNotFoundException with security manager.
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./build.sh -DskipTests -DallTests -Dts.noSmoke
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=InfinispanResourceRefTestCase
> *Actual results:*
> {noformat}
> javax.naming.NameNotFoundException: infinispan
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58)
> at org.jboss.as.naming.ServiceBasedNamingStore$1.run(ServiceBasedNamingStore.java:138)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase.test(InfinispanResourceRefTestCase.java:64)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5290) Adding JGroups stack seems to freeze the UI
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5290?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-5290:
----------------------------------
[17:58] Kabir Khan: @PaulFerraro For https://issues.jboss.org/browse/WFLY-5290, what should the transport=TRANSPORT alias become?
[17:59] Paul Ferraro: @KabirKhan it becomes transport=*
[18:00] Kabir Khan: @PaulFerraro That can't map properly, it needs to map onto one resource
[18:00] Paul Ferraro: e.g. transport=TRANSPORT,type=UDP becomes transport=UDP
[18:00] Kabir Khan: ok, I see
in that case I can try to take a look
[18:01] Paul Ferraro: so - it needs more context than just the address
[18:01] Kabir Khan: and let me guess, that is not available at the moment from AliasEntry
[18:01] Paul Ferraro: right
> Adding JGroups stack seems to freeze the UI
> -------------------------------------------
>
> Key: WFLY-5290
> URL: https://issues.jboss.org/browse/WFLY-5290
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Domain Management
> Reporter: Jan Kašík
> Assignee: Kabir Khan
> Priority: Critical
> Fix For: 10.0.0.Final
>
>
> Adding new JGroups stack with randomly chosen (non existing) socket binding name results in web console freeze.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months