Connection refused message

hello
I am trying to run a sync interface RFC2WS.
I recieve the message and in the response I recieve this message:
  <?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: connect</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
in the comm. channel I recieve a familiar Q,
24.03.2008 08:18:00 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
24.03.2008 08:18:00 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
24.03.2008 08:18:00 Error Exception caught by adapter framework: Connection refused: connect
24.03.2008 08:18:00 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. Setting message to status failed.
24.03.2008 08:18:00 Error The message status set to FAIL.
24.03.2008 08:18:00 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.
I am trying to get to the root of the problem, and from what I know, the problem is not in the XI.
what else can I check in order to be sure that the problem is not in the XI? how can I know exactly where the problem is?
Thanks
Kfir

HI,
The XI monitoring tools are best for troubleshooting these kind of problems.
In RWB, in Adapter Engine..you could monitor the communication Channels you have developed for RFC and SOAP connection.
Check for the log in it. From this you will get where is the problem.
Even the URL that you are using for SOAP receiver , try to copy -paste it in Internet browser and see if you can successfully ping to the Web Service.
Even in SXMB_MONI, you could analyse the whole message flow step-by step
Thanks
Swarup

Similar Messages

  • When I try to log in from desktop I get "Connection Refused" message. How do I fix this?

    I tried to activate Mozilla Firefox today using the normal & routine method, clicking on the Firefox Icon.
    Each time I tried I got the same message "Connection Refused".
    I went to the Firefox site and read the message regarding disabling Java, so I opened ADD ONS and Plug Ins and disabled Java.
    Still no change, so I shut down and restarted my computer.
    I keep getting the same Connection Refused message.
    What needs to be done to restore Firefox?

    Another user also reported a problem with the AT&T Yahoo home page in the past few minutes. When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
    (1) Bypass Firefox's Cache
    Use Ctrl+Shift+r to reload the page fresh from the server.
    Alternately, you also can clear Firefox's cache completely using:
    orange Firefox button (or Tools menu) > Options > Advanced
    On the Network mini-tab > Cached Web Content : "Clear Now"
    If you have a large hard drive, this might take a few minutes.
    (2) Remove the site's cookies (save any pending work first). While viewing a page on the site:
    * right-click and choose View Page Info > Security > "View Cookies"
    * Alt+t (open the classic Tools menu) > Page Info > Security > "View Cookies"
    Then try reloading the page. Does that help?

  • How to get rid of Data Connection Refused message

    I have a blackberry 8703e, i recently disabled my blackberry data pack and ever since i did that I get the message data connection refused on my home screen. I know there is a solution for this problem for other devices like 8830 by simply going to Mobile Network and setting Data Services to OFF, but my device does not have data services as a option, I'm on the lastest OS 4.2.
    Another thing I noticed that now my battery gets drained faster, I have a new battery and lasts less than a day, compared to almost 2 days when I had the data plan on.. strange...

    About the battery - probably you're using some applications which consume energy.
    And check this link

  • 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.

  • Rsh connection refused error.

    Hi.
    rsh returns a connection refused message when trying to connect to a host running solaris 8. I am able to rsh from other client boxes to this host but this one refuses to work. In the /.rhosts I have only a + .
    Any ideas?
    Thanks.
    SN

    "connection refused" means that the remote tcp/ip host you are trying to connect to
    does not have a process listening on the rlogin server port.
    As you say that other machines can rlogin okay to this machine then I would look to make sure that
    the name you are using to rlogin to resolves to the same server machine between a client that works and this client that doesn't
    eg
    getent hosts rlogin_server
    run on both clients
    tim

  • HTTP3068: Error receiving request ip_address (Connection refused)

    Hi,
    I've noticed many failures in my error log. I use SJSWS 6.1u7. Some example are below:
    [04/Jul/2007:11:29:11] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:41] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:35:45] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:37:21] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)The IP address which is noticed in error line is a router of some NAT in my corporation. I want to tune my webserver and receive all request from this address.
    Any idea?
    Irek

    ireneusz.tarnowski wrote:
    Hi,
    I've noticed many failures in my error log. I use SJSWS 6.1u7. Some example are below:
    [04/Jul/2007:11:29:11] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:32:41] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:35:45] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
    [04/Jul/2007:11:37:21] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)The IP address which is noticed in error line is a router of some NAT in my corporation. I want to tune my webserver and receive all request from this address.
    Any idea?
    IrekIrek,
    Did you ever figure out how to fix this issue with the Sun Webserver 6.1 that you had back in July last year with the "Error receiving request from <ip address> (Connection refused)" messages? We are getting the same errors on our Sun ONE / Sun Java System webserver version 6.1 SP6. Please let me know.
    [http://forum.java.sun.com/thread.jspa?messageID=9751068#9751068|http://forum.java.sun.com/thread.jspa?messageID=9751068#9751068]

  • Connect to message server host failed;WSAECONNREFUSED: Connection refused

    Hi All,
    I am getting the following error when I tried to test the system connectivity from the portal to NSP instance.
    Connection failed. Make sure that Single Sign-On is configured correctly
    I found the following entry in the logs
    Error> occured  >Wed Feb 03 22:43:49,875<   
    RfcException:
        message: Connect to message server host failed
    Connect_PM  TYPE=B MSHOST=abchome.abcsap.local GROUP=SPACE R3NAME=NSP MSSERV=sapmsNSP PCS=1
    ERROR       partner '192.xxx.xxx.123:sapmsNSP' not reached
    TIME        Wed Feb 03 22:43:49 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
        Return code: RFC_FAILURE(1)
        error group: 102
        key: RFC_ERROR_COMMUNICATION
    Both NSP and J2E instances are on the same server. OS - win2k3.
    I checked the services file and have the sapmsNSP entry.
    I am able to launch an SAP transaction from System Administration -> Support
    RZ70 from NSP also fails JCo error. SLD_UC RFC itself works fine and the JCo RFC provider SLD_UC program is running
    WEB AS & ITS connections work fine.
    User authentication is from backend, NSP.
    I think I have gone thru all the logs but could not resolve the issue.
    I appreciate any help on this,
    Victor

    I tried to go thru the thread. I did not find any clue as why only server connectivity is failing. ABAP trial version is running fine and the NW trial version is working fine too. These run without crashing. I did a lot of customizing on the portal but dont see any issues except the System Connectivity. Like I mentioned I did UME configuration to point to NSP ABAP instance and I can log into the portal with user credentials that I use to login to ABAP.  I can launch webgui etc without any issues.

  • I am set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    I set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    Thanks. Where could I possibly look for a firewall rule. I knowingly did not creat any. My system has internet coming to a Modem which then is connected to a wireless router. I have computers connecting to the router through cable as well as wireless. One of these computers has been our  mailserver using Mercury and Pegasus and that computer has a static IP address. The Mac Mini also has been assigned a different srtatic IP address. I have only set up user account, none of them an email account as I initially expect them to receive only internal mails. Is it necessary that I must set up an email id for each user while setting up the user account. My server id is server.local. So would the email id for local users be [email protected]?

  • When trying to connect to app store i get message connection refused anyone know what's up with this?

    when trying to connect to the app store i get a message "connection refused" anyone know what's up with this?

    I'm new to this what other posts?

  • Before I had Mavericks I was able to print over the network to a Windows PC. Now I receive the message, "connection refused." Any ideas?

    Before I upgraded to Mavericks, I was able to print over the network to a printer attached to a Windows PC. Now, I receive the message, "connection refused." any ideas as to why this may be and what I can do about it would be appreciated.

    I had reconfigured all of the settings the same as in the previous OS X. The only thing I can think of that may be causing this is that the printer is an older Canon Pixma iP4300 and the Canon site doesn't have a driver for the new OS X. The Canon site said that the new OS X may supply the driver. Is there any one with the same experience as mine?

  • Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

    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(5

    Ok 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.

  • Connection refused.

    Hi,
    i am using NetBeans IDE 5.,5 and trying out the NewsApp tutorial for Entity beans.
    When i run the project I get the following error,
    How shall i fix this,
    Thanks in advance.
    deployment started : 0%
    Deploying application in domain failed;
    Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: java.net.ConnectException : Error opening socket to server localhost on port 1527 with message : Connection refused: no further informationError Code: 0
    E:\Sitaraman\OSS1\Projects\NewsApp\nbproject\build-impl.xml:183: Deployment error:
    The module has not been deployed.
    See the server log for details.
    BUILD FAILED (total time: 13 seconds)

    Hi,
    I had not started the database server. Going to tools->start db server fixed the problem.
    Sitaraman

  • Connection Refused Error while running AS ABAP Initial Load

    All,
    I've never connected SAP NW IdM to an actual SAP system before, and I feel like I'm missing some obvious step of configuration, but I can't figure out what.
    We are in the process of trying provision user accounts to our SAP ABAP systems. My first step was to try to read all of the existing accounts from the ABAP system:
    Our Basis team created me a Communication user with the proper authorizations (I ensured that the authorizations included in SAP_BC_SEC_IDM_COMMUNICATION)
    I created a repository using the SAP NewWeaver AS ABAP (Specific Application Server) Repository Template (No CUA, No SNC) using that user's credentials
    I then used the Job Wizard and used the job template AS ABAP - Initial Load, specifying my repository above.
    When I run the job I get the following:
    Initializing SAP connection with parameters:
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server failed Connect_PM MSHOST=<IPADDRESS>, R3NAME=<SID>, GROUP=PUBLIC LOCATION CPIC (TCP/IP) on local host ERROR partner not reached (host <IPADDRESS>, service sapms<SID>) TIME Wed Jun 01 13:54:36 201 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8840 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
    Error Init failed
    I'm running SAP NW IdM 7.1 SP5 on Windows Server 2003 with MSSQL 2005. The ABAP server is on a UNIX box with an Oracle 10.2 dB.
    Is there additional configuration that needs to take place on the ABAP side to accept the connection?
    I've tried to find documentation on this, but have been unsuccessful. If someone could point me to the correct documents, or at least point me in the right direction for troubleshooting, it would be greatly appreciated.

    Ankur,
    Looks like the endpoint URL of the webservice is not updated and still pointing to the localhost. Try changing it to http://<ip_addres_of_your_server>:7101..... and see if it works fine then.
    -Arun

  • My Time Capsule hard drive shows up in Finder, but I can't access the disk.  I get a connection failed message.

    I can not access my Time Capsule from the Finder.  This was working, but on 12/25/2011, the disk can no longer be accessed.  It shows up in the Finder, but when I try to connect, I get a "Connection Failed" message.  If I cycle the power, it works for a little while and then fails again.

    hello
    No i'm connect via ethernet (cable) with TC. The problem is when I try to connect to my TC when I'm away from home like for ex. using a free wi fi spot!! Well in this case the icon appear on my Finder but refuse to connet!! ( connection faild ).

  • Connection refused error running JSP on Jdev 10.1.3.0.3.3412 with MySL 5.0

    Hello,
    I'm using Jdeveloper 10.1.3.0.3.3412 on a Mac with a MySQL database. In Jdeveloper i can make a connection to the database and create adf business components
    I've made a JSP page with ADF on a single table. No errors when compiling. When I try to run the JSP Page using Embedded OC4J (on Mac OSX Tiger) I get the error:
    5/12/09 00:45:50 java.net.ConnectException: Connection refused
    05/12/09 00:45:50      at java.net.PlainSocketImpl.socketConnect(Native Method)
    05/12/09 00:45:50      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    05/12/09 00:45:50      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    05/12/09 00:45:50      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    05/12/09 00:45:50      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
    05/12/09 00:45:50      at java.net.Socket.connect(Socket.java:507)
    05/12/09 00:45:50      at java.net.Socket.connect(Socket.java:457)
    05/12/09 00:45:50      at java.net.Socket.<init>(Socket.java:365)
    05/12/09 00:45:50      at java.net.Socket.<init>(Socket.java:207)
    05/12/09 00:45:50      at oracle.jdevimpl.runner.oc4j.Oc4jNotifier.sendMessage(Oc4jNotifier.java:98)
    05/12/09 00:45:50      at oracle.jdevimpl.runner.oc4j.Oc4jNotifier.postInitApplicationServer(Oc4jNotifier.java:55)
    05/12/09 00:45:50      at com.evermind.server.ApplicationServer.serverExtensionPostInit(ApplicationServer.java:1041)
    05/12/09 00:45:50      at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:927)
    05/12/09 00:45:50      at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:98)
    05/12/09 00:45:50      at java.lang.Thread.run(Thread.java:613)
    What am I doing wrong? The embedded OC4J library is added to the project. I've tried to use the javac compiler. It looks like the OC4J instance cannot make a connection to the db.
    Thanks,
    Martin

    Hello
    I've added the connection to the web.xml, but still get the same error.
    When I go to embedded OC4J preferences and change the JNDI-names of the datasources (global and current-workspace) to the same name (this was default), i get this error message:
    9-dec-2005 9:30:09 com.evermind.server.ApplicationStateRunning initNativeDataSource
    SEVERE: Error creating native data source. The location 'jdbc/MySQLConnectionCoreDS' is already in use.
    05/12/09 09:30:09 Application: current-workspace-app is in state FAILED
    05/12/09 09:30:09 Error instantiating application 'current-workspace-app' at file:/Users/martinsuijs/jdevhome/mywork/myWorldApp/myWorldApp-oc4j-app.xml: Error creating native data source. The location 'jdbc/MySQLConnectionCoreDS' is already in use.
    05/12/09 09:30:14 java.net.ConnectException: Connection refused
    grtz
    Martin

Maybe you are looking for

  • Artwork doesn't display...

    I got a problem after the last update. I have an iMac and a MB with a synchronized iTunes database and files, in iMac when I'm browsing the albums and I select one album, the artwork doesn't display in the bottom left corner, the album display only i

  • Error in ni visa control out for usb in labview 2009

    Hi, I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface. the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL

  • Cannot Access Firefox Sync in Linux

    I have installed the Sync add-on for my Ubuntu Linux desktop version 10.10. I have Firefox 4.0 for Linux installed. The add-on installs fine and I am able to complete the setup process. When I go to the Sync tab in Preferences I get a error stating "

  • "Edit Effects" button disabled

    I am a new user of Premiere Elements 10. I need to animate the effect in a clip but the Edit Effect button is grayed out. The Apply Effect button is also grayed out (when I select an effect) but I can apply it by dragging it to the monitor window.I d

  • Print preview in ME21N/ME22N/ME23N

    Hi! In transactions ME21N/ME22N/ME23N we can see PO print preview after we click Print preview button. Is it possible to deactivate upper toolbar in this preview?? Or deactivate:  Go to -> 'View list'   in this toolbar?