Expand my Community achievements bar.

Problem Reading Internet based Resources - JBoss - ES2 - windows 2008

Avatar

Level 5

I have an issue trying to use Java via ExecuteScript to get data via URLs on a Staging Server.

The code runs on the server by ends with a Connection Timeout Error.

I have a Production server that does not have the issue, and runs correctly.

Both servers are running LiveCycle ES2 (9.0) JBoss

Staging is Windows Server 2008 R2

Production is Windows Server 2008 Std.

Can anyone give me suggestions where to look in the configuration of LC or Windows to determine why Staging will no return data.

I can remote console onto the Staging box, and retrieve the URL with Internet Explorer OK (using my credentials)  - so the box can 'see' the Internet.

Any help is greatly appreciated!

Thanks

Mark

Example code below (may not run as is):

import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.util.ArrayList;
import java.net.URL;
import java.io.*;
com.adobe.idp.Document pdfDoc;


String error = "";
String tmpStr;
String ddxBody = "";
String outputName = "";
String extendedFeatures = "";


        System.out.println("***START 1***");

com.adobe.idp.Document xmlDoc = patExecContext.getProcessDataDocumentValue("/process_data/xmlData");
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();


        URL url =  new URL("http://help.adobe.com/en_US/livecycle/9.0/createfirstapp.pdf");
        System.out.println("***START 2 ***");

pdfDoc = new com.adobe.idp.Document(url);

        System.out.println("***START 3 ***");

        pdfDoc.passivate();

        System.out.println("***START 4 ***: " + docLength );

        patExecContext.setProcessDataDocumentValue("/process_data/outDoc",pdfDoc);
       
        System.out.println("***START 5 ***");

1 Reply

Avatar

Level 7

Windows Server 2008 R2 is a lot more locked down in terms of security than Windows Server 2008.

Can you Remote Desktop into the staging box, fire up a command prompt and ping help.adobe.com?  Do you get something like this:

C:\TEMP>ping help.adobe.com

Pinging a630.b.akamai.net [64.71.251.185] with 32 bytes of data:
Reply from 64.71.251.185: bytes=32 time=26ms TTL=57
Reply from 64.71.251.185: bytes=32 time=17ms TTL=57
Reply from 64.71.251.185: bytes=32 time=17ms TTL=57
Reply from 64.71.251.185: bytes=32 time=25ms TTL=57

Ping statistics for 64.71.251.185:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 26ms, Average = 21ms

1) Check the Internet Explorer settings to see if it has been configured to use a proxy.

2) Check the Windows Firewall to see if Outbound firewall rules are preventing calls to http://help.adobe.com on port 80