[Design of POJO Server] - Excessive logging in AS 4.2.3 and AS 5
by jbalunas＠redhat.com
Hey guys,
Not 100% if this is the right forum for this - there was not a "Design of AS" ;-)
While doing some performance testing for Seam I noticed that the default logging for AS 4.2.3 and AS 5.0 CR2 was set to debug, Note that console logging is limited to info so this only shows in the log.
This causes huge performance issues and exposes the user to way too much information. I have discussed this on the EAP side in JBPAPP-1187. They fixed it to some degree, but it still needs some work.
This is basically what I'm seeing
Starting 4.2.3 - 1.2 mb - with app
Starting 5.0 CR2 - 1.3 mb - with no app
A few requests with one user and seam app creates MBs of logs.
>From my testing performance hit was huge. The average went from 14 sec to 4 sec with 50 users and 25 requests each when I switched the threshold for the log file to info. The server.log file size (with a few requests) was only 97kb compared to the 1.2 above with just starting the server. That test was with 4.2.3 not 5.0.
Is there a reason that the logging is set this way? My opinion is that we should give the user the best initial performance, and concise information.
Thoughts?
Thanks,
Jay Balunas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176937#4176937
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176937
17 years, 6 months
[Design of JBoss Transaction Services] - Jboss hangs after running for a whiel
by imranpariyani
My application runs fine for a while but after that it just hangs and in the log file is see this warnings
| 2008-09-16 21:03:00,116 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f42 invoked while multiple threads active within it.
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f42 aborting with 1 threads active!
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f48 invoked while multiple threads active within it.
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f48 aborting with 1 threads active!
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f4e invoked while multiple threads active within it.
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f4e aborting with 1 threads active!
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f54 invoked while multiple threads active within it.
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f54 aborting with 1 threads active!
| 2008-09-16 21:05:00,121 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f5e invoked while multiple threads active within it.
| 2008-09-16 21:05:00,121 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f5e aborting with 1 threads active!
| 2008-09-16 21:05:00,122 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f68 invoked while multiple threads active within it.
| 2008-09-16 21:05:00,122 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f68 aborting with 1 threads active!
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 12215920142
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transaction to join
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronization
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transaction to join
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Transaction already joined
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f72 invoked while multiple threads active within it.
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f72 aborting with 1 threads active!
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f78 invoked while multiple threads active within it.
| 2008-09-16 21:07:00,125 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f78 aborting with 1 threads active!
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 12215923142
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transaction to join
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronization
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transaction to join
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Transaction already joined
|
these warnings just keeps repeating .. is it because of some memory leak ?
any help would be appreciated
Thanks
Imran Pariyani
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176900#4176900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176900
17 years, 6 months
[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise
by kukeltje
"alex.guizar(a)jboss.com" wrote : anonymous wrote : on the migration to ejb3: i don't think that is appropriate on jBPM 3. we can consider this on jBPM 4.
| +3.1415926
| ejb3 is definitely a proposal for jbpm 4. I volunteer for that.
|
Aren't you 0.0000001 off? Oh and 'volunteer'? Besides the 40+ hours you make for JBoss? haha
"alex.guizar@jboss.com/tom.baeyens(a)jboss.com" wrote :
| anonymous wrote : i would guess the whole purpose of an appserver is to take care of making a global transaction out of XA transactional resources, no ? even if we would use different DSs.
| managing a global/distributed transaction is the app server's business indeed, except that (1) some databases such as HSQL and (correct me if I'm wrong) MySQL do not provide XA data sources and (2) the EJB timer service's support for 2PC relies on its underlying data source, which affects the EntitySchedulerService. JMS's 2PC support does not rely on the underlying data source's XA capability and therefore the JmsMessageService is unaffected.
Cool... one mind, one vision. Either Tom or Alex is clairvoyant
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176880#4176880
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176880
17 years, 6 months
[Design of AOP on JBoss (Aspects/JBoss)] - Re: Modularising the appserver bootstrap
by kabir.khan＠jboss.com
These are some of the ServiceMBean-/JBossNotificationBroadcasterSupport methods.
| public void addNotificationListener(NotificationListener listener, NotificationFilter filter, Object handback)
| public void removeNotificationListener(NotificationListener listener, NotificationFilter filter, Object handback) throws ListenerNotFoundException
| public void removeNotificationListener(NotificationListener listener) throws ListenerNotFoundException
| public DeploymentInfo getDeploymentInfo() throws JMException
| public MBeanNotificationInfo[] getNotificationInfo()
| public MBeanServer getServer()
| public ObjectName getServiceName()
| public int getState()
| public String getStateString()
| public void jbossInternalLifecycle(String method) throws Exception
| public void postDeregister()
| public void preDeregister() throws Exception
| public ObjectName preRegister(MBeanServer server, ObjectName name) throws Exception
|
The only ones I seem to be using are these:
| public void sendNotification(Notification notification)
| public long nextNotificationSequenceNumber()
| public void postRegister(Boolean registrationDone)
|
>From the previous code it seems that things like postRegister() will get called for an MC bean in AS. But how to implement the following for an MC bean?
| public void addNotificationListener(NotificationListener listener, NotificationFilter filter, Object handback)
| public void removeNotificationListener(NotificationListener listener, NotificationFilter filter, Object handback) throws ListenerNotFoundException
| public void removeNotificationListener(NotificationListener listener) throws ListenerNotFoundException
| public DeploymentInfo getDeploymentInfo() throws JMException
| public MBeanNotificationInfo[] getNotificationInfo()
| public MBeanServer getServer()
| public ObjectName getServiceName()
| public int getState()
| public String getStateString()
| public void jbossInternalLifecycle(String method) throws Exception
|
Are they required at all?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176874#4176874
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176874
17 years, 6 months
[Design of EJB 3.0] - Re: JNDI Bindings
by ALRubinger
"jaikiran" wrote : 1) One of the possible reasons, that i can think of, why the bean developer would want to do this is to provide a different transport to use. Is there any other valid reason why the developer would want to do this?
The most pressing reason is the transport.
I'm sure app developers could come up with a reason for many equivalent bindings - maybe they're migrating to a new JNDI name scheme and want to keep the old for backwards-compatibility?
"jaikiran" wrote : 2) Does this multiple bindings apply on to Remote business interfaces? Is there any specific reason why the same reasoning can't be used to have something like @LocalBindings?
Yes, I'm in favor of adding N Local Bindings support. What's interesting is that there's no backing metadata model (ie. LocalBindingMetaData) for this.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176872#4176872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176872
17 years, 6 months