Gustavo,
Usually the problem is caused by the person who builds or deploys the
app ;-)
Try logging what wotaskd sees to find the root cause:
http://wiki.objectstyle.org/confluence/display/WO/Debugging+wotaskd+and+JavaMonitor
Having said that, the most common things IMHO are:
Permissions
Not using fully embedded apps (and thus having compatability problems
between development frameworks and deployment server frameworks
Incompatible cruft in /Library/WebObjects/Extensions ..... I *never*
put anything in that folder
Incompatible cruft in /Library/Java/Extensions .... I *never* put
anything related to my WO apps in there
Try logging what wotaskd sees to find the root cause:
http://wiki.objectstyle.org/confluence/display/WO/Debugging+wotaskd+and+JavaMonitor
HTH, Kieran
On Oct 16, 2009, at 10:02 AM, Gustavo Pizano wrote:
Hello, I dunno why, sometimes its a PITA to make the app instance to
load.
I have deployed some apps already without problem, but when i add
anohterone, I configure the instance, same as I did before with the
other ones exceto changing the port to a higer one, when I try to
turn the instnace one, it stays in "trying to turn on"(the switch
going up and down) and then I see that there are some instance
death. why this could be happening?
Thanks
gustavo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
