RE: java.net.ConnectException: Connection refused

2004-01-30 Thread Stuart Miller
Mohammed, try setting the system property 'javax.net.ssl.debug' to 'all', and you should see details of the SSL handshake in stdout. It's likely that your client VM doesn't have a suitable certificate for the server (one that is issued by a CA that the server trusts). Also, if you have OpenSSL,

Re: java.net.ConnectException: Connection refused: connect (RESOLVED)

2003-04-02 Thread Hans Russo resowe
ghran" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 9:29 PM Subject: Re: java.net.ConnectException: Connection refused: connect > you should be using forward / in urls and things; the backslash is a > windows only hack. > > Hans Russo resowe

Re: java.net.ConnectException: Connection refused: connect

2003-04-01 Thread Steve Loughran
you should be using forward / in urls and things; the backslash is a windows only hack. Hans Russo resowe wrote: Maybe you are right but the file Zeitansageservislocator was generated by WSDL2Java. Indeed there was a problem: WSDL2Java was not able to write the string Zeitansage_Service_address ,

Re: java.net.ConnectException: Connection refused: connect

2003-04-01 Thread Hans Russo resowe
Maybe you are right but the file Zeitansageservislocator was generated by WSDL2Java. Indeed there was a problem: WSDL2Java was not able to write the string Zeitansage_Service_address , see the listing bellow, correctly. I had to edtit the string Zeitansage_Service_address. It was necessary to write

RE: java.net.ConnectException: Connection refused: connect

2003-04-01 Thread Tom Jordahl
Your server isn't running, or you are trying to connect to the wrong port, so you are getting a connection refused. -- Tom Jordahl Macromedia Server Development -Original Message- From: Hans Russo resowe [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2003 4:01 AM To: [EMAIL PROTECT