Re: my other deployment problem...
Re: my other deployment problem...
- Subject: Re: my other deployment problem...
- From: Kieran Kelleher <email@hidden>
- Date: Thu, 22 Mar 2012 09:15:55 -0400
I install dev tools such as Eclipse in ~/Applications and dev files in ~/Developer. The /Developer folder belongs to Apple, so probably best not to ever put anything of your own in there.
On Mar 22, 2012, at 8:28 AM, James Cicenia wrote:
> I did almost all of that.....
>
> Then I downloaded XCode 4.3 and it threw away my Developer directory.
> After reinstalling everything...Eclipse, Wonder, WO, it all magically worked again.
>
> All my development (project) code was in a different directory. So I am guessing
> that some subtle wonder framework was mismatched or built wrong. But since
> it worked, I immediately said thank you lord, and moved on with development
> which is my strong suit, and not deployments.
>
> I am also now fully git'd and moving to Jenkins.
>
> Thanks
>
> James
>
>
> On Mar 22, 2012, at 1:27 AM, Johan Henselmans wrote:
>
>>
>> On Feb 16, 2012, at 2:22 PM, James Cicenia wrote:
>>
>>> Is Wonan the Destroyer around????
>>>
>>> I HATE DEPLOYMENT. THERE I SAID IT.
>>>
>>> Anyway, my legacy app needs a bit of work but unfortunately I can't get it to show
>>> anything when I deploy to my test server.
>>>
>>> It gets to the point where it is about to show Main and then poof.... nothing happens,
>>> doesn't seem to instantiate Main and then sends back a blank page?! Of course it
>>> works perfectly on my development... full embed, etc. sigh.
>>>
>>
>> Deployment
>> 1-embed all frameworks
>> 2-make sure the webserver resources are in the webserver folder they are expected (On a Mac, In /LibraryWebServer/Documents/WebObjects/yourappname.woa/Contents/WebServerResources)
>> 3-make sure the permissions are allright on both folders: in the webserver, user _www should be able to read it, in the application server, _appserveradm should be able to read it
>> 4-start the application manually from the command line: goto /Library/WebObjects/Applications/yourappname.woa, use ./yourappname, see if anything extraordinary comes up in the logging to the terminal
>> 5-make sure that processes that have to use the terminal are silenced by setting -Djava.awt.headless=true in the Additional Arguments of the instance defaults
>> 6-make sure that the process gets enough memory by setting -Xmx256M (or whatever) in the Additional Arguments of the instance defaults
>>
>> <PastedGraphic-1.png>
>>
>> Let us know if anything extraordinary comes up..
>>
>>> I really need some help or ideas to get this running today.
>>>
>>> Thanks
>>> James _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>> Vriendelijke Groeten,
>>
>> Johan Henselmans
>> email@hidden
>>
>>
>>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden