[JBoss JIRA] (AS7-5996) Servlet deployment view
by Harald Pehl (JIRA)
Harald Pehl created AS7-5996:
--------------------------------
Summary: Servlet deployment view
Key: AS7-5996
URL: https://issues.jboss.org/browse/AS7-5996
Project: Application Server 7
Issue Type: Sub-task
Components: Console
Reporter: Harald Pehl
Assignee: Harald Pehl
Fix For: 7.2.0.CR1
Context view for the servlet subsystem of a deployment. Show the following information:
--
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, 1 month
[JBoss JIRA] (AS7-5991) It’s impossible to set a custom pattern for the handler’s formatter via CLI or native configuration API
by Radoslav Rangelov (JIRA)
Radoslav Rangelov created AS7-5991:
--------------------------------------
Summary: It’s impossible to set a custom pattern for the handler’s formatter via CLI or native configuration API
Key: AS7-5991
URL: https://issues.jboss.org/browse/AS7-5991
Project: Application Server 7
Issue Type: Bug
Components: CLI, Logging
Affects Versions: 7.1.2.Final (EAP)
Reporter: Radoslav Rangelov
Assignee: Alexey Loubyansky
Fix For: 7.1.1.Final
It’s impossible to set a custom pattern string for the handler’s formatter via CLI or native configuration API. The default value for the pattern is always used - not the specified one.
The manual configuration of domain.xml file works fine during startup:
<formatter>
<pattern-formatter pattern="custom pattern string"/>
</formatter>
--
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, 1 month
[JBoss JIRA] (AS7-5728) ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout
by Stian Thorgersen (JIRA)
Stian Thorgersen created AS7-5728:
-------------------------------------
Summary: ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout
Key: AS7-5728
URL: https://issues.jboss.org/browse/AS7-5728
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.3.Final (EAP)
Reporter: Stian Thorgersen
Logging out a user with Request.logout doesn't work with clustered SSO. This is caused by ClusteredSingleSignOn.deregister(String) not remove the ssoId from the SSO cluster. The ClusteredSingleSignOn.sessionEvent removes it from both the local cache and the SSO cluster, so a workaround is to call Session.invalidate() prior to calling Request.logout().
--
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, 1 month
[JBoss JIRA] (AS7-5980) HTTP connector has missing configuration
by Paul Hinds (JIRA)
Paul Hinds created AS7-5980:
-------------------------------
Summary: HTTP connector has missing configuration
Key: AS7-5980
URL: https://issues.jboss.org/browse/AS7-5980
Project: Application Server 7
Issue Type: Feature Request
Components: Web
Affects Versions: 7.1.2.Final (EAP)
Reporter: Paul Hinds
Assignee: Remy Maucherat
We have an application that is using the JBoss HTTP connector without Apache in front. Because keep-alive timeout is not configurable we have to accept defaults which means for a request that takes 10ms to complete we seem to dedicate a thread for 15 seconds. It is impossible to balance performance with concurrency without this option.
Other options are missing from JBossAs7 that are required for performance.
max keep alive requests
tcp no delay
max http header size
connection timeout
compression
These should be configurable in the connector XML having some parameters available via system properties is inconvenient.
max header size and keep alive timeout are the showstoppers for our use of JBoss.
--
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, 1 month
[JBoss JIRA] (AS7-5986) Add possibility to control settings of cache of stateful beans in EJB3 subsystem
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-5986:
-------------------------------------
Summary: Add possibility to control settings of cache of stateful beans in EJB3 subsystem
Key: AS7-5986
URL: https://issues.jboss.org/browse/AS7-5986
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.1.3.Final (EAP)
Reporter: Ondřej Chaloupka
Assignee: Heiko Braun
Priority: Minor
As it was mentioned in comments on JBPAPP6-1450 I'm creating upstream jira for this feature.
It would be fine to have possibility to control settings of cache for stateful beans in EJB3 susbsystem.
Currently there is possible to set up pool for stateless beans but there are no settings possibilities for SFSB.
What I'm missing is the possibility how to define default cache for the stateful beans and how to create and manage things which cover tag <caches> from ejb3 subsystem.
I mean that you can define cache-ref for SFSB and you can set up cache properties in EJB subsystem (eg. <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>) in standalone.xml or via cli (jboss-cli.sh) but this possibility is not accessible in web admin console.
--
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, 1 month