• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Application Instance won't start in monitor
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application Instance won't start in monitor


  • Subject: Re: Application Instance won't start in monitor
  • From: Jake MacMullin <email@hidden>
  • Date: Tue, 9 Mar 2004 13:57:13 +1100

Not a stupid question at all! In fact, that turned out to be the problem - it seems that when Eclipse builds a .woa - it doesn't give the same permissions to the launch script that XCode does. So wotaskd did not have the permissions needed to execute the launch script. I changed the permissions so that they matched those of a default XCode build and it now works as expected. Thanks!

Regards,

Jake


On 9 Mar 2004, at 12:04 PM, Jonathan Rochkind wrote:

Maybe a stupid question, but... is wotaskd running as the same user account as you are trying from the command line? Otherwise, could be a difference in permissions.

--Jonathan

I'm stumped! - I have taken the plunge and built a version of a WebObjects application using Eclipse & WOLips. I'm quite happy with these tools, however I'm having all sorts of strife when it comes to deploying the application. When I try and launch it with Monitor (with the default settings) - it just falls over, it doesn't even write anything to the instance log file - just refuses to start. However if I copy and paste the Monitor generated command-line arguments and launch the application from the command-line, it launches just fine - and even turns up in Monitor. The *only* change I've made when manually launching the application is to put quotes around the -NSProjectSearchPath argument.

Here's the command that I use to launch my application (which works from the command-line):

/Library/WebObjects/Applications/MyApp.woa/MyApp -WOPort 2012 -WOCachingEnabled YES -WODebuggingEnabled NO -WOOutputPath /tmp/MyApp-1 -WOAutoOpenInBrowser NO -WOAutoOpenClientApplication NO -WOLifebeatInterval 30 -WOLifebeatEnabled YES -WOLifebeatDestinationPort 1085 -WOAdaptor WODefaultAdaptor -WOWorkerThreadCount 8 -WOListenQueueSize 128 -WOWorkerThreadCountMin 16 -WOWorkerThreadCountMax 256 -NSProjectSearchPath "()" -WOSessionTimeOut 3600 -WOApplicationName MyApp -WOMonitorEnabled YES -WONoPause YES

Why won't the application start from Monitor? How do I begin to debug this?

Regards,

Jake
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Application Instance won't start in monitor (From: Jake MacMullin <email@hidden>)

  • Prev by Date: Re: Can't insert a second record?!
  • Next by Date: Re: Application Instance won't start in monitor
  • Previous by thread: Application Instance won't start in monitor
  • Next by thread: Re: Application Instance won't start in monitor
  • Index(es):
    • Date
    • Thread