April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6456) Servlet 4.0 Support

by David Lloyd (JIRA)

David Lloyd created WFLY-6456: --------------------------------- Summary: Servlet 4.0 Support Key: WFLY-6456 URL: https://issues.jboss.org/browse/WFLY-6456 Project: WildFly Issue Type: Sub-task Components: EE Reporter: David Lloyd -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6457) JMD 2.1 Support

by David Lloyd (JIRA)

David Lloyd created WFLY-6457: --------------------------------- Summary: JMD 2.1 Support Key: WFLY-6457 URL: https://issues.jboss.org/browse/WFLY-6457 Project: WildFly Issue Type: Sub-task Reporter: David Lloyd -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6455) Parent Issue for Java EE 8 Support

by David Lloyd (JIRA)

David Lloyd created WFLY-6455: --------------------------------- Summary: Parent Issue for Java EE 8 Support Key: WFLY-6455 URL: https://issues.jboss.org/browse/WFLY-6455 Project: WildFly Issue Type: Task Reporter: David Lloyd This is the parent issue for tracking tasks related to completing our Java EE 8 support. Do not close the issue unless Jason has given his blessing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6454) An exception occurring during Servlet.destroy() is not logged

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6454: ------------------------------------ Summary: An exception occurring during Servlet.destroy() is not logged Key: WFLY-6454 URL: https://issues.jboss.org/browse/WFLY-6454 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 9.0.2.Final Reporter: lorenzo benvenuti Assignee: Stuart Douglas 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)

8 years, 1 month

1
0
0 / 0

[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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6410) Domain server suspend does not accept -1 timeout(indefinite)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6410?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6410: ---------------------------------------- This works fine from the CLI and the operation metadata doesn't give any indication that -1 is invalid, so I'm going to move this to HAL. [~harald.pehl] if a metadata change will make this go away with no change in HAL, please move it to WFCORE and set the component to Domain Management. > Domain server suspend does not accept -1 timeout(indefinite) > ------------------------------------------------------------ > > Key: WFLY-6410 > URL: https://issues.jboss.org/browse/WFLY-6410 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[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)

8 years, 1 month

1
0
0 / 0

[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)

8 years, 1 month

1
0
0 / 0

[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)

8 years, 1 month

1
0
0 / 0

[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)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2016