Oracle eWay : Closed Connection problem
Hi everyone,
I hava a collaboration which use an oracle otd.
Unexpected I get next error:
project: runtime, component: OracleVariables, deployment: dpS3SOAServicioAutorizacionProd, environment: envProduction, logicalhost: lhProduction, integration server: isProduction ], monitor: ObjectReference [ name: SeeBeyond:GUID={06000000-D7828CEF100100-AC1907FD-01},Name=prjS3SOAServicioAutor iza_1164935312|runtime|dpS3SOAServicioAutorizacionProd|esS3OracleDBPerfiles_Outb ound Oracle eWay ], alert message: Closed Connection|#]
Why ?
How eWay control session to database?
Thanks
[615 byte] By [
conectora] at [2007-11-26 19:32:25]
# 2
Hi,
Thanks for yor reply.
My first lines on my collaboration are
public void receive( com.stc.connector.appconn.tcpip.ext.TCPIPEXTServerApplication input, com.stc.connector.appconn.ldap.LDAPClientApplication LDAPClient_1, otdS3VariablesEsb.OtdS3VariablesEsbOTD otdS3VariablesEsb_1, otdS3PerfilesUsuario.OtdS3PerfilesUsuarioOTD otdS3PerfilesUsuario_1 )
throws Throwable
{
byte[] datosRespuestaServicio = null;
Comunicador manejadorComunicaciones = null;
String mensajeError = "Error Interno LDAP";
logger.info( "jcd " + collabContext.getCollaborationName() + " recibiendo peticion desde " + input.getSocket().getInetAddress() );
......................
My oracle external systes has next properties:
MinPoolSize:20
MaxPoolSize:40
MaxIdleTimeOut:0
ConnectionRetries:0
ConnectionRetryInterval:10000
My scenario is:
Logical host is up
I Test my collaboartion and it work ok
Database is down for while two hours
Database is now up.
I test my collaboration and it don't work ok. It Do磏't reconnect to database.
I send message to java collaboration but line on my collaboration : logger.info( "jcd " + collabContext.getCollaborationName() + " recibiendo peticion desde " + input.getSocket().getInetAddress() ); is never printed.
I find next lines on server.log when test my collaboration:
[#|2007-02-26T13:14:51.631-0500|INFO|IS5.1.1|STC.eWay.framework.management.com. stc.connector.management.util.Alerter|_ThreadID=73; ThreadName=Worker: 60;|sendAlert(), connection info: ConnectionInfo [ collaboration: cmS3TCPEntregaLdap_jcdS3TcpEntregaLdap1, project: runtime, component: OracleS3VariablesEsb, deployment: dpS3TCPEntregaLdapProd, environment: envProduction, logicalhost: lhProduction, integration server: isProduction ], monitor: ObjectReference [ name: SeeBeyond:GUID={7C020000-D7828CEF100100-AC1907FD-01},Name=prjS3TcpEntregaLdap_u 002_1882209590|runtime|dpS3TCPEntregaLdapProd|esS3OracleDBPerfiles_Outbound Oracle eWay ], alert message: null|#]
[#|2007-02-26T13:14:51.704-0500|FINE|IS5.1.1|STC.eWay.framework.ra.com.stc.conn ector.framework.util.SemiSema|_ThreadID=86; ThreadName=Worker: 72;|acquire true 0|#]
[#|2007-02-26T13:14:51.711-0500|FINE|IS5.1.1|STC.eWay.framework.ra.com.stc.conn ector.framework.util.SemiSema|_ThreadID=86; ThreadName=Worker: 72;|release 1|#]
[#|2007-02-26T13:14:51.953-0500|INFO|IS5.1.1|STC.eWay.framework.management.com. stc.connector.management.util.Alerter|_ThreadID=30; ThreadName=Worker: 19;|sendAlert(), connection info: ConnectionInfo [ collaboration: cmS3TCPEntregaLdap_jcdS3TcpEntregaLdap1, project: runtime, component: OracleS3VariablesEsb, deployment: dpS3TCPEntregaLdapProd, environment: envProduction, logicalhost: lhProduction, integration server: isProduction ], monitor: ObjectReference [ name: SeeBeyond:GUID={7C020000-D7828CEF100100-AC1907FD-01},Name=prjS3TcpEntregaLdap_u 002_1882209590|runtime|dpS3TCPEntregaLdapProd|esS3OracleDBPerfiles_Outbound Oracle eWay ], alert message: null|#]
[#|2007-02-26T13:14:52.249-0500|INFO|IS5.1.1|STC.eWay.framework.management.com. stc.connector.management.util.Alerter|_ThreadID=88; ThreadName=Worker: 74;|sendAlert(), connection info: ConnectionInfo [ collaboration: cmS3TCPEntregaLdap_jcdS3TcpEntregaLdap1, project: runtime, component: OracleS3VariablesEsb, deployment: dpS3TCPEntregaLdapProd, environment: envProduction, logicalhost: lhProduction, integration server: isProduction ], monitor: ObjectReference [ name: SeeBeyond:GUID={7C020000-D7828CEF100100-AC1907FD-01},Name=prjS3TcpEntregaLdap_u 002_1882209590|runtime|dpS3TCPEntregaLdapProd|esS3OracleDBPerfiles_Outbound Oracle eWay ], alert message: null|#]
Thanks on advanced
Hector
# 6
Hi,
According to my knowledge, when we are exectuing a jcd which has oracle OTD first time , then eway tries to establish the connection with oracle. If connection is not success then jcd will not get invoked.
But once a conection is established with oracle, and after then if oracle
server is down or restarted, then eway will try to interact with oracle using already established connection. It is one of the reason to get error. Oracle Eway will not try to reconnect with oracle. In this scenario, according to my knowledge, handling reconnection through[oracleotd.reconnect()] will work.
