There was a form-based authentication bug in Tomcat 6.0.10 code that was corrected in version 6.0.14. In particular, a FireFox user would be displayed the login form again instead of the correct requested resource AFTER authentication was successful. This was reported as Tomcat Bug 43687 (https://issues.apache.org/bugzilla/show_bug.cgi?id=43687).
As I understand it, my implementation of JBoss (4.2.2.GA) uses JBoss Web 2 which is almost identical to the Tomcat 6.0.10 code and duplicates the Tomcat bug discussed above. How do I upgrade the JBoss Web 2 implementation to include the Tomcat 6.0.14 fix I need?
Thanks,
Kerry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174356#4174356
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174356
I have one executor being created at PagingManagerFactoryNIO. That executor is shared with all the PagingStores (i.e. all the addresses):
Before change:
| public PagingManagerFactoryNIO(final String directory)
| {
| this.directory = directory;
| this.executor = Executors.newSingleThreadExecutor();
| }
|
>From what I've seen in other places all I would need to do is change how I initialize the executor? Or I am missing something here?
After change:
public PagingManagerFactoryNIO(final String directory)
{
this.directory = directory;
this.executor = Executors.newCachedThreadPool(new JBMThreadFactory("JBM-depaging-threads"));
}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174338#4174338
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174338
"timfox" wrote : Also:
|
|
| | from QueueImpl
| | public QueueSettings getSettings()
| | {
| | return this.settings;
| | }
| |
|
| This should be unnecessary since the queue settings is only used in the code to get the max-size-bytes which should have been removed (we discussed this).
Yeah... that will go away.
It is still there because places like SessionQueueQueryResponse and Management are still referring to max-size.
I will remove the setting as soon as those uses to MaxSize is removed.
SessionQueueQueryResponse is probably being changed by Andy on his Branch and I wanted to avoid too many changes there ATM on this single huge commit.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174279#4174279
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174279