JCo 3.0.2 RFC Error on HP-UX IA64

[Former Member]

I am taking the stock samples that come with JCo 3.0.2. The client and server samples work fine on 32-bit windows & linux. But, on IA64 HP-UX 11.23 the client sample works fine, but not the server example. (client example - StepByStepClient.java, server example - StepByStepServer.java)

The following is a verbose trace log (the tail end portion of it rather) that I am able to generate. Please confirm if someone else is also having this issue and if there is anyway to fix it.

JCoDispatcherWorkerThread [13:15:38:501]: [JCoApi] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave

main [13:15:38:515]: [JCoRFC] Accept before RfcAccept( -g"sapdb1ci" -x"3306" -a"DB1_JTEST" -t)

[Loaded com.sap.conn.rfc.engine.DefaultRfcTraceWriter$TraceWriterFactory from file:/tibdev/tmp/sapjco32/sapjco3.jar]

[Loaded java.io.FileWriter from /tibdev/tibco/jre/1.5.0/lib/rt.jar]

main [13:15:38:522]: Accept in RfcAccept( -g"sapdb1ci" -x"3306" -a"DB1_JTEST" -t) throws

RfcException: [null]

message: Connect to SAP gateway failed

Connect parameters: TPNAME=DB1_JTEST GWHOST=sapdb1ci GWSERV=3306

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR verify own hostname '192.168.220.1:65000' failed

TIME Wed May 13 13:15:38 200

RELEASE 711

COMPONENT NI (network interface)

VERSION 39

RC -16

MODULE nixxi.cpp

LINE 3585

DETAIL NiIBindSocket: 192.168.220.1:65000

SYSTEM CALL bind

ERRNO 227

ERRNO TEXT Can't assign requested address

COUNTER 4

Return code: RFC_FAILURE(1)

error group: 102

key: RFC_ERROR_COMMUNICATION

>>> Error occured on TIBCO_DB1_JTEST connection null

com.sap.conn.jco.JCoException: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Wed May 13 13:15:38 EDT 2009.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=DB1_JTEST GWHOST=sapdb1ci GWSERV=3306

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR verify own hostname '192.168.220.1:65000' failed

TIME Wed May 13 13:15:38 200

RELEASE 711

COMPONENT NI (network interface)

VERSION 39

RC -16

MODULE nixxi.cpp

LINE 3585

DETAIL NiIBindSocket: 192.168.220.1:65000

SYSTEM CALL bind

ERRNO 227

ERRNO TEXT Can't assign requested address

COUNTER 4

at com.sap.conn.jco.rt.DefaultServer.openConnection(DefaultServer.java:1069)

at com.sap.conn.jco.rt.DefaultServer.adjustConnectionCount(DefaultServer.java:953)

at com.sap.conn.jco.rt.DefaultServer.addListener(DefaultServer.java:273)

at com.sap.conn.jco.rt.DefaultServer.start(DefaultServer.java:653)

at com.sap.conn.jco.rt.DefaultServer.start(DefaultServer.java:628)

at StepByStepServer.step2SimpleServer(StepByStepServer.java:166)

at StepByStepServer.main(StepByStepServer.java:277)

Caused by: com.sap.conn.jco.JCoException: (129) JCO_ERROR_SERVER_STARTUP: Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=DB1_JTEST GWHOST=sapdb1ci GWSERV=3306

Edited by: Sharad Gupta on May 14, 2009 4:39 AM

[Former Member]

Thanks for your reply. SAP hostname & ip is getting resolved through DNS queries, that part is fine. Its when the JCo layer is trying to bind itself to localhost port 65000 for some ICM internal communication needs, is when JCo flips on HP-UX.

On linux & windows machines, localhost is getting resolved to 127.0.0.1 & its able to bind itself to port 65000. My guess is someone must have fat fingered that ip in the libsapjco3.so shared library.

thanks

[Former Member]

Have you enter SAP server ip and host name in your host file if not please enter the same

To go to your window host file Start -> enter commant drivers in run option you will find host file on following path. Edit host file and enter sap server ip & host name.

C:\WINDOWS\system32\drivers\etc

1. Copyright (c) 1993-1999 Microsoft Corp.

#

1. This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

#

1. This file contains the mappings of IP addresses to host names. Each

2. entry should be kept on an individual line. The IP address should

3. be placed in the first column followed by the corresponding host name.

4. The IP address and the host name should be separated by at least one

5. space.

#

1. Additionally, comments (such as these) may be inserted on individual

2. lines or following the machine name denoted by a '#' symbol.

#

1. For example:

#

1. 102.54.94.97 rhino.acme.com # source server

2. 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

124.150.168.1 nmsapdev

192.168.60.4 nmsapqas

192.168.60.5 NMSAPPRD1