[JBoss JIRA] (WFLY-1477) JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1477?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1477:
------------------------------
Component/s: Web (Undertow)
(was: Web (JBoss Web))
> JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1477
> URL: https://issues.jboss.org/browse/WFLY-1477
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha1
> Environment: CentOS 6.x, JBoss AS 7.1.1.Final
> Reporter: Steve S
> Assignee: Remy Maucherat
> Labels: domain, jaas, jboss, jbossweb, login, module, security
>
> Please see the following forum post for a detailed explanation and findings(and potential workaround):
> https://community.jboss.org/message/822054#822054
> If multiple WARs are deployed that depend on a login module leveraging:
> HttpServletRequest request = (HttpServletRequest)PolicyContext.getContext("javax.servlet.http.HttpServletRequest");
> then upon undeploy of any web application in the container the HttpServletRequestPolicyContextHandler is removed(deregistered) in the stop() lifecycle method of the JBossWebRealmService, resulting in:
> 13:03:35,335 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (ajp--0.0.0.0-8009-1) Login failure: javax.security.auth.login.LoginException: java.lang.IllegalArgumentException: No PolicyContextHandler for key=javax.servlet.http.HttpServletRequest at javax.security.jacc.PolicyContext.getContext(PolicyContext.java:117)
> for any webapps still deployed for every subsequent access to them.
> Simply redeploying any ONE of the remaining webapps or the previously undeployed webapp causes this problem to go away for all deployed applications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-2892) Deploying exploded RAR with exploded JAR fails with CNFE
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2892?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-2892:
----------------------------------
Priority: Optional (was: Major)
Assignee: Stefano Maestri (was: Jesper Pedersen)
Fully exploded resource adapters will not a valid specification format
> Deploying exploded RAR with exploded JAR fails with CNFE
> --------------------------------------------------------
>
> Key: WFLY-2892
> URL: https://issues.jboss.org/browse/WFLY-2892
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.CR1
> Reporter: Darryl Miles
> Assignee: Stefano Maestri
> Priority: Optional
>
> This is the default method of deployment for JBoss AS Connector when using Eclipse and JBoss Tools.
> The resulting file layout is like:
> deployments/com.domain.rarproject.rar/com.domain.rarimpl.jar/com/domain/MyClassFile.class
> When the RAR is built into a JAR file, that contains the com.domain.rarimpl.jar inside deployment is sucessfull.
> The RAR deployer should allow the exploded layout where the "com.domain.rarimpl.jar" is of type directory (not file).
> Or JBoss AS Tooling should be fixed to understand the limitation of the AS RAR deployer during development of RAR/JCA driver.
> Other kinds of deployments allow exploded format via JBoss VFS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-1477) JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1477?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1477:
---------------------------------
Assignee: Tomaz Cerar (was: Remy Maucherat)
> JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1477
> URL: https://issues.jboss.org/browse/WFLY-1477
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha1
> Environment: CentOS 6.x, JBoss AS 7.1.1.Final
> Reporter: Steve S
> Assignee: Tomaz Cerar
> Labels: domain, jaas, jboss, jbossweb, login, module, security
>
> Please see the following forum post for a detailed explanation and findings(and potential workaround):
> https://community.jboss.org/message/822054#822054
> If multiple WARs are deployed that depend on a login module leveraging:
> HttpServletRequest request = (HttpServletRequest)PolicyContext.getContext("javax.servlet.http.HttpServletRequest");
> then upon undeploy of any web application in the container the HttpServletRequestPolicyContextHandler is removed(deregistered) in the stop() lifecycle method of the JBossWebRealmService, resulting in:
> 13:03:35,335 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (ajp--0.0.0.0-8009-1) Login failure: javax.security.auth.login.LoginException: java.lang.IllegalArgumentException: No PolicyContextHandler for key=javax.servlet.http.HttpServletRequest at javax.security.jacc.PolicyContext.getContext(PolicyContext.java:117)
> for any webapps still deployed for every subsequent access to them.
> Simply redeploying any ONE of the remaining webapps or the previously undeployed webapp causes this problem to go away for all deployed applications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-974) "java.lang.IllegalStateException: Parameters processing failed" for IE browser only
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-974?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar closed WFLY-974.
----------------------------
Resolution: Out of Date
JbossWeb is no longer used in WildFly8.
If same issue still occurs with Undertow, please create new issue.
> "java.lang.IllegalStateException: Parameters processing failed" for IE browser only
> -----------------------------------------------------------------------------------
>
> Key: WFLY-974
> URL: https://issues.jboss.org/browse/WFLY-974
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Environment: Windows 7 Enterprise Service Pack 1, JDK-1.7.0_05, jboss-as-7.1.1.Final/jboss-eap-6.0.0(Evaluation)
> Reporter: Vaibhav N
> Assignee: Remy Maucherat
> Labels: jboss
>
> Application throws an exception for IE browser only with "JBoss-as-7.1.1.Final" & "JBoss-eap-6.0.0(Evaluation version)" only, but it is working correctly for Firefox browser.
> Note : It is working fine with "jboss-as-7.1.0.Final" version for all browsers.
> Exception details :
> Unhandled Exception / Error:
> Internal Error (757457307) at :: Exception (Parameters processing failed.)
> java.lang.IllegalStateException: Parameters processing failed.
> at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:407)
> at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:229)
> at org.apache.catalina.connector.Request.parseParameters(Request.java:2874)
> at org.apache.catalina.connector.Request.getParameterNames(Request.java:1333)
> at org.apache.catalina.connector.RequestFacade.getParameterNames(RequestFacade.java:379).........................
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-1331) JBossWebParsingDeploymentProcessorTest fails if ran after any WebSubsystemTestCase
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1331?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-1331.
-------------------------------
Resolution: Out of Date
> JBossWebParsingDeploymentProcessorTest fails if ran after any WebSubsystemTestCase
> ----------------------------------------------------------------------------------
>
> Key: WFLY-1331
> URL: https://issues.jboss.org/browse/WFLY-1331
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Reporter: James Perkins
> Priority: Minor
> Attachments: org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessorTest.txt
>
>
> The order in which the tests run seem to be an issue. My assumption is it has something to do with powermock, but I didn't dig in all that much.
> {code}
> Caused by: java.lang.ClassCastException: __redirected.__XMLInputFactory cannot be cast to javax.xml.stream.XMLInputFactory
> at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:153)
> at __redirected.__XMLInputFactory.<clinit>(__XMLInputFactory.java:67)
> {code}
> The tests for me on Fedora 18 run in the following order:
> {code}
> Running org.jboss.as.web.test.WebSubsystemTestCase
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.42 sec
> Running org.jboss.as.web.test.WebSubsystemBareTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.166 sec
> Running org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessorTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.423 sec <<< FAILURE!
> Running org.jboss.as.web.deployment.WarDeploymentProcessorTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.932 sec
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-883) Socket bind for Http11Apr fails on startup when using link-local IPv6 address
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-883?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar closed WFLY-883.
----------------------------
Resolution: Migrated to another ITS
WildFly 8 does not have JbossWeb and APR connectors anymore.
Please use bugzilla for tracking EAP6.x related issued.
> Socket bind for Http11Apr fails on startup when using link-local IPv6 address
> -----------------------------------------------------------------------------
>
> Key: WFLY-883
> URL: https://issues.jboss.org/browse/WFLY-883
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Reporter: Richard Achmatowicz
> Assignee: Mladen Turk
> Labels: eap6_need_triage
>
> Start AS 7.1.0.Final with a link local IPv6 address:
> {noformat}
> [nrla@lenovo ~]$ /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr F0:DE:F1:40:75:B8
> inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::f2de:f1ff:fe40:75b8/64 Scope:Link
> inet6 addr: 3ffe:ffff:100:f101::1/64 Scope:Global
> [nrla@lenovo ~]$ ./standalone.sh -Djboss.bind.address=fe80::f2de:f1ff:fe40:75b8 -Djboss.bind.address.management=fe80::f2de:f1ff:fe40:75b8
> {noformat}
> and the following exception occurs:
> {noformat}
> 11:01:28,909 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:4447
> 11:01:29,013 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.1.GA
> 11:01:29,185 ERROR [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Error initializing endpoint: java.lang.Exception: Socket bind failed: [22] Invalid argument
> at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:578) [jbossweb-7.0.10.Final.jar:]
> at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) [jbossweb-7.0.10.Final.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.10.Final.jar:]
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> 11:01:29,254 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [22] Invalid argument
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> 11:01:29,442 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:9999
> 11:01:29,462 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/jboss-as/build/target/jboss-as-7.1.0.Final-SNAPSHOT/standalone/deployments
> 11:01:29,615 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 11:01:29,626 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> 11:01:29,649 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" started (with errors) in 2317ms - Started 133 of 203 services (1 services failed or missing dependencies, 68 services are passive or on-demand)
> {noformat}
> I had a look around and found this related (in fact the same) bug report:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=43327
> Looks like it may have been fixed for IPv6 addresses other than link-local.
> Link-local addresses are used often for running on a local network segment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-1013) Can't set attribute "suffix" on web access-log
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1013?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1013:
---------------------------------
Assignee: Tomaz Cerar (was: Remy Maucherat)
> Can't set attribute "suffix" on web access-log
> ----------------------------------------------
>
> Key: WFLY-1013
> URL: https://issues.jboss.org/browse/WFLY-1013
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Environment: N/A
> Reporter: Ed Roberts
> Assignee: Tomaz Cerar
> Labels: logging, suffix, web
>
> In JBoss 5.x you used to be able to specify a suffix attribute value for the JBossWeb access log file, which would be appended to generated log file names.
> In JBoss 7.x you can only specify a prefix. For the logging handlers you can specify both a prefix and a suffix, which is inconsistent.
> Please add the suffix attribute to the access-log element within the parent virtual-server element of the web subsystem xml configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-1013) Can't set attribute "suffix" on web access-log
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1013?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1013:
------------------------------
Component/s: Web (Undertow)
(was: Web (JBoss Web))
> Can't set attribute "suffix" on web access-log
> ----------------------------------------------
>
> Key: WFLY-1013
> URL: https://issues.jboss.org/browse/WFLY-1013
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Environment: N/A
> Reporter: Ed Roberts
> Assignee: Remy Maucherat
> Labels: logging, suffix, web
>
> In JBoss 5.x you used to be able to specify a suffix attribute value for the JBossWeb access log file, which would be appended to generated log file names.
> In JBoss 7.x you can only specify a prefix. For the logging handlers you can specify both a prefix and a suffix, which is inconsistent.
> Please add the suffix attribute to the access-log element within the parent virtual-server element of the web subsystem xml configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months