On 09/04/2008, at 8:31 AM, Aurelien Minet wrote:
Hi,
I just had a weird problem deploying an app. I could use JavaMonitor
to start the app and go to the home page of the app but as soon as I
tried to go any further or use an ajax auto complete on the home page
I would get "No Instance Available". I started the app from the
command line with no arguments and it would start fine and run fine
including ajax auto complete and navigating to other pages. I
started
the app from the command line with all the JavaMonitor arguments and
it wouldn't start fully. I removed the arguments one by one and when
I removed "-WODebuggingEnabled NO" the app started. So I went to
JavaMonitor and checked the Debugging enabled check box and now the
app runs fine.
I am not sure what this check box does and I have never needed to
check it before.
As far as know the check box set YES or NO to WODebuggingEnabled. I
would expect that setting WODebuggingEnabled to NO is equivalent not
setting WODebuggingEnabled.
From the monitor or from the command line it should start in the same
way with WODebuggingEnabled set to NO.
I think the default value when starting from the command line is
WODebuggingEnabled YES
Development environment
Mac OS X 10.4.11
WebObjects 5.3.3
wolips 5073
eclipse 3.3.2
Wonder frameworks 4.0.0.540
built using ant script with embed = true to embed all frameworks and
jars including WebObjects 5.3.3
Deployment environment
Mac OS X Server 10.5.1
WebObjects 5.4.1 (although I originally had WebObjects 5.3.3 using
symlinks in /System/Library/Frameworks)
I don't know how you embed 5.3.3 stuff but on your deployement
platform
it may load 5.4.1 jar and as it's built for 5.3.3 it could be the
cause
of the problem (wonder has specific build for 5.4).
I embed WebObjects 5.3.3 by modifying the build.xml script created by
wolips when I created my project. I set embed to true in the three
cases. The last one is the one that embeds WebObjects 5.3.3
<frameworks root="${wo.wolocalroot}" embed="true">
<patternset>
<includesfile
name="woproject/ant.frameworks.wo.wolocalroot"/>
</patternset>
</frameworks>
<frameworks root="${user.home}" embed="true">
<patternset>
<includesfile
name="woproject/ant.frameworks.user.home"/>
</patternset>
</frameworks>
<frameworks root="${wo.wosystemroot}" embed="true">
<patternset>
<includesfile
name="woproject/ant.frameworks.wo.wosystemroot"/>
</patternset>
</frameworks>
On deployment
environment is your app running with java 1.4.2 ?
I am compiling for Java 1.5 so I am pretty sure it is using the Java
1.5 JVM, otherwise it wouldn't ever get started.
Do you try ./app -WODebuggingEnabled NO -WOPort 1234 on you
development
box ?
I just tried it then and the app started fine on my development box.
Regards,
Aurelien
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
