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

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:

On 04/15/2009 05:48 AM, 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: The rules are: - One-time, terse messages can be at INFO - Per-deployment/lifecycle stuff can be no higher than DEBUG - Per-request stuff can be no higher than TRACE AFAICT, Seam is not "above the law" here. So why are we talking about yet more exceptions in the logging config? How about the SEAM guys fix the problem? I hope you guys are aware that we have a reputation for having absurdly spammy log files - especially Seam apps.

On 04/15/2009 05:48 AM, 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: The rules are: - One-time, terse messages can be at INFO - Per-deployment/lifecycle stuff can be no higher than DEBUG

- Per-request stuff can be no higher than TRACE AFAICT, Seam is not "above the law" here. So why are we talking about yet more exceptions in the logging config? How about the SEAM guys fix the problem? I hope you guys are aware that we have a reputation for having absurdly spammy log files - especially Seam apps. - DML

Carlo de Wolf wrote: > David M. Lloyd wrote: >> On 04/15/2009 05:48 AM, 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: >> >> The rules are: >> >> - One-time, terse messages can be at INFO >> - Per-deployment/lifecycle stuff can be no higher than DEBUG > From http://www.jboss.org/community/wiki/LoggingStandards: > # INFO - Use the INFO level priority for service life-cycle events and > other crucial related information. > > The most common user error on AS 5 is having your dependencies not > sorted out. So people will see that stuff being deployed, but not > being started. That's why EJB3s not only show deployment, but also the > start conditions at INFO level, it'll remain to be so. > > Carlo The same could be said for mbeans and pojo services. Do you want to see all dependencies printed out in the console? Send them to the server.log.

Jason T. Greene wrote: > Dimitris Andreadis wrote: >> Carlo de Wolf wrote: >>> David M. Lloyd wrote: >>>> On 04/15/2009 05:48 AM, 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: >>>> >>>> The rules are: >>>> >>>> - One-time, terse messages can be at INFO >>>> - Per-deployment/lifecycle stuff can be no higher than DEBUG >>> From http://www.jboss.org/community/wiki/LoggingStandards: >>> # INFO - Use the INFO level priority for service life-cycle events >>> and other crucial related information. >>> >>> The most common user error on AS 5 is having your dependencies not >>> sorted out. So people will see that stuff being deployed, but not >>> being started. That's why EJB3s not only show deployment, but also >>> the start conditions at INFO level, it'll remain to be so. >>> >>> Carlo >> >> The same could be said for mbeans and pojo services. Do you want to >> see all dependencies printed out in the console? >> >> Send them to the server.log. >> > > I have to admit I like seeing service startup messages on the console > (it makes me feel like the as is doing something). Although maybe we > can reduce this to global services and deployment messages. Something > like: > > [INFO] Deployed foo.jar successfully (15 EJBS started) > > But what if foo.jar contained 16 EJBs. :-P How about: [INFO] Deployed foo.jar successfully (15 EJBS started / 1 EJB(s) pending) [INFO] Summary of pending deployments: *** Contexts missing dependencies: Name -> Dependency{Required State:Actual State} EJB3EndpointDeployer -> interface org.jboss.ejb3.endpoint.deployers.EndpointResolver{Configured:** NOT FOUND interface org.jboss.ejb3.endpoint.deployers.EndpointResolver (NOTE: using autowiring to resolve this dependency) **} (I've edited the message to be a little less shouty ;-) ) That would solve my use case. Carlo

Interesting. Does this mean that we intend to ship GUI admin capability with 5.x? Robb Greathouse JBoss CELL 505-480-4639 OFFICE 505-255-2652 FAX 505-554-2834 ----- Original Message ----- From: "Dimitris Andreadis" <dandread(a)redhat.com&gt; To: "JBoss.org development list" <jboss-development(a)lists.jboss.org&gt; Cc: "JBoss AS" <jboss-as(a)redhat.com&gt; Sent: Wednesday, April 15, 2009 3:42:11 AM GMT -06:00 Central America Subject: [jboss-dev] Embedded Jopr snapshot included in the build! 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

Interesting. Does this mean that we intend to ship GUI admin capability with 5.x? Robb Greathouse JBoss CELL 505-480-4639 OFFICE 505-255-2652 FAX 505-554-2834 ----- Original Message ----- From: "Dimitris Andreadis" <dandread(a)redhat.com&gt; To: "JBoss.org development list" <jboss-development(a)lists.jboss.org&gt; Cc: "JBoss AS" <jboss-as(a)redhat.com&gt; Sent: Wednesday, April 15, 2009 3:42:11 AM GMT -06:00 Central America Subject: [jboss-dev] Embedded Jopr snapshot included in the build! 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