Missing required extension methods detected on 'javax.transaction.TransactionManager'

While running ws-at tests, I see this in the server log:

[#|2011-12-01T09:54:44.731+0530|INFO|glassfish3.1.2|com.sun.xml.ws.monitoring|_ThreadID=18;_ThreadName=Thread-2;|Metro monitoring rootname successfully set to: amx:pp=/mon/server-mon[server],type=WSEndpoint,name=/sqe-wstx-tx04-service-UsertransactionService-UsertransactionPort|#]

[#|2011-12-01T09:54:44.787+0530|INFO|glassfish3.1.2|com.sun.metro.tx|_ThreadID=18;_ThreadName=Thread-2;|Missing required extension methods detected on 'javax.transaction.TransactionManager' implementation 'com.sun.enterprise.transaction.TransactionManagerHelper':
getTxLogLocation

| #] |

[#|2011-12-01T09:54:44.795+0530|WARNING|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=18;_ThreadName=Thread-2;|JTS5020: Invalid log path. Using [./jts].|#]

[#|2011-12-01T09:54:44.796+0530|WARNING|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=18;_ThreadName=Thread-2;|JTS5021: Invalid default log path. Using current directory.|#]
#### Environment
Glassfish 3.1.2
#### Affected Versions
[2.2]

Source: [https://github.com/javaee/metro-wsit/issues/1599](https://github.com/javaee/metro-wsit/issues/1599)
Author: glassfishrobot

Start by running the ws-at tests in GlassFish 3.1.2 and inspect the transaction manager implementation named in the log, com.sun.enterprise.transaction.TransactionManagerHelper. Check how the missing getTxLogLocation method relates to the JTS5020 and JTS5021 warnings; done means the extension-method message and invalid log-path warnings no longer occur.

Written by the indexing model from the issue text.