error log files

[chandu_wildfly]

hi all,

i am getting this eroor continuously in the server log file....i checked with data source it is enable...

can u please help thanks in advance.

10:00:42,388 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:

ould not create connection): javax.resource.ResourceException: Could not create connection

    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:524)

    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:415)

    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:412)

    at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_66]

    at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_66]

    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:411)

    at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.open(XAResourceRecoveryImpl.java:343)

    at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:170)

    at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [naray

.Final (revision: 9aa71)]

    at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:

:5.0.0.Final (revision: 9aa71)]

    at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jac

: 9aa71)]

    at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final

    at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.

Caused by: java.sql.SQLException: Listener refused the connection with the following error:

ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:755)

    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:721)

    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:415)

    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:26)

    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:597)

    at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:457)

    at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:763)

    at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:293)

    at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:220)

    at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:507)

    ... 12 more

Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:

ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

    at oracle.net.ns.NSProtocolStream.negotiateConnection(NSProtocolStream.java:312)

    at oracle.net.ns.NSProtocol.connect(NSProtocol.java:286)

    at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1871)

    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:554)

    ... 21 more

[mayerw01]

Please check the Oracle documentation:

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action:

- Wait a moment and try to connect a second time.

- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>

- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.

- Check for an event in the listener.log file.