[JBoss JIRA] (AS7-3565) Failed to get file from remote repository error
by Rich Raposa (JIRA)
Rich Raposa created AS7-3565:
--------------------------------
Summary: Failed to get file from remote repository error
Key: AS7-3565
URL: https://issues.jboss.org/browse/AS7-3565
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.CR1b
Environment: Three RHEL5.4 machines: one configured as the DC and no servers; the second machine has one server; third machine has two servers. All servers are in the same Server Group.
Reporter: Rich Raposa
I am getting this error on a fairly regular basis - it only occurs when I reboot the host machines. The error message is below, and whenever it occurs that particular server does not start, nor can you start it later from the Admin Console. For some reason the host is not able to retrieve the deployed WAR file from the repository on the DC.
[Server:prod-server-B] 18:40:41,446 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([("deployment" => "cluster_test.war")]): java.lang.RuntimeException: JBAS015835: Failed to get file from remote repository
[Server:prod-server-B] at org.jboss.as.server.mgmt.domain.HostControllerServerClient$RemoteFileRepositoryExecutorImpl.getFile(HostControllerServerClient.java:248)
[Server:prod-server-B] at org.jboss.as.server.mgmt.domain.RemoteFileRepository.getFile(RemoteFileRepository.java:102)
[Server:prod-server-B] at org.jboss.as.server.mgmt.domain.RemoteFileRepository.getDeploymentFiles(RemoteFileRepository.java:73)
[Server:prod-server-B] at org.jboss.as.server.deployment.DeploymentAddHandler$DomainServerDeploymentAddHandler.addFromHash(DeploymentAddHandler.java:222)
[Server:prod-server-B] at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:154)
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.ParallelBootOperationStepHandler.execute(ParallelBootOperationStepHandler.java:161) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:165) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:192) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.server.ServerService.boot(ServerService.java:272)
[Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:187) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.server.ServerService.boot(ServerService.java:261)
[Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at java.lang.Thread.run(Thread.java:619) [:1.6.0_15]
[Server:prod-server-B] Caused by: java.util.concurrent.ExecutionException: Operation failed
[Server:prod-server-B] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Server:prod-server-B] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Server:prod-server-B] at org.jboss.as.server.mgmt.domain.HostControllerServerClient$RemoteFileRepositoryExecutorImpl.getFile(HostControllerServerClient.java:246)
[Server:prod-server-B] ... 18 more
[Server:prod-server-B] Caused by: java.io.IOException: JBAS010985: unrecognized type 36
[Server:prod-server-B] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:110) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:57) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:79) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Server:prod-server-B] at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:409) [jboss-remoting-3.2.0.CR9.jar:3.2.0.CR9]
[Server:prod-server-B] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_15]
[Server:prod-server-B] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_15]
[Server:prod-server-B] ... 1 more
[Server:prod-server-B]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3543) Remove EndpointRegistryDeploymentAspect
by Richard Opalka (JIRA)
Richard Opalka created AS7-3543:
-----------------------------------
Summary: Remove EndpointRegistryDeploymentAspect
Key: AS7-3543
URL: https://issues.jboss.org/browse/AS7-3543
Project: Application Server 7
Issue Type: Bug
Reporter: Richard Opalka
Assignee: Richard Opalka
Our EndpointRegistryDeploymentAspect relies on AS7 runtime services that are not available on server shut down.
The reason is runtime MSC services EndpointRegistryDeploymentAspect is depending on are stopped before aspect
stop() method is being called.
---
10:16:29,835 ERROR [org.jboss.as.server.deployment] JBAS015892: Deployment unit processor org.jboss.as.webservices.deployers.AspectDeploymentProcessor@90acb9b unexpectedly threw an exception during undeploy phase INSTALL of deployment "jaxws-samples-oneway.war": java.lang.IllegalStateException: Endpoint not registered: jboss.ws:context=jaxws-samples-oneway,endpoint=TestService
at org.jboss.ws.common.management.DefaultEndpointRegistry.unregister(DefaultEndpointRegistry.java:104)
at org.jboss.ws.common.deployment.EndpointRegistryDeploymentAspect.stop(EndpointRegistryDeploymentAspect.java:63)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.undeploy(AspectDeploymentProcessor.java:102)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3551) Rewrite EndpointRecordProcessorDeploymentAspect to don't use MBeanServer
by Richard Opalka (JIRA)
Richard Opalka created AS7-3551:
-----------------------------------
Summary: Rewrite EndpointRecordProcessorDeploymentAspect to don't use MBeanServer
Key: AS7-3551
URL: https://issues.jboss.org/browse/AS7-3551
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.0.CR1b, 7.1.0.CR1
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 7.1.0.Final
Our EndpointRecordProcessorDeploymentAspect relies on AS7 runtime services that are not available on server shut down.
The reason is runtime MSC services EndpointRecordProcessorDeploymentAspect is depending on are stopped before aspect
stop() method is being called.
---
11:49:53,571 ERROR [org.jboss.as.webservices.deployers.EndpointRecordProcessorDeploymentAspect] Cannot unregister record processor with JMX server: javax.management.InstanceNotFoundException: jboss.ws:context=jaxws-samples-oneway,endpoint=TestService,recordProcessor=MemoryBufferRecorder
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094) [:1.6.0_29]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415) [:1.6.0_29]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403) [:1.6.0_29]
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506) [:1.6.0_29]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.unregisterMBean(PluggableMBeanServerImpl.java:575)
at org.jboss.as.jmx.PluggableMBeanServerImpl.unregisterMBean(PluggableMBeanServerImpl.java:328)
at org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect.unregisterRecordProcessor(EndpointRecordProcessorDeploymentAspect.java:119) [jbossws-common.jar:2.0.1-SNAPSHOT]
at org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect.stop(EndpointRecordProcessorDeploymentAspect.java:90) [jbossws-common.jar:2.0.1-SNAPSHOT]
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.undeploy(AspectDeploymentProcessor.java:102) [jboss-as-webservices-server-integration-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-2493) Member names are not uniquely generated: Found member perf17/web in current view that duplicates us (perf17/web)
by Radoslav Husar (Created) (JIRA)
Member names are not uniquely generated: Found member perf17/web in current view that duplicates us (perf17/web)
----------------------------------------------------------------------------------------------------------------
Key: AS7-2493
URL: https://issues.jboss.org/browse/AS7-2493
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: No Release
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Blocker
Fix For: 7.1.0.Beta1
# If 2 servers are started on the same node
# and clustered application is deployed
# clustering fails with "Caused by: java.lang.IllegalStateException: JBAS010281: Found member perf17/web in current view that duplicates us (perf17/web). This node cannot join partition until duplicate member has been removed"
{code}
08:57:21,063 INFO [stdout] (MSC service thread 1-11)
08:57:21,063 INFO [stdout] (MSC service thread 1-11) -------------------------------------------------------------------
08:57:21,063 INFO [stdout] (MSC service thread 1-11) GMS: address=perf17/web, cluster=web, physical address=10.16.90.52:55200
08:57:21,063 INFO [stdout] (MSC service thread 1-11) -------------------------------------------------------------------
08:57:21,471 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-3) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
08:57:21,599 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000078: Starting JGroups Channel
08:57:21,604 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000094: Received new cluster view: [perf17/web|1] [perf17/web, perf17/web]
08:57:21,605 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000079: Cache local address is perf17/web, physical addresses are [10.16.90.52:55200]
08:57:21,609 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA2
08:57:21,609 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA2
08:57:21,719 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-3) ISPN000031: MBeans were successfully registered to the platform mbean server.
08:57:21,860 INFO [org.jboss.as.clustering] (MSC service thread 1-3) JBAS010301: Started repl cache from web container
08:57:21,900 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-3) JBAS010207: Number of cluster members: 2
08:57:21,902 WARN [org.jboss.as.web.deployment.JBossContextConfig] (MSC service thread 1-3) Clustering not supported, falling back to non-clustered session manager.: java.lang.IllegalStateException: JBAS010330: Unexpected exception while starting group communication service for web
at org.jboss.as.clustering.web.infinispan.DefaultLockManagerSource$LockManagerEntry.<init>(DefaultLockManagerSource.java:107)
at org.jboss.as.clustering.web.infinispan.DefaultLockManagerSource.getLockManager(DefaultLockManagerSource.java:74)
at org.jboss.as.clustering.web.infinispan.DistributedCacheManagerFactory.getDistributedCacheManager(DistributedCacheManagerFactory.java:95)
at org.jboss.as.web.session.DistributableSessionManager.<init>(DistributableSessionManager.java:176) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.session.DistributableSessionManager.<init>(DistributableSessionManager.java:144) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:280) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:164) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:157) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.IllegalStateException: JBAS010281: Found member perf17/web in current view that duplicates us (perf17/web). This node cannot join partition until duplicate member has been removed
at org.jboss.as.clustering.CoreGroupCommunicationService.verifyNodeIsUnique(CoreGroupCommunicationService.java:1197)
at org.jboss.as.clustering.CoreGroupCommunicationService.startService(CoreGroupCommunicationService.java:915)
at org.jboss.as.clustering.CoreGroupCommunicationService.start(CoreGroupCommunicationService.java:805)
at org.jboss.as.clustering.web.infinispan.DefaultLockManagerSource$LockManagerEntry.<init>(DefaultLockManagerSource.java:105)
... 17 more
08:57:21,982 INFO [org.jboss.web] (MSC service thread 1-3) registering web context: /clusterbench-web
08:57:22,032 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "clusterbench-ear-1.0.0-SNAPSHOT.ear"
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-2877) Removing a connector does not wait for wait for requests to finish
by Radoslav Husar (Created) (JIRA)
Removing a connector does not wait for wait for requests to finish
------------------------------------------------------------------
Key: AS7-2877
URL: https://issues.jboss.org/browse/AS7-2877
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.Beta1
Reporter: Radoslav Husar
Assignee: Remy Maucherat
When you remove a AJP connector current requests end up with NullPointerException.
If the quiesce requirement has been dropped for 7.1 then please reschedule to open to community.
{code}
[JBossINF] 09:47:47,140 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-16) Pausing Coyote AJP/1.3 on ajp-perf20-10.16.90.58-8009
[JBossINF] 09:47:47,140 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-16) Stopping Coyote AJP/1.3 on ajp-perf20-10.16.90.58-8009
[JBossINF] 09:47:47,144 ERROR [org.apache.catalina.connector.CoyoteAdapter] (ajp-perf20-10.16.90.58-8009-431) An exception or error occurred in the container during the request processing: java.lang.NullPointerException
[JBossINF] at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:524) [jbossweb-7.0.4.Final.jar:]
[JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) [jbossweb-7.0.4.Final.jar:]
[JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.4.Final.jar:]
[JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:445) [jbossweb-7.0.4.Final.jar:]
[JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.4.Final.jar:]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3282) HTTP Basic authentication fails due to changed JBossWebRealm defaults (AS6->AS7)
by Robert Reimann (JIRA)
Robert Reimann created AS7-3282:
-----------------------------------
Summary: HTTP Basic authentication fails due to changed JBossWebRealm defaults (AS6->AS7)
Key: AS7-3282
URL: https://issues.jboss.org/browse/AS7-3282
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Reporter: Robert Reimann
Assignee: Remy Maucherat
The change of the JBossWebRealm allRolesMode property from authOnly to strict leads to HTTP Basic authentication failures. Accessing HTTP Basic protected resources always returns a 403 forbidden response when using the security-constraint configuration below which worked well under (JBoss AS4 and AS6).
The security-constraint inside the web.xml is defined as follws:
{code}
<security-constraint>
<web-resource-collection>
<web-resource-name>protected resources</web-resource-name>
<url-pattern>/protected/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<description>any rolle allowed</description>
<role-name>*</role-name>
</auth-constraint>
</security-constraint>
{code}
Activating trace logging revealed the following message:
{code}
13:35:59,019 TRACE [org.jboss.as.web.security.JBossWebRealm] (http-localhost-127.0.0.1-8080-1) hasRole:RealmBase says:false::Authz framework says:true:final=false
{code}
In AS6 the meaning of <role-name>*</role-name> was determined by the allRolesMode property of the JBossWebRealm which was configured in jbossweb.sar/server.xml and set to authOnly (= Allow any authenticated user) by default.
In AS7 the default of allRolesMode seems to be strict (= Use the strict servlet spec interpretation which requires that the user have one of the web-app/security-role/role-name).
The workaround to add all security-rolles in the web.xml described in one of the forum references (https://community.jboss.org/message/617196#617196) is no viable option for applications with a large number of dynamically changing roles.
So please provide a configuration option for the allRolesMode property to allow for changes of the default behavior and ease the migration from earlier JBoss AS versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months