| Hi Valerio,
I experience the same problem on a Cent OS instance (I think this is a VMWare distribution) but it works on others...
There is a major difference between starting the instance and other function like stop and refuse new session. Start is done by wotaskd that launc the process, others are http call to the instance by wotaskd, to some direct actions (womp handler I think).
I suspect that the communication between wotaskd and instance is blocked by the firewall or system policy but I do not have a definitive proof of this.
Regards,
Samuel
Thanks Lon, I didn't see your answer until now because gmail (which I hate every day more) had hidden it.
I'll see what I can find in the logs, although "start" works fine, why would "stop" be different ?
Look in your application log, do you see messages about not being able to communicate with monitor? I found this problem happens if I don't have JavaXML as part of my project (or classpath defined to whatever the xml jars are).
-Lon
I recently ported my WebObjects app from an old OS X server to a
CentOS 8 server. The WOMonitor on CentOS allows me to configure the app and start
it, but it will not stop it (I end up doing with pkill from
command line) and the Auto-Recover does not work. I also tried
from command line using curl to communicate to WOMonitor, it does
the info and start correctly, but it will not stop the app. I've looked at the log file for the WOMonitor, but there was
nothing useful. Any ideas ? Thanks in advance,
--
| Valerio Luccio |
|
|
| High Performance Computing |
|
|
| New York University |
|
New York, NY 10003 |
"In an open world, who needs windows or gates ?"
-- | Valerio Luccio |
|
|
| High Performance Computing |
|
10 Astor Place, Room 415 |
| New York University |
|
New York, NY 10003 |
"In an open world, who needs windows or gates ?"
|