[JBoss JIRA] Created: (JBTM-128) warning with TransactionManager interface in JTS with external TM
by Jonathan Halliday (JIRA)
warning with TransactionManager interface in JTS with external TM
-----------------------------------------------------------------
Key: JBTM-128
URL: http://jira.jboss.com/jira/browse/JBTM-128
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTS Implementation
Affects Versions: 4.2.1
Environment: TS 4.2.1 with JacORB on jdk 1.5.0_07, fedora core 5 linux
Reporter: Jonathan Halliday
Assigned To: Mark Little
When using JTS with external transaction manager and accessing transaction via javax.transaction.TransactionManager interface, an empty transaction generates a warning:
2006-09-22 14:35:10,928 [main] WARN com.arjuna.ats.jta.logging.loggerI18N - [com.arjuna.ats.internal.jta.transaction.jts.syncproblem] [com.arjuna.ats.internal.jta.transaction.jts.syncproble] - cleanup synchronization failed to register:
java.lang.NullPointerException
at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.<init>(TransactionImple.java:136)
at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.begin(BaseTransaction.java:128)
This does not occur when using a local transaction manager or managing the transaction through OTSManager.get_current instead.
Test code to reproduce warning:
System.setProperty("com.arjuna.ats.jta.jtaTMImplementation","com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple");
System.setProperty("com.arjuna.ats.jta.jtaUTImplementation","com.arjuna.ats.internal.jta.transaction.jts.UserTransactionImple");
ORB myORB = ORB.getInstance("ServerSide");
OA myOA = OA.getRootOA(myORB);
myORB.initORB(args, null);
myOA.initOA();
javax.transaction.TransactionManager transactionManager = com.arjuna.ats.jta.TransactionManager.transactionManager();
transactionManager.begin();
transactionManager.commit();
--
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] Commented: (JBAS-3683) snmp-adaptor.sar/attributes.mib MIB syntax errors
by Gerald Turner (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3683?page=comments#action_12343889 ]
Gerald Turner commented on JBAS-3683:
-------------------------------------
Dimitris, the reason that I changed some types to Gauge32 is because NET-SNMP complains about the type returned by the SNMP Agent not matching the MIB - though I don't recall if these were merely warnings versus failure like the other syntax errors. The reason I left some as INTEGER is because snmp-adaptor / RequestHandlerImpl converts Long attributes to SnmpUInt32 (Gauge32), and Integer attributes to SnmpInt32 (INTEGER), for example jboss.system:type=ServerInfo ActiveThreadCount is an Integer, thus it matced the MIB.
> snmp-adaptor.sar/attributes.mib MIB syntax errors
> -------------------------------------------------
>
> Key: JBAS-3683
> URL: http://jira.jboss.com/jira/browse/JBAS-3683
> Project: JBoss Application Server
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.4.GA
> Environment: Using NET-SNMP 5.2.3 to parse the MIB
> Reporter: Gerald Turner
> Assigned To: Dimitris Andreadis
> Priority: Trivial
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: snmp-adaptor-attributes.mib.patch.gz
>
>
> Trivial patch to fix some syntax errors in attributes.mib. Things like the operator ":: =" cannot include a space and STATUS must be defined in an OBJECT-TYPE.
--
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