FAIL: NIECONN_REFUSED (EDC8128I Connection refused.),

Hi All,
We are receiving the message "FAIL: NIECONN_REFUSED (EDC8128I Connection refused.)," on our CI server which is on OS/390 Operating system. The message comes every time when we restart our SAP system.
Our application server's are on AIX 5.3 Operating system, but the error is coming on CI (Central Instance) which is on MAinframe.
Regards
BAsis Team

Hi,
I have similar problem, it arised after the change of the kernel.
Sapstartsrv is not started, the abend S0C4 is in the z/OS system log and in the work directory is CEEDUMP.
Regards
Vladislav

Similar Messages

  • SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

    I am getting the following message when I start the agent.  I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects.  Just eventually times out after 30 mins.
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.

    cat dev_SMDAgent
    trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
    node name   : smdagent
    pid         : 17393
    system name : SMD
    system nr.  : 98
    started at  : Wed Oct  7 08:56:32 2009
    arguments         :
              arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
              arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
              arg[02] : -DSAPINFO=SMD_98_server
              arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
    -> ms host    :
    -> ms port    : 36
    -> OS libs    : /usr/sap/SMD/exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SMD/J98/profile/smd.properties
    Instance properties
    -> ms host    :
    -> ms port    : 36
    -> os libs    : /usr/sap/SMD/exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
    [Thr 182894174624] Wed Oct  7 08:56:32 2009
    [Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
    [Thr 182894174624] SigISetDefaultAction : default handling for signal 17
    [Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182894174624] CPIC (version=701.2009.01.26)
    [Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
            Java Home: /opt/IBMJava2-amd64-142
    [Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
    JStartupIReadSection: read node properties [smdagent]
    -> node name          : SMDAgent
    -> node type          : server
    -> node id            : 1
    -> node execute       : yes
    -> java path          : /opt/IBMJava2-amd64-142
    -> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 256M
    -> init heap size     : 256M
    -> root path          : ../SMDAgent
    -> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> OS libs path       : /usr/sap/SMD/exe
    -> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
    -> parameters         : run jcontrol
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 58981
    -> shutdown timeout   : 20000
    [Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -DP4ClassLoad=P4Connection
    -> arg[  4]: -Xj9
    -> arg[  5]: -Xmn50m
    -> arg[  6]: -Xgcpolicy:gencon
    -> arg[  7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
    -> arg[  8]: -Dapplication.home=/usr/sap/SMD/exe
    -> arg[  9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    -> arg[ 11]: -Dmemory.manager=256M
    -> arg[ 12]: -Xmx256M
    -> arg[ 13]: -Xms256M
    -> arg[ 14]: -DLoadBalanceRestricted=no
    -> arg[ 15]: -Djstartup.mode=JCONTROL
    -> arg[ 16]: -Djstartup.ownProcessId=17393
    -> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
    -> arg[ 18]: -Djstartup.whoami=server
    -> arg[ 19]: -Djstartup.debuggable=yes
    -> arg[ 20]: -DSAPINFO=SMD_98_server
    -> arg[ 21]: -DSAPSTARTUP=1
    -> arg[ 22]: -DSAPSYSTEM=98
    -> arg[ 23]: -DSAPSYSTEMNAME=SMD
    -> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
    -> arg[ 25]: -DSAPDBHOST=
    -> arg[ 26]: -Dj2ee.dbhost=
    [Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
    -> arg[  0]: run
    -> arg[  1]: jcontrol
    [Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1086335328] Wed Oct  7 08:56:35 2009
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1086335328] Wed Oct  7 08:56:38 2009
    [Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
    [Thr 1101334880] Wed Oct  7 08:56:43 2009
    [Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
    [Thr 1101334880] Wed Oct  7 08:56:48 2009
    [Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

  • Decision Service calls failing with connection refused

    Hi All,
    Breifing of the bpel process - Async bpel process XX_BPEL_ASYNC_002 calls decision services and a sync bpel process XX_BPEL_SYNC_001.
    We have moved to cluster 10.1.3.5.0 from 10.1.3.3.0 and the deployement of the bpel process and the decision service done on two nodes i.e., node51 and node55.
    But the bpel process is able to call the decision service only when the node 51 is UP and running, but if node 51 is down and node 55 is up and running it is failing with connection refused error. It is also working when 55 is DOWN and 051 is UP.
    the exact error is:
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused.
    We are using file based repository.
    It is failing when it tries to call particular url:
    http://loadbalancerurl:7777/orabpel/domain001/XX_BPEL_ASYNC_002/1.0/decisionservices.decs
    Can anyone please help me or advice me for finding some solution.
    Thanks
    Sreejit

    Hi Fatsah,
    It has been a while since we resolved this problem. But these were  the basic steps that we had taken.
    The receiver was configured a File adatpter with FTP:
    Port: 10021
    Connection security : FTPS (FTP using SSL/TLS) for Control and Data Connection
    Command Order: AUTH TLS,USER,PASS,PBSZ,PROT
    Problem: The message was blocked in our firewall.
    FTPS in this case used 10021 as the control port and the firewall allowed to pass the control request.
    Once the connection was accepted at the control level, it generated a random port number  to pass data on the channel.
    This random port number was blocked in the firewall.
    We monitored the data port numbers generated at firewall. Then we configured the firewall to open any port number  between the specific IP addresses of the sender and the receiver. That resolved the problem.
    Hope this helps!
    Please give points if this is helpful.
    Thank you.
    Dharmasiri Amith

  • Sccheck fails with connection refused

    I have a 2 node cluster that was just upgraded from SC3.0 to SC3.1u4 (8/05). sccheck passes on node aemhrsDV1 and fails with the following message on aemhrsDV2:
    root@aemhrsDV2 # sccheck -b -v2 -h aemhrsDV2
    sccheck: Requesting explorer data and node report from aemhrsDV2.
    sccheck: aemhrsDV2 error: Connection refused
    sccheck: Unable to run checks on: aemhrsDV2All SC3.1 patches have been applied. All availble agents were updated using 'scinstall -u update -s all' and re-registered. Test ip addresses were supplied during 'scinstall -u update -S interact'.
    Both nodes come up fine individually in cluster (through step 10) but together the log /var/cluster/ucmm/ucmm_reconf.log shows:
    Thu Aug  9 21:47:04 EST 2007 SUNWscucm.ucmm_reconf udlm started in cmmstep2
    Thu Aug  9 21:48:44 EST 2007 SUNWscucm.ucmm_reconf udlm completed successfully in cmmstep2
    Thu Aug  9 21:48:44 EST 2007 SUNWscucm.ucmm_reconf cvm started in cmmstep2
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf cvm completed successfully in cmmstep2
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf ucmm reconfiguration step 2 completed
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf Step: cmmreturn CURRNODES=0 1Running scstat -i hangs forever at IPMP Groups with both nodes in cluster but separately displays the adapters and status.
    Node 1
    root@aemhrsDV1 # ifconfig -a
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
            inet 127.0.0.1 netmask ff000000
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.100.30 netmask ffffff00 broadcast 192.168.100.255
            ether 0:3:ba:39:f5:62
    ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.101.30 netmask ffffff00 broadcast 192.168.101.255
    ce1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
            inet 192.168.251.30 netmask ffffff00 broadcast 192.168.251.255
            ether 0:3:ba:39:f5:ef
    ge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
            inet 10.10.3.30 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:b:e:8
    ge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
            inet 10.10.3.31 netmask ffffff00 broadcast 10.10.3.255
    qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
            inet 10.10.3.33 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:17:97:d5
    qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 5
            inet 10.10.3.32 netmask ffffff00 broadcast 10.10.3.255
    qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
            inet 192.168.2.112 netmask ffffff00 broadcast 192.168.2.255
            ether 0:3:ba:17:97:d7
    qfe7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 7
            inet 172.16.1.1 netmask ffffff80 broadcast 172.16.1.127
            ether 0:3:ba:17:98:68
    qfe3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 8
            inet 172.16.0.129 netmask ffffff80 broadcast 172.16.0.255
            ether 0:3:ba:17:97:d8
    clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1486 index 9
            inet 172.16.193.1 netmask ffffff00 broadcast 172.16.193.255
            ether 0:0:0:0:0:1Node 2
    root@aemhrsDV2 # ifconfig -a
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
            inet 127.0.0.1 netmask ff000000
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.100.40 netmask ffffff00 broadcast 192.168.100.255
            ether 0:3:ba:39:f5:50
    ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.101.40 netmask ffffff00 broadcast 192.168.101.255
    ce1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
            inet 192.168.251.40 netmask ffffff00 broadcast 192.168.251.255
            ether 0:3:ba:39:f5:20
    ge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
            inet 10.10.3.40 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:b:41:22
    ge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
            inet 10.10.3.41 netmask ffffff00 broadcast 10.10.3.255
    qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
            inet 10.10.3.43 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:17:96:2d
    qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 5
            inet 10.10.3.42 netmask ffffff00 broadcast 10.10.3.255
    qfe0:2: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 5
            inet 10.10.3.35 netmask ffffff00 broadcast 10.10.3.255
    qfe7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 6
            inet 172.16.1.2 netmask ffffff80 broadcast 172.16.1.127
            ether 0:3:ba:17:97:18
    qfe3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 7
            inet 172.16.0.130 netmask ffffff80 broadcast 172.16.0.255
            ether 0:3:ba:17:96:30
    clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1486 index 8
            inet 172.16.193.2 netmask ffffff00 broadcast 172.16.193.255
            ether 0:0:0:0:0:2
    root@aemhrsDV1 # scstat
    -- Cluster Nodes --
                        Node name           Status
      Cluster node:     aemhrsDV1           Online
      Cluster node:     aemhrsDV2           Online
    -- Cluster Transport Paths --
                        Endpoint               Endpoint               Status
      Transport path:   aemhrsDV1:qfe7         aemhrsDV2:qfe7         Path online
      Transport path:   aemhrsDV1:qfe3         aemhrsDV2:qfe3         Path online
    -- Quorum Summary --
      Quorum votes possible:      3
      Quorum votes needed:        2
      Quorum votes present:       3
    -- Quorum Votes by Node --
                        Node Name           Present Possible Status
      Node votes:       aemhrsDV1           1        1       Online
      Node votes:       aemhrsDV2           1        1       Online
    -- Quorum Votes by Device --
                        Device Name         Present Possible Status
      Device votes:     /dev/did/rdsk/d3s2  1        1       Online
    -- Device Group Servers --
                             Device Group        Primary             Secondary
      Device group servers:  rmt/1               -                   -
      Device group servers:  rmt/2               -                   -
    -- Device Group Status --
                                  Device Group        Status
      Device group status:        rmt/1               Offline
      Device group status:        rmt/2               Offline
    -- Multi-owner Device Groups --
                                  Device Group        Online Status
    -- Resource Groups and Resources --
                Group Name          Resources
    Resources: nfs-test            aemhrsDVlh
    Resources: hastp-aemhrsDV1-rg  -
    Resources: hastp-aemhrsDV2-rg  -
    Resources: rac-framework-rg    rac_framework rac_udlm rac_cvm
    -- Resource Groups --
                Group Name          Node Name           State
         Group: nfs-test            aemhrsDV1           Offline
         Group: nfs-test            aemhrsDV2           Online
         Group: hastp-aemhrsDV1-rg  aemhrsDV1           Online
         Group: hastp-aemhrsDV2-rg  aemhrsDV2           Online
         Group: rac-framework-rg    aemhrsDV1           Pending online
         Group: rac-framework-rg    aemhrsDV2           Online
    -- Resources --
                Resource Name       Node Name           State     Status Message
      Resource: aemhrsDVlh          aemhrsDV1           Offline   Offline
      Resource: aemhrsDVlh          aemhrsDV2           Online    Online - LogicalHostname online.
      Resource: rac_framework       aemhrsDV1           Starting  Degraded - reconfiguration in progress
      Resource: rac_framework       aemhrsDV2           Online    Online
      Resource: rac_udlm            aemhrsDV1           Offline   Offline
      Resource: rac_udlm            aemhrsDV2           Online    Online
      Resource: rac_cvm             aemhrsDV1           Offline   Offline
      Resource: rac_cvm             aemhrsDV2           Online    Online
    -- IPMP Groups --
                  Node Name           Group   Status         Adapter   Status
                  ---------           -----   ------         -------   ------I believe the reconfig is coming from aemhrsDV2 since sccheck will not run.
    Suggestions?

    Also the output from the sccheck commad using 'ksh -x' shows where the error is occurring and exiting with a status of 107.
    The line executed is 765 of the script.
    # echo "CLASSPATH: ${CLASSPATH}"
    ${JAVA} -classpath ${CLASSPATH} ${JDEFINES_LIST} ${JAVA_CLIENT} &
    JVM_PID=$!
    + JVM_PID=13881
    # now wait for java to exit
    wait $JVM_PID
    + wait 13881
    + /usr/java/bin/java -classpath /usr/cluster/lib/sccheck:/usr/cluster/lib/sccheck/sccheck.jar:/usr/cluster/lib/sccheck/k
    ae/kae.jar:/usr/cluster/lib/sccheck/kae/kae-libs.jar:/usr/cluster/lib/sccheck/kae/eras-common.jar:/usr/cluster/lib/scche
    ck/kae/common-libs.jar:/usr/cluster/lib/sccheck/kae/eras-parsers.jar:/usr/cluster/lib/sccheck/kae/explorer-input-source.
    jar:/usr/cluster/lib/sccheck/kae/resources:/var/cluster/sccheck/tmp/client.0 -Dcom.sun.eras.common.logging4.config.file=
    /usr/cluster/lib/sccheck/sccheck.logging4.properties -Dke.client.log=/var/cluster/logs/sccheck/ke-client.log.0 -Dke.clie
    nt.xsldir=/var/cluster/sccheck/tmp/client.0 -Dsccheck.clustername=aemhrsDV -Dsccheck.clustermode=true -Dsccheck.localnam
    e=aemhrsDV2 -Dsccheck.privatelocalname=clusternode2-priv -Dsccheck.publicnodenames=aemhrsDV1,aemhrsDV2 -Dsccheck.private
    nodenames=clusternode1-priv,clusternode2-priv -Dsccheck.clientnumber=0 -Dsccheck.explorersgzDir=/var/cluster/sccheck/exp
    lorers-gz -Dsccheck.explorersUnpackDir=/var/cluster/sccheck/explorers.0 -Dsccheck.gunzip=/usr/bin/gunzip -Dsccheck.tar=/
    usr/bin/tar -Dsccheck.brief=true -Dsccheck.vverbose=true -Dsccheck.hostlist=aemhrsDV2 -Dsccheck.outputDir=/var/cluster/s
    ccheck/reports.2007-08-10.09:19:37 com.sun.cluster.sccheck.SccheckClient
    sccheck: Requesting explorer data and node report from aemhrsDV2.
    sccheck: aemhrsDV2 error: Connection refused
    sccheck: Unable to run checks on: aemhrsDV2
    typeset -i exitstatus=$?
    + typeset -i exitstatus=107
    # constuct closing message if reports were created
    if ((${exitstatus} > 0)) && ((${exitstatus} < 100)); then
        typeset severity=""
        printf ""
        case "${exitstatus}" in
            1)      severity=$(gettext '1 (LOW)');;
            2)      severity=$(gettext '2 (MODERATE)');;
            3)      severity=$(gettext '3 (HIGH)');;
            4)      severity=$(gettext '4 (CRITICAL)');;
        esac
        printf "$(gettext '%s: One or more checks failed.')\n" ${PROG}
        printf "$(gettext '%s: The greatest severity of all check failures was %s.')\n" ${PROG} "${severity}"
        printf "$(gettext '%s: Reports are in %s.')\n" ${PROG} ${OUTPUTDIR}
    fi
    + (( 107 > 0 ))
    + (( 107 < 100 ))
    cleanup
    + cleanup
    exit ${exitstatus}
    + exit 107

  • Tcp/ip  bconnection to host has failed,connection refused

    Exception in thread "main" com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(UnknownSource)
    Can anyone pls help me out .
    I ve tried netstat -an port 1433 is not listed
    firewall is diasbled .

    You need to enable TCP services on SQL Server.

  • Pulseaudio problem , snd_pcm_open failed: Connection refused.

    Hello everyone, i have this problem that appeared last week.
    I cant play music in any player cause i get this error : snd_pcm_open failed: Connection refused.
    i tried things like adding the user to audio group, creating a "pulse" user cause pulseaudio gave me an error like "pulse user" not existent .
    but if i test the sound card in the kde4 audio setup it works
    anyone have any ideea on how to fix this ?

    just restart alsa.
    sudo /etc/rc.d/alsa restart
    it solved my problem.

  • Connection refused: proxy: HTTP: attempt to connect to failed [error] ap_proxy_connect_backend disabling worker

    Hi all,
    I'm investigating cause of a wedged wiki this morning. The MacMini (10.7.5) was working well for the last year but we're not sure when it gave up the ghost.
    I've already applied the fixes detailed at Mac OS X v10.5, Mac OS X Server v10.5: Web, Mail, Wiki, Personal Web Sharing, Parental Controls services may not start after restoring a Time Machine backup but it has't helped.
    The error we see when we visit the top level of the server is:
    Service Temporarily Unavailable
    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
    Apache/2.2.22 (Unix) PHP/5.3.15 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/0.9.8r DAV/2 Server at sacmini.local Port 80
    The message in the httpd error logs is:
    Connection refused: proxy: HTTP: attempt to connect to failed [error] ap_proxy_connect_backend disabling worker
    Let me know if you have any ideas.  Thank you.
    --Athonia

    Thanks for the reply.
    So, there were some Ruby related log file entries. Do these have any meaning to you?  I'm checking to see what collabcored2 does exactly.
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /usr/share/collabd/coreclient/config/environment.rb:11
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /usr/share/collabd/coreclient/config.ru:13
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/builder.rb:46:in `instance_eval'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/builder.rb:46:in `initialize'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /usr/share/collabd/coreclient/config.ru:1:in `new'
    May  7 14:22:33 sacmini com.apple.collabcored2[22106]:
    from /usr/share/collabd/coreclient/config.ru:1
    May  7 14:22:33 sacmini com.apple.launchd[1] (com.apple.collabcored2[22106]): Exited with code: 1
    May  7 14:22:33 sacmini com.apple.launchd[1] (com.apple.collabcored2): Throttling respawn: Will start in 9 seconds

  • Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)

    Hello All,
      There are some changes in out portal sever, but not related to SAP EP.
    So it is needed to restart the server. After restarting the server,
    we are not avail to start the server. There is nothing in the SAPMMC.
    "There is no item to display" is showing in the SAPMMC.
    So we tried couple of time to get the SAPMMC icons by restarting the server.
    But it is not getting any display in SAPMMC.
    I am sending some part of the latest log file of that server below:
    Our server name is INMAA02AS03.
    1.5#00145E3D3B630046000000000000175000041A3F6EB5EB39#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed#
    #1.5#00145E3D3B630046000000010000175000041A3F6EB5EC0B#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed
         at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
         at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
         at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
         at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
    #1.5#00145E3D3B630046000000020000175000041A3F6EB5F178#1154759649523#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Cannot update HTTP load balancing information in the Message service
    com.sap.engine.frame.cluster.ClusterException: Socket closed
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1377)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
         at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
         at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
         at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
    Caused by: java.net.SocketException: Socket closed
         at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
         at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
         ... 10 more
    #1.5#00145E3D3B6300400000000B0000175000041A3F6EC43762#1154759650461#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000000D0000175000041A3F6EF146BF#1154759653414#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000000F0000175000041A3F6F1E56B0#1154759656367#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000110000175000041A3F6F4B6526#1154759659320#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000130000175000041A3F6F787519#1154759662273#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000150000175000041A3F6FA584C7#1154759665226#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000170000175000041A3F6FD29438#1154759668179#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000190000175000041A3F70014F86#1154759671242#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000001B0000175000041A3F70300A99#1154759674304#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000001D0000175000041A3F705D1A24#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000001F0000175000041A3F705D1B81#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 11 times#
    #1.5#00145E3D3B630040000000210000175000041A3F708A296B#1154759680210#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000230000175000041A3F70B738CB#1154759683163#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000250000175000041A3F70E4487A#1154759686116#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000270000175000041A3F7111581F#1154759689069#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000290000175000041A3F713E67B3#1154759692022#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000002B0000175000041A3F716B77A1#1154759694976#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000002D0000175000041A3F719886C2#1154759697929#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000002F0000175000041A3F71C596D5#1154759700882#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000310000175000041A3F71F45176#1154759703944#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000330000175000041A3F72230C96#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000350000175000041A3F72230DF3#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 21 times#
    #1.5#00145E3D3B630040000000370000175000041A3F72501BF9#1154759709960#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000390000175000041A3F727D2BC1#1154759712913#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000003B0000175000041A3F72AA3BCA#1154759715866#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000003D0000175000041A3F72D74B1A#1154759718819#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000003F0000175000041A3F73045A4C#1154759721772#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000410000175000041A3F73316A0D#1154759724725#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000430000175000041A3F735E799A#1154759727678#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000450000175000041A3F738D34D0#1154759730740#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000470000175000041A3F73BBEF81#1154759733803#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000490000175000041A3F73E8FF05#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000004B0000175000041A3F73E90064#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 31 times#
    #1.5#00145E3D3B6300400000004D0000175000041A3F74160E68#1154759739709#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000004F0000175000041A3F74431E16#1154759742662#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000510000175000041A3F74702DEA#1154759745615#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000530000175000041A3F749D421D#1154759748568#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000550000175000041A3F74CA4CD6#1154759751521#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000570000175000041A3F74F75CC8#1154759754474#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000590000175000041A3F75246C5C#1154759757427#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000005B0000175000041A3F75517C0B#1154759760381#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000005D0000175000041A3F7580368E#1154759763443#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B6300400000005F0000175000041A3F75AEF19A#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
    #1.5#00145E3D3B630040000000610000175000041A3F75AEF2F2#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 41 times#
    Any idea what to do?
    Please help me out.
    **Points will be rewarded for a suitable answer.
    Regards,
    Uttam.

    Hi Uttam,
    Were you able to solve the problem? I am also getting a similar error message. If you had solved your problem, please share, how?
    Thanks & Regards,
    Santhosh.C

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

  • Opmn fails with connection refused

    Hi all,
    I've successfully installed Oracle Application Server 10g AS R2.
    After installation I could successfull login and access both Infra and Middle Tier using OEM, which were configured under a single Farm.
    But unfortunately, after and when the server is restarted... opmnctl startall hangs with ons.log contents as below
    08/06/23 16:25:14 [4] ONS server initiated
    08/06/23 16:53:15 [4] Logging disabled
    08/06/23 16:57:43 [4] ONS server initiated
    08/06/23 16:57:43 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
    08/06/23 16:59:42 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
    08/06/23 17:01:41 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
    08/06/23 17:03:40 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)08/06/23 17:04:00 [4] Logging disabled
    As a workaround I verified /etc/hosts file... it is as below
    127.0.0.1 localhost.localdomain localhost
    192.168.6.183 oravis.dsrc2.com oravis
    I'm performing the start-up & shutdown in the following order
    START DB Tier
    Start Database as
    Make sure your are in DB Home
    $ sqlplus "/as sysdba"
    SQL> startup
    Start DB Listener as
    Make sure your are in DB Home
    $ lsnrctl start RETEK
    Startup 10gAS Server
    Start Middle Tier iAS Console
    Make sure your are in Middle Tier Home
    cd $ORACLE_HOME/bin
    emctl start iasconsole
    Start Infra iAS Console
    Make sure your are in Infra Home
    cd $ORACLE_HOME/bin
    emctl start iasconsole
    Start Infra listener as
    $ lsnrctl start
    Start Infra Database as -
    $sqlplus "/as sysdba"
    SQL> startup
    Start Infra OC4J Services as
    Make sure your are in Infra Home
    $./opmnctl startall
    Start Middle Tier OC4J Services as
    Make sure your are in Middle Tier Home
    $./opmnctl startall
    Shutdown 10gAS Server
    Stop Middle Tier Services as
    Make sure your are in Middle Tier Home
    cd $ORACLE_HOME/opmn/bin
    $./opmnctl stopall
    Stop Infrastructure Services as
    Make sure your are in Infra Home
    $ ./opmnctl stopall
    Stop Infra Listener as
    Make sure your are in Infra Home
    $ lsnrctl stop [listener_name]
    Stop Infra Database as
    Make sure your are in Infra Home
    $ sqlplus "/as sysdba"
    SQL> shutdown immediate
    Stop Infra iAS Console
    Make sure your are in Infra Home
    cd $ORACLE_HOME/bin
    emctl stop iasconsole
    Stop Middle Tier iAS Console
    Make sure your are in Middle Tier Home
    cd $ORACLE_HOME/bin
    emctl stop iasconsole
    Stop DB Tier
    Stop Listener as
    Make sure your are in DB Home
    $ lsnrctl stop [listener_name]
    Stop Database as
    Make sure your are in DB Home
    $ sqlplus "/as sysdba"
    SQL> shutdown immediate
    Now... I'm able to access the Infra & Middle tier throgh OEM but the status is Unavailable. Moreover now they not under the Farm (Which they were earlier in).
    Also it is giving error connecting to repository database.
    Please anybody, who have come across this kind of problem, kindly guide me, where actually I'm missing.
    -Mahesh

    Hi Adith,
    Thanx a lot for the updates and correcting me. I've gone through the documents and corrected the way by which I was starting the services.
    But... when I try to do opmnctl startall, now I again got struck up with this strange error in ons.log
    08/06/24 10:26:02 [4] ONS server initiated
    08/06/24 10:47:51 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
    08/06/24 10:47:51 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
    08/06/24 10:49:50 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
    08/06/24 10:49:50 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
    08/06/24 10:51:49 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
    08/06/24 10:51:49 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
    I've gone through metalink and found out that this is a problem with SSL Authentication which been stated as a bug.
    Can anybody answer my following queries...
    1. Is it mandatory to enable SSL in 10g AS? Can we run server without SSL?
    2. If not mandatory, then how to disable SSL?
    3. If the handshake error is a bug, how to fix? Do I need to apply any patch for this?
    Looking forward for immediate response,
    Regards
    -Mahesh

  • Enqu-Error: Encomi: failed to connect to xyz/3277(Connection refused

    Hi Basis Experts,
    I am getting the following error in J2ee Engine
    The system config is
    CRM 2007 SP9
    DATABASE - ORACLE
    OS : WINDOWS 2003 X64
    The Java HTTP service is not coming up. All the status is in green in MMC
    Unable to open an web based Java application
    Thanks in Advance
    Date : 04/4/2008
    Time : 17:05:47:500
    *Message : Encomi: failed to connect to infoxsap/3203/Connection refused: connect)*
    *Severity : Error*
    Category : /System/Server
    Location : com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib
    Application :
    Thread : Thread[SAPEngine_EnquReader,5,main]
    Datasource : 24663050:D:\usr\sap\CRM\DVEBMGS02\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00188B74DBD7010800000031000027940004486C08C3557A
    Source Name : com.sap.engine.core.locking.impl3.LockingManagerImpl
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : 48f4cdb0f20a11dc9af100188b74dbd7
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : /System/Server
    Resource Bundlename :
    Session :
    Source : com.sap.engine.core.locking.impl3.LockingManagerImpl
    ThreadObject : Thread[SAPEngine_EnquReader,5,main]
    Transaction :
    User :

    Hi,
    your hostname http://A01CAC01/172.22.2.97 does look rather strange.
    Can the configtool connect to your database?
    Check your profiles for the MS host.
    regards,
    Andi

  • Encomi: failed to connect to XYZ/3203/Connection refused: connect

    Hi Basis Experts,
    I am getting the following error in J2ee Engine
    The system config is
    CRM 2007 SP9
    DATABASE - ORACLE
    OS : WINDOWS 2003 X64
    The Java HTTP service is not coming up. All the status is in green in MMC
    Unable to open an web based Java application
    Thanks in Advance
    Date : 04/4/2008
    Time : 17:05:47:500
    *Message : Encomi: failed to connect to infoxsap/3203/Connection refused: connect)*
    *Severity : Error*
    Category : /System/Server
    Location : com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib
    Application :
    Thread : ThreadSAPEngine_EnquReader,5,main
    Datasource : 24663050:D:\usr\sap\CRM\DVEBMGS02\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00188B74DBD7010800000031000027940004486C08C3557A
    Source Name : com.sap.engine.core.locking.impl3.LockingManagerImpl
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : 48f4cdb0f20a11dc9af100188b74dbd7
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : /System/Server
    Resource Bundlename :
    Session :
    Source : com.sap.engine.core.locking.impl3.LockingManagerImpl
    ThreadObject : ThreadSAPEngine_EnquReader,5,main
    Transaction :
    User :

    This is a x64 jvm bug which makes the server crash when a par file contains a corrupted zip.
    Please refer to this Note 696611 - Check j2ee lockhandler
    If lockhandler unreachable, an error message is returned:
    Enqu-Error: Encomi: failed to connect to binmain/3277(Connection refused)
    I wanted help in how to fix this issue.
    Thanks
    Sam Raju
    Edited by: Sam Raju on Apr 5, 2008 1:07 AM

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

  • Certificate authority export fails connection refused

    I am trying to export zenwork certificate and I receive the following error:
    Command
    zman --debug certificate-authority-export /root/cert
    Error:Could not connect to the ZENworks Server. Ensure that the server is running, and the host and port information specified is correct.
    Debug:
    com.novell.zenworks.datamodel.exceptions.Connectio nException: Connection refused
    What can I look at?

    zman certificate-authority-export /root/cert --debug
    Error:Could not connect to the ZENworks Server. Ensure that the server is runnin g, and the host and port information specified is correct.
    Debug:
    com.novell.zenworks.datamodel.exceptions.Connectio nException: Connection refused
    at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.createExcept ion(ZManExceptionHandler.java:286)
    at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.makeDataMode lException(ZManExceptionHandler.java:260)
    at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.processRemot eException(ZManExceptionHandler.java:390)
    at com.novell.zenworks.zman.commands.CAHandler.<init> (CAHandler.java:72)
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(NativeConstruct orAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingC onstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:501)
    at com.novell.zenworks.zman.CommandRunner.execute(Com mandRunner.java:86)
    at com.novell.zenworks.zman.ZMan.executeRunner(ZMan.j ava:321)
    at com.novell.zenworks.zman.ZMan.main(ZMan.java:505)
    Caused by: java.rmi.ConnectException: Connection refused
    at com.novell.soa.ws.portable.ApplicationException.ma pToRemote(Applicati onException.java:207)
    at com.novell.zenworks.datamodel.services.zoneconfig. soap.ZoneConfigAdmi nServiceBinding_Stub.hasZENServerRole(ZoneConfigAd minServiceBinding_Stub.java:50 71)
    at com.novell.zenworks.zman.commands.CAHandler.<init> (CAHandler.java:68

  • RemoteGui.bat Login attempt failed:connection refuse to SDM

    Heloo Guru's,
    I am trying to deploy service via running path: D:\usr\sap\XIG\DVEBMGS00\SDM\program <b>RemoteGui.bat</b> file .
    I am giving password for SDM user but error coming on clicking login button
    Error:could not establish connection to server <host> at port <50018>:connection refused:connect.
    Please advise.

    Hi Gaurav,
    You can find the SDM configuration file in \usr\sap\<system_id>\<instance no>\SDM\program\config with file name sdmrepository.sdc. In this file you will find your sdm host name and gui port number (default 50018). You change it from here and restart the server if its not set properly.
    Go to the mmc, select your serve node, expand instance 0 and look at the process table, you should have dispatcher / server0 and SDM nodes with their states set as started.
    It is possible that SDM was kept in standalone mode and not started with your server. If that is the case
    Run sdm jstartup "mode=integrated"
    restart your cluster.
    Regards,
    Prateek

Maybe you are looking for