[Design of the JBoss EJB Container] - Re: jndi lookup during restart
by jcreynol
The ZIP was provided to us by a JBoss Consultant back in October. It says jboss-EAP-4.2.CR1.zip. When I open the MANIFEST.MF for jboss.jar, it does say this is Spec Version "4.2.0.GA_CP01".
The readme.html says "JBoss AS 4.2.0.GA Release Notes" and "Detailed Release Notes
Includes versions: JBossAS-4.2.0.CR1, JBossAS-4.2.0.CR2, JBossAS-4.2.0.GA".
So what I meant was what I wrote, EAP 4.2CR1. :)
However, as I try to get a handle on all the various numbering techniques, the MANIFEST.MF is probably the most meaningful for those of you that are digging into the code and need an actual branch/tag to reference. As far as I can tell, 4.2.0.GA_CP01 *is* 4.2.0.CR1, but apparently 4.2.0.GA_CP01 is the more specific way to reference the build we're using...
So, any ideas if this particular error discussed in this thread is indeed also occuring in this build, within the Remoting code?
I've posted the topic under Remoting:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129993
And opened an issue, here:
http://jira.jboss.com/jira/browse/JBREM-906
Thanks, much!!
John
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129846#4129846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129846
18 years, 1 month
[Design of JCA on JBoss] - Re: JBAS-1808 - MCF MBeans
by vickyk
"vickyk" wrote :
| Looking at the original requirement I could think of pulling the PreparedStatementCache from the JbossManagedConnectionPool MBean per DataSource.
| As per the original requirement we need to
| 1) Get all the ManagedConnection from the Pool.
| 2) Find out the PreparedStatementCache associated with these ManagedConneciton in the pool.
|
| Here I see the related data being pulled from the JbossManagedConnectionPool/InternalManagedConnectionPool .
|
|
Adrian , I have tried this option .
I tried this code in the JbossManagedConnectionPool
+ public Object listUnderlyingNativeConnectionStatistics()
| + {
| + String statistics = "";
| + for(Iterator iter = subPools.values().iterator(); iter.hasNext();)
| + {
| + SubPoolContext subContext = (SubPoolContext)iter.next();
| + InternalManagedConnectionPool internalPool = subContext.getSubPool();
| + java.util.ArrayList cels = internalPool.getCELs();
| + int connectionCount = cels.size();
| + for(int i=0;i<connectionCount;i++)
| + {
| + ConnectionListener cl = (ConnectionListener) cels.get(i);
| + javax.resource.spi.ManagedConnection mc = cl.getManagedConnection();
| + if (mc instanceof org.jboss.resource.statistic.JBossConnectionStatistics)
| + {
| + org.jboss.resource.statistic.JBossConnectionStatistics stats = (org.jboss.resource.statistic.JBossConnectionStatistics)mc;
| + statistics += stats.listConnectionStats();
| + }
| + else
| + {
| + statistics = mc + " does not implement org.jboss.resource.statistic.JBossConnectionStatistics , <br><font color='red'>So this Operation is Not available!!!</font> ";
| + break;
| + }
| + }
| + }
| + return statistics;
| + }
|
With this approach we can expose the underlying connection specific statistics in the JbossManagedConnectionPool MBean .
The required statistics should be formated in the the listUnderlyingNativeConnectionStatistics() method and the ManagedConnection should implement JbossConnectionStatistics .
Before I go fully on this I would like to know your opinion on this .
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129837#4129837
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129837
18 years, 1 month