On 25/04/2013 19:37, MJ wrote:
I set maxpermsize and it looks a lot better, thanks.
[...]
WARNING: The following warnings have been detected with resource and/or
provider classes:
WARNING: A HTTP GET method, public void
org.apache.clerezza.platform.security.permissioncheck.PermissionCheck.checkPermission(java.lang.String),
MUST return a non-void type.
Apr 25, 2013 9:32:51 PM
com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.15 10/30/2012 02:40 PM'
Apr 25, 2013 9:32:52 PM com.sun.jersey.spi.inject.Errors processErrorMessages
WARNING: The following warnings have been detected with resource and/or
provider classes:
WARNING: A HTTP GET method, public void
org.apache.clerezza.platform.security.permissioncheck.PermissionCheck.checkPermission(java.lang.String),
MUST return a non-void type.
25.04.2013 21:32:52.696 *INFO * [main] Startup completed
Is this warning serious?
That would be for the security manager people to say. I cannot even see
what component is causing these warnings.
I do remember the security manager was blocking some OWL API HTTP calls
and temporary file creations, so if you're using the Ontology Manager it
might refuse to load ontologies. If you do, you may also want to pass
"-no-security" as a Stanbol launch param (but I'm opening a can of worms
here).
There's a chance it was fixed by then, though.
Best,
Alessandro
On Apr 25, 2013, at 9:15 PM, Alessandro Adamou <ada...@cs.unibo.it> wrote:
Launched fine here on r1475855 and the following environment
Maven 3.0.4
OpenJDK 1.6.0_24 i386
CrunchBang Linux i386 kernel 3.2.0-4-686-pae
...but before we investigate further: are those all the arguments you've set
for your JVM/Stanbol?
did you ever set the permanent generation size? The default is not enough for
the full launcher. If you did not set it, it might just by chance have gone out
of memory at the time of activating the ontologymanager.servicesapi bundle.
Try also to pass
-XX:MaxPermSize=192m
alongside the max heap ( -Xmx)
IIRC from my VisualVM benchmarks, 192 megabytes is kind of a borderline value
for the full launcher. If it is not enough, try 256m or 320m but try to be
conservative. If you are not activating additional custom bundles, you won't
need a larger permanent generation than the one necessary for getting Stanbol
running.
Best,
Alessandro
On 25/04/2013 18:02, Alessandro Adamou wrote:
That's odd. Let me try a fresh rebuild/launch.
Alessandro
On 25/04/2013 18:00, MJ wrote:
Hi,
I searched the mailing list archives, but didn't find any useful tips to
resolve my problem.
I built the subversion snapshot using Maven 3 and Sun JDK 1.7 on FreeBSD using
Linux emulation layer. I tried to run with Sun JDK, but alas
KqueueSelectorProvider is non-existent, so I switched to running with OpenJDK
since I really need the event-based I/O.
Anyhow, I tried starting Stanbol with Sun JDK 1.7, OpenJDK 1.6, and OpenJDK
1.7, all with exactly the same problem.
The startup command line:
/usr/local/openjdk7/bin/java -Xmx1g -jar
/usr/local/infra/stanbol-svn/launchers/full/target/org.apache.stanbol.launchers.full-0.10.0-SNAPSHOT.jar
The problem:
ERROR: Bundle org.apache.stanbol.enhancer.engines.refactor [40]: Error starting
slinginstall:org.apache.stanbol.enhancer.engines.refactor-0.10.0-SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.stanbol.enhancer.engines.refactor [40]: Unable to resolve 40.0: missing
requirement [40.0] package;
(&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.0)(!(version>=1.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.stanbol.enhancer.engines.refactor [40]: Unable to resolve 40.0: missing
requirement [40.0] package;
(&(package=org.apache.stanbol.ontologymanager.servicesapi.collector)(version>=0.10.0)(!(version>=1.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:722)
25.04.2013 19:42:16.289 *INFO * [main] Startup completed
I would be highly appreciative if somebody would advise me on how to get the
Ontology Manager going. The Ontology Manager is actually the most important
reason for my using Stanbol.
Thank you,
Mike
--
Alessandro Adamou, Ph.D.
Knowledge Media Institute
The Open University
Walton Hall, Milton Keynes MK7 6AA
United Kingdom
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna
Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
--
Alessandro Adamou, Ph.D.
Knowledge Media Institute
The Open University
Walton Hall, Milton Keynes MK7 6AA
United Kingdom
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna
Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
