ESB and Registry WSDL key problem

Hi

You can use any valid value to key. Both 'WSDL/myappservice?wsdl' and 'WSDL/myappservice' as key is okay as logg as there is an resource(wsdl) in the registry with that key. Please check the content of the resource with key 'WSDL/myappservice'. It should contains wsdl.

Thanks
Indika

Hi,

under both names/keys is the same wsdl, I have check this and synapse shows the same wsdl. The only difference is that I change the "Resource Name".

When I send a request to the changed resource name I become following log message:

DEBUG [14 May 2009 08:31:52] ServerHandler - New incoming connection
DEBUG [14 May 2009 08:31:52] ServerHandler - Connection closed

With the unchanged resource name in the Registry I become following log message (the correct):

DEBUG [14 May 2009 08:37:32] ServerHandler - New incoming connection
DEBUG [14 May 2009 08:37:32] ConnectionPool - closing stale connection to : 10.0.0.14:8080
DEBUG [14 May 2009 08:37:32] HttpCoreNIOSender - A new connection established to : 10.0.0.14:8080
DEBUG [14 May 2009 08:37:32] Axis2HttpRequest - Start streaming outgoing http request : [Message ID : urn:uuid:5C1205FF41220993E82301259864000267-209743644]
DEBUG [14 May 2009 08:37:32] ClientHandler - ClientHandler connected : [/10.0.0.14:8080]
DEBUG [14 May 2009 08:37:32] Axis2HttpRequest - Message [Request Message ID : urn:uuid:5C1205FF41220993E82301259864000267-209743644] [Request Message Payload : [ ]
DEBUG [14 May 2009 08:37:32] headers - >> POST http://10.0.0.14:8080/myapp/myappservice HTTP/1.1
DEBUG [14 May 2009 08:37:32] headers - >> Soapaction:
DEBUG [14 May 2009 08:37:32] headers - >> Content-Type: text/xml; charset=UTF-8
DEBUG [14 May 2009 08:37:32] headers - >> Transfer-Encoding: chunked
DEBUG [14 May 2009 08:37:32] headers - >> Host: 10.0.0.14:8080
DEBUG [14 May 2009 08:37:32] headers - >> Connection: Keep-Alive
DEBUG [14 May 2009 08:37:32] headers - >> User-Agent: Synapse-HttpComponents-NIO
DEBUG [14 May 2009 08:37:32] ClientHandler - Response Received for Request : Axis2Request [Message ID : urn:uuid:5C1205FF41220993E82301259864000267-209743644] [Status Completed : true] [Status SendingCompleted : true]
DEBUG [14 May 2009 08:37:32] ConnectionPool - Released a connection to host: 10.0.0.14 on port : 8080 to the connection pool of current size : 1
DEBUG [14 May 2009 08:37:32] ServerHandler - Connection closed

Is it a bug?

Thanks,
Piioo

Hi

Is proxy service is available after resource name changed? you can check with http://localhost:8280/services/proxy service name.

By looking logs , I can only say that with the changed resource , external service call hasn't been occurred.This may happen, if the proxy service is not available and request has been dispatched to main message mediation and it didn't contain send mediator.

Thanks
Indika

Hi,

the Proxy service is over http://localhost:8280/services/myappservice and http://localhost:8280/services/myappservice2 available and the wsdl's are shown. The wsdl's are the same, only the name of the service differ.

myappservice is the with the change resource name in the registry. I have change the name by creating the resource, so the proxy must be all right.

Here is the complete log from the service, which do not work:

DEBUG [14 May 2009 09:30:05] SimpleScheduler - CHECK STALE NODES started
DEBUG [14 May 2009 09:30:08] SSLIOSession - I/O session sslserver-7 [interested ops: []; ready ops: []][SSL handshake status: NOT_HANDSHAKING][0][0][0][0]: Set event [r]
DEBUG [14 May 2009 09:30:08] ServerHandler - New incoming connection
DEBUG [14 May 2009 09:30:08] DefaultNHttpServerConnection - Consume input
DEBUG [14 May 2009 09:30:08] SSLIOSession - I/O session sslserver-7 [interested ops: [r]; ready ops: [r]][SSL handshake status: NEED_UNWRAP][0][0][0][0]: -1 bytes read
DEBUG [14 May 2009 09:30:08] SSLIOSession - I/O session sslserver-7 [interested ops: [r]; ready ops: [r]][SSL handshake status: NEED_UNWRAP][0][0][0][0]: Close
DEBUG [14 May 2009 09:30:08] DefaultNHttpServerConnection - Shutdown connection
DEBUG [14 May 2009 09:30:08] SSLIOSession - I/O session sslserver-7 [invalid][SSL handshake status: NEED_UNWRAP][0][0][0][0]: Shutdown
DEBUG [14 May 2009 09:30:08] ServerHandler - Connection closed
DEBUG [14 May 2009 09:30:09] SimpleScheduler - LOAD IMMEDIATE started
DEBUG [14 May 2009 09:30:09] SinglePoolConnectionInterceptor - Supplying pooled connection MCI: org.apache.geronimo.connector.outbound.ManagedConnectionInfo@17ec4e2 MC: org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 from pool: org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor@31bd0
DEBUG [14 May 2009 09:30:09] TransactionCachingInterceptor - supplying connection from pool null for managed connection org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 to tx caching interceptor org.apache.geronimo.connector.outbound.TransactionCachingInterceptor@13cc05f
DEBUG [14 May 2009 09:30:09] GeronimoConnectionEventListener - connectionClosed called with org.tranql.connector.jdbc.ConnectionHandle@8b62eb for MCI: org.apache.geronimo.connector.outbound.ManagedConnectionInfo@17ec4e2 and MC: org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195
DEBUG [14 May 2009 09:30:09] TransactionCachingInterceptor - tx active, not returning connectionorg.tranql.connector.jdbc.ConnectionHandle@8b62eb for managed connection org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 to tx caching interceptor org.apache.geronimo.connector.outbound.TransactionCachingInterceptor@13cc05f
DEBUG [14 May 2009 09:30:09] TransactionCachingInterceptor - Transaction completed, attempting to return shared connection MCI: org.apache.geronimo.connector.outbound.ManagedConnectionInfo@17ec4e2 for managed connection org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 to tx caching interceptor org.apache.geronimo.connector.outbound.TransactionCachingInterceptor@13cc05f
DEBUG [14 May 2009 09:30:09] AbstractSinglePoolConnectionInterceptor - returning connection null for MCI org.apache.geronimo.connector.outbound.ManagedConnectionInfo@17ec4e2 and MC org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 to pool org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor@31bd0
DEBUG [14 May 2009 09:30:09] TransactionCachingInterceptor - completed return of connection through tx cache null for MCI: org.apache.geronimo.connector.outbound.ManagedConnectionInfo@17ec4e2 and MC org.tranql.connector.jdbc.ManagedJDBCConnection@1afe195 to tx caching interceptor org.apache.geronimo.connector.outbound.TransactionCachingInterceptor@13cc05f
DEBUG [14 May 2009 09:30:09] SimpleScheduler - LOAD IMMEDIATE complete

----------------

I do not understand this:

I have change now the publishWSDL in the synapse configuration from the not working proxy, it is the same now then the working proxy. But this Proxy do not work anyway.

synapse.xml see file

Thanks,
Piioo

I was sending the request over https and dont have the certificate. This was the problem with the Handshake

Thanks,
Piioo

Hi

Nice to here that you got success .
What was the relation with 'Resource Rename'?.

Thanks
Indika

There wasn't a relation with resource rename.

It was the https problem. I don't know why my tool (SOAP Client for Mac) was sending the requests over http and in all other cases over https.

Thanks,
Piioo