Utilizamos o Fluig 1.6.4 conectado em um banco de dados Oracle através da conexão JDBC.
Houve a necessidade de conectarmos a outro banco Oracle através do Painel de Controle > Gerais > Serviços > Adicionar Novo Serviço.
Adicionamos o novo serviço com o driver Oracle e utilizamos a seguinte configuração na URL: - jdbc:oracle:thin:@192.86.220.100:1521:wint
Em seguida colocamos o usuário e senha, clicamos em testar conexão ele emite a seguinte mensagem de erro no Fluig:
- Erro ao conectar:
No log do Fluig fica da seguinte forma:
2018-07-18 17:16:00,046 INFO [com.datasul.technology.webdesk.taskmanager.notifier.Notifier] (WebdeskScheduler_Worker-2) Starting Job: +LIPAR DOCUMENTOS
2018-07-18 17:17:00,015 INFO [com.datasul.technology.webdesk.taskmanager.notifier.Notifier] (WebdeskScheduler_Worker-2) Starting Job: +LIPAR DOCUMENTOS
2018-07-18 17:17:41,921 INFO [com.datasul.technology.webdesk.util.TokenManager] (Token Cleaner) clean
2018-07-18 17:17:41,921 INFO [com.datasul.technology.webdesk.util.TokenManager] (Token Cleaner) deletado 0
2018-07-18 17:17:59,437 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (WebdeskScheduler_QuartzSchedulerThread) IJ030027: Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@2b54be2f: java.sql.SQLException: pingDatabase failed status=-1
at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1272)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.getInvalidConnections(BaseWrapperManagedConnectionFactory.java:1085)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:378)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:617)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:589)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:590)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:563)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.bull.javamelody.JdbcWrapper$3.invoke(JdbcWrapper.java:805)
at net.bull.javamelody.JdbcWrapper$DelegatingInvocationHandler.invoke(JdbcWrapper.java:286)
at com.sun.proxy.$Proxy239.getConnection(Unknown Source)
at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:159)
at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:111)
at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:1431)
at org.quartz.impl.jdbcjobstore.JobStoreCMT.acquireNextTrigger(JobStoreCMT.java:1171)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
2018-07-18 17:17:59,437 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (WebdeskScheduler_QuartzSchedulerThread) IJ000621: Destroying connection that could not be validated: org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@6d2bb459[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@6d75c3e4 connection handles=0 lastReturned=1531945061921 lastValidated=1531944219873 lastCheckedOut=1531945061921 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@4d7a7c83 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@431a4bb2[pool=FluigDSRO]]
2018-07-18 17:18:00,015 INFO [com.datasul.technology.webdesk.taskmanager.notifier.Notifier] (WebdeskScheduler_Worker-3) Starting Job: +LIPAR DOCUMENTOS
Boa tarde Helcio, a base oracle do fluig também fica no 192.86.220.100? No caso de não ficar a partir da máquina do server do fluig funciona o telnet 192.86.220.100 1521 ?
— Diogo Boegershausen 19 de Jul de 2018Fica sim, é o mesmo Oracle com dois bancos diferentes, um banco para o Fluig e um Banco do ERP. Estou tentando conectar no banco do ERP.
— Helcio Penha 19 de Jul de 2018Teria que verificar como ficaram os datasources no domain.xml. Você abriu algum chamado pro fluig?
— Diogo Boegershausen 19 de Jul de 2018De uma olhada se no seu Fluig/appserver/domain/configuration/domain.xml dentro da tag datasources se foi criado algum datasource com o nome que você deu a ele no cadastro de serviços.
— Diogo Boegershausen 19 de Jul de 2018