|
Home > Archive > Apache Server configuration support > February 2004 > Apache Tomcat setup - GET not working
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Apache Tomcat setup - GET not working
|
|
|
| Hi,
I am running servlets through port 8090 on a Tomcat server and all is
working fine, our jsps display and function correctly, accessing the
database on their way.
Through port 8091 we are pointing at the same code but using apache (for
security/logging on purposes) and it works until a page tries to use GET
parameters (rather than POST).
Just get the bog standard :
The page cannot be displayed
The page you are looking for is currently unavailable.
By stripping the GET parameters out of the URL the page displays.
In the error log we get :
[notice] child pid 15944 exit signal Bus Error (10)
Have scoured google groups and Java sun site and the only mentions I can
find seem to have no answers.
I have ensuredthat all requestsare being forwarded to the worker and have
JkMount /*.jsp apacheJavaPages
.... I am also using mod_jk rather than mod_webapp...
I'm all out of ideas... I did start just converting to POST's everywhere but
it's gonna become a horendous mess and pretty 'hacked' to do it...
(btw using 4.1.24-1 tomcat - 1.3.29 apache)
Any suggestions gratefully received.
cNp
| |
| Davide Bianchi 2004-02-26, 10:33 am |
| In alt.apache.configuration cNp <ur50g4y@aol.com> wrote:
> [notice] child pid 15944 exit signal Bus Error (10)
> (btw using 4.1.24-1 tomcat - 1.3.29 apache)
I'm using 1.3.29 with Tomcat 4.1.29 and never saw such problem,
maybe you should try to get a newer version of Tomcat.
Davide
--
| The idea there was that consumers would bring their broken electronic
| devices, such as television sets and VCR's, to the destruction
| centers, where trained personnel would whack them (the devices) with
| sledgehammers. With their devices thus permanently destroyed,
| |
|
|
> I'm using 1.3.29 with Tomcat 4.1.29 and never saw such problem,
> maybe you should try to get a newer version of Tomcat.
Afraid I have no control over the versions we have... they are the 'known
good' ones in the company... we're usually running at least one whole
version behind.
It's just very peculiar that something as simple and fundamental as GET
would cause problems!
cNp
|
|
|
|
|