[Glass] Fwd: loading seaside and zinc
Locked
12
12
[Glass] Fwd: loading seaside and zinc
 
|
Begin forwarded message: > From: Paul DeBruicker <[hidden email]> > Subject: Re: [Glass] loading seaside and zinc > Date: November 14, 2013 6:27:18 AM PST > To: Otto Behrens <[hidden email]> > > If you use the config from Sven's main repo here: > > Http://mc.stfx.eu/ZincHTTPComponents > > Or > > Http://www.squeaksource.com/MetacelloRepository > > And do a > > ConfigurationOfZincHTTPComponents load. > > It should load 2.4.3 into GS 2.4.4.4 assuming an up to date version of Metacello > > Dale will know better about the github repos. > > > > > > > > On Nov 14, 2013, at 2:04 AM, Otto Behrens <[hidden email]> wrote: > >> Hi, >> >> I cloned github.com/glassdb/glass, github.com/glassdb/zinc and >> github.com/glassdb/Seaside30. >> >> I'm now trying to load seaside from the cloned filetree repo and have >> trouble with the loading of Zinc. >> >> It's trying to load Zinc-HTTP-SvenVanCaekenberghe.162 because this is >> derived from the #stable blessing in >> ConfigurationOfZincHTTPComponents, specified as "#gemstone version: >> '1.1'". >> >> Is this correct? The current stable for pharo is 2.4.3. This GS one is >> then a bit old, isn't it? >> >> What would be nice is if BaselineOfSeaside30 uses >> ConfigurationOfZincHTTPComponents to get it's stuff whereas I've got a >> local clone of glassdb/zinc and would prefer to use >> BaselineOfZincHTTPComponents. If I understand this, the "version" >> checked out in the git repo is then loaded. >> >> Anyway, my mission right now is just to get a working Zinc client >> loaded into GS 2.4.4.4 (because seaside loads it and we also use it to >> do HTTP to the outside world. >> >> Any help / ideas will be welcome. >> >> Thanks >> Otto >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
Paul, Otto,
Instructions for installing Zinc on Gemstone are on github: https://github.com/glassdb/zinc I don't think the changes for Gemstone are/can be backported to main Zinc, so for Gemstone you always need to use the github repo. The current version of Zinc for Gemstone is also 2.4.3. We did an effort some months ago but the server functionality has not been tested. Fwiw, I also still am using Zinc 1.7 in production but I am now moving 2.4.3 to our staging setup. The ConfigurationOfZincHTTPComponents does not refer to this repo. I can see Paul's changes in the commit log in the main Zinc repo, but does this final version of the config really work for you? Because the referenced packages are not in any repo that is referenced from that configuration. Let me know if the instructions on github are incomplete. And yes, we need to fix the configuration in main repo to make it load from github, otherwise there is too much confusion. Cheers Johan On 14 Nov 2013, at 16:14, Paul DeBruicker <[hidden email]> wrote: > > > Begin forwarded message: > >> From: Paul DeBruicker <[hidden email]> >> Subject: Re: [Glass] loading seaside and zinc >> Date: November 14, 2013 6:27:18 AM PST >> To: Otto Behrens <[hidden email]> >> >> If you use the config from Sven's main repo here: >> >> Http://mc.stfx.eu/ZincHTTPComponents >> >> Or >> >> Http://www.squeaksource.com/MetacelloRepository >> >> And do a >> >> ConfigurationOfZincHTTPComponents load. >> >> It should load 2.4.3 into GS 2.4.4.4 assuming an up to date version of Metacello >> >> Dale will know better about the github repos. >> >> >> >> >> >> >> >> On Nov 14, 2013, at 2:04 AM, Otto Behrens <[hidden email]> wrote: >> >>> Hi, >>> >>> I cloned github.com/glassdb/glass, github.com/glassdb/zinc and >>> github.com/glassdb/Seaside30. >>> >>> I'm now trying to load seaside from the cloned filetree repo and have >>> trouble with the loading of Zinc. >>> >>> It's trying to load Zinc-HTTP-SvenVanCaekenberghe.162 because this is >>> derived from the #stable blessing in >>> ConfigurationOfZincHTTPComponents, specified as "#gemstone version: >>> '1.1'". >>> >>> Is this correct? The current stable for pharo is 2.4.3. This GS one is >>> then a bit old, isn't it? >>> >>> What would be nice is if BaselineOfSeaside30 uses >>> ConfigurationOfZincHTTPComponents to get it's stuff whereas I've got a >>> local clone of glassdb/zinc and would prefer to use >>> BaselineOfZincHTTPComponents. If I understand this, the "version" >>> checked out in the git repo is then loaded. >>> >>> Anyway, my mission right now is just to get a working Zinc client >>> loaded into GS 2.4.4.4 (because seaside loads it and we also use it to >>> do HTTP to the outside world. >>> >>> Any help / ideas will be welcome. >>> >>> Thanks >>> Otto >>> _______________________________________________ >>> Glass mailing list >>> [hidden email] >>> http://lists.gemtalksystems.com/mailman/listinfo/glass > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On Thu, Nov 14, 2013 at 5:39 PM, Johan Brichau <[hidden email]> wrote: Paul, Otto, Hi Johan, I am starting to use Zinc-Seasider (which I guess is under what you mention as "server functionality") and I've been having some problems. They could be because I am still learning GemStone or becuase there is indeed something wrong.
So...I want to test with another seaside adaptor to see if there is a different. My GemStone is still running locally because I am still porting my app there. So...besides Zinc, which is the easiest web adaptor to use with GemStone? Also, if you have some doc on how to use it, I would be very happy. I would like to avoid any none-smalltalk web server for the moment....(unless the conf files were very easy)... so I guess the only option left is WAGsSwazooAdaptor ?
Thanks in advance, Cheers Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
Mariano,
Yes, we also use Swazoo when Gemstone is running on our development machine. I would never use it for production (rather use FastCGI behind nginx) but for development setups, it does the job. Mind that we start it as follows: WAGemStoneRunSeasideGems default name: 'Swazoo'; adaptorClass: WAGsSwazooAdaptor; ports: #(8383). WAGemStoneRunSeasideGems restartGems. Running the other snippet below works but we also got strange behavior when using that. Now, that also dates back to the time we started with Gemstone, but I seem to remember we noted that using the following snippet to start swazoo from gemtools was not a reliable way to run the app. WAGsSwazooAdaptor startOn: 8383. Besides that, how are you starting the Zinc adaptor? I would want to quickly setup an extent here with a Zinc server so I can check out what the problems are. Since a lot of people are interested, it's worth diving into. Johan On 14 Nov 2013, at 21:45, Mariano Martinez Peck <[hidden email]> wrote: > I am starting to use Zinc-Seasider (which I guess is under what you mention as "server functionality") and I've been having some problems. They could be because I am still learning GemStone or becuase there is indeed something wrong. > So...I want to test with another seaside adaptor to see if there is a different. My GemStone is still running locally because I am still porting my app there. So...besides Zinc, which is the easiest web adaptor to use with GemStone? Also, if you have some doc on how to use it, I would be very happy. I would like to avoid any none-smalltalk web server for the moment....(unless the conf files were very easy)... so I guess the only option left is WAGsSwazooAdaptor ? _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
In reply to this post by Johan Brichau-3
I must correct myself. The current version for gemstone 2.3.2
I should also clarify that the github repository's master branch is an exact copy of the Pharo version. The gemstone ports are in their respective branches. But all that is on github too: https://github.com/glassdb/zinc/releases/ On 14 Nov 2013, at 21:39, Johan Brichau <[hidden email]> wrote: > Paul, Otto, > > Instructions for installing Zinc on Gemstone are on github: https://github.com/glassdb/zinc > I don't think the changes for Gemstone are/can be backported to main Zinc, so for Gemstone you always need to use the github repo. > > The current version of Zinc for Gemstone is also 2.4.3. We did an effort some months ago but the server functionality has not been tested. > Fwiw, I also still am using Zinc 1.7 in production but I am now moving 2.4.3 to our staging setup. > > The ConfigurationOfZincHTTPComponents does not refer to this repo. > I can see Paul's changes in the commit log in the main Zinc repo, but does this final version of the config really work for you? Because the referenced packages are not in any repo that is referenced from that configuration. > > Let me know if the instructions on github are incomplete. > And yes, we need to fix the configuration in main repo to make it load from github, otherwise there is too much confusion. > > Cheers > Johan > > On 14 Nov 2013, at 16:14, Paul DeBruicker <[hidden email]> wrote: > >> >> >> Begin forwarded message: >> >>> From: Paul DeBruicker <[hidden email]> >>> Subject: Re: [Glass] loading seaside and zinc >>> Date: November 14, 2013 6:27:18 AM PST >>> To: Otto Behrens <[hidden email]> >>> >>> If you use the config from Sven's main repo here: >>> >>> Http://mc.stfx.eu/ZincHTTPComponents >>> >>> Or >>> >>> Http://www.squeaksource.com/MetacelloRepository >>> >>> And do a >>> >>> ConfigurationOfZincHTTPComponents load. >>> >>> It should load 2.4.3 into GS 2.4.4.4 assuming an up to date version of Metacello >>> >>> Dale will know better about the github repos. >>> >>> >>> >>> >>> >>> >>> >>> On Nov 14, 2013, at 2:04 AM, Otto Behrens <[hidden email]> wrote: >>> >>>> Hi, >>>> >>>> I cloned github.com/glassdb/glass, github.com/glassdb/zinc and >>>> github.com/glassdb/Seaside30. >>>> >>>> I'm now trying to load seaside from the cloned filetree repo and have >>>> trouble with the loading of Zinc. >>>> >>>> It's trying to load Zinc-HTTP-SvenVanCaekenberghe.162 because this is >>>> derived from the #stable blessing in >>>> ConfigurationOfZincHTTPComponents, specified as "#gemstone version: >>>> '1.1'". >>>> >>>> Is this correct? The current stable for pharo is 2.4.3. This GS one is >>>> then a bit old, isn't it? >>>> >>>> What would be nice is if BaselineOfSeaside30 uses >>>> ConfigurationOfZincHTTPComponents to get it's stuff whereas I've got a >>>> local clone of glassdb/zinc and would prefer to use >>>> BaselineOfZincHTTPComponents. If I understand this, the "version" >>>> checked out in the git repo is then loaded. >>>> >>>> Anyway, my mission right now is just to get a working Zinc client >>>> loaded into GS 2.4.4.4 (because seaside loads it and we also use it to >>>> do HTTP to the outside world. >>>> >>>> Any help / ideas will be welcome. >>>> >>>> Thanks >>>> Otto >>>> _______________________________________________ >>>> Glass mailing list >>>> [hidden email] >>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >> >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass > _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
In reply to this post by Johan Brichau-3
On Thu, Nov 14, 2013 at 5:54 PM, Johan Brichau <[hidden email]> wrote: Mariano, Cool. I will try with that and come back once I have experimented a bit. Running the other snippet below works but we also got strange behavior when using that. Now, that also dates back to the time we started with Gemstone, but I seem to remember we noted that using the following snippet to start swazoo from gemtools was not a reliable way to run the app. (WAGsZincAdaptor port: 8888) start. I would want to quickly setup an extent here with a Zinc server so I can check out what the problems are. Since a lot of people are interested, it's worth diving into. What I did is I loaded latest GLASS and Metacello and then I did:
Metacello new load: #('Core' 'Zinc-Seaside') baseline: 'Zinc'; repository: 'github://glassdb/zinc:gemstone3.1/repository'; load: 'Tests'. Metacello new configuration: 'Seaside3'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: '3.0.9'; But one of my problems with Zinc might be the "expected" behavior in GemStone. I paste what I have asked today in another thread: Another question....maybe weird.... when I launch zinc like this: (WAGsZincAdaptor port: 8888) start.
I do it as a "do it" in the GemClient workspace. When I do that, the UI is not responsive anymore and the gemstone cursor appears. It only goes away when I manually interrupt it of i a debugger comes. When that happens... the zinc server is down!! So I have to re-start zinc after each debug? I can imagine that maybe this is because Zinc was started from a Gem or something in my GemClient and when I interrupt that I might be kick off or something and cleans what I did...
So I wonder, is this the correct way to run the web adaptor? Or I have to run the adaptor inside a transaction (so that I could remain after):
MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ (WAGsZincAdaptor port: 8888) start.
] Johan Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
Mariano,
Yes, if you start an adaptor directly from gemtools, it does not return and when an error happens, the debugger pops up but the adaptor is stopped. If you use the WAGemStoneRunSeasideGems, what actually happens is that the adaptor is started in another gem (vm). You can start/stop that gem using the menu items in gemtools (or the command-line scripts, which are actually invoked by the menu items). So... that is indeed expected and should solve that 'problem'. Ok, I am loading Zinc in an extent as I write this to experiment too but it's getting late on this side of the ocean so I might get back only tomorrow. Johan On 14 Nov 2013, at 22:06, Mariano Martinez Peck <[hidden email]> wrote: > > > > On Thu, Nov 14, 2013 at 5:54 PM, Johan Brichau <[hidden email]> wrote: > Mariano, > > Yes, we also use Swazoo when Gemstone is running on our development machine. I would never use it for production (rather use FastCGI behind nginx) but for development setups, it does the job. > > Mind that we start it as follows: > > WAGemStoneRunSeasideGems default > name: 'Swazoo'; > adaptorClass: WAGsSwazooAdaptor; > ports: #(8383). > WAGemStoneRunSeasideGems restartGems. > > > Cool. I will try with that and come back once I have experimented a bit. > > Running the other snippet below works but we also got strange behavior when using that. Now, that also dates back to the time we started with Gemstone, but I seem to remember we noted that using the following snippet to start swazoo from gemtools was not a reliable way to run the app. > > WAGsSwazooAdaptor startOn: 8383. > > Besides that, how are you starting the Zinc adaptor? > > (WAGsZincAdaptor port: 8888) start. > > I would want to quickly setup an extent here with a Zinc server so I can check out what the problems are. Since a lot of people are interested, it's worth diving into. > > > What I did is I loaded latest GLASS and Metacello and then I did: > > Metacello new > baseline: 'Zinc'; > repository: 'github://glassdb/zinc:gemstone3.1/repository'; > load: 'Tests'. > Metacello new > configuration: 'Seaside3'; > repository: > 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > version: '3.0.9'; > load: #('Core' 'Zinc-Seaside') > > > But one of my problems with Zinc might be the "expected" behavior in GemStone. I paste what I have asked today in another thread: > > > > Another question....maybe weird.... when I launch zinc like this: > > (WAGsZincAdaptor port: 8888) start. > > I do it as a "do it" in the GemClient workspace. When I do that, the UI is not responsive anymore and the gemstone cursor appears. It only goes away when I manually interrupt it of i a debugger comes. When that happens... the zinc server is down!! So I have to re-start zinc after each debug? I can imagine that maybe this is because Zinc was started from a Gem or something in my GemClient and when I interrupt that I might be kick off or something and cleans what I did... > > So I wonder, is this the correct way to run the web adaptor? Or I have to run the adaptor inside a transaction (so that I could remain after): > > MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ > > (WAGsZincAdaptor port: 8888) start. > > ] > > > > Johan > > On 14 Nov 2013, at 21:45, Mariano Martinez Peck <[hidden email]> wrote: > > > I am starting to use Zinc-Seasider (which I guess is under what you mention as "server functionality") and I've been having some problems. They could be because I am still learning GemStone or becuase there is indeed something wrong. > > So...I want to test with another seaside adaptor to see if there is a different. My GemStone is still running locally because I am still porting my app there. So...besides Zinc, which is the easiest web adaptor to use with GemStone? Also, if you have some doc on how to use it, I would be very happy. I would like to avoid any none-smalltalk web server for the moment....(unless the conf files were very easy)... so I guess the only option left is WAGsSwazooAdaptor ? > > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass > > > > -- > Mariano > http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
In reply to this post by Mariano Martinez Peck
On Thu, Nov 14, 2013 at 8:11 PM, Mariano Martinez Peck <[hidden email]> wrote:
Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
From: "Mariano Martinez Peck" <[hidden email]>This implies that you are not connecting to swazoo ... and implies that a fastcgi gem was already listening on 8787 ... if you were using 8787 from gemtools, then there is possibly a process there listening ... logging in/out of gemtools will get rid of any rogue listeners ... doing a: ps -efw | grep TCP ps -efw | grep topaz will help you find gemstone gems (the first case) and gemstone topaz processes that might be running (the TCP grep will find pgsvrmain processes as well but you can ignore them ... its the gem TCP guys that you are looking for). You should have one gem for each GemTools login and you may have a topaz running as a maintenance gem and then multiple topazs running as web servers ... Dale
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
|
|
In reply to this post by Johan Brichau-3
> Instructions for installing Zinc on Gemstone are on github: https://github.com/glassdb/zinc
Thanks, yes. But, firstly, we work from a cloned repository, which we submodule under our main repo. This is because we like to pin the version that works and upgrade explicitly when we need to. We do a lot of deploys / loads in a day and doing it via github every time is expensive and not reliable. We are busy with an upgrade from GS 2 to GS 3, which makes it a bit more complicated because we have to use the correct branch. This is cool, we'll do it. Secondly, we are trying to use Metacello to specify all our dependencies in one place. We have a configuration to load all the packages we use (from a local git repo) and one for all our own code. Currently, the glass, seaside and whatever packages is a mix of git repos and mcz files. We can change to the BaselineOf<OurInfrastructure> model, but this is not going to change much, I think. I still think that using ConfigurationOfZincHTTPComponents in BaselineOfSeaside30 could be a problem. We must find a way to use the "spec baseline: 'Zinc' with: ..." approach in BaselineOfSeaside30. Or am I missing it here? I have to dig a bit more in the Metacello scripting api and more recent stuff as I've been out of the loop a bit, so take my comments with a pinch of salt. I could be making our lives unnecessarily difficult here, so if you spot where I'm missing it, please let me know. Thanks for the feedback. Otto _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
----- Original Message ----- | From: "Otto Behrens" <[hidden email]> | To: "Johan Brichau" <[hidden email]> | Cc: [hidden email] | Sent: Thursday, November 14, 2013 10:34:06 PM | Subject: Re: [Glass] loading seaside and zinc | | > Instructions for installing Zinc on Gemstone are on github: | > https://github.com/glassdb/zinc | | Thanks, yes. But, firstly, we work from a cloned repository, which we | submodule under our main repo. This is because we like to pin the | version that works and upgrade explicitly when we need to. We do a | lot | of deploys / loads in a day and doing it via github every time is | expensive and not reliable. We are busy with an upgrade from GS 2 to | GS 3, which makes it a bit more complicated because we have to use | the | correct branch. This is cool, we'll do it. | | Secondly, we are trying to use Metacello to specify all our | dependencies in one place. We have a configuration to load all the | packages we use (from a local git repo) and one for all our own code. | Currently, the glass, seaside and whatever packages is a mix of git | repos and mcz files. We can change to the | BaselineOf<OurInfrastructure> model, but this is not going to change | much, I think. | | I still think that using ConfigurationOfZincHTTPComponents in | BaselineOfSeaside30 could be a problem. We must find a way to use the | "spec baseline: 'Zinc' with: ..." approach in BaselineOfSeaside30. Or | am I missing it here? Yes I think you are right about this ... however the `lock` api in Metacello is intended to address this kind of issue. The fact that the project names are different: ZincHTTPComponents vs. Zinc is a problem, but if we change the name of the baseline in github to match ZincHTTPComponents we can use the `lock` api ... Basically the `lock` api allows you to declare a particular projeect spec (project name, project version, project repository) should be used in all Metacello operations involving that project ... So you can declare that your local git repository for ZincHTTPComponents should be used always ... | | I have to dig a bit more in the Metacello scripting api and more | recent stuff as I've been out of the loop a bit, so take my comments | with a pinch of salt. Your use case is exactly why I invented the lock command ... you need to have complete control over which repositories get used in your project ... without having to edit (and take ownership) all of the configurations... | | I could be making our lives unnecessarily difficult here, so if you | spot where I'm missing it, please let me know. | | Thanks for the feedback. | | Otto | _______________________________________________ | Glass mailing list | [hidden email] | http://lists.gemtalksystems.com/mailman/listinfo/glass | _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
In reply to this post by Mariano Martinez Peck
Hi Mariano,
On 14 Nov 2013, at 22:06, Mariano Martinez Peck <[hidden email]> wrote: > What I did is I loaded latest GLASS and Metacello and then I did: > > Metacello new > baseline: 'Zinc'; > repository: 'github://glassdb/zinc:gemstone3.1/repository'; > load: 'Tests'. > Metacello new > configuration: 'Seaside3'; > repository: > 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > version: '3.0.9'; > load: #('Core' 'Zinc-Seaside') hm... I am suspicious here: this will load the Zinc-Seaside package from the Smalltalkhub repository, but that one does not contain the WAGsZincServerAdaptor In fact, where are you getting that class? If its from the seaside.gemstone.com/ZincHTTPComponents repository, I am also suspicious that it needs adapting because it was written for an older version of Zinc. I'm currently hacking on this... let me know if my assumptions are right. Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On Fri, Nov 15, 2013 at 5:49 PM, Johan Brichau <[hidden email]> wrote:
Hi Mariano, Hi Johan, my class WAGsZincAdaptor is being get from http://mc.stfx.eu/ZincHTTPComponents. As far as I remember I simply run the above script.
Where did it get from in your case? Thanks! _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On 15 Nov 2013, at 22:53, Mariano Martinez Peck <[hidden email]> wrote: > Hi Johan, my class WAGsZincAdaptor is being get from http://mc.stfx.eu/ZincHTTPComponents. > As far as I remember I simply run the above script. > Where did it get from in your case? Ok, I found it in http://seaside.gemtalksystems.com/ss/Seaside30 But it's not working with the latest Zinc version for gemstone (from github). I'm taking a look... Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
Seems like the requestUrlFor: methode override on WAGsZincAdaptor is the culprit.
If Paul is following this thread, he may perhaps comment on why that was done. However, right now, it sends a message that is not implemented. Simply removing that method from the class makes it work. On 15 Nov 2013, at 23:08, Johan Brichau <[hidden email]> wrote: > > On 15 Nov 2013, at 22:53, Mariano Martinez Peck <[hidden email]> wrote: > >> Hi Johan, my class WAGsZincAdaptor is being get from http://mc.stfx.eu/ZincHTTPComponents. >> As far as I remember I simply run the above script. >> Where did it get from in your case? > > Ok, I found it in http://seaside.gemtalksystems.com/ss/Seaside30 > But it's not working with the latest Zinc version for gemstone (from github). > > I'm taking a look... > > Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On Fri, Nov 15, 2013 at 7:30 PM, Johan Brichau <[hidden email]> wrote: Seems like the requestUrlFor: methode override on WAGsZincAdaptor is the culprit. Hi Johan, Yes, Dale found that as well. But even removing that method, and causing it to "work", I have found it quite unstable. I cannot explain why, but it didn't work well for me. It would hung very frequently (try raising errors from seaside and debug them). There was also an Internal Error that causes the kill of the gem that we suspect it was something with Zinc (because with Swazoo I don't have that problem anymore).
But maybe it works stable for you. Which GemStone version are you using? Mine is 3.1.0.4. Cheers,
Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On 15 Nov 2013, at 23:34, Mariano Martinez Peck <[hidden email]> wrote: > Yes, Dale found that as well. Ha... I probably missed some emails :-/ > But even removing that method, and causing it to "work", I have found it quite unstable. I cannot explain why, but it didn't work well for me. It would hung very frequently (try raising errors from seaside and debug them). There was also an Internal Error that causes the kill of the gem that we suspect it was something with Zinc (because with Swazoo I don't have that problem anymore). Did you test with the adaptor running in another gem or did you use the adaptor right from gemtools (the 'blocking' start one) ? > But maybe it works stable for you. Which GemStone version are you using? Mine is 3.1.0.4. I'm on 2.4.4.1 right now. As I understand it, there are some differences with gemstone 3.1 so if I cannot make it crash, I will move over to a 3.1 We'll see where we end up ;-) Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
Yes, the long term goal is to get the zinc server-side code running reliably in GemStone ...
Dale ----- Original Message ----- | From: "Johan Brichau" <[hidden email]> | To: "Mariano Martinez Peck" <[hidden email]> | Cc: [hidden email] | Sent: Friday, November 15, 2013 2:38:29 PM | Subject: Re: [Glass] loading seaside and zinc | | | On 15 Nov 2013, at 23:34, Mariano Martinez Peck | <[hidden email]> wrote: | | > Yes, Dale found that as well. | | Ha... I probably missed some emails :-/ | | > But even removing that method, and causing it to "work", I have | > found it quite unstable. I cannot explain why, but it didn't work | > well for me. It would hung very frequently (try raising errors | > from seaside and debug them). There was also an Internal Error | > that causes the kill of the gem that we suspect it was something | > with Zinc (because with Swazoo I don't have that problem anymore). | | Did you test with the adaptor running in another gem or did you use | the adaptor right from gemtools (the 'blocking' start one) ? | | > But maybe it works stable for you. Which GemStone version are you | > using? Mine is 3.1.0.4. | | I'm on 2.4.4.1 right now. | As I understand it, there are some differences with gemstone 3.1 so | if I cannot make it crash, I will move over to a 3.1 | | We'll see where we end up ;-) | | Johan | _______________________________________________ | Glass mailing list | [hidden email] | http://lists.gemtalksystems.com/mailman/listinfo/glass | _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
In reply to this post by Johan Brichau-3
On Fri, Nov 15, 2013 at 7:38 PM, Johan Brichau <[hidden email]> wrote:
hehehhehe
I launched it from GemTools itself, so yes, the blocking one. BTW...with your magic lines to start Swazoo...that doens't block!! It works perfect. Why it doesn't block that one while Zinc does? It open another gem or something?
Ok, cool. In the meanwhile I continue using Swazoo that for my current needs (start porting) works fine. If there is anything I could do/test, let me know!
Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] loading seaside and zinc
|
|
On 16 Nov 2013, at 00:07, Mariano Martinez Peck <[hidden email]> wrote: > BTW...with your magic lines to start Swazoo...that doens't block!! It works perfect. Why it doesn't block that one while Zinc does? It open another gem or something? No magic and not mine :-) Just gemstone multi-vm. So yes, it actually invokes the command-line scripts that start other topaz processes where the blocking call to the adaptor happens. You can take a look at the startSeaside30Adaptor script in the $gemstone/product/seaside/bin directory > Ok, cool. In the meanwhile I continue using Swazoo that for my current needs (start porting) works fine. > If there is anything I could do/test, let me know! When an error is raised inside the app, the adaptor indeed crashes. The funny thing is that the handleRequest: method returns a WAResponse class instead of an instance. I have to digg deeper to understand where that happens but it is the same error that I got before removing the #requestFor: method. It seems that an error occurs deeper in the code that is handled and then the WAResponse class is returned as a value... Johan _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |