You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2011/01/02 16:44:45 UTC
[jira] Created: (CLEREZZA-382) Use a TDB optimizer and get rid of
warning when starting clerezza
Use a TDB optimizer and get rid of warning when starting clerezza
-----------------------------------------------------------------
Key: CLEREZZA-382
URL: https://issues.apache.org/jira/browse/CLEREZZA-382
Project: Clerezza
Issue Type: Improvement
Reporter: Reto Bachmann-Gmür
Assignee: Reto Bachmann-Gmür
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-382) Use a TDB optimizer and get rid of
warning when starting clerezza
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976538#action_12976538 ]
Reto Bachmann-Gmür commented on CLEREZZA-382:
---------------------------------------------
it turns out that enabling optimizer was easier than getting rid of wrong directed log output...
> Use a TDB optimizer and get rid of warning when starting clerezza
> -----------------------------------------------------------------
>
> Key: CLEREZZA-382
> URL: https://issues.apache.org/jira/browse/CLEREZZA-382
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-382) Use a TDB optimizer and get rid of
warning when starting clerezza
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976539#action_12976539 ]
Reto Bachmann-Gmür commented on CLEREZZA-382:
---------------------------------------------
Tried removing log4j from the jars included into the ext.tdb bundle. now it fails because of an unavailable log4j.LogManager. Reporducible on the command line:
zz>import org.apache.log4j.LogManager
import org.apache.log4j.LogManager
zz>new LogManager
console terminated
org.apache.clerezza.shell.Shell$$anon$1@17c5b480: caught java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
at java.lang.Class.getMethod0(Class.java:2687)
at java.lang.Class.getMethod(Class.java:1620)
at scala.tools.nsc.Interpreter$Request.loadAndRun(Interpreter.scala:965)
at scala.tools.nsc.Interpreter.loadAndRunReq$1(Interpreter.scala:578)
at scala.tools.nsc.Interpreter.interpret(Interpreter.scala:597)
at scala.tools.nsc.Interpreter.interpret(Interpreter.scala:575)
at scala.tools.nsc.InterpreterLoop.reallyInterpret$1(InterpreterLoop.scala:471)
at scala.tools.nsc.InterpreterLoop.interpretStartingWith(InterpreterLoop.scala:514)
at scala.tools.nsc.InterpreterLoop.command(InterpreterLoop.scala:361)
at scala.tools.nsc.InterpreterLoop.processLine$1(InterpreterLoop.scala:242)
at scala.tools.nsc.InterpreterLoop.repl(InterpreterLoop.scala:248)
at org.apache.clerezza.shell.Shell$$anon$2.main(Shell.scala:161)
at scala.tools.nsc.InterpreterLoop.main(InterpreterLoop.scala:609)
at org.apache.clerezza.shell.Shell$$anon$1.act(Shell.scala:182)
at scala.actors.Reactor$$anonfun$dostart$1.apply(Reactor.scala:222)
at scala.actors.Reactor$$anonfun$dostart$1.apply(Reactor.scala:222)
at scala.actors.ReactorTask.run(ReactorTask.scala:36)
at scala.concurrent.forkjoin.ForkJoinPool$AdaptedRunnable.exec(ForkJoinPool.java:611)
at scala.concurrent.forkjoin.ForkJoinTask.quietlyExec(ForkJoinTask.java:422)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.mainLoop(ForkJoinWorkerThread.java:340)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:325)
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.LogManager
at scala.tools.nsc.interpreter.AbstractFileClassLoader.onull$1(AbstractFileClassLoader.scala:21)
at scala.tools.nsc.interpreter.AbstractFileClassLoader$$anonfun$getBytesForClass$1.apply(AbstractFileClassLoader.scala:26)
at scala.tools.nsc.interpreter.AbstractFileClassLoader$$anonfun$getBytesForClass$1.apply(AbstractFileClassLoader.scala:25)
at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:61)
at scala.collection.immutable.List.foreach(List.scala:45)
at scala.tools.nsc.interpreter.AbstractFileClassLoader.getBytesForClass(AbstractFileClassLoader.scala:25)
at scala.tools.nsc.interpreter.AbstractFileClassLoader.findClass(AbstractFileClassLoader.scala:33)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at scala.tools.nsc.interpreter.AbstractFileClassLoader.scala$tools$nsc$util$ScalaClassLoader$$super$loadClass(AbstractFileClassLoader.scala:16)
at scala.tools.nsc.util.ScalaClassLoader$class.loadClass(ScalaClassLoader.scala:57)
at scala.tools.nsc.interpreter.AbstractFileClassLoader.loadClass(AbstractFileClassLoader.scala:16)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 23 more
> Use a TDB optimizer and get rid of warning when starting clerezza
> -----------------------------------------------------------------
>
> Key: CLEREZZA-382
> URL: https://issues.apache.org/jira/browse/CLEREZZA-382
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CLEREZZA-382) Use a TDB optimizer and get rid of
warning when starting clerezza
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-382.
---------------------------------------
Resolution: Fixed
> Use a TDB optimizer and get rid of warning when starting clerezza
> -----------------------------------------------------------------
>
> Key: CLEREZZA-382
> URL: https://issues.apache.org/jira/browse/CLEREZZA-382
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
> WARN [SCR Component Actor] (SetupTDB.java:755) - No BGP optimizer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.