• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Problems with Apache - JK - JBoss first running fine then loosing connections and stop working

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, I have 3 machines with the same systems

Apache 2.2
JBoss 4.0.3_SP1
JKConnector 1.2.25

Running on an ESX VM Ware Server.

The Servers are for development, test and production, so they are not connected. I checked the SIDs on the VMWare machines, they are unique. I don't know this machines can interact, perhaps it is a problem with the same domain user or something...

I start the first one, everything fine.
I start the second one, still everything fine.
But after starting the third one it takes some minutes and then I get 500 errors from the JBoss and in the JK log it looks like no Tomcat is running on 8009 but 8080 is still working. Also windows has problems with new sockets after this, restarting JBoss and Apache does not help, Windows needs to be rebootet.


jk is is not longer working and throwing errors in the mod_jk.log like:
Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port.

I'm running out of ideas does somebody have anything for me to test?








 
Martin mo
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Found it on my own, the problem is that I use UNC paths in the Apache configuration for some resources and this is causing network trouble, the rest are just symptoms of this root cause.

reply
    Bookmark Topic Watch Topic
  • New Topic