SOAP: Connection refused: Issue
Hi Guru's ,
We are facing trouble in executing outbound scenarios using SOAP channel.
All the messages are getting processed fine in SXMB_MONI but in comm channel monitoring we are getting below mention message
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect"
"SOAP: call failed: java.net.ConnectException: Connection refused: connect"
Inbound is working fine for this scenario its just for outbound its not working.
This issue is for all the outbound interfaces using SOAP Communication Channel.
This is issue is in our new production server having clusters (2 nodes).
The same interface works fine in QA and Dev.
Any idea's what could be the issue.
Cheers !
PI Rocker
Hi Volker,
We were using this option because we were facing issues in SOAP reciver system while reciving messages in QA and Dev .
But just to give a try I removed the tick from "Do Not use SOAP Envelope".
Now I am getting below message in Communication Channel.
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 415 Unsupported Media Type: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 415 Unsupported Media Type
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 415 Unsupported Media Type "
Any clues ?
Similar Messages
-
SOAP 'Connection refused' in java
I am using the code attached to Log onto the SOAP Actuate reporting server using HttpURLConnection in Java. I get "java.net.ConnectException: Connection refused" while calling connection.getInputStream(); PLease note I do not get error while openConnection() but get it while getting the InputStream.
URL u = new URL("http://devserver:8000//soap/servlet/acweb");
System.out.println("Opening connection...");
URLConnection uc = u.openConnection();
System.out.println("Opening connection Done...");
HttpURLConnection connection = (HttpURLConnection) uc;
connection.setDoOutput(true);
connection.setDoInput(true);
connection.setRequestMethod("POST");
connection.setRequestProperty("Connection", "Keep-Alive");
connection.setRequestProperty("Content-Type", "text/xml;charset-'utf-8'");
connection.setRequestProperty("SOAPAction", "");
Writer wout = new OutputStreamWriter(connection.getOutputStream());
System.out.println("connection.getOutputStream...");
wout.write("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n");
wout.write("<SOAP-ENV:Envelope xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"");
wout.write("xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"");
wout.write("xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">");
wout.write("<SOAP-ENV:Body>");
wout.write("<SOAP-ACTU:Login xmlns:SOAP-ACTU=\"http://schemas.actuate.com/actuate6\">");
wout.write("<User>testuser</User>");
wout.write("<Password>tsetpwd</Password>");
wout.write("<Domain>HQ</Domain>");
wout.write("<UserSettings>true</UserSettings>");
wout.write("</SOAP-ACTU:Login>");
wout.write(" </SOAP-ENV:Body>");
wout.write("</SOAP-ENV:Envelope>");
wout.flush();
wout.close();
System.out.println("Wout.close...");
InputStream in = connection.getInputStream();
System.out.println("connection.ger Input Stream...");
int c;
while ((c = in.read()) != -1) System.out.print(c);
in.close();
System.out.println("Input Stream closed...");
catch (IOException e)
System.out.println("IO EXception : "+e);
catch (Exception ee)
System.out.println("EXception : "+ee);"Connection refused" generally means there is no server listening at the port you tried to connect to.
-
Receiver SOAP Adapter : Error Connection Refused (errno: 239)
Hello
I am testing a simple scenario using SOAP Adapter. I am getting the following error.
com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please tell me what could be the error for the following scenario.
Best Regards,
KiranHi Venkat,
We are actually not using the sender comm channel
http://<server>:<port>/ sap/xi/engine?type=entry&version=3.0&Sender.Party=<party name>&Sender.Service=<>&Interface=<namespace>^<interface>
This stated endpoint is fine there is no error with it.
Thanks.
Kiran -
SOAP (Receiver): error occured: Connection refused:
Hi experts,
I have a RFC -> XI -> SOAP scenario and while testing the same it gets cancelled with the following errors:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
Exception caught by adapter framework: Connection refused: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.
Please help me out.
Regards,
DanielaHi,
1. Either the SOAP Url in the SOAP adapter is wrong,
2. Or there is a proxy server between XI and the Webserivce and so provide the proxy server details in the SOAP adapter ( with Authentication ) if needed and give it a shot.
Regards
Bhavesh -
SOAP Exception, Connection refused error in jdeveloper 11g
Hello,
I am using jdeveloper 11g 11.1.2.3.0.
I have been experiencing the following error everytime I try to run the applicaiton. I use webservices in my applicaiton and recently the webservices url were changed pointing now to dev instead of the lab environment. The code has been migrated to dev environment, I tested the webservices in my browser, they seem to be working fine and are pulling up the required data.
ERROR:
javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
Error
Message send failed: Connection refused: connect
Error
Connection refused: connect
I am not sure what is causing this. Any help would be appreciated.
Thanks in advance,
SalHello Frank,
Thanks for your response. I checked the browser proxy settings in Jdeveloper, nothing is set there right now. Use HTTP Proxy Server is unchecked. What do I need to set this to?
Thanks,
Sal -
I am new to Mac and i managed to install and configure all the services. Now my issue is when i sending mail using the local server to internal, mails are not receiving. Mail queue showing Connection refused error. Please help me
Thanks
GIRITry this -> http://support.apple.com/kb/TA38632?viewlocale=en_US
-
ReportViewer control not connecting to the report server - Connection refused
I'm having an issue with connecting to SQL report server using the ReportViewer control. Thing is when I connect to the reporting services web service (http://10.3.27.80/ReportServer/ReportService2010.asmx)
it works fine and I can successfully pull the data I need. But when I use the web control, its then that I cannot connect. Here's my code:
ASP.net code:
<%@ Page Title="Reports" Language="C#" MasterPageFile="~/Site.Master" AutoEventWireup="true" CodeBehind="Results.aspx.cs" Inherits="RSReportViewer.Results" %>
<%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>
<asp:Content ID="BodyContent" ContentPlaceHolderID="MainContent" runat="server">
<rsweb:ReportViewer ID="ReportViewer2" runat="server" Width="90%" ProcessingMode="Remote">
<ServerReport ReportServerUrl="http://10.3.27.80:80/" />
</rsweb:ReportViewer>
Error message:
ConnectionRefused
Inner Exception: No connection could be made because the target machine actively refused it 176.74.176.178:8080
I have not got the IP signified above configured anywhere throughout my solution! So not sure where its getting that in the message.
Stack trace:
at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.SetConnectionSSLForMethod(String methodname)
at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WebForms.SoapReportExecutionService.LoadReport(String report, String historyId)
at Microsoft.Reporting.WebForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WebForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at RSReportViewer.Results.Page_Load(Object sender, EventArgs e) in c:\Users\admin\Desktop\RSViewer\RSViewer\RSReportViewer\Results.aspx.cs:line 71
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Firewalls are disabled between the two boxes.
Thanks in advance for any pointers!Hi rmccabe82,
Generally, “actively refused it" means that the host sent a reset instead of an acknowledge when you tried to connect. As per my understanding, the issue can be caused by the process that is hosting the service is not listening on that port, this may be
because it is not running at all or because it is listening on a different port. Please try to ping ‘netstat –anb’ (requires admin privileges) to verify that it is running and listening on the expected port.
Furthermore, please make sure the user has permissions to access the report server.
References:
http://www.smartftp.com/support/kb/connection-refused-f58.html
http://stackoverflow.com/questions/9695224/no-connection-could-be-made-because-the-target-machine-actively-refused-it-127-0
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
Hi,
I try to load test my web site using apache soap 2.2 for doing some web services. However, when I increase the number of threads in the load test. I got connection refused exception from OC4J and also find SOAPException : msg=Error opening socket...
Is there a max. connection setting in oc4j?
Can any one give me a hand in this issue?
Thanks in advanced!
Regards,
--kennethThe problem is addressed (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665037):
Use this code to test the localhost, and I found that those successful machines returned hostname/correct IP, those unsuccessful machines returned hostname/127.0.0.1.
----------------- BEGIN SOURCE --------------------
import java.net.*;
public class LocalHostTest {
public static void main(String[] args) {
try {
System.out.println(InetAddress.getLocalHost());
} catch (Exception e) { e.printStackTrace(); }
----------------- END SOURCE -------------------- -
Hello,
We have created a webservice deployed to WebLogic Server 9.2. It requires secure transport using the annotation
@UserDataConstraint(transport=UserDataConstraint.Transport.CONFIDENTIAL)
We're able to test this successfully using an XSmiles client browser.
However, I've written a Java client started with "clientgen" that runs successfully when connecting in nonsecure mode (annotation removed) to a local instance. But when I try to connect to our remote server in secure mode I get "connection refused" (the lengthy call stack is copied below).
The client code is also copied below (a few strings and IPs were changed). It's able to retrieve the WSDL, but then bombs when calling a port method. This is probably something simple but I've followed tutorials and have not found reference to this particular error on forums or via Google. Any ideas would be appreciated!
Thanks,
CJ
= = = = = = = =
System.setProperty ("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
java.security.Security.addProvider (new com.sun.net.ssl.internal.ssl.Provider());
// must define .trustStoreType, .trustStore, and .trustStorePassword
System.setProperty("javax.net.ssl.trustStore", "c:\\client-keytool.ts");
System.setProperty("javax.net.ssl.trustStorePassword", "password");
System.setProperty("javax.net.ssl.trustStoreType", "JCEKS");
System.setProperty("weblogic.wsee.client.ssl.stricthostchecking", "false");
System.out.println ("Connecting to the webservice...");
PatientRegistrationService service = new PatientRegistrationService_Impl ("https://domain/ws/services/PatientRegistrationPort?WSDL");
PatientRegistrationPort port = service.getPatientRegistrationPort();
SecurityQuestionRequestType request = new SecurityQuestionRequestType();
RequestHeaderType requestHeader = new RequestHeaderType();
requestHeader.setApplication("x");
requestHeader.setAppLoginId("x");
requestHeader.setAppPassword("x");
request.setRegistrationRequest (requestHeader);
System.out.println ("Calling getSecurityQuestion method...");
SecurityQuestionResponseType response = port.getSecurityQuestion (request);
System.out.println ("...just called getSecurityQuestion.");
= = = = = = = =
Connecting to the webservice...
Calling getSecurityQuestion method...
Exception in thread "Main Thread" java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [Failed to send message using connection:(SoapClientConnection@41626058 <transport=(HTTPSClientTransport@41626055 <url=https://IPADDRESS:9223/domain/ws/PatientRegistrationPort>)>)Connection refused: connect] FaultActor [null] Detail [<detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0"></bea_fault:stacktrace>java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Ljava.net.InetAddress;II)V(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:280)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:337)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:176)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:162)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:836)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
at weblogic.wsee.connection.transport.http.HTTPClientTransport.send(HTTPClientTransport.java:161)
at weblogic.wsee.connection.soap.SoapConnection.send(SoapConnection.java:54)
at weblogic.wsee.connection.soap.SoapClientConnection.send(SoapClientConnection.java:89)
at weblogic.wsee.ws.dispatch.client.ConnectionHandler.handleRequest(ConnectionHandler.java:89)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:100)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:101)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)
</detail>]; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Failed to send message using connection:(SoapClientConnection@41626058 <transport=(HTTPSClientTransport@41626055 <url=https://IPADDRESS:9223/domain/ws/PatientRegistrationPort>)>)Connection refused: connect
at test.wsclient.PatientRegistrationPort_Stub.getSecurityQuestion(PatientRegistrationPort_Stub.java:337)
at test.client.TestClient4.main(TestClient4.java:80)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Failed to send message using connection:(SoapClientConnection@41626058 <transport=(HTTPSClientTransport@41626055 <url=https://IPADDRESS:9223/domain/ws/PatientRegistrationPort>)>)Connection refused: connect
at weblogic.wsee.codec.soap11.SoapCodec.decodeFault(SoapCodec.java:259)
at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeFault(CodecHandler.java:105)
at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:90)
at weblogic.wsee.ws.dispatch.client.CodecHandler.handleFault(CodecHandler.java:78)
at weblogic.wsee.handler.HandlerIterator.handleFault(HandlerIterator.java:254)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:224)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:161)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:116)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)
at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:335)
at test.wsclient.PatientRegistrationPort_Stub.getSecurityQuestion(PatientRegistrationPort_Stub.java:332)
... 1 more
Caused by: weblogic.wsee.handler.InvocationException: Failed to send message using connection:(SoapClientConnection@41626058 <transport=(HTTPSClientTransport@41626055 <url=https://IPADDRESS:9223/domain/ws/PatientRegistrationPort>)>)
at weblogic.wsee.ws.dispatch.client.ConnectionHandler.handleRequest(ConnectionHandler.java:91)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:100)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:101)
... 4 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Ljava.net.InetAddress;II)V(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:280)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:337)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:176)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:162)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:836)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
at weblogic.wsee.connection.transport.http.HTTPClientTransport.send(HTTPClientTransport.java:161)
at weblogic.wsee.connection.soap.SoapConnection.send(SoapConnection.java:54)
at weblogic.wsee.connection.soap.SoapClientConnection.send(SoapClientConnection.java:89)
at weblogic.wsee.ws.dispatch.client.ConnectionHandler.handleRequest(ConnectionHandler.java:89)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:100)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:101)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)Never mind, my silly mistake!
Thanks to http://jordan.fortwayne.com/oracle/oralinux.html
I realized that I had forgotten to do 'lsnrctl start'
R. Inamdar (guest) wrote:
: I downloaded Oracle 805 for Linux. I was able to successfully
: able to connect to the test database and issue queries with
: SVRMGRL. However, I get a 'Connection Refused' exception
: while connecting through the JDBC sample program.
: How do I enable diagnostics. I tried
: TRACE_LEVEL_LISTENER = SUPPORT
: but no trace file was created.
: What am I doing wrong. Thanks for the help...
: My evironment is:
: JDK1.1.7
: Linux Red Hat 5.2
: Thin JDBC driver
: Code fragment:
: DriverManager.registerDriver(new
jdbc.driver.OracleDriver());
: Connection conn =
: DriverManager.getConnection (
: "jdbc:oracle:thin:@localhost.localdomain:1521:test",
: "system",
: "manager"
: I tried with "localhost" in place of "localhost.localdomain"
: without success.
: Following is my listener.ora
: # Installation Generated Net8 Configuration
: # Version Date: Jun-17-97
: # Filename: Listener.ora
: LISTENER =
: (ADDRESS_LIST =
: (ADDRESS= (PROTOCOL= IPC)(KEY= test))
: (ADDRESS= (PROTOCOL= IPC)(KEY= PNPKEY))
: (ADDRESS= (PROTOCOL= TCP)(Host=
: localhost.localdomain)(Port= 1521))
: SID_LIST_LISTENER =
: (SID_LIST =
: (SID_DESC =
: (GLOBAL_DBNAME= localhost.localdomain.)
: (ORACLE_HOME= /usr/local/oracle/805)
: (SID_NAME = test)
: (SID_DESC =
: (SID_NAME = extproc)
: (ORACLE_HOME = /usr/local/oracle/805)
: (PROGRAM = extproc)
: STARTUP_WAIT_TIME_LISTENER = 0
: CONNECT_TIMEOUT_LISTENER = 10
: TRACE_LEVEL_LISTENER = OFF
: # TRACE_LEVEL_LISTENER = SUPPORT
: # TRACE_FILE_LISTENER = lsnr
: # TRACE_DIRECTORY_LISTENER=/usr/local/oracle/805/network/trace
null -
All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint. -
My Internet Connection Dropping Issues...
I too am having the occasional Internet connection dropping issues. Phone and TV continue to work.
Since I had Fios installed last November I am on my third ONT and 2nd router. When I called in my latest drop yesterday the call center person told me I had a hardware issue because my computer had a valid IP address assigned. I tried to teach her something about DHCP but she would not listen to me. I asked her to please reboot the ONT and she refused because "nothing was indicating a problem with it". Whatever...
Each time the Internet goes out the router acts fat and happy. I have full green on WAN Coax, and strangely enough, a flashing green Internet activity indicator. Logging into the router shows that I am MOCA connected and assigned a WAN IP address. But I can't get out past the router at all. On the event that led to me getting a replacement router the lady said she could talk to the ONT just fine, but not the router. We reset the router and ONT port numerous times and the connection finally came back up.
I am not sure of the protocol between the ONT and router, but I think the ONT is keeping enough signal going to make the router "think" its happy, but then the ONT is not passing packets at some point. After yesterdays call and the refusal to reset the ONT I just hung up on her and reset it myself. Of course everything started working just fine...like I thought it would.
So what is the issue here? Is MOCA a mess? Is an Ethernet connection to the ONT better? I am utterly disgusted with this miserable system and can't afford to continue having these outages.
I should also add the other wonderful features I have seen. When I tried to powercycle the *new* router yesterday it decided to dump its entire config including my port forwarding. Nice... And I have given up using wireless because if I set the router for WPA it locks up so hard that it takes a master reset to get going again.
Anyone have some advice on getting this system stable?I would try using a non-verizon router. I used the Netgear router and it fixed my problem. The Verizon router seem to be pieces of garbage and they over-hear.
-
Remote Desktop 'Connection Refused'
Modem/Router Model: GT704-WG-B
Firmware Version: 30.17.0 (Red background)
Operating System: Windows 7 Enterprise
Here is what I have set up to allow me access from outside my network via RDP.
Router config: Security > Applications "RDP" Rule Applied | Port 3389 Start/End/Port Map Start
UPnP is on
Modem/Router Firewall is OFF
Windows Firewall is ON with TCP 3389 allowed In/Out
Local PC has static IP address outside of DHCP range
Remote desktop (any version of RDP) allowed in Computer > Properties > Remote
I use Jaadu RDP iPhone application and have used it successfully for quite some time. When I first got Verizon service I set up RDP on the router and everything worked fine. I ran into an issue that caused a verizon tech to tell me to reset my modem/router to the factory defaults. Ever since, I have not been able to access my local PC via RDP. Every time I attempt to connect I get a connection refused message. I receive the same type of message when attempting to RDP in from another PC. I am able to RDP from within my LAN from both my iPhone and my other PC.
I have crossed my Ts and dotted my Is and am at a loss at this point. If anyone has experienced this issue and found a fix, I would appreciate some help.
Thanks#1 If the router turn off UPnP, since you will not be needing it.
#2 If that does not resolve it / or it happen again, please post...
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button. -
Connection refused While Calling a Web Service from WebDynpro Application.
Hi all,
I've created a Webdynpro application by importing a WSDL file which is created from a
Web Service from XI.
While I run this Application, and while it tries to connect to XI, I am getting following
error.
<b>Service call exception; nested exception is: java.net.ConnectException: Connection refused</b>
Can Someone please help me out on this issue?
Thanks in advance,
Tejas.Hi,
In my WebDynpro Application which is created by Importing a WSDL file from XI Web
Service is giving error : <b>Service call exception; nested exception is: java.net.ConnectException: Connection </b>
In NWDS-> Windows Menu-> Preferances -> Wrokbench -> Proxy Settings
Use Proxy Settings is <b>Checked</b>.
My Settings in Model's Logical Port is
<b>Use HTTP Port</b> is <b>Checked</b>.
In Securities-> <b>Authentication</b> is set to '<b>None</b>'
With this While I Execute the Application and when it tries to connect to XI..it throws
an error :
Service call exception; nested exception is: java.net.ConnectException: Connection
refused
Kindly help me on this issue.
Thanks in advance,
Tejas. -
Calling a WebServices From Java Stored Proc fails with Connection refused
I have followed the example in Note:220662.1 on Metalink step by step.
I am using two windows machines (2000 SP4). I have Oracle 9.2.0.5 EE on one of them and OC4J 9.0.4 standalone on the other(running on JVM 1.4.2_05-b04). The 2 servers "see" each other over the network.
I can execute the stub from the database machine:
C:\WebServices\HelloWorld>java HelloWorldImplWSStub
Hello World - The current time is Sat Aug 21 11:56:20 EDT 2004When running it from the database, I get:
SQL> select ws_hello_world from dual;
select ws_hello_world from dual
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception: [SOAPException:
faultCode=SOAP-ENV:IOException; msg=Connection refused;
targetException=java.net.ConnectException: Connection refused]
Elapsed: 00:00:21.02The trace file generated on the database server machine looks like:
[SOAPException: faultCode=SOAP-ENV:IOException; msg=Connection refused; targetException=java.net.ConnectException: Connection refused]
at oracle.soap.transport.http.OracleSOAPHTTPConnection.send(OracleSOAPHTTPConnection.java:765)
at org.apache.soap.rpc.Call.invoke(Call.java:261)
at HelloWorldImplWSStub.sayHelloWorld(HelloWorldImplWSStub.java:52)Here is the stub code generated using JDeveloper 9.0.5.1:
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.SOAPMappingRegistry;
import java.net.URL;
import org.apache.soap.rpc.Call;
import org.apache.soap.Constants;
import java.util.Vector;
import org.apache.soap.rpc.Response;
import org.apache.soap.rpc.Parameter;
import org.apache.soap.Fault;
import org.apache.soap.SOAPException;
import java.util.Properties;
public class HelloWorldImplWSStub {
public HelloWorldImplWSStub() {
m_httpConnection = new OracleSOAPHTTPConnection();
m_smr = new SOAPMappingRegistry();
public static String endpoint = "http://oc4jsrv:8888/MyWorkarea-OC4J-context-root/HelloWorldImplWS";
public String getEndpoint() {
return _endpoint;
public void setEndpoint(String endpoint) {
_endpoint = endpoint;
private static OracleSOAPHTTPConnection m_httpConnection = null;
private static SOAPMappingRegistry m_smr = null;
public static String sayHelloWorld() throws Exception {
String returnVal = null;
URL endpointURL = new URL(_endpoint);
Call call = new Call();
call.setSOAPTransport(m_httpConnection);
call.setTargetObjectURI("HelloWorldImplWS");
call.setMethodName("sayHelloWorld");
call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
Vector params = new Vector();
call.setParams(params);
call.setSOAPMappingRegistry(m_smr);
Response response = call.invoke(endpointURL, "");
if (!response.generatedFault()) {
Parameter result = response.getReturnValue();
returnVal = (String)result.getValue();
else {
Fault fault = response.getFault();
throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
return returnVal;
public void setMaintainSession(boolean maintainSession) {
m_httpConnection.setMaintainSession(maintainSession);
public boolean getMaintainSession() {
return m_httpConnection.getMaintainSession();
public void setTransportProperties(Properties props) {
m_httpConnection.setProperties(props);
public Properties getTransportProperties() {
return m_httpConnection.getProperties();
public static void main(String[] argv) throws Exception {
HelloWorldImplWSStub hstub = new HelloWorldImplWSStub();
System.out.println(hstub.sayHelloWorld());
}The PL/SQL function code:
CREATE OR REPLACE FUNCTION ws_hello_world RETURN VARCHAR2
AS LANGUAGE JAVA
NAME 'HelloWorldImplWSStub.sayHelloWorld() return java.lang.String';Any help would be greatly appreciated.Hello,I have the same problem. Did you find any solution to it?
Thanks. Diego (Argentina) -
Connection Refused while invoking Web Service from BPEL process
Hie
I am getting the following error when I try to invoke a web service (created in JDeveloper) from a BPEL process.
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="code">
<code>Server.userException</code>
</part>
<part name="summary">
<summary>when invoking endpointAddress '.......................', java.net.ConnectException: Connection refused: connect</summary>
</part>
<part name="detail">
<detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.net.ConnectException: Connection refused: connect faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection refused:
Did anyone come across a similar problem...??? Plz help:(Hi everybody,
I have the same problem. I developed a sample bpel process and tried to access it form another one, but still having the same exception :
<remoteFault>
<part name="code" >
<code>Server.userException</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'http://set.by.caller', java.net.UnknownHostException: set.by.caller</summary>
</part>
<part name="detail" >.......
Thanks for your help!
miroo
Maybe you are looking for
-
I gave my daughter my original iPad when I upgraded to iPad2. I deleted iTunes and Quick Time from my computer thinking it would get rid of the old info from the original iPad. I reinstalled iTunes and Quick Time and tried synching my new iPad2. It
-
About Apple Mac Mail Application
I Have a Problem with 1 of My E-Mail Accounts that I Use on Apple Mac Mail Application on My Apple iMac Computer I Have an AOL AIM E-Mail Account that i use to check My E-Mail Every day on Apple Mac Mail but for Some Reason it's not working no more t
-
Hi, I am having a lot of trouble with the xml parser in oracle, i have an app that uses JDOM and would like to continue using this, despite having followed the article by Jason Hunter i still receive exceptions when i try to run the code!!! i am usin
-
Wireless dot1x authenticated but no IPv4 DHCP assignment
Hi all, facing some issue on wireless not getting IP from the external DHCP server. 01. Problem statement After authentication success, client PC cannot get IP from DHCP server. This is the error log found at the WLC *RRM-MGR-2_4-GRP: May 21 15:23:02
-
Avahi conflicts with nss-mdns. [solved]
I'm confused. Went to update today, and got this message: :: avahi conflicts with nss-mdns. Remove nss-mdns? [Y/n] I thought 'Fair enough...' but I always check packages like this with -Si to know what's actually happening in my system. Soo, I run: