Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DF1E99E1A for ; Tue, 20 Dec 2011 19:07:01 +0000 (UTC) Received: (qmail 32300 invoked by uid 500); 20 Dec 2011 19:07:01 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 32255 invoked by uid 500); 20 Dec 2011 19:07:01 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 32248 invoked by uid 99); 20 Dec 2011 19:07:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 19:07:01 +0000 X-ASF-Spam-Status: No, hits=3.5 required=5.0 tests=HTML_MESSAGE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.136.44.57] (HELO smtp102.prem.mail.sp1.yahoo.com) (98.136.44.57) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 20 Dec 2011 19:06:54 +0000 Received: (qmail 34989 invoked from network); 20 Dec 2011 19:06:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=rD0gU9GYifPPFU5llKwqP4oQskTvS1ycLAiI9Let35ciYqw9FkGXgOgUgP+60JwxECnYL7Iu+A6aaLR5lB5D/IfnQMtniY10dZI5IsAWJkoRP91Y48KYg7KJ3n1GiJIF29h0fvfFhzbVauyVRpa7m8P19tT82+xZ0n79e8hN7TU= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1324407991; bh=zv+o+o7z4i6TcmvopBIRD7vgykpZRGypS1Yqh9bGXsc=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=5egk/VhnAnnU65pKOEmS/rkp9PIGsaj1MxFRYJpECel82/eMVKFXPlYAzhg11YDkgSbs70p32priMxfz7kLCcnwUrsY636ruMNbz42X+ntmxG8hbF7vDlRHVQKF7P84fGPBsYSCO4WiWhtA/BFkADlwLlAJJ3/C0XC86OaZ8w58= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: cHFseX4VM1naOo57ZwJ1oV3d0QJdqPEA_9b966cIPek4JA9 2TVUwzV_Y.y.XvpB0C5VPcRM59tACUHI.uw1U2D8qhyZpR0Z3ZIMbZuyE5cD sMJU3XmWIMQKlHC8OH.ninOHQXAS1EE.DPVDYZEA3e33H5Qqi2b6X7jqjaCk bHkMn.1Tgvh3Kr0x84GWB1XTWweyzV6eTMotR_qUt9G_TIIIGjb596qt7JfV NJAbNUeO.LCQRDT5hedTeLpgKsA5fuL6jiHUqPU7lyvnQ7eA3PrtnnmAdxFA 0pY.ZqaO51H4vecAkC94Xmfj6CNPiEgkP9RAq1LjXsqtmGTIHwSk80Zt2IYw 1e1lFjBaGlzhohTZazlceZI.PkPZnzODm56QGPAltWzc6jyT2F7f6RGtupRv BlxhFEyqRDNx1xvxIUm9cGIJG3TNCwXElmV1uKBrEF2_g2GDykbN7NWhVv5E i7xO7uWh_HdXzyjFlIVl1Q3f.D.oyp2eb6Q44TUyDov8te4gPC.LzxS_8LE4 SmbfJoNtHWeTvSP958ED4GjoL28gj1JMIwhcgSi1E1a7KjOHVJtG.dgA5CWN ulu7V.rrtTdIofwn4M617hIbPIg_G9TofuiAL3l7VZeyaDYTGuBiru_vrPgM BinDjlBE8WVMd_7BIbWgSDZxi_TxfmKUqNMCJti9Jbxcz2hKan8UnpTIWjtx sGTjKaUPdR.pxOXotd0wSZD487Lf5oef5Nz24FZc16Zl3Tj_mVZpqV.CD73J I6Q-- X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ-- Received: from [10.0.1.4] (david_jencks@98.246.196.64 with plain) by smtp102.prem.mail.sp1.yahoo.com with SMTP; 20 Dec 2011 11:06:31 -0800 PST From: David Jencks Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-2-355923949 Subject: Re: Geronimo 3 and karaf 3 Date: Tue, 20 Dec 2011 11:06:31 -0800 In-Reply-To: <74DEC439-60C9-488B-9A96-71AFBA25F734@yahoo.com> To: dev@geronimo.apache.org References: <4A5E63D9-87FB-4408-8BA3-440D757A3A70@yahoo.com> <74DEC439-60C9-488B-9A96-71AFBA25F734@yahoo.com> Message-Id: <00692F05-4BEA-4272-B11B-A04969583159@yahoo.com> X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-2-355923949 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii BTW, to get the regions/isolation stuff working I think we are going to = need to replace our use of BundleListener/SynchronousBundleListener with = the (updated-for-4.3) aries RecursiveBundleTracker. I think we'll need = also change from ConfigurationActivator to an extender pattern. I'd = guess the ConfigurationActivator functionality could be moved to = DependencyManager rather than having an additional tracker. thanks david jencks On Dec 20, 2011, at 10:13 AM, David Jencks wrote: > OK, I just committed this stuff, with reference to GERONIMO-6240. >=20 > Some more hints.... >=20 > I can build all the way through with=20 > MAVEN_OPTS=3D"-XX:MaxPermSize=3D2048m -Xms2048m -Xmx4096m" >=20 > I can start karaf after setting >=20 > export JAVA_MAX_MEM=3D2048m > export JAVA_MAX_PERM_MEM=3D512m >=20 > The car packaging is set up to stop and wait if it gets stuck. In an = earlier version of this you'd get the karaf console and you could use = karaf commands to investigate what was going on. For some reason this = isn't working now. If you get into this situation, you need to kill the = maven java process some way. Usually setting a breakpoint at = DependencyManager line 571 will show you a bundle that has a resolution = problem that you can then fix. >=20 > The problem with the console deploy-type commands I think relates to = using the karaf RMIRegistry. I'm going to modify it so it includes the = port as a service property, then we can look for the osgi service and = get its port instead of the port gbean attribute. >=20 > thanks > david jencks >=20 > On Dec 19, 2011, at 9:10 PM, David Jencks wrote: >=20 >> more not-yet-working inline >>=20 >> On Dec 19, 2011, at 5:08 PM, David Jencks wrote: >>=20 >>> I've been spending a lot of time working to rebase geronimo on karaf = 3 so we can have a maintainable future and get stuff like osgi 4.3, up = to date aries components, and the experimental region support now in = karaf. >>>=20 >>> After a lot of work I have everything except clustering building and = after turning off a couple problematic modules the tomcat-javaee6 server = starts and the web admin console appears to work at least a little bit. = I'd like a little vacation this year and would like to commit this work = first so that others can help with the loose ends if they like. I'll = probably be around to answer questions in any case. >>>=20 >>> The modules that don't start are: >>>=20 >>> activemq-broker-blueprint. The ${X + Y} stuff is not getting = evaluated at all. I don't know if this is an xbean-blueprint problem or = an aries blueprint problem or a side effect of running in geronimo. >>> As a result activemq-ra and tomcat-console-activemq can't be = started. >>>=20 >>> client-deployer. I think this is a pretty simple gbean name problem = but I haven't looked into it. >>>=20 >>>=20 >>> Here are some of the changes: >>>=20 >>> -- assemble the server using a combination of karaf assembly from = features and kars and geronimo assembly from geronimo plugins. We now = use the same base karaf assembly stuff as the normal default full karaf = assembly (except I might have left out the spring feature repository). >>>=20 >>> -- basic geronimo components such as the kernel, configuration = manager, dependency manager, deployer, and service config builder are = set up as osgi declarative services so they start without any geronimo = configuration. They are generally configured through config admin as = appropriate. Most of these also have gbean wrappers so they can be = accessed through gbean references. >>>=20 >>> -- "geronimo" is started from a DS component, EmbeddedDaemon. >>>=20 >>> -- I think I'm using the karaf remote jmx security rather than ours. = The capabilities are similar but not identical. >>>=20 >>> Some other things that are not working yet: >>>=20 >>> -- The (gogo) geronimo console commands that work through "remote" = gbean proxies don't work AFAIK. Probably one way to fix this would be = to expose some more of the DS components using gbean wrappers, but I = haven't looked into this yet. >>>=20 >>> -- the app client (as well as the client-deployer) is not working = yet at all. We may be able to use command line args to tell the = EmbeddedDaemon it's an app client, or possibly not. We may be able to = use a karaf instance to supply different ConfigAdmin settings to e.g. = the local attribute manager to convince it it's an app client. = Similarly the separate console-like things presumably won't work either. >>>=20 >>> -- the EditableConfigurationManager needs to be replaced by a = separate component that edits the configuration it gets from the normal = configuration manager. I think this affects some part of the admin = console. >>=20 >> --I couldn't get the xml stream 1.2 and jaxb 2.2 to work with the = spec jars as bundles. According to = http://servicemix.396122.n5.nabble.com/DISCUSS-Enhance-specs-to-work-bette= r-with-JRE-td5001108.html even if you do get them to work (as we seem to = have up to now by not exposing the packages from the framework) that = breaks other stuff. I think we need to investigate the karaf-activator = stuff guillaume wrote and adapt our specs to use it. At the moment I = have the framework lying and claiming later versions for the xmlstream = and jaxb packages. I haven't found any documentation for = karaf-activator yet. >>=20 >> -- the build uses a lot more memory. I typically run out of permgen = twice during the build with MAVEN_OPTS =3D -XX:MaxPermSize=3D512m = -Xms1024m -Xmx2048m >>=20 >> -- startup AFAIK only works as ./bin/karaf -l rather than our = geronimo scripts. Again, I have to increase memory settings for the = server to fully start. >>=20 >>>=20 >>>=20 >>> I'f there's no strong opposition I'd like to commit this tomorrow. >>>=20 >>> Many thanks >>> david jencks >>>=20 >>=20 >> david jencks >=20 --Apple-Mail-2-355923949 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii BTW, = to get the regions/isolation stuff working I think we are going to need = to replace our use of BundleListener/SynchronousBundleListener with the = (updated-for-4.3) aries RecursiveBundleTracker.  I think we'll need = also change from ConfigurationActivator to an extender pattern. =  I'd guess the ConfigurationActivator functionality could be moved = to DependencyManager rather than having an additional = tracker.

thanks
david = jencks

On Dec 20, 2011, at 10:13 AM, David = Jencks wrote:

OK, I just committed = this stuff, with reference to GERONIMO-6240= .

Some more hints....

I = can build all the way through = with 
MAVEN_OPTS=3D"-XX:MaxPermSize=3D2048m = -Xms2048m -Xmx4096m"

I can start karaf = after setting

export = JAVA_MAX_MEM=3D2048m
export = JAVA_MAX_PERM_MEM=3D512m

The car packaging is = set up to stop and wait if it gets stuck.  In an earlier version of = this you'd get the karaf console and you could use karaf commands to = investigate what was going on.  For some reason this isn't working = now.  If you get into this situation, you need to kill the maven = java process some way.  Usually setting a breakpoint at = DependencyManager line 571 will show you a bundle that has a resolution = problem that you can then fix.

The problem with = the console deploy-type commands I think relates to using the karaf = RMIRegistry.  I'm going to modify it so it includes the port as a = service property, then we can look for the osgi service and get its port = instead of the port gbean = attribute.

thanks
david = jencks

On Dec 19, 2011, at 9:10 PM, David Jencks = wrote:

more not-yet-working inline

On Dec 19, 2011, = at 5:08 PM, David Jencks wrote:

I've = been spending a lot of time working to rebase geronimo on karaf 3 so we = can have a maintainable future and get stuff like osgi 4.3, up to date = aries components, and the experimental region support now in = karaf.

