[EJB 3.0 Development] - EJB3 project integration in AS
by jaikiran
Right now the AS pulls in EJB3 through the "as-int" component (which is "ejb3" component + a bit more). Now that we are going to have EJB3.1 features, we will now have an "ejb3_1" component. The "ejb3_1" component is expected to bring in all other EJB3 components (like core, proxy etc...) and EJB3.1 components (like no-interface, async etc...). Basically, it brings in EJB3.1 feature set. So here are some questions:
1) What was our reason of having using "as-int" to bring in the EJB3 components in AS? I mean why not just use "ejb3" component in the component-matrix of AS?
2) What distinguishes "as-int" and the "ejb3" component? I see that "as-int" right now has "ejb3" + "metrics-deployer" + "mc-int". But probably we do not require this separate component for AS integration (see #3 below)
3) Do we really need "as-int" going forward? I mean we could use "ejb3" or "ejb3_1" in the component matrix of AS (depending on what it wants). Then any additional AS integration components(like "metrics-deployer") could probably be explicitly added in the component-matrix.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269641#4269641
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269641
16 years
[JBoss ESB Development] - Re: Performance Improvement Prop: Cache PortReference.extend
by dward
"Kevin.Conner(a)jboss.com" wrote : So DEBUG is still enabled, and being invoked, but not being logged? Eeek.
Out-of-the-box, the (.org ESB) default profile's jboss-log4j.xml is configured such that the FILE appender will output DEBUG statements to server.log. This can be changed if you add a non-DEBUG Threshold to the FILE appender (it currently doesn't have a Threshold set)
<param name="Threshold" value="INFO"/>
, or you can just remove the FILE appender completely.
The CONSOLE appender is set with a Threshold of INFO, so you don't see any DEBUG output, however debug statements are still called (logger.isDebugEnabled() still returns true) unless you uncomment this section:
<!-- Limit JBoss categories
| <category name="org.jboss">
| <priority value="INFO"/>
| </category>
| -->
to set the log level of that logger. So, in summary, log events are still being created (which means unecessary debug code like String-building is still occurring), even if the Threshold of the Appender is filtering them out. We need to stop the events from being fired in the first place, which means setting a priority/level on the right logger categories.
Can I change this along with JBESB-3044, or should it be it's own Jira issue?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269638#4269638
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269638
16 years