Actually the permission was changed by myself only.
Since we didnt get clues,finally we gave full permission for the lib
directory.
And I guess,is the ulimit in solaris playing any role here?
As I saw in the internet,it may affect the overall file descriptors since we
have lot of jars.
I really
thanks for replay..
but already did taht steps... and i think u didtn read my message...
Dear I am getting warnig messge after hiting the url in the browser
so i think i am missing some setting...
Thanks again...
On Wed, Oct 28, 2009 at 5:51 PM, Nilesh Patil wrote:
> Dear forum ,
>I
Hi,
It's working great with roleSearch="(member={0})", but not with
roleSearch="(member={1})"
>From tomcat doc :
Use {0} to substitute the distinguished name (DN) of the user, and/or {1} to
substitute the username.
I guess line :
filter = roleFormat.format(new String[] { groupDN });
should be
"Christopher Schultz" wrote in message
news:4ae758a0.5050...@christopherschultz.net...
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bill,
>
> On 10/26/2009 9:44 PM, Bill Barker wrote:
>> "Christopher Schultz" wrote in message
>>> On the other hand, shouldn't the JSP compiler pass-throu
Hi,
>From what I can remember, which has been a long time ago, requests are
being handled by servlets after the shutdown process has started and
the pool was closed. I would imagine that this is a violation of the
spec as well, but I am not sure. You would imagine that JNDI resources
should be avai
[Alan]
>>> I need to find out what is the difference between running Tomcat 6 as
>>> a Windows Service and running it from the command line.
>>>
>>> The reason is that I'm getting a bizarre bug when a jython based
>>> servlet is run under Tomcat6-as-Service. But the bug does NOT appear
>>> when Tom
I actually have worked on C but didn't read the line about bit mask. Sorry.
On Wed, Oct 28, 2009 at 12:44 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mohit,
>
> On 10/28/2009 2:29 PM, Mohit Anchlia wrote:
>> Regarding recovery_options: Is there a default v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nilesh,
On 10/28/2009 8:21 AM, Nilesh Patil wrote:
> Please guide me...
http://lmgtfy.com/?q=thawte+trial+certificate+installation+instructions
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohit,
On 10/28/2009 2:29 PM, Mohit Anchlia wrote:
> Regarding recovery_options: Is there a default value it's set to? On
> the link http://tomcat.apache.org/connectors-doc/reference/workers.html
> it doesn't have option "7"
That's because 7 isn't a
Thanks. I couldn't find what option retry_options 7 in
http://tomcat.apache.org/connectors-doc/reference/workers.html is for.
On Wed, Oct 28, 2009 at 11:37 AM, Rainer Jung wrote:
> On 28.10.2009 19:29, Mohit Anchlia wrote:
>> Thanks a lot!
>>
>> Would this work with 1.2.27?
>
> Remove the escalat
On 28.10.2009 19:29, Mohit Anchlia wrote:
> Thanks a lot!
>
> Would this work with 1.2.27?
Remove the escalation parameter, I guess that's the only 1.2.28 special
param.
> Regarding recovery_options: Is there a default value it's set to? On
> the link http://tomcat.apache.org/connectors-doc/refe
Thanks a lot!
Would this work with 1.2.27?
Regarding recovery_options: Is there a default value it's set to? On
the link http://tomcat.apache.org/connectors-doc/reference/workers.html
it doesn't have option "7"
Regarding ping_mode:
What happens when Cping returns error for ping_mode "C"? Does it
Thanks for letting us know!
On 28.10.2009 16:23, Bocalinda wrote:
> Hi again Rainer,
>
> It seems some of our software updates must have solved the issue, as it's
> been working perfectly now for several weeks.
> I think we may conclude that it didn't had to do with the the clustering
> implement
On 28.10.2009 17:29, Mohit Anchlia wrote:
> Based on what I have seen is that we often get HTTP code 502 and by
> increasing socket timeout those errors disappear. I am not sure why
> that happens.
>
> Based on the feedback I got it looks like the below properties file is
> ok except the socket ti
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 10/28/2009 11:55 AM, Joe Wallace wrote:
From Firefox Live HTTP Headers
Set-Cookie: JSESSIONID=B4F06784FE4EAA0A7C9830BBF86D85B4; Path=/inetwork; Secure
Location: https://216.94.100.154/inetwork/Start.jsp
H.
Mohit Anchlia wrote:
Based on the feedback I got it looks like the below properties file is
ok except the socket timeout piece and I should probably remove that?
Do I not recall Rainer already telling you that ?
-
To unsubscr
OK. Thanks to all.
Joe
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Wednesday, October 28, 2009 12:40 PM
To: Tomcat Users List
Cc: p...@pidster.com
Subject: Re: SessionID cookie not secure over SSL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elli,
On 10/28/2009 12:21 AM, Elli Albek wrote:
> In terms of listeners, I saw that Tomcat executes requests while in
> the closing process.
That's a problem. What kind of listener are you using?
>> My understanding was that:
>>
>> 1. Tomcat does no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 10/28/2009 11:55 AM, Joe Wallace wrote:
> From Firefox Live HTTP Headers
>
> Set-Cookie: JSESSIONID=B4F06784FE4EAA0A7C9830BBF86D85B4; Path=/inetwork;
> Secure
> Location: https://216.94.100.154/inetwork/Start.jsp
>
> H. That looks like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 10/27/2009 5:34 PM, Joe Wallace wrote:
> Hi Chris,
> You wrote:
>> Tomcat will create its JSESSIONID cookie like this in all cases:
>
>> Cookie cookie = new Cookie("JSESSIONID", sessionId);
>> if(request.isSecure())
>> cookie.setSecure(true)
Based on what I have seen is that we often get HTTP code 502 and by
increasing socket timeout those errors disappear. I am not sure why
that happens.
Based on the feedback I got it looks like the below properties file is
ok except the socket timeout piece and I should probably remove that?
Here i
Hi again Rainer,
It seems some of our software updates must have solved the issue, as it's
been working perfectly now for several weeks.
I think we may conclude that it didn't had to do with the the clustering
implementation.
I feel sorry that you put time into patching the issue. In case the prob
From Firefox Live HTTP Headers
Set-Cookie: JSESSIONID=B4F06784FE4EAA0A7C9830BBF86D85B4; Path=/inetwork; Secure
Location: https://216.94.100.154/inetwork/Start.jsp
H. That looks like it is secure
My filter is getting this.
Cookie0 name= JSESSIONID
Cookie0 value= B4F06784FE4EAA0A7C9830BBF8
Pid wrote:
On 27/10/2009 22:31, Joe Wallace wrote:
André Warnier wrote:
Am I mistaken then to think that since the connection B from IIS to
Tomcat is not over HTTPS but over AJP, Tomcat has no idea that HTTPS is
being used ?
Whatever consequences this has in the context (and which are beyond m
Hi Mark,
Thanks for the quick response. I think for me the intention that there
is always a ROOT webapp wasn't clear to me. I'll ensure we have one in
future.
Simon
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: 28 October 2009 14:08
To: Tomcat Users List
Subject:
Simon MaticLangford wrote:
> 2 questions come from this:
>
> - From a user perspective, I would expect to get a 404 Not Found. Is
> there a reason we get the bad request instead?
Yes. You removed the ROOT web application. You need a ROOT webapp to
handle requests that don't map to any o
On 27/10/2009 22:31, Joe Wallace wrote:
André Warnier wrote:
Am I mistaken then to think that since the connection B from IIS to
Tomcat is not over HTTPS but over AJP, Tomcat has no idea that HTTPS is
being used ?
Whatever consequences this has in the context (and which are beyond my
expertise)
Hi there,
I had a recent problem caused by a client sending a request to the wrong url
that took days to find because the requests never appeared in the access logs.
I have now cleared away all the clutter of my application and managed to
reproduce against a virgin Tomcat 6.0.20 using the fo
Dear forum ,
I am working on SLL Implemetaion. we are using jboss app server. I am
using thawte's trail certificate for test purpose.
The application is running well but when i hit the URL with https the
browser warns me regarding Untrusted web page. when i click on certificate
Install , in cer
Hello,
I tried to configure isapi_redirect.dll for IIS7 - tomcat 6.0 in 32-bit
emulation mode. That did not work.
I installed 64-bit java, 64-bit tomcat 6.0, isapi_redirect.dll for amd64
(machine has Intel Core 2),disable 32-bit applications in IIS7 application pool.
I used registry settings for
30 matches
Mail list logo
