On 3 Jan 2026, at 11:34 am, Theodore Petrosky <[email protected]> wrote:
> the app claims to be "ON" > Excellent! You should also take a look at the logs, which ideally will be in /var/log/webobjects/NewApp-1 for this instance, though depends where you've told JavaMonitor to send output. > but when I click the NewApp-1 above I get: > > Not Found > > The requested URL was not found on this server. > What was the URL? In my experience, that hyperlink never gives you the correct URL—I simply never use it. > And in the Site tab: > > URL to Adaptor: > http://ec2-44-223-43-102.compute-1.amazonaws.com/cgi-bin/WebObjects > In that case, try: http://ec2-44-223-43-102.compute-1.amazonaws.com/cgi-bin/WebObjects/NewApp.woa/ (Your security group on the EC2 instance will need to allow HTTP traffic through.) > based on your help below, here is my build.properties: > > principalClass=com.abc.Application > ApplicationClass = com.abc.Application > Delete "ApplicationClass". Otherwise looks fine. > BTW, where are you in the world? > Adelaide, Australia. UTC+1030. > when I examine on the server in; /opt/WOApplications/NewApp.woa/Contents/UNIX > > The top of UNIXClassPath.txt is: > > # JVM == java > # JVMOptions == --add-exports java.base/sun.security.action=ALL-UNNAMED > # JDB == jdb > # JDBOptions == > # ApplicationClass == com.abc.Application > Looks fine. Next steps: 1. Find the logs. You should have told JavaMonitor where to put them. wo-on-ec2 created /var/log/webobjects/ for the purpose. 2. Make sure you're using the correct URL. -- Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/
