From: David T. <dav...@cl...> - 2003-09-03 13:02:36
|
Hi, we have an application that does not start up if it runs on a dual cpu mac. We notice that models get loaded twice and that there is a problem with notifications. Does anyone know if WO / Wonder uses multiple threads in the startup / init phase? The way how WO and Wonder uses lazy initialisation makes it absolutely incompatible with multiple threads. In theory there are also problems with multiple CPU's. I can reproduce this problem and thanks to mac os x i can turn on / off the second CPU and check the app. Does anyone else found 'strange' things on a dual mac and webobjects? regards David |
From: Max M. <max...@ma...> - 2003-09-03 23:23:36
|
Hi David, Almost all the developers I work with work on dual processor macs and we have not seen any of the problems that you are seeing. Only a single thread is used for startup within WebObjects and Wonder isn't spinning off any threads to do special stuff during any of the init process. Likewise all notifications are processed by the thread posting the notification. What version of WO are you running and in what env are you deploying? Regards, Max On Wednesday, September 3, 2003, at 06:02 AM, David Teran wrote: > Hi, > > we have an application that does not start up if it runs on a dual cpu > mac. We notice that models get loaded twice and that there is a > problem with notifications. Does anyone know if WO / Wonder uses > multiple threads in the startup / init phase? The way how WO and > Wonder uses lazy initialisation makes it absolutely incompatible with > multiple threads. In theory there are also problems with multiple > CPU's. > > I can reproduce this problem and thanks to mac os x i can turn on / > off the second CPU and check the app. > > Does anyone else found 'strange' things on a dual mac and webobjects? > > regards David > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: David T. <dav...@cl...> - 2003-09-24 18:51:13
Attachments:
David Terán.vcf
|
Hi Max, sorry for the delay but i tried various things and course the setup / init phase is single threaded. Here the result: 1) when we compile the whole wonder stuff with ant and our own frameworks with javac it makes problems. Models get loaded twice and i think the main problem is the NSNotificationCenter (again). 2) Some time ago i read an article from ibm about lazy initialization and multiple cpus and multiple threads, very interesting and maybe this might be another problem 3) The problem occured mostly in deployment mode with two CPUs, deactivating one CPU in Panther makes it a little bit better, sometime the app starts up but not often. Starting the app in ProjectBuilder was OK about 99%. Maybe this is also Panther related but we have the same problem under jaguar, too. Always with dual CPU machines. Best solution: clean -everyting- and recompile -everything- with javac, throw away jikes. Maybe this helps anyone else. cheers David On 04.09.2003, at 01:23, Max Muller wrote: > Hi David, > Almost all the developers I work with work on dual processor macs and > we have not seen any of the problems that you are seeing. Only a > single thread is used for startup within WebObjects and Wonder isn't > spinning off any threads to do special stuff during any of the init > process. Likewise all notifications are processed by the thread > posting the notification. What version of WO are you running and in > what env are you deploying? > > Regards, > Max > > On Wednesday, September 3, 2003, at 06:02 AM, David Teran wrote: > >> Hi, >> >> we have an application that does not start up if it runs on a dual >> cpu mac. We notice that models get loaded twice and that there is a >> problem with notifications. Does anyone know if WO / Wonder uses >> multiple threads in the startup / init phase? The way how WO and >> Wonder uses lazy initialisation makes it absolutely incompatible with >> multiple threads. In theory there are also problems with multiple >> CPU's. >> >> I can reproduce this problem and thanks to mac os x i can turn on / >> off the second CPU and check the app. >> >> Does anyone else found 'strange' things on a dual mac and webobjects? >> >> regards David >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > |
From: Max M. <max...@ma...> - 2003-09-29 21:24:05
|
Hi David, What version of jikes are you using? We use version 1.15 and = haven't=20 had a problem. We deploy on dual cpu XServes running Jaguar and Java=20 1.4.1 and haven't had a problem yet. Regards, Max On Wednesday, September 24, 2003, at 11:51 AM, David Teran wrote: > Hi Max, > > sorry for the delay but i tried various things and course the setup /=20= > init phase is single threaded. Here the result: > > 1) when we compile the whole wonder stuff with ant and our own=20 > frameworks with javac it makes problems. Models get loaded twice and i=20= > think the main problem is the NSNotificationCenter (again). > 2) Some time ago i read an article from ibm about lazy initialization=20= > and multiple cpus and multiple threads, very interesting and maybe=20 > this might be another problem > 3) The problem occured mostly in deployment mode with two CPUs,=20 > deactivating one CPU in Panther makes it a little bit better, sometime=20= > the app starts up but not often. Starting the app in ProjectBuilder=20 > was OK about 99%. > > Maybe this is also Panther related but we have the same problem under=20= > jaguar, too. Always with dual CPU machines. > > Best solution: clean -everyting- and recompile -everything- with=20 > javac, throw away jikes. > > Maybe this helps anyone else. > > cheers David > > > On 04.09.2003, at 01:23, Max Muller wrote: > >> Hi David, >> Almost all the developers I work with work on dual processor = macs=20 >> and we have not seen any of the problems that you are seeing. Only a=20= >> single thread is used for startup within WebObjects and Wonder isn't=20= >> spinning off any threads to do special stuff during any of the init=20= >> process. Likewise all notifications are processed by the thread=20 >> posting the notification. What version of WO are you running and in=20= >> what env are you deploying? >> >> Regards, >> Max >> >> On Wednesday, September 3, 2003, at 06:02 AM, David Teran wrote: >> >>> Hi, >>> >>> we have an application that does not start up if it runs on a dual=20= >>> cpu mac. We notice that models get loaded twice and that there is a=20= >>> problem with notifications. Does anyone know if WO / Wonder uses=20 >>> multiple threads in the startup / init phase? The way how WO and=20 >>> Wonder uses lazy initialisation makes it absolutely incompatible=20 >>> with multiple threads. In theory there are also problems with=20 >>> multiple CPU's. >>> >>> I can reproduce this problem and thanks to mac os x i can turn on /=20= >>> off the second CPU and check the app. >>> >>> Does anyone else found 'strange' things on a dual mac and = webobjects? >>> >>> regards David >>> >>> >>> >>> ------------------------------------------------------- >>> This sf.net email is sponsored by:ThinkGeek >>> Welcome to geek heaven. >>> http://thinkgeek.com/sf >>> _______________________________________________ >>> Wonder-disc mailing list >>> Won...@li... >>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >> >> >> > <David Ter=E1n.vcf> |
From: David T. <dav...@cl...> - 2003-09-30 21:06:30
Attachments:
David Terán.vcf
|
Hi Max, it turns out that it was indeed jikes. We used version 1.18 on ... ok=20 panther ;-) but had the same problems on jaguar, too. Anjo pointed out=20= that jikes 1.15 is the newest 'stable' version. Currently we make sure=20= that our apps and all frameworks are compiled with either jikes 1.15 or=20= javac and since then all these strange errors disappeared. Regards David On 29.09.2003, at 23:23, Max Muller wrote: > Hi David, > What version of jikes are you using? We use version 1.15 and = haven't=20 > had a problem. We deploy on dual cpu XServes running Jaguar and Java=20= > 1.4.1 and haven't had a problem yet. > > Regards, > Max > > On Wednesday, September 24, 2003, at 11:51 AM, David Teran wrote: > >> Hi Max, >> >> sorry for the delay but i tried various things and course the setup /=20= >> init phase is single threaded. Here the result: >> >> 1) when we compile the whole wonder stuff with ant and our own=20 >> frameworks with javac it makes problems. Models get loaded twice and=20= >> i think the main problem is the NSNotificationCenter (again). >> 2) Some time ago i read an article from ibm about lazy initialization=20= >> and multiple cpus and multiple threads, very interesting and maybe=20 >> this might be another problem >> 3) The problem occured mostly in deployment mode with two CPUs,=20 >> deactivating one CPU in Panther makes it a little bit better,=20 >> sometime the app starts up but not often. Starting the app in=20 >> ProjectBuilder was OK about 99%. >> >> Maybe this is also Panther related but we have the same problem under=20= >> jaguar, too. Always with dual CPU machines. >> >> Best solution: clean -everyting- and recompile -everything- with=20 >> javac, throw away jikes. >> >> Maybe this helps anyone else. >> >> cheers David >> >> >> On 04.09.2003, at 01:23, Max Muller wrote: >> >>> Hi David, >>> Almost all the developers I work with work on dual processor = macs=20 >>> and we have not seen any of the problems that you are seeing. Only a=20= >>> single thread is used for startup within WebObjects and Wonder isn't=20= >>> spinning off any threads to do special stuff during any of the init=20= >>> process. Likewise all notifications are processed by the thread=20 >>> posting the notification. What version of WO are you running and in=20= >>> what env are you deploying? >>> >>> Regards, >>> Max >>> >>> On Wednesday, September 3, 2003, at 06:02 AM, David Teran wrote: >>> >>>> Hi, >>>> >>>> we have an application that does not start up if it runs on a dual=20= >>>> cpu mac. We notice that models get loaded twice and that there is a=20= >>>> problem with notifications. Does anyone know if WO / Wonder uses=20 >>>> multiple threads in the startup / init phase? The way how WO and=20 >>>> Wonder uses lazy initialisation makes it absolutely incompatible=20 >>>> with multiple threads. In theory there are also problems with=20 >>>> multiple CPU's. >>>> >>>> I can reproduce this problem and thanks to mac os x i can turn on /=20= >>>> off the second CPU and check the app. >>>> >>>> Does anyone else found 'strange' things on a dual mac and=20 >>>> webobjects? >>>> >>>> regards David >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This sf.net email is sponsored by:ThinkGeek >>>> Welcome to geek heaven. >>>> http://thinkgeek.com/sf >>>> _______________________________________________ >>>> Wonder-disc mailing list >>>> Won...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >>> >>> >>> >> <David Ter=E1n.vcf> > > > |