[JBoss JIRA] Created: (JBAS-3674) service MetricsLookup dont show invocations
by abo abo (JIRA)
service MetricsLookup dont show invocations
-------------------------------------------
Key: JBAS-3674
URL: http://jira.jboss.com/jira/browse/JBAS-3674
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-3.2.7 Final
Environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
jdk1.5.0_06
Intel Xeon CPU
Reporter: abo abo
on 3.0.6 i see lot of invocations in MetricsLookup service but in 3.2.7 field is always blank, no information given. same configuration both servers.
metrics-service.xml:
=============================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>
<!-- $Id: metrics-service.xml,v 1.1 2004/05/31 08:40:40 u07286 Exp $ -->
<server>
<classpath codebase="lib"
archives="jboss.jar"/>
<!-- ==================================================================== -->
<!-- Metrics Service -->
<!-- ==================================================================== -->
<mbean code="org.jboss.ejb.plugins.MetricsLookup"
name="jboss:service=MetricsLookup">
<attribute name="SanityInterval">120000</attribute>
<attribute name="AlarmProcess">/app/jboss-3.2.7/bin/rec_stackdump</attribute>
<attribute name="EjbPattern">*</attribute>
<attribute name="MethodPattern">*</attribute>
<attribute name="ShowParams">true</attribute>
</mbean>
</server>
=============================================================
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBAS-3685) References to TxManager
by Kevin Conner (JIRA)
References to TxManager
-----------------------
Key: JBAS-3685
URL: http://jira.jboss.com/jira/browse/JBAS-3685
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Kevin Conner
Priority: Critical
The following class contains direct references to org.jboss.tm.TxManager. These references prevent JBossTS being used as a replacement for TxManager.
aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java
These should be changed to refer to the TransactionTimeoutConfiguration interface instead of TxManager.
Index: aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java
===================================================================
--- aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java (revision 57055)+++ aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java (working copy)
@@ -26,6 +26,7 @@
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
import org.jboss.logging.Logger;
+import org.jboss.tm.TransactionTimeoutConfiguration;
/**
* This interceptor handles transactions for AOP
@@ -174,20 +175,18 @@
public Object invoke(Invocation invocation) throws Throwable
{
- org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
int oldTimeout = 0;
- if (tm instanceof org.jboss.tm.TxManager)
+ if (tm instanceof TransactionTimeoutConfiguration)
{
- txManager = (org.jboss.tm.TxManager)tm;
- oldTimeout = txManager.getTransactionTimeout();
+ oldTimeout = ((TransactionTimeoutConfiguration)tm).getTransactionTimeout();
}
try
{
- if (timeout != -1 && txManager != null)
+ if (timeout != -1 && tm != null)
{
- txManager.setTransactionTimeout(timeout);
+ tm.setTransactionTimeout(timeout);
}
Transaction tx = tm.getTransaction();
@@ -203,9 +202,9 @@
}
finally
{
- if (txManager != null)
+ if (tm != null)
{
- txManager.setTransactionTimeout(oldTimeout);
+ tm.setTransactionTimeout(oldTimeout);
}
}
}
@@ -241,20 +240,18 @@
public Object invoke(Invocation invocation) throws Throwable
{
- org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
int oldTimeout = 0;
- if (tm instanceof org.jboss.tm.TxManager)
+ if (tm instanceof TransactionTimeoutConfiguration)
{
- txManager = (org.jboss.tm.TxManager)tm;
- oldTimeout = txManager.getTransactionTimeout();
+ oldTimeout = ((TransactionTimeoutConfiguration)tm).getTransactionTimeout();
}
try
{
- if (timeout != -1 && txManager != null)
+ if (timeout != -1 && tm != null)
{
- txManager.setTransactionTimeout(timeout);
+ tm.setTransactionTimeout(timeout);
}
Transaction tx = tm.getTransaction();
@@ -277,9 +274,9 @@
}
finally
{
- if (txManager != null)
+ if (tm != null)
{
- txManager.setTransactionTimeout(oldTimeout);
+ tm.setTransactionTimeout(oldTimeout);
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months