Hello,

I'm using the JBoss server as a client of a "Smalltalk" webservice. I did not want to deploy stubs on the JBoss server with the EJB's. I want to use just the material JBoss offers to use an stateless session bean as a client. So I deployed a stateless session bean with 2 service-ref elements. The first for using with dynamic proxy, the second for using with DII.

Dynamic proxy

InitialContext context = new InitialContext();
WOnSoapInterface_Service service = (WOnSoapInterface_Service) context.lookup("java:comp/env/service/WOnSoapService");
WOnSoapInterface_PortType port = service.getWOnSoapInterface();
result = port.getDomainInformation(clientId, domain);

InitialContext context = new InitialContext();
Service service = (Service) context.lookup("java:comp/env/service/WOnSoapService2");
QName port = new QName("ns:WOnSoapInterface", "WOnSoapInterface");
QName operation = new QName("ns:WOnSoapInterface", "GetDomainInformation");
Call call = service.createCall(port, operation);
Object[] inputParams = new Object[] {clientId, domain};
result = (String) call.invoke(inputParams);

Hello,

I forgot to tell that all things are happening on my Windows laptop and I do have Ethereal. I'm testing JBoss 4 to see if we can replace the Jboss 3 (production) server. The JBoss 3 server now uses SLSB's and Axis 1.1 client stubs to access the HTTPS webservice.

Also I did the wscompile on my laptop for generating stubs.

Stub call

WOnSoapInterface_Service_Impl service = new WOnSoapInterface_Service_Impl();
WOnSoapInterface_PortType_Stub stub = (WOnSoapInterface_PortType_Stub) service.getWOnSoapInterface();
stub._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, "https://[server]:[port]/WOn");
result = stub.getDomainInformation(clientId, domain);

Pfff... You really are naming some network technical things.
I'm not a network expert :-( but I will try to look for some things.
B.t.w. I do use Ethereal for seeing how the SOAP messages look like.

I'm still wondering why the Stub call works over https and the dynamic proxy and DII calls not.
I can see that the Stub call is working because Ethereal does show the SOAP message scrambled if I follow the tcp stream and I'm getting the good result.

T.I.A.

Johan

Hello,

Thanks for answers. I did some work with Ethereal.
The test environment on the smalltalk side has 2 urls, one without https and one with https. I only have to change the port and protocol.
I did generate stubs with (jwsdp-1.5) wscompile. The smalltalk side has not a wsdl document available on the site but we get the WSDL private. With the stub test I only use the SUN libs delivered with jwsdp-1.5.
What I could see was that working with the stub version of SUN the the 2 urls do return good data. Because I do get a good results in both cases. I checked with Ethereal if one test is really over https and this was the case as I could see the scrambled data coming in and information of the certificate.

So back to JBoss and using the 4.0.1sp1 as it is. I do the same test again with the dynamic proxy, one call over http and one call over htpps with the SLSB. The call over http gives a good result and the call over https gives a time out :-(

But what I saw with Ethereal was that with the call over https all the data is coming back after 2 seconds in bot cases. I also could see the scrambles data coming back over https an information about the certificate info.
But in the case of https the data comes back in about 2 seconds but JBoss never sees that it has arrived. Or it can't see a sort of EOF.
JBoss waits 1 minute and then gives the error which you can see at the top of this thread.

So it seems that I do not have network problems with the https url.
But why does JBoss not see that the data has been received?

T.I.A. Johan

Hello,

I did also a test with JBoss-4.0.2RC1. The same results. I still get the time out over https.

But I think I know why do get the time out. The URL below is an example of the data that is coming back asking for countries of the http connection.
But if I do ask another domain I do get back data over https.
But what is the difference?
I think it has do do something with corrupt characters. If e.g. the word Slovenië is returned you can see in the example that the value is Slovenië.
I also tried another domain with a few special characters and that domain also gives a time out.
It seems that with https the reader gets confused and waits for some ending which wil not come and after 1 minute he gives up.

We should talk with the people on the other side why they give bad characters.
But on the other hand the stubs of SUN are able to read over https and JBoss is only able to read over http those bad characters.

http://www.solcon.nl/jborchers/GetDomainInformation.txt

T.I.A. Johan.

Hello,

Is there a possibility that a reader in JBoss can have a time out because it sees no end due to bad characters while using https!

Johan

Hello,

Also a test with Axis 1.1 stubs, just as we are using now, the reader gets the time out exception when used over https.

Johan

Hello,

I'm getting tired but debugging in Eclipse shows that the characters ë in the word Slovenië are correct translated to ë. Because a test with a lot bigger result coming with the same characters gives a good result over https.

So for me it is a mystery why you can see that after 2 seconds you see the result coming in over https with Ethereal and the reader in JBoss still waits for some ending.

Johan

Hello,

I did not get an answer on the question if bad characters could disturb the reading of SOAP. So I assume this is not the case.

But why can I read 2 domains over https with the SUN stubs and why not with JBossWS or Axis?
Someone was saying to me that it could be that a port is not closed????
I'm not a http expert so I will show the 2 SOAP calls over http.

JBoss Dynamic Proxy SOAP call over http

POST /WOn HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/#axisVersion#
Host: [server]:[port]
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 515

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <ns1:GetDomainInformation xmlns:ns1="urn:wonsoapnamespace">
 <clientID>
 <user>[username]</user>
 <password>[password]</password>
 <departmentId>[department]</departmentId>
 </clientID>
 <domainID>Country</domainID>
 </ns1:GetDomainInformation>
 </soapenv:Body>
</soapenv:Envelope>HTTP/1.1 200
Content-Type: text/xml;charset=utf-8
Content-Length: 25694
Connection: close

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
 xmlns:m="urn:wonsoapnamespace"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:s="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:GetDomainInformationResponse>
 <return xsi:type="s:string">[lot of text]</return>
 </m:GetDomainInformationResponse>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

POST /WOn HTTP/1.1
Content-Type: text/xml; charset=utf-8
Content-Length: 536
SOAPAction: ""
User-Agent: Java/1.4.2_07
Host: [server]:[port]
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope
 xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
 xmlns:ns0="urn:wonsoapnamespace">
 <env:Body>
 <ns0:GetDomainInformation>
 <clientID>
 <ns0:user>[username]</ns0:user>
 <ns0:password>[password]</ns0:password>
 <ns0:departmentId>[department]</ns0:departmentId>
 </clientID>
 <domainID>Country</domainID>
 </ns0:GetDomainInformation>
</env:Body>
</env:Envelope>HTTP/1.1 200
Content-Type: text/xml;charset=utf-8
Content-Length: 25694
Connection: Keep-Alive

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
 xmlns:m="urn:wonsoapnamespace"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:s="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:GetDomainInformationResponse>
 <return xsi:type="s:string">[lot of text]</return>
 </m:GetDomainInformationResponse>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

 TCP [mylaptop]:2141 [server]:[port] ESTABLISHED 616
 [javaw.exe]