[JBoss JIRA] Created: (JBAS-3495) Windows service for JBossAS
by Luc Texier (JIRA)
Windows service for JBossAS
---------------------------
Key: JBAS-3495
URL: http://jira.jboss.com/jira/browse/JBAS-3495
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Environment: Win32
Reporter: Luc Texier
Fix For: JBossAS-5.0.0.Beta
Windows users have a hard time deploying JBossAS as a Windows service. Most of them try to use JavaService from ObjectWeb which is too generic to support properly an application server instance. For exemple, generating thread dumps is impossible. Also the experience has shown that this tool is fairly broken causing hang-ups.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBAS-3864) HttpSession replication does not always retry if replication fails
by Brian Stansberry (JIRA)
HttpSession replication does not always retry if replication fails
------------------------------------------------------------------
Key: JBAS-3864
URL: http://jira.jboss.com/jira/browse/JBAS-3864
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.0.CR1
If replication of a session fails, the session replication layer does not retry. This leaves the local session map in JBossCacheManager out of sync with the distributed cache. If there is a failover while the distributed cache is out of sync, the user will see stale data.
Need to retry a (configurable) X number of times. If the session still doesn't replicate, need to decide what to do -- i.e. is it too late in the request cycle to throw an exception and return an error to the client?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBAS-3624) <security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans
by David Green (JIRA)
<security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans
-------------------------------------------------------------------------------------------------------------------------
Key: JBAS-3624
URL: http://jira.jboss.com/jira/browse/JBAS-3624
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.0.4.GA
Reporter: David Green
Assigned To: Bill Burke
Specifying a <security-domain> in the jboss-app.xml incorrectly sets the @SecurityDomain on EJB3 session beans.
In the jboss-app.xml the security domain is specified as follows:
<jboss-app>
<security-domain>java:/jaas/hch</security-domain>
</jboss-app>
In Ejb3DescriptorHandler the security-domain is copied directly into the SecurityDomainImpl instance as "java:/jaas/hch", however the @SecurityDomain annotation should be populated with the value "hch" (without the leading "java:/jaas/" prefix). This causes the EJB3 session bean authentication to behave unexpectedly, since the authentication for the bean reverts to the default domain instead of the specified one.
The only way I've found to workaround this issue is to specify the @SecurityDomain individually on every session bean in the project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months