[JBoss JIRA] (WFCORE-1460) Ensure that tests don't leave the server in reload-required
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1460:
----------------------------------------
Summary: Ensure that tests don't leave the server in reload-required
Key: WFCORE-1460
URL: https://issues.jboss.org/browse/WFCORE-1460
Project: WildFly Core
Issue Type: Enhancement
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 3.0.0.Alpha1
A proper test class should not complete while leaving a running server in reload-required state. That state means the runtime is inconsistent with the persistent config. The next test class has no way to figure out how it is inconsistent, and shouldn't bear responsibility for making it consistent.
Fixing this was a requirement for getting a testsuite to work once the WFCORE-1106 are in place, so I already have changes to fix it. This JIRA is just so I can assign a label to those changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6418) IIOP subsystem intermittently does not start if SSL is used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6418?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6418:
-----------------------------------
Priority: Major (was: Blocker)
I'm changing the priority to match the downstream issue.
> IIOP subsystem intermittently does not start if SSL is used
> ------------------------------------------------------------
>
> Key: WFLY-6418
> URL: https://issues.jboss.org/browse/WFLY-6418
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondřej Chaloupka
> Assignee: Tomasz Adamski
>
> As part of TCK testing I can see intermittent failure where IIOP subsystem does not start (which causes whole server fails to start) with message of not found a JSEE security domain.
> That means if IIOP subsytem is configured to run with ssl it causes whole server failing to start.
> {code}
> \u001b[0m\u001b[31m09:03:12,609 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 227 completed: No at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:142) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]Caused by: org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 227 completed: No at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:558) [rt.jar:1.8.0_71] at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:576) [rt.jar:1.8.0_71] at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:485) [rt.jar:1.8.0_71] at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:543) [rt.jar:1.8.0_71] at org.omg.CORBA.ORB.init(ORB.java:353) [rt.jar:1.8.0_71] at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:126) ... 5 moreCaused by: java.lang.RuntimeException: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain at org.wildfly.iiop.openjdk.security.SocketFactory.setORB(SocketFactory.java:92) at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.initializeTransport(ORBConfiguratorImpl.java:271) [rt.jar:1.8.0_71] at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:149) [rt.jar:1.8.0_71] at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:483) [rt.jar:1.8.0_71] ... 8 moreCaused by: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain ... 12 more
> ...
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.iiop-openjdk.orb-service (missing) dependents: [service jboss.iiop-openjdk.naming-service, service jboss.iiop-openjdk.poa-service.rootpoa]
> service jboss.iiop-openjdk.poa-service.namingpoa (missing) dependents: [service jboss.iiop-openjdk.naming-service]
> service jboss.iiop-openjdk.poa-service.rootpoa (missing) dependents: [service jboss.iiop-openjdk.poa-service.irpoa, service jboss.iiop-openjdk.poa-service.namingpoa, service jboss.iiop-openjdk.naming-service]
> WFLYCTL0186: Services which failed to start: service jboss.iiop-openjdk.orb-service
> \u001b[0m\u001b[0m09:03:15,758 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
> \u001b[0m\u001b[0m09:03:15,770 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.0.Final-redhat-1) stopped in 787ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6427) An exception occurring during Servlet.destroy() is not logged
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6427?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6427:
-----------------------------------
Component/s: Web (Undertow)
> An exception occurring during Servlet.destroy() is not logged
> -------------------------------------------------------------
>
> Key: WFLY-6427
> URL: https://issues.jboss.org/browse/WFLY-6427
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.2.Final
> Reporter: lorenzo benvenuti
> Assignee: Jason Greene
> Attachments: WildflyTestException.zip
>
>
> There's no evidence of an exception thrown in a Servlet destroy method; the only hint you have that something has gone wrong is the fact that the ServletContextListener.contextDestroyed methods are not invoked (I don't know if this is the expected behavior: for instance JBoss 7.1.1 logs the Servlet.destroy exception and then invokes ServletContextListener.contextDestroyed anyway).
> Thank you,
> lorenzo
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6427) An exception occurring during Servlet.destroy() is not logged
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6427?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-6427:
--------------------------------------
Assignee: Stuart Douglas (was: Jason Greene)
> An exception occurring during Servlet.destroy() is not logged
> -------------------------------------------------------------
>
> Key: WFLY-6427
> URL: https://issues.jboss.org/browse/WFLY-6427
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.2.Final
> Reporter: lorenzo benvenuti
> Assignee: Stuart Douglas
> Attachments: WildflyTestException.zip
>
>
> There's no evidence of an exception thrown in a Servlet destroy method; the only hint you have that something has gone wrong is the fact that the ServletContextListener.contextDestroyed methods are not invoked (I don't know if this is the expected behavior: for instance JBoss 7.1.1 logs the Servlet.destroy exception and then invokes ServletContextListener.contextDestroyed anyway).
> Thank you,
> lorenzo
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6452) Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-6452?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-6452:
----------------------------------------
Yes I do agree that there is an issue that need to be solved otherwise the Jira issue would be closed.
WildFly 10 contains new code, part of that has allowed us to review what we did before so the exact place decisions are made may be altered. However yes LoginModules being repeatedly called for users that have been recently authenticated is a bad thing.
> Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6452
> URL: https://issues.jboss.org/browse/WFLY-6452
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Juan AMAT
> Assignee: Darran Lofthouse
>
> While doing some performance testing of our application on Wildfly 10.0.0.Final we noticed a huge difference in CPU utlization version the same test on JBoss EAP 6.4.
> What the test is doing is to run concurrently 2500 clients that log in webapp (FORM bases authentication) and that send a request every 15 seconds on average.
> In JBoss EAP 6.4 cpu utilization was about 10% on a 24 cores machine with one 20G JVM.
> With wildfly it was 95+%.
> Threads dumps showed a lot of threads in the JAAS Login Module.
> We are using org.jboss.security.auth.spi.DatabaseServerLoginModule.
> This was strange because all the users were already authenticated.
> It turns out that in Wildfly JBossCachedAuthenticationManager.isValid is called on every HTTP request. This is not the case in EAP 6.4.
> The problem then is that we have configured the security-domain with 'cache-type=default' which will use a cache with 1000 entries less than the number of our clients.
> The 'isValid' method will try to find the Principal in the cache, will not find it (most of the time) and will trigger an authentication.
> We can workaround this using 'cache-type=infinispan' with a local-cache with more entries. (and this is what I did not set this ticket as blocker).
> But this is just a workaround IMO.
> Why is 'isValid' called on every request in Wildfly?
> On a related note, it would also be nice to be able to configure the number of entries in the cache when using 'cache-type=default'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6452) Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
by Juan AMAT (JIRA)
[ https://issues.jboss.org/browse/WFLY-6452?page=com.atlassian.jira.plugin.... ]
Juan AMAT commented on WFLY-6452:
---------------------------------
I guess we are talking past each other because for me the cache should not be involved at that stage (and again it was not in JBoss EAP 6.4).
I do not think that I can change your mind but I do feel that the current implementation will cause pain to other users that will hit this same issue.
Especially people coming from JBoss EAP 6 that will migrate to EAP 7.
And it should be documented.
> Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6452
> URL: https://issues.jboss.org/browse/WFLY-6452
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Juan AMAT
> Assignee: Darran Lofthouse
>
> While doing some performance testing of our application on Wildfly 10.0.0.Final we noticed a huge difference in CPU utlization version the same test on JBoss EAP 6.4.
> What the test is doing is to run concurrently 2500 clients that log in webapp (FORM bases authentication) and that send a request every 15 seconds on average.
> In JBoss EAP 6.4 cpu utilization was about 10% on a 24 cores machine with one 20G JVM.
> With wildfly it was 95+%.
> Threads dumps showed a lot of threads in the JAAS Login Module.
> We are using org.jboss.security.auth.spi.DatabaseServerLoginModule.
> This was strange because all the users were already authenticated.
> It turns out that in Wildfly JBossCachedAuthenticationManager.isValid is called on every HTTP request. This is not the case in EAP 6.4.
> The problem then is that we have configured the security-domain with 'cache-type=default' which will use a cache with 1000 entries less than the number of our clients.
> The 'isValid' method will try to find the Principal in the cache, will not find it (most of the time) and will trigger an authentication.
> We can workaround this using 'cache-type=infinispan' with a local-cache with more entries. (and this is what I did not set this ticket as blocker).
> But this is just a workaround IMO.
> Why is 'isValid' called on every request in Wildfly?
> On a related note, it would also be nice to be able to configure the number of entries in the cache when using 'cache-type=default'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6452) Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-6452?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-6452:
----------------------------------------
Yes the LoginModule should not be called, we should have been able to identify the corresponding entry in the cache used by JBossCachedAuthenticationManager,
> Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6452
> URL: https://issues.jboss.org/browse/WFLY-6452
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Juan AMAT
> Assignee: Darran Lofthouse
>
> While doing some performance testing of our application on Wildfly 10.0.0.Final we noticed a huge difference in CPU utlization version the same test on JBoss EAP 6.4.
> What the test is doing is to run concurrently 2500 clients that log in webapp (FORM bases authentication) and that send a request every 15 seconds on average.
> In JBoss EAP 6.4 cpu utilization was about 10% on a 24 cores machine with one 20G JVM.
> With wildfly it was 95+%.
> Threads dumps showed a lot of threads in the JAAS Login Module.
> We are using org.jboss.security.auth.spi.DatabaseServerLoginModule.
> This was strange because all the users were already authenticated.
> It turns out that in Wildfly JBossCachedAuthenticationManager.isValid is called on every HTTP request. This is not the case in EAP 6.4.
> The problem then is that we have configured the security-domain with 'cache-type=default' which will use a cache with 1000 entries less than the number of our clients.
> The 'isValid' method will try to find the Principal in the cache, will not find it (most of the time) and will trigger an authentication.
> We can workaround this using 'cache-type=infinispan' with a local-cache with more entries. (and this is what I did not set this ticket as blocker).
> But this is just a workaround IMO.
> Why is 'isValid' called on every request in Wildfly?
> On a related note, it would also be nice to be able to configure the number of entries in the cache when using 'cache-type=default'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6452) Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
by Juan AMAT (JIRA)
[ https://issues.jboss.org/browse/WFLY-6452?page=com.atlassian.jira.plugin.... ]
Juan AMAT commented on WFLY-6452:
---------------------------------
OK but once you are authenticated...
I still feel the need to configure a cache with some 'random' number of entries counter-intuitive. Worst case we will need to configure a cache with no limit and maybe an expiration time greater that our max session timeout. Hoping that we will not have memory issues.
Again that the LoginModule was called again for an already authenticated user is not something that I would expect. IOW either I am authenticated and nothing should be done. Or I am not then a 401 should be returned for the http request or I should be redirected to my login page.
> Unable to tune 'default' cache as used by JBossCachedAuthenticationManager leading to valid entries being prematurely evicted.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6452
> URL: https://issues.jboss.org/browse/WFLY-6452
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Juan AMAT
> Assignee: Darran Lofthouse
>
> While doing some performance testing of our application on Wildfly 10.0.0.Final we noticed a huge difference in CPU utlization version the same test on JBoss EAP 6.4.
> What the test is doing is to run concurrently 2500 clients that log in webapp (FORM bases authentication) and that send a request every 15 seconds on average.
> In JBoss EAP 6.4 cpu utilization was about 10% on a 24 cores machine with one 20G JVM.
> With wildfly it was 95+%.
> Threads dumps showed a lot of threads in the JAAS Login Module.
> We are using org.jboss.security.auth.spi.DatabaseServerLoginModule.
> This was strange because all the users were already authenticated.
> It turns out that in Wildfly JBossCachedAuthenticationManager.isValid is called on every HTTP request. This is not the case in EAP 6.4.
> The problem then is that we have configured the security-domain with 'cache-type=default' which will use a cache with 1000 entries less than the number of our clients.
> The 'isValid' method will try to find the Principal in the cache, will not find it (most of the time) and will trigger an authentication.
> We can workaround this using 'cache-type=infinispan' with a local-cache with more entries. (and this is what I did not set this ticket as blocker).
> But this is just a workaround IMO.
> Why is 'isValid' called on every request in Wildfly?
> On a related note, it would also be nice to be able to configure the number of entries in the cache when using 'cache-type=default'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6294?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-6294:
--------------------------------------
Created WFLY-6453 to fix the issue with the session manager too.
> Session draining always takes maximum configured timeout
> --------------------------------------------------------
>
> Key: WFLY-6294
> URL: https://issues.jboss.org/browse/WFLY-6294
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Minor
>
> The mod_cluster session drain wait is not ending as expected. mod_cluster adds a session listener to be notified of session destruction. That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active. Thus, this drain loop doesn't end after the notify because it still sees the active session:
> {code}
> while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) {
> ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context);
> listener.wait(noTimeout ? 0 : timeout);
> current = System.currentTimeMillis();
> timeout = end - current;
> remainingSessions = context.getActiveSessionCount();
> }
> {code}
> Can the listeners be invoked when the session is fully removed and no longer considered active?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month