Vinoth Rajendran

I have generated the stub using axis2 xmlbeans options.

I do set the request params and call the method like below

RetrievePartyResponseDocument document = stub
               .retrieveParty(retrievePartyDocument,
                       msgDetlDocument, traceDocument,
                       extendedHeaderDocument);
and the response comes like below. I could only read the retrievePartyResponse details not the details from the Header part. Webservice team updating details in Header section for one of the exception scenario. I need to retrieve it. Please advise how can it be done

<?xml version="1.0" encoding="UTF-8"?> <env:Envelope> <env:Header>        <com:MsgDetl mustUnderstand="false">            <com:MsgVersion>4.0</com:MsgVersion>            <com:SvcVersion>4.0</com:SvcVersion>        </com:MsgDetl>          </env:Header>    <env:Body>        <op:retrievePartyResponse>            <op:Detl>                <op:OptOutInd>false</op:OptOutInd>            </op:Detl>        </op:retrievePartyResponse>       </env:Body> </env:Envelope>

Hi,

We have an application to consume webservice over SSL. We have created stub using AXIS2 1.6.2 and application is deployed in websphere 8.5.5.4. Below error is thrown when it initiates the request over SSL. Please advise whether any extra settings required on the Websphere side.

9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O exception (javax.net.ssl.SSLException) caught when processing request: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set. [9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry Retrying request [9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O exception (javax.net.ssl.SSLException) caught when processing request: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set. [9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry Retrying request [9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O exception (javax.net.ssl.SSLException) caught when processing request: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set. [9/23/15 0:50:17:219 SGT] 000001f1 HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector executeWithRetry Retrying request [9/23/15 0:50:17:219 SGT] 000001f1 HTTPSender I org.apache.axis2.transport.http.HTTPSender sendViaPost Unable to sendViaPost to url[https://10.91.35.41:37157/Services/EventInq] javax.net.ssl.SSLException: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set. at com.ibm.websphere.ssl.protocol.SSLSocketFactory.createSocket(SSLSocketFactory.java:334) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:116) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:130) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) at com.avaya.aps.cep.stub.EventInqStub.eventInq(EventInqStub.java:220) at com.avaya.aps.selfservice.host.services.impl.CEPServiceImpl.getCEPEventDetails(CEPServiceImpl.java:138) at flow.CEPLookup.servletImplementation(CEPLookup.java:65) at com.avaya.sce.runtime.BasicServlet.handleRequest(BasicServlet.java:99) at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96) at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:285) at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.java:190) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1111) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3901) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1865)

[9/23/15 0:50:17:219 SGT] 000001f1 SystemOut O - [12423435435353]AxisFault while connecting to CEPSSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set.

I meant, the middle layer was consuming the webservice.

Client application required to send http request middle layer instead of soap.

Used HttpClient example from http://stackoverflow.com/questions/2735839/posting-xml-request-in-java to make it work.

It doesnt work directly.

It works through HttpClient. Thanks

Hi,

WAS server doesn't have network connection to WS . But there is network connection from intermediate layer system.

That is the way it is designed and they say it is consumed by other projects.

I think we can consider it is like middle layer or proxy layer.

Please advice which approach can be used to consume it.


Thanks
Vinoth

Hi Ulf Dittmer,

Thanks.
Yes. intermediate layer perform an actual client-side HTTP redirect.
It connects to webservice and receives the response.

They have provided new http URL(intermediate layer) to access the webservice. The request xml sent to http URL provided and from there it is sent to actual webservices.
Please advice on the approach to write the client code. can this be done using Restful or xml over http.

Provided intermediate layer URL is accessible from soap UI and we could send the request and receive the response.

This redirection in place as the webservice is not in customer network and they want every request to go through their path.

Thanks
VInoth

Hi,

I have a requirement to consume the webservices.

I have genereted the client using axis2 and I could consume it if it can be accessed directly.

Client --> Webservice

I have an issue when there is an intermediate layer.

Client - -> Intermidate Layer(Http Request Redirector) -- > Webservice.

Please advice whether it can be accessed with the client generated or any other settings required on the axis2 side?

Is there any other alternate way to communicate with axis2?



Thank
Vinoth

Hi All,

Thanks for the information.
I have tries tuning the JAVA options but it doesn't seems to be helping.

Physical memory always keeps increasing and the server could sustain only for a day with 2 GB.

Thanks.

Hi Tim,

Thanks.
I am monitoring server with java melody.

I am using tomcat 6.0.35 and JDK 1.7. Is it compatible?. Can it create an issue?

Hi,

I have set the JAVA options settings value for tomcat 6.0.35 as

"-Xms2048m -Xmx2048m -XX:PermSize Size=1024m -XX:MaxPermSize=1024m -XX:NewSize=512m "

Physical memory keeps increasing for every request. 70 request is coming into server at a time.

It has grown up to 2384,012K and didn't crash.

I have restarted the server when it reach 2384,012K. There was no impact to the system and I don't see any errors.

I have Java application to connect to MQ Series via MQQuemanager. It creates new connection for every request and then closes it.

Also it has JDBC connection to get details from Database.

is there any log generated by tomcat if there is a memory leak.

Please advice to validate it.

Thanks in advance

Hi,

I have a requirement to transfer the file to remote systems.

I wanted to do it with the FileChannel and don't want to use FTPClient.

FileChannel ic = new FileInputStream(sourcePath).getChannel();
FileChannel oc = new FileOutputStream("\\\\117.254.24.154\\Endhiran").getChannel());
ic.transferTo(0, ic.size(), oc);
ic.close();
oc.close();

Application throws an exception when it reach FileChannel oc = new FileOutputStream("\\\\117.254.24.154\\Endhiran").getChannel()); with unavailable destination path.

There is no issues when the destinationpath is reachable.

I wanted to know why does it takes 4 minutes to throw exception when the destination path is not available.

Can anyone advice on how to make it throw exception immediately when the dest is not reachable?

Thanks in advance.

Thanks
Vinoth