[Dspace-tech] SWORD servlet client installed on Amazon Cloud -- not connecting -- please help!
Hi SWORD experts, I have SWORD installed on my local machine. I built the sword.war file, installed it under tomcat/webapps and am able to view the servicedocument at localhost in the browser. I then copied over the same sword.war file to my dspace instance on Amazon Cloud. When I try to connect to it, it fails with the error: Server returned: org.purl.sword.client.SWORDClientExcpetion: Connection refused The catalina.out log has the error: at java.lang.Thread.run(Thread.java:675) Caused by: org.purl.sword.base.UnmarshallException: Error acessing the file? at org.purl.sword.base.ServiceDocument.unmarshall(ServiceDocument.java:182) at org.purl.sword.client.Client.getServiceDocument(Client.java:285) ... 16 more Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection .java:1322) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity( XMLEntityManager.java:654) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEnti tyManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLE ntityManager.java:1259) .. .. org.purl.sword.client.SWORDClientException: Connection refused at org.purl.sword.client.Client.getServiceDocument(Client.java:294) at org.purl.sword.client.ServletClient.doServiceDocument(ServletClient.java:413 ) at org.purl.sword.client.ServletClient.doPost(ServletClient.java:306) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) .. .. Did not post the complete error file.will provide if it is needed. Have highlighted the line that I believe is at the root of the connection problem. Please help! -Debashree -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] SWORD servlet client installed on Amazon Cloud -- not connecting -- please help!
Debashree, Nice to see a message from you. I suspect that the person who created your AMI image placed an incorrect entry into the Linux iptables. Entries were placed into the iptables to implement port forwarding on incoming connections from standard port 80 to Tomcat port 8080. The most likely problem is that an entry was accidentally placed into the iptables that also implements this forwarding on outgoing connections. This is causing problems when the SWORD application tries to access the DTD at http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd. Have your systems person check the Linux iptables entries and look to see if anything is out of place. Please let me know of the resolution for this issue. Keith Gilbertson Consultant for Library and Educational Computer Systems On Tue, Sep 8, 2009 at 11:07 AM, Debashree Pati dp...@oln.org wrote: Hi SWORD experts, I have SWORD installed on my local machine. I built the sword.war file, installed it under tomcat/webapps and am able to view the servicedocument at localhost in the browser. I then copied over the same sword.war file to my dspace instance on Amazon Cloud. When I try to connect to it, it fails with the error: Server returned: org.purl.sword.client.SWORDClientExcpetion: Connection refused The catalina.out log has the error: at java.lang.Thread.run(Thread.java:675) Caused by: org.purl.sword.base.UnmarshallException: Error acessing the file? at org.purl.sword.base.ServiceDocument.unmarshall(ServiceDocument.java:182) at org.purl.sword.client.Client.getServiceDocument(Client.java:285) ... 16 more Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:654) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1259) …… …… org.purl.sword.client.SWORDClientException: Connection refused at org.purl.sword.client.Client.getServiceDocument(Client.java:294) at org.purl.sword.client.ServletClient.doServiceDocument(ServletClient.java:413) at org.purl.sword.client.ServletClient.doPost(ServletClient.java:306) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) …. …. Did not post the complete error file…will provide if it is needed. Have highlighted the line that I believe is at the root of the connection problem. Please help! -Debashree -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] SWORD servlet client installed on Amazon Cloud -- not connecting -- please help!
Hey Keith, It's wonderful to get your expert advice. Actually, the person who created my AMI did not implement port forwarding in my image. He checked the iptables and confirmed it. There was an error on my part in the dspace config for SWORD module that was carried over from my early experimentation with bulk-submission using SWORD. Thank you very much for the quick reply! -Debashree From: Keith Gilbertson [mailto:keith.gilbert...@gmail.com] Sent: Tuesday, September 08, 2009 11:30 AM To: Debashree Pati Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] SWORD servlet client installed on Amazon Cloud -- not connecting -- please help! Debashree, Nice to see a message from you. I suspect that the person who created your AMI image placed an incorrect entry into the Linux iptables. Entries were placed into the iptables to implement port forwarding on incoming connections from standard port 80 to Tomcat port 8080. The most likely problem is that an entry was accidentally placed into the iptables that also implements this forwarding on outgoing connections. This is causing problems when the SWORD application tries to access the DTD at http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd. Have your systems person check the Linux iptables entries and look to see if anything is out of place. Please let me know of the resolution for this issue. Keith Gilbertson Consultant for Library and Educational Computer Systems On Tue, Sep 8, 2009 at 11:07 AM, Debashree Pati dp...@oln.org wrote: Hi SWORD experts, I have SWORD installed on my local machine. I built the sword.war file, installed it under tomcat/webapps and am able to view the servicedocument at localhost in the browser. I then copied over the same sword.war file to my dspace instance on Amazon Cloud. When I try to connect to it, it fails with the error: Server returned: org.purl.sword.client.SWORDClientExcpetion: Connection refused The catalina.out log has the error: at java.lang.Thread.run(Thread.java:675) Caused by: org.purl.sword.base.UnmarshallException: Error acessing the file? at org.purl.sword.base.ServiceDocument.unmarshall(ServiceDocument.java:182) at org.purl.sword.client.Client.getServiceDocument(Client.java:285) ... 16 more Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection .java:1322) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity( XMLEntityManager.java:654) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEnti tyManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLE ntityManager.java:1259) .. .. org.purl.sword.client.SWORDClientException: Connection refused at org.purl.sword.client.Client.getServiceDocument(Client.java:294) at org.purl.sword.client.ServletClient.doServiceDocument(ServletClient.java:413 ) at org.purl.sword.client.ServletClient.doPost(ServletClient.java:306) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) .. .. Did not post the complete error file.will provide if it is needed. Have highlighted the line that I believe is at the root of the connection problem. Please help! -Debashree -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists
