On Jun 26, 2012 6:13 AM, "Rupert Westenthaler" < [email protected]> wrote: > > Hi > > On 25.06.2012, at 21:26, Reto Bachmann-Gmür wrote: > > > > Similar here, but given that stanbol needs normally to be started (as per > > the recomenation on the website) with 1g of heap space, what's the problem > > with increasing PermGenSpace to 256Mb? > > > > Did you happen to see which bundle uses such a lot of PermGenSpace? > > > > I was not able to find a way to split up the PermGen usage > by package. One can only see about 10 different categories > that are not specific to bundles. > > The increate of the PermGen is not specific to a specific category. So > using java VisualVM there seams to be no possibility to further inspect > what is causing this. > > Regarding Heap: > > The initial heap size of the full launcher is about 200MByte. During the > integration-tests the heap is stable by about 250MByte. > The max Heap size is set to 556 for the Integration test.
The building and running instructions on the websie suggests 1 GB for running. So I think this confirms that having a low memory footprint is not a main goal of the full launcher, as long of course as there is no leak that would affect stability. Cheers, Reto > > > best > Rupert > > > > > Cheers, > > Reto > > > > > >> > >> WDYT > >> Rupert > >> > >> On Mon, Jun 25, 2012 at 9:07 AM, Reto Bachmann-Gmür <[email protected]> > >> wrote: > >>> On Jun 24, 2012 11:13 PM, "Fabian Christ" < [email protected]> > >>> wrote: > >>>> > >>>> Hi, > >>>> > >>>> cool. So this is something that can be used, e.g. for live debugging > >>>> in the console > >>> > >>> You can interactively play around with the exposed java api and the > >>> available services. This can well be used in combination with a debugger > >>> allowing to be more quickly at a breakpoint (by calling the service > >> method > >>> right away, skipping the web request). > >>> > >>>> and making changes that are directly applied? > >>> > >>> No, it is by itself not a tool to modify existing code. You could write > >>> classes, instantiate them and register them as services all on the > >> console. > >>> But as these classes are not persitence this is mainly of use for testing > >>> purposes. > >>> > >>>> > >>>> Best, > >>>> - Fabian > >>>> > >>>> 2012/6/22 Reto Bachmann-Gmür <[email protected]>: > >>>>> Hi > >>>>> > >>>>> I've resolved STANBOL-312 and added the ssh accessible and scala based > >>>>> clerezza shell to stanbol. > >>>>> > >>>>> The bad news first: on my machine the additional bundles caused the > >> jvm > >>> to > >>>>> require more permsize than its default, so I hat to launch with the > >>>>> -XX:MaxPermSize=256m vm option. > >>>>> > >>>>> The ssh daemon is listening on port 8022 (this can of course be > >> changed > >>> via > >>>>> service property), to connect to it use: > >>>>> > >>>>> ssh -p 8022 admin@localhost > >>>>> > >>>>> the default pwd for the admin user is "admin" > >>>>> > >>>>> Once connected you have a full scala console with access to the OSGi > >>>>> service registry. To get an instance of a service you can use the > >>>>> $[<className>] shortcut, for example: > >>>>> > >>>>> zz>import org.apache.stanbol.enhancer.servicesapi._ > >>>>> zz>val jm = $[EnhancementJobManager] > >>>>> > >>>>> jm now point to an EnhancementJobManager instance, you can use the tab > >>> key > >>>>> to find the methods than can be invoked on an object: > >>>>> > >>>>> zz>jm. > >>>>> asInstanceOf enhanceContent getActiveEngines isInstanceOf > >>>>> toString > >>>>> > >>>>> I hope this is of use. > >>>>> > >>>>> Reto > >>>> > >>>> > >>>> > >>>> -- > >>>> Fabian > >>>> http://twitter.com/fctwitt > >> > >> > >> > >> -- > >> | Rupert Westenthaler [email protected] > >> | Bodenlehenstraße 11 ++43-699-11108907 > >> | A-5500 Bischofshofen > >> >
