on 02-18-2014 10:53 AM
Hello,
I have created a project with a reference table query. I have installed HANA ODBC client and it works perfectly with another project which has HANA Output Adapter.
The CCL file contains :
CREATE INPUT STREAM reciever
SCHEMA (id integer, pos integer, datatype string);
CREATE REFERENCE maptabRef
SCHEMA (id integer, pos integer, datatype string)
PROPERTIES service='ND7ODBCService',source='maptaba', sourceSchema='M2M';
CREATE OUTPUT STREAM outputStream
SCHEMA (id integer, pos integer, datatype string)
AS SELECT maptabRef.id, maptabRef.pos, maptabRef.datatype
FROM reciever, maptabRef
WHERE reciever.pos = maptabRef.pos;
But when I am trying to run the same it gives following error:
Failed call to:http://localhost:56105/RPC2 (Failed to read server's response: Connection refused: connect)
Can somebody tell what could be the reason for this.
Thanks,
Gaurav Singh
Hi Gaurav,
Will you please describe how you are trying to run the project? Where are you deploying from, and where to?
When you say "it gives the following error", is that a message you are seeing in an ESP Studio dialog, or is it appearing elsewhere?
Errors like these can occur when you deploy a project from one machine to a remote machine whose ESP node configuration file HOSTNAME macro is set to localhost. Parts of the deployment will work, but other parts will fail due to the HOSTNAME setting.
Can you find the stdstreams and esp_server.log file of the project you ran and attach them to this thread?
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mike,
I am running the project in SYBASE ESP Studio and the error comes in a pop up window.
In my localnode.xml the hostname is configured as follows:
<Macro name="ESP_HOSTNAME">localhost</Macro>
And in node1.xml the same is configured as follows:
<Macro name="ESP_HOSTNAME">INLN50800330A</Macro>
And the log file is as follows:
2014-02-18 20:44:26.313 | 8592 | container | [SP-1-135021] (0.002) sp(5084) Platform::main() -- REVISION <ESP 5.1.04.00>, start timestamp (gmt): 02/18/2014 20:44:26
2014-02-18 20:44:26.313 | 8592 | container | [SP-3-100005] (0.002) sp(5084) ------ License check started ------
2014-02-18 20:44:26.602 | 8592 | container | [SP-3-100005] (0.291) sp(5084) ------ License check succeeded ------
2014-02-18 20:44:26.603 | 8592 | container | [SP-1-135036] (0.292) sp(5084) Platform::main() -- Starting initialization sequence.
2014-02-18 20:44:28.491 | 8592 | container | [SP-2-722005] (2.180) sp(5084) Associating connection to application
2014-02-18 20:44:28.495 | 8592 | container | [SP-2-722007] (2.184) sp(5084) Application successfully associated with connection
2014-02-18 20:44:28.495 | 8592 | container | [SP-2-722008] (2.184) sp(5084) Attempting to register application with cluster
2014-02-18 20:44:28.498 | 8592 | container | [SP-2-722011] (2.187) sp(5084) Application successfully registered
2014-02-18 20:44:28.498 | 8592 | container | [SP-2-722023] (2.187) sp(5084) The application successfully registered
2014-02-18 20:44:28.498 | 8592 | container | [SP-2-722025] (2.187) sp(5084) Starting application heartbeats on new connection
2014-02-18 20:44:28.499 | 9032 | container | [SP-2-722012] (2.188) sp(5084) Entering heartbeat loop
2014-02-18 20:44:28.502 | 8592 | container | [SP-4-114126] (2.191) sp(5084) Platform(): Auto Checkpoint interval is set to 0.
2014-02-18 20:44:28.851 | 8592 | container | [SP-3-114113] (2.540) sp(5084) Platform()::processSignal(): fatal error (signal=11) in thread id 8592, thread name 'unknown thread'; aborting.
Hi Gaurav,
Please try commenting out everything but the INPUT STREAM definition, compile, then see if you can deploy successfully. If that fails, then there may be an issue with configuration of your ESP Studio.
If that succeeds, then please post your complete project and service.xml file and localnode.xml file and all related log files to our internal SAP JAM site for review.
Mike
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.