After a lot of = work I have everything except clustering building and after turning off = a couple problematic modules the tomcat-javaee6 server starts and the = web admin console appears to work at least a little bit.   I'd = like a little vacation this year and would like to commit this work = first so that others can help with the loose ends if they like. =  I'll probably be around to answer questions in any = case.

The modules = that don't start are:

activemq-broker-blueprint.  The ${X + Y} stuff is not = getting evaluated at all.  I don't know if this is an = xbean-blueprint problem or an aries blueprint problem or a side effect = of running in geronimo.
As a = result activemq-ra and tomcat-console-activemq can't be = started.

client-deployer. =  I think this is a pretty simple gbean name problem but I haven't = looked into it.


Here are some = of the changes:

-- assemble the = server using a combination of karaf assembly from features and kars and = geronimo assembly from geronimo plugins.  We now use the same base = karaf assembly stuff as the normal default full karaf assembly (except I = might have left out the spring feature = repository).

-- basic = geronimo components such as the kernel, configuration manager, = dependency manager, deployer, and service config builder are set up as = osgi declarative services so they start without any geronimo = configuration.  They are generally configured through config admin = as appropriate.  Most of these also have gbean wrappers so they can = be accessed through gbean references.

-- "geronimo" = is started from a DS component, = EmbeddedDaemon.

-- I think I'm = using the karaf remote jmx security rather than ours.  The = capabilities are similar but not identical.

Some other = things that are not working yet:

-- The (gogo) = geronimo console commands that work through "remote" gbean proxies don't = work AFAIK.  Probably one way to fix this would be to expose some = more of the DS components using gbean wrappers, but I haven't looked = into this yet.

-- the app = client (as well as the client-deployer) is not working yet at all. =  We may be able to use command line args to tell the EmbeddedDaemon = it's an app client, or possibly not.  We may be able to use a karaf = instance to supply different ConfigAdmin settings to e.g. the local = attribute manager to convince it it's an app client.  Similarly the = separate console-like things presumably won't work = either.

-- the = EditableConfigurationManager needs to be replaced by a separate = component that edits the configuration it gets from the normal = configuration manager.  I think this affects some part of the admin = console.

--I couldn't get the xml stream 1.2 and = jaxb 2.2 to work with the spec jars as bundles. =    According to http://servicemix.396122.n5.nabble.com/= DISCUSS-Enhance-specs-to-work-better-with-JRE-td5001108.html even if = you do get them to work (as we seem to have up to now by not exposing = the packages from the framework) that breaks other stuff.  I think = we need to investigate the karaf-activator stuff guillaume wrote and = adapt our specs to use it.  At the moment I have the framework = lying and claiming later versions for the xmlstream and jaxb packages. =  I haven't found any documentation for karaf-activator = yet.

-- the build uses a lot more memory.  I typically run = out of permgen twice during the build with MAVEN_OPTS =3D =  -XX:MaxPermSize=3D512m -Xms1024m -Xmx2048m

-- startup AFAIK = only works as ./bin/karaf -l rather than our geronimo scripts. =  Again, I have to increase memory settings for the server to fully = start.



I'f there's no = strong opposition I'd like to commit this = tomorrow.

Many = thanks
david = jencks


david = jencks


= --Apple-Mail-2-355923949--