.
awarnier wrote:
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
What I mean by internally is the application works on the intranet within our
corporate domain. I'm trying to get the application to work externally
outside the corporate firewall.
awarnier wrote:
amythyst wrote:
I'm fairly certain the tomcat server is up and running because
and one of them is conf and that is where my server.xml file is and some
other files. So, I'm not sure how I would test what you were suggesting.
awarnier wrote:
amythyst wrote:
Sorry for all the posts... I have a specific question... I'm reading the
isapi_redirector.log which shows the errors
working. I have tried every avenue to fix this and you guys are kinda
my last hope. :) I have been trying to fix this for over a month and I
can't figure it out.
awarnier wrote:
amythyst wrote:
Yes, I'm still getting those error messages in the isapi_connector log.
I don't think
Woo I fixed it! I changed the listener port from 8009 to 8010! And
now it works! Thank you guys so much for the assistance and the guidance.
:)
awarnier wrote:
amythyst wrote:
Yes, I'm still getting those error messages in the isapi_connector log.
I don't think the application
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.
I changed the port in the worker.properties and the server.xml
Michael Ludwig-6 wrote:
amythyst schrieb am 03.01.2011 um 07:36 (-0800):
Woo I
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 schrieb am
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?
And changing the port to 8010 seems
the one.
Michael Ludwig-6 wrote:
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
(the important part being that :8009 part)
Do you see that ?
amythyst wrote:
Thanks for the reply.
With that script, how exactly would I execute that script?
Pardon my ignorance, but I am a database developer that has been thrown
into
networking because our network admin
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.
Michael Ludwig-6 wrote:
But the ISAPI redirector doesn't get a reply
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 127.0.0.1:8009
=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 Bad Gateway error and the ISAPI logs say this:
[Thu Dec
Hi, I am trying to get an application called JIRA to work externally on our
corporate domain. We believe we have everything set up properly and have
followed numoerous online instructions. The default website in IIS (version
6) is up and the ISAPI filter is loaded with the green light.
14 matches
Mail list logo
