Home
Extended ECM
API, SDK, REST and Web Services
LAPI behind a proxy and through port 80
ATHANASSIOS_FAMELIARIS
Hello all! We really need your help with an issue we are facing in LAPI. We are interested in connecting to a server running Livelink through port 80, with the clients behind a proxy server. We used tunneling for this, following the instructions described in the LAPI documentation, to create java applets which use the Livelink cookie. We managed to connect when not behind a proxy server only. We use the following piece of code for both versions: LLSession ll = new LLSession (server, port, cookie, config); We just need to set the config, server and port: config.setAssoc(); config.add ("HTTPS", LLValue.LL_FALSE); config.add ("LivelinkCGI", "/livelink/livelink.exe"); server= “THE_SERVER_WE_ACCESS”; port = 80; For the version which uses the proxy we made the following settings: config.setAssoc();config.add ("HTTPS", LLValue.LL_FALSE);config.add ("LivelinkCGI", " THE_SERVER_WE_ACCESS :80/livelink/livelink.exe"); server=”OUR_PROXY_SERVER”; port=8080; We get the following exception with the proxy version: java.lang.NumberFormatException: For input string: "2358 " We think that there one of the following is happening: 1) There is some bug in LAPI's LLConnect.readResponseHeaders() method which causes the above exception2) The settings described in the documentation are wrong. We would greatly appreciate any help on this! Thank you in advance! Yours truly,Ys
Find more posts tagged with
Comments
Claudia_Meyer
Message from Christopher Meyer via eLinkHi,I looked over your message and don't immediately see the problem. Couldyou give us the entire stack trace? I'm curious on which line the java.lang.NumberFormatException: For input string: "2358 "error took place. Do you know what this 2358 might be (userid? nodeid?)chris-----Original Message-----From: eLink Discussion: LAPI Discussion[mailto:lapi@elinkkc.opentext.com] Sent: Monday, February 07, 2005 9:01 AMTo: eLink RecipientSubject: LAPI behind a proxy and through port 80LAPI behind a proxy and through port 80Posted by Zeti, Stavroula on 02/07/2005 02:56 AMHello all! We really need your help with an issue we are facing in LAPI. We areinterested in connecting to a server running Livelink through port 80,with the clients behind a proxy server. We used tunneling for this,following the instructions described in the LAPI documentation, tocreate java applets which use the Livelink cookie. We managed to connectwhen not behind a proxy server only. We use the following piece of codefor both versions: LLSession ll = new LLSession (server, port, cookie, config); We just need to set the config, server and port: config.setAssoc(); config.add ("HTTPS", LLValue.LL_FALSE); config.add ("LivelinkCGI", "/livelink/livelink.exe"); server= “THE_SERVER_WE_ACCESS”; port = 80; For the version which uses the proxy we made the following settings: config.setAssoc();config.add ("HTTPS", LLValue.LL_FALSE);config.add ("LivelinkCGI", " THE_SERVER_WE_ACCESS:80/livelink/livelink.exe"); server=”OUR_PROXY_SERVER”; port=8080; We get the following exception with the proxy version: java.lang.NumberFormatException: For input string: "2358 " We think that there one of the following is happening: 1) There is some bug in LAPI's LLConnect.readResponseHeaders() methodwhich causes the above exception2) The settings described in the documentation are wrong. We would greatly appreciate any help on this! Thank you in advance! Yours truly,Ys[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: LAPI Discussion
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink
Server:
https://knowledge.opentext.com/knowledge/livelink.exe
ATHANASSIOS_FAMELIARIS
The trace of the exception is the following, but please have a look at the attachments for some further into on our code and settings:java.lang.NumberFormatException: For input string: "2358 " at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.(Unknown Source) at com.opentext.api.LLConnect.readResponseHeaders(LLConnect.java:983) at com.opentext.api.LLConnect.executeHTTP(LLConnect.java:1378) at com.opentext.api.LLConnect.execute(LLConnect.java:334) at com.opentext.api.LAPI_DOCUMENTS.AccessPersonalWS(LAPI_DOCUMENTS.java:93) at llcookie.start(llcookie.java:70) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
John_Shoun
We are seeing a similar problem now.The exception is raised either from LAPI_DOCUMENTS.ListObjects or a fetch version call. The goes up through and ends with .In one case it happened with a document that had a "tab" embedded in the document name (don't ask me how that got loaded, but we verified it through the database). Now we are seeing this happen in many other areas as well.However our configuration is different. We are using HTTP connect directly to the Livelink server without a proxy and not using SSL.Any further ideas?