When i include
It does not work in tomcat 8.0.15.
and my included jsp file contents are something like :
...
What could be the problem?
> *sigh*
>
> If you only want to proxy for one VirtualHost, then only set up
> JkMounts in that one VirtualHost.
>
> Like this:
>
>
>ServerName share2..xxx
>
>JkMount /* worker1 (or "balancer", whichever you want)
>
Maybe I wasn't clear in my other reply, the above jkmount /* wo
We use an Ant script to configure Tomcat during installation, so I ended
up just using a task to set the address used to
InetAddress.getLoopbackAddress().getHostAddress() by default.
On 1/23/2015 3:05 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1
On 23/01/2015 21:16, Christopher Schultz wrote:
> David,
>
> On 1/23/15 8:26 AM, David kerber wrote:
>> On 1/23/2015 5:04 AM, André Warnier wrote:
>>> A part of what I wanted to say in my original answer, is that
>>> just by taking the time to actually think about the problem you
>>> are having, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason,
On 1/23/15 3:27 AM, Jason Y wrote:
> Thank you Chris for your reply.
>
> I think I was mislead by this error. My services--both REST and
> SOAP--are hosted by tomcat and used by downstream users with HTTPS.
> They are running well for long t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 1/23/15 8:26 AM, David kerber wrote:
> On 1/23/2015 5:04 AM, André Warnier wrote:
>> A part of what I wanted to say in my original answer, is that
>> just by taking the time to actually think about the problem you
>> are having, and writin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/23/15 5:04 AM, André Warnier wrote:
> It was actually a good question, and a good explanation of your
> problem. Bonus points for that. That you found the solution
> yourself afterward, and communicated this to the list, are two
> additi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/23/15 10:40 AM, Chris Arnold wrote:
>> What you want is:
>
>> JkMount /share2/* worker1
>
>> or maybe:
>
>> JkMount /share2/* balancer
>
>> workers.properties defines the workers (target host/port,
>> connection options, etc.) and th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/23/15 3:35 PM, André Warnier wrote:
> Jess Holle wrote:
>> It seems that
>> java.net.InetAddress.getLoopbackAddress().getHostAddress() should
>> give the right answer -- if one is running with Java 7.
>>
>> That said, is there a value
Jess Holle wrote:
It seems that java.net.InetAddress.getLoopbackAddress().getHostAddress()
should give the right answer -- if one is running with Java 7.
That said, is there a value that can be used for AJP's "address"
attribute that simply does the right thing here?
On 1/23/2015 1:38 PM, Je
It seems that java.net.InetAddress.getLoopbackAddress().getHostAddress()
should give the right answer -- if one is running with Java 7.
That said, is there a value that can be used for AJP's "address"
attribute that simply does the right thing here?
On 1/23/2015 1:38 PM, Jess Holle wrote:
I'd
I'd like to set the "address" attribute on the AJP connector when
deploying Tomcat to only allow loopback connections.
But I want to do so in a general way that works for:
* IPv4
* IPv4 + IPv6 mixed/dual stack
* IPv6 (pure)
Is there any such option? The documentation speaks of setting
127
>What you want is:
>JkMount /share2/* worker1
>or maybe:
>JkMount /share2/* balancer
>workers.properties defines the workers (target host/port, connection
>options, etc.) and the JkMount directives in httpd.conf map URL
>patterns to those workers.
So JkMount /* proxied everything and we only
>What you want is:
>JkMount /share2/* worker1
>or maybe:
>JkMount /share2/* balancer
>workers.properties defines the workers (target host/port, connection
>options, etc.) and the JkMount directives in httpd.conf map URL
>patterns to those workers.
So JkMount /* proxied everything and we only
On 1/23/2015 5:04 AM, André Warnier wrote:
A part of what I wanted to say in my original answer, is that just by
taking the time to actually think about the problem you are having, and
writing down a clear explanation for someone else, you often find the
solution yourself.
Add in the exercise o
On 22/01/2015 11:48, Mark Thomas wrote:
> On 21/01/2015 22:40, Shaun Morton wrote:
>> We will be creating a .jsp and putting it in a .war for you. Should be
>> tomorrow.
>
> The issue is confirmed. We are working on the fix and a new 8.0.x
> release now.
The 8.0.18 release candidate has been ma
Hi Prabhu Mannu.
Answer below.
Prabhu Mannu wrote:
Hi all/ Dear André Warnier,
I understand that I cannot ask questions or help without actually telling
what I did so resolve the issue in the first place.
Initially I followed this
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
I wanted t
Hi all/ Dear André Warnier,
I understand that I cannot ask questions or help without actually telling
what I did so resolve the issue in the first place.
Initially I followed this
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
I wanted to get the minimal setting which would help, some of th
Thank you Chris for your reply.
I think I was mislead by this error. My services--both REST and SOAP--are
hosted by tomcat and used by downstream users with HTTPS. They are running
well for long time until some day one of downstream developers reported
that the WSDL URL cannot be accessible by his
Prabhu Mannu wrote:
Hi all,
Found the issue it's the jsp page itself that was encoded in iso-8859-1
format.
Sighs .. I became such a noob.
Sorry all for the trouble.
With regards
Prabhu
No problem.
That is one reason why this Tomcat Users list is great and unique on the www : just the
f
20 matches
Mail list logo
