On Sun, Jun 6, 2010 at 6:40 AM, Rainer Jung wrote:
> On 06.06.2010 03:52, Mohit Anchlia wrote:
>>
>> On Sat, Jun 5, 2010 at 2:02 AM, Rainer Jung
>> wrote:
>>>
>>> On 04.06.2010 01:30, Mohit Anchlia wrote:
In our present environment we have a WS and APP server. When request
comes in
HI
for right knowledge
I am able, now, to reproduce the socket error that occur.
In my lan i have a proxy server (192.168.0.254) so on server win2003 on
which i have tomcat5.5.28 (IP: 192..168.0.100) if i don't use in IE proxy
configuration all it's ok but if i configure proxy server and po
Fully understood -- and very clearly explained.
Again, thanks Chuck.
Cheers,
Frank
On Sun, Jun 6, 2010 at 3:25 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Frank Burns [mailto:francisbu...@gmail.com]
> > Subject: Re: Web app using JDBCRealm runs on Tomcat 5.5.20 but
> From: Frank Burns [mailto:francisbu...@gmail.com]
> Subject: Re: Web app using JDBCRealm runs on Tomcat 5.5.20 but will not
> run on Tomcat 6.0.26 ...
>
> didn't realise that specifying the context in the server.xml
> was poor practice and that if you did so then you had to be
> careful.
>
> Ca
On 06.06.2010 03:52, Mohit Anchlia wrote:
On Sat, Jun 5, 2010 at 2:02 AM, Rainer Jung wrote:
On 04.06.2010 01:30, Mohit Anchlia wrote:
In our present environment we have a WS and APP server. When request
comes in, WS sends it to APP server using mod_jk and then APP server
inserts it into JMS
