Deal ! The agreement has been signed :-)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261334#4261334
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261334
___
jboss-user mai
Yes, I can do it without problems, I just need directions on how submit it.
It would also be good to have someone with more knowledge about the Token
structure having a look at the code, as the fix I did was mostly based on
observations.
I tested the fix on two different environments and worked
I think I've found an issue with JBoss Negotiation 2.0.3.GA on the
"org.jboss.security.negotiation.spnego.encoding.NegTokenTargDecoder" class when
using Windows Vista/IE as the Client to authenticate against AD.
I have an AD configured and working.
XP clients can successfully authenticate again
Thanks very much Darran,
I just needed to be sure !
I had to replace log.trace for log.debug, than I ran without problems on 4.0.5.
But it was version Beta... I didn't try with the new version and I saw that
the new one has much more classes !!!
The ideal would be to have an updated version
Hi guys,
good work
What's the compatibility with JBoss 4.0.5 ?
I'm testing the Beta1 release under JBoss 4.0.5 and saw a problem because the
jboss log4j-boot.jar is incompatible with Logger.trace() that is being used in
the negotiation code...
Tried finding something related to it in the
Excelent ! It now worked as I expected !
I hadn't noticed this option there !!!
Thanks very much for the help !
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160550#4160550
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=rep
That's it !
It's possible to see it, because the 2 html results are concatenated..
The results from the pushlet that was on server1.. are still at the beginning
of the HTML, then there are the contents from the pushlet that is on server2.
It's as if the loadbalancer(mod_jk) x browser connectio
Hi..
Do you have any information of any problems to reset the JSESSIONID cookie,
when there´s a pushlet running ?
The thing is I have a pushlet running, when server1 goes down and server2
assumes, the pushlet is the 1st request answered by server2, and this is the
request that resets the Ses
It must be some issue with the session cookie !
I was tracing JK log... and saw that even setting the new route on the cookie,
JK still identifies the last rout on the requests...
I'll keep testing.. I won't post the log here as it's too big...
anyway.. thanks for the help !!!
View the origin
First of all, thanks a lot for your help !
I tested it again, with the trace.. but I wasn't able to find out anything.
One thing that I noticed is that, this behaviour is not always the same...
sometimes the session keeps with server2.
Another thing I noticed on the log is a
org.jboss.cache.in
We don´t have URLRewriting..
But yes we have a session cookie... JSESSIONID=**.tomcatX
Do you think this could be some issue with apache/mod_jk
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159654#4159654
Reply to the post :
http://www.jboss.
Hi, I´ve some doubts about how the server should behave in case of a failover,
and also check if thereôs any configuration to change this behaviour.
My environment:
2 jboss 4.0.5 servers, (jvmRoute="tomcat1" and jvmRoute="tomcat2", useJK=true)
1 apache 2.2.8 + mod_jk 1.2.26 for load balancin
12 matches
Mail list logo
