JBoss Branch_5_x fails to boot
by Radoslav Husar
Hello, I am using the following command to bootup JBAS but getting the
output below. Any idea? I noticed this happening after Thursday (after
the Hudson problem we had then...). Cheers.
java -server -Xms256m -Xmx768m -XX:MaxPermSize=256m
-XX:+PrintGCTimeStamps -XX:+PrintGCDetails
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djgroups.udp.ip_ttl=1
-Djava.net.preferIPv4Stack=true -Djboss.messaging.ServerPeerID=0 -jar
bin/run.jar -c all -b perf01 -Djboss.partition.name=SoakTestPartition
-Dcluster.route.name=perf01 -u 234.1.79.89
Output:
17:29:48,243 INFO [ServerImpl] Starting JBoss (Microcontainer)...
17:29:48,244 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1
(build: SVNTag=JBoss_5_1_0_CR1 date=200904151444)
17:29:48,245 INFO [ServerImpl] Bootstrap URL: null
17:29:48,245 INFO [ServerImpl] Home Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1
17:29:48,245 INFO [ServerImpl] Home URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/
17:29:48,245 INFO [ServerImpl] Library URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/lib/
17:29:48,246 INFO [ServerImpl] Patch URL: null
17:29:48,246 INFO [ServerImpl] Common Base URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/common/
17:29:48,246 INFO [ServerImpl] Common Library URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/common/lib/
17:29:48,246 INFO [ServerImpl] Server Name: all
17:29:48,247 INFO [ServerImpl] Server Base Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server
17:29:48,247 INFO [ServerImpl] Server Base URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/
17:29:48,247 INFO [ServerImpl] Server Config URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/conf/
17:29:48,247 INFO [ServerImpl] Server Home Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all
17:29:48,247 INFO [ServerImpl] Server Home URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/
17:29:48,247 INFO [ServerImpl] Server Data Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/data
17:29:48,248 INFO [ServerImpl] Server Library URL:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/lib/
17:29:48,248 INFO [ServerImpl] Server Log Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/log
17:29:48,248 INFO [ServerImpl] Server Native Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/tmp/native
17:29:48,248 INFO [ServerImpl] Server Temp Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/tmp
17:29:48,248 INFO [ServerImpl] Server Temp Deploy Dir:
/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/tmp/deploy
17:29:49,685 INFO [ServerImpl] Starting Microcontainer,
bootstrapURL=file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/conf/bootstrap.xml
3.330: [GC [PSYoungGen: 23040K->1383K(26880K)] 23040K->1383K(260352K),
0.0153472 secs] [Times: user=0.02 sys=0.01, real=0.02 secs]
Failed to boot JBoss:
org.jboss.xb.binding.JBossXBException: Failed to parse source:
file:/export/home/rhusar/svn/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/conf/bootstrap/vfs.xml@13,37
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177)
at
org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147)
at
org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:150)
at
org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)
at org.jboss.Main.boot(Main.java:216)
at org.jboss.Main$1.run(Main.java:546)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBRuntimeException:
{urn:jboss:bean-deployer:2.0}property cannot appear in this position.
Expected content of {urn:jboss:bean-deployer:2.0}bean is sequence:
{urn:jboss:bean-deployer:2.0}alias*
{urn:jboss:bean-deployer:2.0}related-class*
{urn:jboss:bean-deployer:2.0}annotation*
{urn:jboss:bean-deployer:2.0}classloader?
{urn:jboss:bean-deployer:2.0}constructor?
{urn:jboss:bean-deployer:2.0}property*
{urn:jboss:bean-deployer:2.0}create? {urn:jboss:bean-deployer:2.0}start?
{urn:jboss:bean-deployer:2.0}stop? {urn:jboss:bean-deployer:2.0}destroy?
{urn:jboss:bean-deployer:2.0}depends*
{urn:jboss:bean-deployer:2.0}demand*
{urn:jboss:bean-deployer:2.0}supply*
{urn:jboss:bean-deployer:2.0}install*
{urn:jboss:bean-deployer:2.0}uninstall*
{urn:jboss:bean-deployer:2.0}incallback*
{urn:jboss:bean-deployer:2.0}uncallback*
at
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:494)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173)
... 7 more
17:29:50,761 INFO [ServerImpl] Runtime shutdown hook called, forceHalt:
true
17:29:50,783 INFO [ServerImpl] Shutdown complete
PS:
$ java -version
java version "1.6.0_10"
Java(TM) Platform, Standard Edition for Business (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
--
Radoslav Husar
IRC irc.devel.redhat.com at #brno #jboss #jbossqa
http://intranet.corp.redhat.com/ic/intranet/RadoslavHusar.html
15 years, 8 months
weird 5.1.x compile error
by Dimitris Andreadis
Anyone else seeing this???
X:\svn\jboss-5.x\build>java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode)
[...]
======================================================================
== Executing 'most' in module 'tomcat'...
==
_buildmagic:init:
configure:
init:
_buildmagic:build-bypass-checker:
_buildmagic:build-bypass-notice:
_buildmagic:build-bypass-check:
jars:
_buildmagic:init:
init:
compile-classes:
[javac] Compiling 12 source files to X:\svn\jboss-5.x\tomcat\output\classes
An exception has occurred in the compiler (1.5.0_16). Please file a bug at the J
ava Developer Connection (http://java.sun.com/webapps/bugreport) after checking
the Bug Parade for duplicates. Include your program and the following diagnosti
c in your report. Thank you.
java.lang.AssertionError: com.sun.tools.javac.jvm.Gen$1ComplexityScanner
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.visitTypeArgument(Gen.
java:1559)
at com.sun.tools.javac.tree.Tree$TypeArgument.accept(Tree.java:1085)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitTypeApply(TreeScanner.java:
252)
at com.sun.tools.javac.tree.Tree$TypeApply.accept(Tree.java:1058)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitTypeApply(TreeScanner.java:
252)
at com.sun.tools.javac.tree.Tree$TypeApply.accept(Tree.java:1058)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.visitVarDef(TreeScanner.java:78)
at com.sun.tools.javac.tree.Tree$VarDef.accept(Tree.java:507)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitBlock(TreeScanner.java:86)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.visitForLoop(TreeScanner.java:10
3)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.visitForLoop(Gen.java:
1497)
at com.sun.tools.javac.tree.Tree$ForLoop.accept(Tree.java:581)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitBlock(TreeScanner.java:86)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.visitIf(TreeScanner.java:150)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.visitIf(Gen.java:1512)
at com.sun.tools.javac.tree.Tree$If.accept(Tree.java:715)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitBlock(TreeScanner.java:86)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.visitIf(TreeScanner.java:151)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.visitIf(Gen.java:1512)
at com.sun.tools.javac.tree.Tree$If.accept(Tree.java:715)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitBlock(TreeScanner.java:86)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.visitTry(TreeScanner.java:132)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.visitTry(Gen.java:1505
)
at com.sun.tools.javac.tree.Tree$Try.accept(Tree.java:669)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:34)
at com.sun.tools.javac.jvm.Gen$1ComplexityScanner.scan(Gen.java:1489)
at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:42)
at com.sun.tools.javac.tree.TreeScanner.visitBlock(TreeScanner.java:86)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.jvm.Gen.estimateCodeComplexity(Gen.java:1563)
at com.sun.tools.javac.jvm.Gen.visitTry(Gen.java:1283)
at com.sun.tools.javac.tree.Tree$Try.accept(Tree.java:669)
at com.sun.tools.javac.jvm.Gen.genDef(Gen.java:658)
at com.sun.tools.javac.jvm.Gen.genStat(Gen.java:693)
at com.sun.tools.javac.jvm.Gen.genStat(Gen.java:679)
at com.sun.tools.javac.jvm.Gen.genStats(Gen.java:730)
at com.sun.tools.javac.jvm.Gen.visitBlock(Gen.java:999)
at com.sun.tools.javac.tree.Tree$Block.accept(Tree.java:535)
at com.sun.tools.javac.jvm.Gen.genDef(Gen.java:658)
at com.sun.tools.javac.jvm.Gen.genStat(Gen.java:693)
at com.sun.tools.javac.jvm.Gen.genMethod(Gen.java:885)
at com.sun.tools.javac.jvm.Gen.visitMethodDef(Gen.java:858)
at com.sun.tools.javac.tree.Tree$MethodDef.accept(Tree.java:478)
at com.sun.tools.javac.jvm.Gen.genDef(Gen.java:658)
at com.sun.tools.javac.jvm.Gen.genClass(Gen.java:2181)
at com.sun.tools.javac.main.JavaCompiler.genCode(JavaCompiler.java:347)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:499)
at com.sun.tools.javac.main.Main.compile(Main.java:592)
at com.sun.tools.javac.main.Main.compile(Main.java:544)
at com.sun.tools.javac.Main.compile(Main.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac13.java:
56)
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1065)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:882)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.jboss.tools.buildmagic.task.CallTarget.execute(CallTarget.java:17
0)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261)
at org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteMo
dules.java:386)
at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(E
xecuteModules.java:402)
at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(E
xecuteModules.java:261)
at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(Execute
Modules.java:242)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
BUILD FAILED
X:\svn\jboss-5.x\tomcat\build.xml:185: Compile failed; see the compiler error ou
tput for details.
Total time: 1 minute 14 seconds
15 years, 8 months
Re: [jboss-dev] Embedded Jopr snapshot included in the build!
by Dimitris Andreadis
Pete Muir wrote:
> Hi Dimitris,
>
> Not quite sure how you would do it I'm afraid - the obvious way would be
> to allow the application to bundle it's own log4j.xml file which
> overrides the AS one, but that doesn't seem to work in the current code
> base. Want me to file a feature request?
>
> But I do believe Seam is using log levels consistently with JBoss AS.
AFAICT, Seam is very noisy. Most of the info I'm trying to avoid should be logged at DEBUG
level.
Jaikiran proposed to still log this info, but only to the server.log, not the console.
> Could you comment on which reduction you would like to see? I would
> prefer to not loose most of those messages for the majority of users in
> JBoss, as they are very help for debugging, and most people will adjust
> their logging in production anyway (definitely we should have WARN on a
> production profile).
>
> 1) Version number logged at INFO - see
>
> * INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build:
> SVNTag=JBoss_5_0_1_GA date=200902232048)
> * INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
> * INFO [NativeServerConfig] 3.0.5.GA
> * INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
> * INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
>
> etc.
This is OK
>
> 2) Logging discovery of components
>
> INFO [JBossASKernel] installing bean:
> jboss.j2ee:ear=webbeans-translator.ear,jar=webbeans-translator.jar,name=SentenceTranslator,service=EJB3
>
> INFO [JBossASKernel] with dependencies:
> INFO [JBossASKernel] and demands:
> INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
> INFO [JBossASKernel] and supplies:
> INFO [JBossASKernel]
> jndi:webbeans-translator/SentenceTranslator/local-org.jboss.webbeans.examples.translator.Translator
>
> INFO [JBossASKernel]
> Class:org.jboss.webbeans.examples.translator.Translator
> INFO [JBossASKernel] jndi:webbeans-translator/SentenceTranslator/local
> INFO [JBossASKernel]
> jndi:webbeans-translator/SentenceTranslator/remote
> INFO [JBossASKernel] Added
> bean(jboss.j2ee:ear=webbeans-translator.ear,jar=webbeans-translator.jar,name=SentenceTranslator,service=EJB3)
> to KernelDeployment of: webbeans-translator.jar
> INFO [JBossASKernel] installing bean:
> jboss.j2ee:ear=webbeans-translator.ear,jar=webbeans-translator.jar,name=TranslatorControllerBean,service=EJB3
>
> INFO [JBossASKernel] with dependencies:
> INFO [JBossASKernel] and demands:
> INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
> INFO [JBossASKernel] and supplies:
> INFO [JBossASKernel]
> jndi:webbeans-translator/TranslatorControllerBean/local-org.jboss.webbeans.examples.translator.TranslatorController
>
> INFO [JBossASKernel]
> Class:org.jboss.webbeans.examples.translator.TranslatorController
> INFO [JBossASKernel]
> jndi:webbeans-translator/TranslatorControllerBean/remote
> INFO [JBossASKernel]
> jndi:webbeans-translator/TranslatorControllerBean/local
> INFO [JBossASKernel] Added
> bean(jboss.j2ee:ear=webbeans-translator.ear,jar=webbeans-translator.jar,name=TranslatorControllerBean,service=EJB3)
> to KernelDeployment of: webbeans-translator.jar
>
> etc.
This is probably crap. It doesn't have to be that verbose in the console. You just need to
know that something got deployed, you don't need to know the full dependency list, it should
be at DEBUG level.
>
> 3) warning people about deprecation (standard practice, easy to fix :-)
>
> 4) Logging start of components
>
> INFO [EJBContainer] STARTED EJB:
> org.jboss.webbeans.examples.translator.SentenceTranslator ejbName:
> SentenceTranslator
> INFO [JndiSessionRegistrarBase] Binding the following Entries in
> Global JNDI:
>
> webbeans-translator/SentenceTranslator/local - EJB3.x Default Local
> Business Interface
> webbeans-translator/SentenceTranslator/local-org.jboss.webbeans.examples.translator.Translator
> - EJB3.x Local Business Interface
>
> INFO [SessionSpecContainer] Starting
> jboss.j2ee:ear=webbeans-translator.ear,jar=webbeans-translator.jar,name=TranslatorControllerBean,service=EJB3
>
> INFO [EJBContainer] STARTED EJB:
> org.jboss.webbeans.examples.translator.TranslatorControllerBean ejbName:
> TranslatorControllerBean
> INFO [JndiSessionRegistrarBase] Binding the following Entries in
> Global JNDI:
>
> webbeans-translator/TranslatorControllerBean/local - EJB3.x Default
> Local Business Interface
> webbeans-translator/TranslatorControllerBean/local-org.jboss.webbeans.examples.translator.TranslatorController
> - EJB3.x Local Business Interface
>
This, too, should be DEBUG.
> 5) where configuration is read from e.g.
>
> INFO [ServerImpl] Starting Microcontainer,
> bootstrapURL=file:/Applications/jboss-5.0.1.GA/server/default/conf/bootstrap.xml
>
> INFO [RARDeployment] Required license terms exist, view
> vfszip:/Applications/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
>
> INFO [RARDeployment] Required license terms exist, view
> vfszip:/Applications/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
>
> INFO [RARDeployment] Required license terms exist, view
> vfszip:/Applications/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
>
> INFO [RARDeployment] Required license terms exist, view
> vfszip:/Applications/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
>
> INFO [RARDeployment] Required license terms exist, view
> vfszip:/Applications/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
>
That's probably Okay.
>
> 6) Enabled configurations (namespaces)
>
> INFO [ServerImpl] Server Name: default
> INFO [ServerImpl] Server Base Dir: /Applications/jboss-5.0.1.GA/server
> INFO [ServerImpl] Server Base URL:
> file:/Applications/jboss-5.0.1.GA/server/
> INFO [ServerImpl] Server Config URL:
> file:/Applications/jboss-5.0.1.GA/server/default/conf/
> INFO [ServerImpl] Server Home Dir:
> /Applications/jboss-5.0.1.GA/server/default
> INFO [ServerImpl] Server Home URL:
> file:/Applications/jboss-5.0.1.GA/server/default/
> INFO [ServerImpl] Server Data Dir:
> /Applications/jboss-5.0.1.GA/server/default/data
> INFO [ServerImpl] Server Library URL:
> file:/Applications/jboss-5.0.1.GA/server/default/lib/
> INFO [ServerImpl] Server Log Dir:
> /Applications/jboss-5.0.1.GA/server/default/log
> INFO [ServerImpl] Server Native Dir:
> /Applications/jboss-5.0.1.GA/server/default/tmp/native
> INFO [ServerImpl] Server Temp Dir:
> /Applications/jboss-5.0.1.GA/server/default/tmp
> INFO [ServerImpl] Server Temp Deploy Dir:
> /Applications/jboss-5.0.1.GA/server/default/tmp/deploy
I think that's probably okay, too.
>
> On 15 Apr 2009, at 12:18, Dimitris Andreadis wrote:
>
>> How? The log4j settings are global.
>>
>> You need to make sure you use properly the various logging levels.
>>
>> Pete Muir wrote:
>>> Can we make sure this is for just the admin-console, not the whole AS
>>> please?
>>> On 15 Apr 2009, at 11:58, Dimitris Andreadis wrote:
>>>> I'm thinking of applying the following to reduce the verbose logging:
>>>>
>>>> <!-- Limit the verbose facelets compiler -->
>>>> <category name="facelets.compiler">
>>>> <priority value="WARN"/>
>>>> </category>
>>>>
>>>> <!-- Limit the verbose ajax4jsf cache initialization -->
>>>> <category name="org.ajax4jsf.cache">
>>>> <priority value="WARN"/>
>>>> </category>
>>>>
>>>> <!-- Limit the verbose embedded jopr categories -->
>>>> <category name="org.rhq">
>>>> <priority value="WARN"/>
>>>> </category>
>>>>
>>>> <!-- Limit the verbose seam categories -->
>>>> <category name="org.jboss.seam">
>>>> <priority value="WARN"/>
>>>> </category>
>>>>
>>>> Jaikiran Pai wrote:
>>>>> Looks good :)
>>>>> On a related note, I guess we could do something about the INFO
>>>>> level logs that flood the console when the admin-console is being
>>>>> deployed and accessed? Looking at what is being logged, it doesn't
>>>>> look like they should be logged at INFO level:
>>>>> During deploy:
>>>>> 16:10:56,870 INFO [config] Initializing Mojarra (1.2_12-b01-FCS)
>>>>> for context '/admin-console'
>>>>> 16:10:59,852 INFO [ServletContextListener] Welcome to Seam 2.1.0.SP1
>>>>> 16:11:03,583 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/security, package:
>>>>> org.jboss.seam.security, prefix: org.jboss.seam.security
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/international, package:
>>>>> org.jboss.seam.international, prefix: org.jboss.seam.international
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/document, package:
>>>>> org.jboss.seam.document, prefix: org.jboss.seam.document
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/persistence, package:
>>>>> org.jboss.seam.persistence, prefix: org.jboss.seam.persistence
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/cache, package:
>>>>> org.jboss.seam.cache, prefix: org.jboss.seam.cache
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/ui, package: org.jboss.seam.ui,
>>>>> prefix: org.jboss.seam.ui
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/security, package:
>>>>> org.jboss.seam.security.permission, prefix: org.jboss.seam.security
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/core, package: org.jboss.seam.core,
>>>>> prefix: org.jboss.seam.core
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/captcha, package:
>>>>> org.jboss.seam.captcha, prefix: org.jboss.seam.captcha
>>>>> 16:11:03,584 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/async, package:
>>>>> org.jboss.seam.async, prefix: org.jboss.seam.async
>>>>> 16:11:03,585 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/drools, package:
>>>>> org.jboss.seam.drools, prefix: org.jboss.seam.drools
>>>>> 16:11:03,585 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/mail, package: org.jboss.seam.mail,
>>>>> prefix: org.jboss.seam.mail
>>>>> 16:11:03,585 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/transaction, package:
>>>>> org.jboss.seam.transaction, prefix: org.jboss.seam.transaction
>>>>> 16:11:03,585 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/web, package: org.jboss.seam.web,
>>>>> prefix: org.jboss.seam.web
>>>>> 16:11:03,585 INFO [Initialization] Namespace:
>>>>> http://jboss.com/products/seam/security, package:
>>>>> org.jboss.seam.security.management, prefix: org.jboss.seam.security
>>>>> ...//trimmed more similar log
>>>>> 16:11:03,587 INFO [Initialization] reading /WEB-INF/components.xml
>>>>> 16:11:03,598 WARN [Initialization] <action
>>>>> expression="#{redirect.captureCurrentView}" /> has been deprecated,
>>>>> use <action execute="#{redirect.captureCurrentView}" /> instead
>>>>> 16:11:03,598 WARN [Initialization] <action
>>>>> expression="#{redirect.returnToCapturedView}" /> has been
>>>>> deprecated, use <action execute="#{redirect.returnToCapturedView}"
>>>>> /> instead
>>>>> 16:11:03,622 INFO [Initialization] reading properties from:
>>>>> /seam.properties
>>>>> 16:11:03,623 INFO [Initialization] reading properties from:
>>>>> /jndi.properties
>>>>> 16:11:03,626 INFO [Initialization] initializing Seam
>>>>> 16:11:03,666 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.jms.topicConnection
>>>>> 16:11:03,671 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.core.locale
>>>>> 16:11:03,675 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.persistence.persistenceProvider
>>>>> 16:11:03,680 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.core.manager
>>>>> 16:11:03,680 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.core.expressions
>>>>> 16:11:03,682 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.web.isUserInRole
>>>>> 16:11:03,684 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.transaction.synchronizations
>>>>> 16:11:03,686 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.web.parameters
>>>>> 16:11:03,689 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.core.locale
>>>>> 16:11:03,690 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.web.userPrincipal
>>>>> 16:11:03,690 INFO [Initialization] two components with same name,
>>>>> higher precedence wins: org.jboss.seam.core.resourceLoader
>>>>> 16:11:03,710 INFO [Component] Component: org.jboss.seam.core.init,
>>>>> scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init
>>>>> 16:11:04,182 INFO [Initialization] Installing components...
>>>>> 16:11:04,218 INFO [Component] Component: addNewOpenMap, scope:
>>>>> EVENT, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.ui.configuration.resource.AddNewOpenMapMemberPropertyToResourceConfigurationUIBean
>>>>> 16:11:04,239 INFO [Component] Component: applicationInfoAction,
>>>>> scope: APPLICATION, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.ui.ApplicationInfoAction
>>>>> 16:11:04,246 INFO [Component] Component: bootstrapAction, scope:
>>>>> APPLICATION, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.BootstrapAction
>>>>> 16:11:04,265 INFO [Component] Component: commonActionUtil, scope:
>>>>> EVENT, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.ui.CommonActionUtil
>>>>> 16:11:04,502 INFO [Component] Component: configHelperFactory,
>>>>> scope: EVENT, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.ui.configuration.resource.ConfigHelperFactory
>>>>> 16:11:04,504 INFO [Component] Component: contentDisplayAction,
>>>>> scope: SESSION, type: JAVA_BEAN, class:
>>>>> org.jboss.on.embedded.ui.SingleResourceContentAction
>>>>> // ... trimmed a lot more similar log
>>>>> On access:
>>>>> 16:11:58,257 INFO [compiler] Added Library from:
>>>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.taglib.xml
>>>>> 16:11:58,267 INFO [compiler] Added Library from:
>>>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/s.taglib.xml
>>>>> 16:11:58,289 INFO [compiler] Added Library from:
>>>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-core.taglib.xml
>>>>> 16:11:58,295 INFO [compiler] Added Library from:
>>>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-html.taglib.xml
>>>>> // ... trimmed more similar logs
>>>>> regards,
>>>>> -Jaikiran
>>>>> Dimitris Andreadis wrote:
>>>>>> In case you haven't noticed:
>>>>>> https://jira.jboss.org/jira/browse/JBAS-6750
>>>>>>
>>>>>> The embedded Jopr (snapshot) is included in the 5.1.x. build
>>>>>> (default & all configs) at
>>>>>> http://localhost:8080/admin-console.
>>>>>>
>>>>>> And it looks good!!!
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>> --
>>> Pete Muir
>>> http://www.seamframework.org
>>> http://in.relation.to/Bloggers/Pete
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
15 years, 8 months
Booting the 'all' config fails
by Dimitris Andreadis
It fails for me in Branch_5_x:
14:19:20,343 INFO [JMXKernel] Legacy JMX core initialized
14:19:23,296 ERROR [AbstractKernelController] Error installing to Instantiated:
name=ClusteredDeploymentRepositoryMetadataPersister state=Described
java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.re
flect.Constructor expected=[java.net.URI] actual=[org.jboss.bootstrap.microconta
iner.ServerImpl]
at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(
ReflectionUtils.java:395)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(R
eflectionUtils.java:153)
at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.ne
wInstance(ReflectConstructorInfoImpl.java:106)
at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicC
onstructorJoinPoint.java:80)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.crea
teTarget(AOPConstructorJoinpoint.java:276)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.disp
atch(AOPConstructorJoinpoint.java:97)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$Joi
npointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(Executio
nWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionIn
ternal(InstantiateAction.java:66)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.sim
pleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins
tall(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:540)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
(AbstractKernelDeployer.java:319)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
s(AbstractKernelDeployer.java:297)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(Abs
tractKernelDeployer.java:130)
at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicK
ernelDeployer.java:76)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:91)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:161)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:138)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:216)
at org.jboss.Main$1.run(Main.java:546)
at java.lang.Thread.run(Thread.java:595)
Failed to boot JBoss:
java.lang.IllegalStateException: Incompletely deployed:
DEPLOYMENTS IN ERROR:
Deployment "ClusteredDeploymentRepositoryMetadataPersister" is in error due to
: java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.
reflect.Constructor expected=[java.net.URI] actual=[org.jboss.bootstrap.microcon
tainer.ServerImpl]
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "FilesystemLocalContentManagerFactory" is missing the following dep
endencies:
Dependency "ClusteredDeploymentRepositoryMetadataPersister" (should be in st
ate "Installed", but is actually in state "**ERROR**")
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalVa
lidate(AbstractKernelDeployer.java:278)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(A
bstractKernelDeployer.java:174)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:142)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:216)
at org.jboss.Main$1.run(Main.java:546)
at java.lang.Thread.run(Thread.java:595)
14:19:24,437 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
14:19:24,453 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Press any key to continue . . .
15 years, 8 months
Re: [jboss-dev] Embedded Jopr snapshot included in the build!
by Chris Bredesen
Pete Muir wrote:
>
> On 15 Apr 2009, at 14:28, Chris Bredesen wrote:
>
>> Dimitris Andreadis wrote:
>>> Pete Muir wrote:
>>>> Hi Dimitris,
>>>>
>>>> Not quite sure how you would do it I'm afraid - the obvious way
>>>> would be to allow the application to bundle it's own log4j.xml file
>>>> which overrides the AS one, but that doesn't seem to work in the
>>>> current code base. Want me to file a feature request?
>>>>
>>>> But I do believe Seam is using log levels consistently with JBoss AS.
>>> AFAICT, Seam is very noisy. Most of the info I'm trying to avoid
>>> should be logged at DEBUG level.
>>> Jaikiran proposed to still log this info, but only to the server.log,
>>> not the console.
>>
>> +1 on logging only to the file. Most of that stuff does fit INFO IMO.
>
> Actually, what I would like to do is maintain this logging to the
> console at INFO level if Seam is in "debug" mode, but reduce it to DEBUG
> if not. WDYT?
This is a fairly reasonable solution but it seems a bit elusive to
change log4j output somewhere outside log4j.xml. Could be the only way
to address all concerns, though.
-CB
15 years, 8 months
Re: [jboss-dev] Embedded Jopr snapshot included in the build!
by Dimitris Andreadis
How? The log4j settings are global.
You need to make sure you use properly the various logging levels.
Pete Muir wrote:
> Can we make sure this is for just the admin-console, not the whole AS
> please?
>
> On 15 Apr 2009, at 11:58, Dimitris Andreadis wrote:
>
>> I'm thinking of applying the following to reduce the verbose logging:
>>
>> <!-- Limit the verbose facelets compiler -->
>> <category name="facelets.compiler">
>> <priority value="WARN"/>
>> </category>
>>
>> <!-- Limit the verbose ajax4jsf cache initialization -->
>> <category name="org.ajax4jsf.cache">
>> <priority value="WARN"/>
>> </category>
>>
>> <!-- Limit the verbose embedded jopr categories -->
>> <category name="org.rhq">
>> <priority value="WARN"/>
>> </category>
>>
>> <!-- Limit the verbose seam categories -->
>> <category name="org.jboss.seam">
>> <priority value="WARN"/>
>> </category>
>>
>> Jaikiran Pai wrote:
>>> Looks good :)
>>> On a related note, I guess we could do something about the INFO level
>>> logs that flood the console when the admin-console is being deployed
>>> and accessed? Looking at what is being logged, it doesn't look like
>>> they should be logged at INFO level:
>>> During deploy:
>>> 16:10:56,870 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for
>>> context '/admin-console'
>>> 16:10:59,852 INFO [ServletContextListener] Welcome to Seam 2.1.0.SP1
>>> 16:11:03,583 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/security, package:
>>> org.jboss.seam.security, prefix: org.jboss.seam.security
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/international, package:
>>> org.jboss.seam.international, prefix: org.jboss.seam.international
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/document, package:
>>> org.jboss.seam.document, prefix: org.jboss.seam.document
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/persistence, package:
>>> org.jboss.seam.persistence, prefix: org.jboss.seam.persistence
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/cache, package: org.jboss.seam.cache,
>>> prefix: org.jboss.seam.cache
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/ui, package: org.jboss.seam.ui,
>>> prefix: org.jboss.seam.ui
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/security, package:
>>> org.jboss.seam.security.permission, prefix: org.jboss.seam.security
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/core, package: org.jboss.seam.core,
>>> prefix: org.jboss.seam.core
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/captcha, package:
>>> org.jboss.seam.captcha, prefix: org.jboss.seam.captcha
>>> 16:11:03,584 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/async, package: org.jboss.seam.async,
>>> prefix: org.jboss.seam.async
>>> 16:11:03,585 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/drools, package:
>>> org.jboss.seam.drools, prefix: org.jboss.seam.drools
>>> 16:11:03,585 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/mail, package: org.jboss.seam.mail,
>>> prefix: org.jboss.seam.mail
>>> 16:11:03,585 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/transaction, package:
>>> org.jboss.seam.transaction, prefix: org.jboss.seam.transaction
>>> 16:11:03,585 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/web, package: org.jboss.seam.web,
>>> prefix: org.jboss.seam.web
>>> 16:11:03,585 INFO [Initialization] Namespace:
>>> http://jboss.com/products/seam/security, package:
>>> org.jboss.seam.security.management, prefix: org.jboss.seam.security
>>> ...//trimmed more similar log
>>> 16:11:03,587 INFO [Initialization] reading /WEB-INF/components.xml
>>> 16:11:03,598 WARN [Initialization] <action
>>> expression="#{redirect.captureCurrentView}" /> has been deprecated,
>>> use <action execute="#{redirect.captureCurrentView}" /> instead
>>> 16:11:03,598 WARN [Initialization] <action
>>> expression="#{redirect.returnToCapturedView}" /> has been deprecated,
>>> use <action execute="#{redirect.returnToCapturedView}" /> instead
>>> 16:11:03,622 INFO [Initialization] reading properties from:
>>> /seam.properties
>>> 16:11:03,623 INFO [Initialization] reading properties from:
>>> /jndi.properties
>>> 16:11:03,626 INFO [Initialization] initializing Seam
>>> 16:11:03,666 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.jms.topicConnection
>>> 16:11:03,671 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.core.locale
>>> 16:11:03,675 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.persistence.persistenceProvider
>>> 16:11:03,680 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.core.manager
>>> 16:11:03,680 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.core.expressions
>>> 16:11:03,682 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.web.isUserInRole
>>> 16:11:03,684 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.transaction.synchronizations
>>> 16:11:03,686 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.web.parameters
>>> 16:11:03,689 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.core.locale
>>> 16:11:03,690 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.web.userPrincipal
>>> 16:11:03,690 INFO [Initialization] two components with same name,
>>> higher precedence wins: org.jboss.seam.core.resourceLoader
>>> 16:11:03,710 INFO [Component] Component: org.jboss.seam.core.init,
>>> scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init
>>> 16:11:04,182 INFO [Initialization] Installing components...
>>> 16:11:04,218 INFO [Component] Component: addNewOpenMap, scope:
>>> EVENT, type: JAVA_BEAN, class:
>>> org.jboss.on.embedded.ui.configuration.resource.AddNewOpenMapMemberPropertyToResourceConfigurationUIBean
>>> 16:11:04,239 INFO [Component] Component: applicationInfoAction,
>>> scope: APPLICATION, type: JAVA_BEAN, class:
>>> org.jboss.on.embedded.ui.ApplicationInfoAction
>>> 16:11:04,246 INFO [Component] Component: bootstrapAction, scope:
>>> APPLICATION, type: JAVA_BEAN, class:
>>> org.jboss.on.embedded.BootstrapAction
>>> 16:11:04,265 INFO [Component] Component: commonActionUtil, scope:
>>> EVENT, type: JAVA_BEAN, class: org.jboss.on.embedded.ui.CommonActionUtil
>>> 16:11:04,502 INFO [Component] Component: configHelperFactory, scope:
>>> EVENT, type: JAVA_BEAN, class:
>>> org.jboss.on.embedded.ui.configuration.resource.ConfigHelperFactory
>>> 16:11:04,504 INFO [Component] Component: contentDisplayAction,
>>> scope: SESSION, type: JAVA_BEAN, class:
>>> org.jboss.on.embedded.ui.SingleResourceContentAction
>>> // ... trimmed a lot more similar log
>>> On access:
>>> 16:11:58,257 INFO [compiler] Added Library from:
>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.taglib.xml
>>> 16:11:58,267 INFO [compiler] Added Library from:
>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/s.taglib.xml
>>> 16:11:58,289 INFO [compiler] Added Library from:
>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-core.taglib.xml
>>> 16:11:58,295 INFO [compiler] Added Library from:
>>> vfszip:/NotBackedUp/jpai/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/jopr-embedded-jbas5.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-html.taglib.xml
>>> // ... trimmed more similar logs
>>> regards,
>>> -Jaikiran
>>> Dimitris Andreadis wrote:
>>>> In case you haven't noticed:
>>>> https://jira.jboss.org/jira/browse/JBAS-6750
>>>>
>>>> The embedded Jopr (snapshot) is included in the 5.1.x. build
>>>> (default & all configs) at
>>>> http://localhost:8080/admin-console.
>>>>
>>>> And it looks good!!!
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
15 years, 8 months
Re: [jbosstools-dev] JSR-77 Summary
by Max Rydahl Andersen
Hi JBoss AS guys,
Here is another area tooling could need some help from the runtime...
We are looking at finding a way to introspect AS and have some basic
*remote* control over the deployed modules.
Could you guys give some insight to Rob and the rest of us ?
Is JSR-77 supported ? Will it be in EAP 5 ?
JSR-288 had similar issues earlier - are they fixed ? will they be fixed ?
What are the alternatives, if any ?
/max
> JSR-77 allows, via JMX, to get a list of which servers are running,
> which modules they have, which resources they have, etc. From this
> model I can make an effective list of what's deployed on the server
> through simple JMX calls.
>
> What I still cannot do, though, is control the modules. The portions
> of the spec which deal with managing (starting, stopping) the modules
> is optional, and JBoss does not support this. So, while I can get a
> nice list of what's deployed / running, I cannot manage any of it.
>
> Is it worth-while for me to add to the Servers View a tree element
> (and children) dealing with deployed / running modules considering I
> cannot control them? Is this worth pushing up to the platform to force
> them to implement when JSR-77 is being removed in the future?
>
> Thoughts appreciated.
>
> - Rob
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
15 years, 8 months
Status - 4/13/2009
by Jason T. Greene
Last Week
---------
- Performance analysis of EJB boot time, and subsequent AOP analysis/fix
JBAOP-716
- Investigated Console bootup time
- Build/testsuite fixes
- Investigated regressions
- EAP6 & Embedded discussions
- Dealt with Console Scheduling Problems
- Investigated JBAS-6720 (Topic/Queue metric issues)
- Started looking at/discussing EE6 @Datasource proposal
This Week
---------
- Cleanup CR1 JIRA
- Get JBAS-6720 fully resolved
- Track the critical path (Profile Service/console work)
- Meet our component freeze date
- More EE6 spec work
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 8 months
Re: [jboss-dev] Re: [jbosstools-dev] JSR-77 Summary
by Jason T. Greene
If JMX is all you need, why wasn't the work done in JBAS-6330 sufficient?
Rob Stryker wrote:
> JSR-77 type management isn't exactly crazy-go-nuts-complicated (at least
> it doesn't appear so to me. Under the hood it could be I suppose, but
> what needs to be exposed doesn't seem that bad). What doesn't seem done
> is just the ability to start / stop / undeploy / redeploy a module via
> JMX. I would say this set *is* a basic set of features, and it is pretty
> much exactly what JSR-77 outlines.
>
> Whether or not it's part of the future JEE doesn't mean it's not a good
> management layer to expose. In all honesty I don't know if it's a great
> one or not... but all I'd like to have is the ability to start / stop /
> undeploy / redeploy via JMX, and parts of 77 do that ;)
>
> Question: If something can be done via profile service, how hard / how
> much work for the AS team is it to just expose that via a JMX interface?
> Is this a lot of work, or do we just need to define the interface and
> then it's pretty simple? The reason I ask is because the tooling likes
> JMX much more than compiling against different versions of profile service.
>
> - Rob
>
> Jason T. Greene wrote:
>> Before, when we discussed the JMX option, and the potential for a REST
>> API, I was working under the assumption that tools only needed a basic
>> set of operations. Once this thread started talking about JSR-77
>> management functions, this to me says the profile service is the way
>> forward.
>>
>> As to the tomcat API, I don't see how it provides anything close to
>> JSR-77.
>>
>> Scott Stark wrote:
>>> Neither JSR-77 or JSR-88 are going to be part of EE in the future.
>>>
>>> The profileservice certainly is available remotely, but I thought we
>>> were focusing on the hotdeployment jmx based api as discussed in:
>>> https://jira.jboss.org/jira/browse/JBAS-6330
>>>
>>> If we want this mapped into a resty type api ala the tomcat then that
>>> needs to be defined.
>>>
>>> Max Rydahl Andersen wrote:
>>>> Anyone out there listening ?
>>>>
>>>> Should we just drop this idea of having good remote control over AS
>>>> from tooling ?
>>>>
>>>> /max
>>>>
>>>> Max Rydahl Andersen wrote:
>>>>>>> Is JSR-77 supported ? Will it be in EAP 5 ?
>>>>>>> JSR-288 had similar issues earlier - are they fixed ? will they
>>>>>>> be fixed ?
>>>>>>
>>>>>> JSR-77 is required for EE, but it is very out of date, and will
>>>>>> likely get killed in a future release. JSR-88 is already scheduled
>>>>>> for removal in EE7.
>>>>> So we should not even consider using it for remote access ?
>>>>>>> What are the alternatives, if any ?
>>>>>>
>>>>>> If you guys need advanced management functionality, it sounds like
>>>>>> the Profile Service is going to be what you need.
>>>>> Sure, but profile service is not available to us remotely.
>>>>>
>>>>> Btw. I don't consider any of the things we want to do very advanced
>>>>> - we don't want to be another JON.
>>>>>
>>>>> Something basic and simple as i.e. Tomcat Management API would be
>>>>> enough for us afaics.
>>>>>
>>>>> http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html
>>>>>
>>>>> It provides a simple http api to list, start/stop/undeploy
>>>>> applications/resources (both local and remote resources)
>>>>>
>>>>> btw. this is not just for *us* this is for the greater good of AS :)
>>>>>
>>>>> /max
>>>>
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>>
>
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 8 months
problem with jboss-test 1.1.4.GA?
by Alexey Loubyansky
Branch_5_x is failing to build for me. The reason is jboss-test.jar is
not downloaded. The lib directory contains only jboss-test-sources.jar.
Does anybody else see this?
Thanks,
Alexey
15 years, 8 months
