On 30.06.2008, at 12:11, Xia, Wen wrote:
Both of the above running app has the same URL as before:
http://budgetdevxs/cgi-bin/WebObjects/StaffDirectory.woa/-54324
But this looks like a development URL. So there is still something
wrong. You should be able to connect without specifying the po
Hi Guido,
Thank you so much for your help.
I tried what you suggested and it worked.
I also tried only adding the -WOPort parameter to the command and the app
runs as well.
Both of the above running app has the same URL as before:
http://budgetdevxs/cgi-bin/WebObjects/StaffDirectory.woa/-54324
On 30.06.2008, at 11:00, Xia, Wen wrote:
http://budgetdevxs/cgi-bin/WebObjects/StaffDirectory.woa/-54324
There is something wrong with your start script. It seems to not
specify a listen port. Copy the start parameters from Monitor and run
the application with the exact same parameters (on
The application is launched without exception at all:
[2008-6-26 11:33:19 PDT] WebObjects version = 5.4.1
Welcome to StaffDirectory !
-- Cleaning Log Files More Than 30 Days Old
[2008-6-26 11:33:19 PDT] The URL for webserver connect is:
http://budgetdevxs/cgi-bin/WebObjects/StaffDirectory.woa/-54
Okay, next question: you have the right permissions? What error
message do you get when trying to start the app from the command line?
cug
On 30.06.2008, at 10:25, Xia, Wen wrote:
Yes.
On 6/30/08 9:13 AM, "Guido Neitzer" <[EMAIL PROTECTED]> wrote:
On 30.06.2008, at 09:57, Xia, Wen wrote:
Yes.
On 6/30/08 9:13 AM, "Guido Neitzer" <[EMAIL PROTECTED]> wrote:
> On 30.06.2008, at 09:57, Xia, Wen wrote:
>
>> If I just ran the app through command line and paste the URL in the
>> browser,
>> it will always give "The requested application was not found on this
>> server"
>> message.
>>
On 30.06.2008, at 09:57, Xia, Wen wrote:
If I just ran the app through command line and paste the URL in the
browser,
it will always give "The requested application was not found on this
server"
message.
If I add an instance through the JavaMonitor, and run from there
(same URL
basically
If I just ran the app through command line and paste the URL in the browser,
it will always give "The requested application was not found on this server"
message.
If I add an instance through the JavaMonitor, and run from there (same URL
basically), it works.
For deployment on non-leopard server,
On Jun 26, 2008, at 4:26 AM, Yves Selliez wrote:
I don’t know if that may help you, but what is sure is that you
should modify your woapp with this set of permission :
chown -R appserver:appserveradm yourapp.woa
chmod -R 755 yourapp.woa
For me the group “appserverusr” (as written somewhere)
I tried the command, the host name matches the reverse DNS lookup.
On 6/26/08 1:43 PM, "Pascal Robert" <[EMAIL PROTECTED]> wrote:
> To do a reserve DNS (IP -> name) lookup, open Terminal and type :
>
> host 192.168.11.21
>
> And to check forward DNS (name -> IP):
>
> host budgetdevxs.dof.fina
To do a reserve DNS (IP -> name) lookup, open Terminal and type :
host 192.168.11.21
And to check forward DNS (name -> IP):
host budgetdevxs.dof.finance
On the deployment machine, in Java Monitor -> Hosts tab, I got the
host name
as "budgetdevxs.dof.finance" with IP address
On the deployment machine, in Java Monitor -> Hosts tab, I got the host name
as "budgetdevxs.dof.finance" with IP address 192.168.11.21.
When I ran the application from command line on the server with -WOHost
budgetdevxs.dof.finance, the URL for web server connect is:
http://192.168.11.21/cgi-bin/
What host name are you using? For a dev machine, this should be
localhost. For deployment it should be the same as what hostname
returns. I think. It should match the reverse DNS lookup
On Jun 26, 2008, at 1:14 PM, Xia, Wen wrote:
Thank you, Chuck. I got the host name in wotaskd conf
Thank you, Chuck. I got the host name in wotaskd configuration and used it
as -WOHost when launching the app, but still the same error occurred. I
wonder what else I should check?
On 6/26/08 11:59 AM, "Chuck Hill" <[EMAIL PROTECTED]> wrote:
>
> On Jun 26, 2008, at 11:35 AM, Xia, Wen wrote:
>
It may be filtered out though. If you are not seeing it, WOLips is
likely filtering it out so you don't see it (as you really _shouldn't_
have to mess with it).
See the Wiki here for instructions on changing WOLips' filtering
settings:
http://wiki.objectstyle.org/confluence/display/WOL/WO
On Jun 26, 2008, at 11:35 AM, Xia, Wen wrote:
Thank you both for your help.
But where is build.properties?
It should be in the top level of your project.
In build.xml, it looks for it in my home
directory, but I can't find it there. Is it generated/updated when I
compiled the applicatio
Thank you, Yves. But doing this does not solve the problem.
On 6/26/08 7:26 AM, "Yves Selliez" <[EMAIL PROTECTED]> wrote:
> Hi Wen,
>
> I also encountered a lot of problem deploying my apps on a very new Leopard
> server. Strangely, I had no problem at all with another Leopard server I set
> u
Thank you both for your help.
But where is build.properties? In build.xml, it looks for it in my home
directory, but I can't find it there. Is it generated/updated when I
compiled the application?
I changed the principal class in the Properties for the project, and now it
launches the applicati
Hi Wen,
I also encountered a lot of problem deploying my apps on a very new Leopard
server. Strangely, I had no problem at all with another Leopard server I set
up just one month ago.
I don¹t know if that may help you, but what is sure is that you should
modify your woapp with this set of permiss
This is the problem ... Or rather, your build.properties is
probably the root cause. This variable should have been resolved
at the time build.properties was generated.
Isn't that changed whenever you change the principal class in the
Properties for that project?
Yep.
ms
___
On 25.06.2008, at 18:12, Mike Schrag wrote:
This is the problem ... Or rather, your build.properties is probably
the root cause. This variable should have been resolved at the time
build.properties was generated.
Isn't that changed whenever you change the principal class in the
Propertie
# ApplicationClass == ${basePackage}.Application
This is the problem ... Or rather, your build.properties is probably
the root cause. This variable should have been resolved at the time
build.properties was generated.
ms
___
Do not post admin req
Thank you for your reply. Here is the classpath.txt:
# JVM == java
# JVMOptions ==
# JDB == jdb
# JDBOptions ==
# ApplicationClass == ${basePackage}.Application
APPROOT\Resources\Java\
APPROOT\Resources\Java\staffdirectory.jar
LOCALROOT\Library\Frameworks\Jav
Finally, our new Leopard servers are here. I started moving
applications to the new server. But I have problem running the app on
the server, it always gives me following error:
Can't load .Application class, exiting...
java.lang.ClassNotFoundException: .Application
at java.net.URLC
24 matches
Mail list logo
