Existe uma forma de habilitar o trace do driver JDBC do OpenEdge, e direcionar essas informações para o arquivo de log padrão do Jboss. Para isso, altere o arquivo "progress-ds.xml", nos pools que forem necessários, com a seguinte informação:
<connection-url>jdbc:datadirect:openedge://<servidor>:<porta_sql>;databaseName=<banco>;defaultSchema=pub;SpyAttributes=(log=System.out;logTName=yes;timestamp=yes);</connection-url>
Basicamente adicionar as informações "SpyAttributes" no final da URL.
Após este ajuste, será necessário reiniciar o JBoss para que este arquivo seja relido.
Para ter certeza que está gerando o log, basta localizar pela string "spy"
Exemplo de um trecho de log:
2018-01-04 15:27:08,024 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.024)>> Connection[1]sql = select position0_.DTSUID as DTSUID84_, position0_.CODE as CODE84_, position0_.POSITIONLEVEL as POSITION3_84_, position0_.DESCRIPTION as DESCRIPT4_84_, position0_.SYNCHRONIZEDATE as SYNCHRON5_84_, position0_.HIERARLEVE_DTSUID as HIERARLEVE7_84_, position0_.CHECKSUM as CHECKSUM84_ from POSITIONEMPLOYEE position0_ where position0_.CODE=? and position0_.POSITIONLEVEL=?
2018-01-04 15:27:08,024 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.024)>> Connection[1]resultSetType = 1003
2018-01-04 15:27:08,024 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.024)>> Connection[1]resultSetConcurrency = 1007
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> OK (PreparedStatement[4826])
2018-01-04 15:27:08,025 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> PreparedStatement[4826].setString(int parameterIndex, String x)
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> parameterIndex = 1
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> x = 0
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> OK
2018-01-04 15:27:08,025 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> PreparedStatement[4826].setInt(int parameterIndex, int x)
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> parameterIndex = 2
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> x = 0
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> OK
2018-01-04 15:27:08,025 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> PreparedStatement[4826].executeQuery()
2018-01-04 15:27:08,025 INFO [STDOUT] spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> OK (ResultSet[4826])
2018-01-04 15:27:08,025 INFO [STDOUT]
spy(http-erp2.unimednordesters.com.br%2F10.0.2.42-80-60)(2018/01/04 15:27:08.025)>> ResultSet[4826].next()
Detalhes procurar pelos documentos:
Progress DataDirect Connect Series for JDBC Reference, Chapter 9, "Tracking JDBC Calls with DataDirect Spy"
Progress DataDirect Connect Series for JDBC User's Guide, Chapter 9, "Progress OpenEdge Driver > Connection Properties > SpyAttributes"
Estes documentos estão disponíveis em:
https://www.progress.com/documentation/datadirect-connectors
Localizar a sessão sobre o driver "Progress OpenEdge", sub-item "jdbc".