On 24/08/17 11:43, Petr Nemecek wrote:
> Hi,
>
> this error occurs even if I bypass IIS i.e. go directly to Tomcat.
>
> My request are SOAP requests, I get thet bad gateway error on the client
> side, then when the processing of the request finishes I could see following
Hi,
this error occurs even if I bypass IIS i.e. go directly to Tomcat.
My request are SOAP requests, I get thet bad gateway error on the client side,
then when the processing of the request finishes I could see following error in
Tomcat/stderr
On 24/08/17 08:39, Petr Nemecek wrote:
> Hello,
>
> I have a Tomcat behind IIS, and I get the 502: Bad Gateway error for long
> running requests.
>
> After some experiments I've found out, that if I use connector 8082 (see
> below), I have this problem, but when I
Hello,
I have a Tomcat behind IIS, and I get the 502: Bad Gateway error for long
running requests.
After some experiments I've found out, that if I use connector 8082 (see
below), I have this problem, but when I switch to 8084 (see below), the problem
disappears. The only difference is
t;> Mark
>
> Thank you Mark.
>
> That was it.
Happy to help.
> I added SSLEnabled="true" to the Tomcat connector, restarted Tomcat and
> the Bad Gateway error disappeared.
> Don't know why the production system works without that setting, unless
> it is
>You appear to be missing SSLEnabled="true" on your Tomcat connector.
>
>The start-up log messages for that connector will confirm whether that
>analysis is correct.
>
>Mark
Thank you Mark.
That was it.
I added SSLEnabled="true" to the Tomcat connector
On 09/10/2013 04:43, Salisbury, Richard W DLA CTR TRANSACTION SERVICES
> We confirmed that Tomcat on server-B is configured to handle port 53309,
> from this excerpt from its server.xml:
> maxThreads="150"
> minSpareThreads="25" maxSpareThreads="75" enableLookups="false"
> disableUploadTimeout=
We are getting a "Bad Gateway" error when attempting to go to a web app
in our test environment. As far as we know it has never worked in our
test environment, but it is working in our production environment. I
know this appears backwards, but we inherited this system as is. I hope
th
s when Tomcat started.
> (It should not have been able to start that Connector, if the port was not
> free).
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: us
amythyst wrote:
Yea I don't know... I'm not the network person so I don't have access to see
what is in the firewall. He told me everything was set up properly in the
firewall and when I changed the port to 8010, we made no changes in the
firewall whatsoever.
Michael Ludwig-6 wrote:
amythyst
Hmm... maybe. :) I was calling it that because that is the port tomcat is
"listening" on to forward the requests right?
n828cl wrote:
>
>> From: amythyst [mailto:roxanne.ga...@deltasolutions.com]
>> Subject: Re: isapi_redirector.dll Problems - Bad Gateway?
>
>
> From: amythyst [mailto:roxanne.ga...@deltasolutions.com]
> Subject: Re: isapi_redirector.dll Problems - Bad Gateway?
> And changing the port to 8010 seems to
> have resolved it.
> I changed the port in the worker.properties and the server.xml
You earlier stated that you change
firewall configuration?
>
> --
> Michael Ludwig
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/isapi_redi
amythyst schrieb am 03.01.2011 um 09:15 (-0800):
>
> Yup you are correct. It was 8009. And changing the port to 8010
> seems to have resolved it. But I'm not sure why this has fixed it.
Unfavourable firewall configuration?
--
Michael Ludwig
--
: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/isapi_redirector.dll-Problems---Bad-Gateway--tp30500400p30579733.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To
amythyst schrieb am 03.01.2011 um 07:36 (-0800):
>
> Woo I fixed it! I changed the listener port from 8009 to
> 8010! And now it works!
Congrats.
The worker.properties you posted last year, however, read as follows:
| worker.worker1.type=ajp13
| worker.worker1.host=localhost
| worker
amythyst wrote:
They do not offer any support with getting their application to work
externally. They provide an online walkthrough document which is here:
http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+IIS
And that is how I and the network guy set it up however, as yo
..@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/isapi_redirector.dll-Problems---Bad-Gateway--tp30500400p30578925.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
l: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/isapi_redirector.dll-Problems---Bad-Gateway--tp30500400p30578822.html
Sent from the Tomcat - User mailing list archive a
amythyst wrote:
Yes, I'm still getting those error messages in the isapi_connector log.
I don't think the application installs a standard tomcat installation.
Basically, I have a directory in the program files folder called "Atlassian"
then under that I have JIRA 4.2. In that directory I have
) http://yourhostname:80/test/test.html
> (where 80) is the port on which IIS is listening)
>
> Do both work and show the page "test.html" ?
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apach
t somehow).
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http
amythyst wrote:
I'm fairly certain the tomcat server is up and running because the
application works internally. If tomcat wasn't working then I assume I
wouldn't be able to access the app internally as it requires tomcat to
function.
Define what you mean by "internally", as opposed to the oth
amythyst wrote:
Sorry for all the posts... I have a specific question... I'm reading the
isapi_redirector.log which shows the errors... it says things like this:
shutting down the read side of socket 576 [127.0.0.1:1145 ->
127.0.0.1:8009]
To me, it seems like its trying to connect to tomcat on
0.1:8009 but
tomcat is listening on 0.0.0.0:8009 ... does that make a difference?
--
View this message in context:
http://old.nabble.com/isapi_redirector.dll-Problems---Bad-Gateway--tp30500400p30546699.html
Sent from the Tomcat - User mailing list archive at Na
-
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/isapi_redirector.dll-P
the AJP connection between IIS and Tomcat.
>>>
>>>> Below are my worker files for the connector:
>>>>
>>>> # uriworkermap.properties - IIS
>>>> /jira/*=worker1
>>> Okay.
>>>
>>>> # workers.properties.minimal -
>>>> worker.list=worke
When you ask how many threads I have configured you're talking about
worker threads right? I only have the one.
There are threads on both sides. If you haven't configured anything for
your AJP connector the default applies, which is 200.
http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.htm
amythyst schrieb am 28.12.2010 um 07:12 (-0800):
>
> With that script, how exactly would I execute that script?
Save it to a file called, say, "ajp.pl", and then:
perl ajp.pl
Windows doesn't come with Perl out of the box, so if you don't
use Perl yet maybe it's not worth while downloading it.
oh oh. So it looks like you have been thrown to the wolves, he ?
The positive side of it, is that if you solve it, you'll be the star.
Time for some ascii-art I think.
Except for firewalls, you have the following schema :
Browser-1 <---> <---> - webapp
Browser-2 <--->
rkers.html
>
> How many threads have you configured for your AJP connector?
>
> --
> Michael Ludwig
>
> ---------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional c
amythyst schrieb am 27.12.2010 um 06:52 (-0800):
>
> Hi, yes we have a connector configured for port 8009.
Configured, okay; but it is not replying to your redirector's requests.
You can test AJP connectivity using this Perl script:
http://www.perlmonks.org/?node_id=766945
> Question about the
=8009
Michael Ludwig-6 wrote:
>
> amythyst schrieb am 20.12.2010 um 10:17 (-0800):
>>
>> The default website in IIS (version 6) is up and the ISAPI filter is
>> "loaded" with the green light. However, when we go to the website
>> we're getting a &q
amythyst schrieb am 20.12.2010 um 10:17 (-0800):
>
> The default website in IIS (version 6) is up and the ISAPI filter is
> "loaded" with the green light. However, when we go to the website
> we're getting a "Bad Gateway" error and the ISAPI logs say this
reen light. However,
when we go to the website we're getting a "Bad Gateway" error and the ISAPI
logs say this:
[Thu Dec 16 11:20:10.559 2010] [1508:1800] [error]
ajp_get_reply::jk_ajp_common.c (2058): (worker1) Tomcat is down or refused
connection. No response has been sent to the client
HttpServlet.service(HttpServlet.java:802)
Thanks,
Trent
--
View this message in context:
http://www.nabble.com/Bad-gateway-502-error-trying-to-reach-external-URL-through-proxy-t1402806.html#a3775342
Sent from the Tomcat - User forum at Nabble.com.
36 matches
Mail list logo
