Page 1 of 1
Scan Problem
PostPosted:Fri Apr 16, 2010 11:22 am
by jloureiro
Hi,
I´m new to OpenKM (Study fase).
I´m traing to use the scanning and upload function but in the final stage of the process (Upload fase) I get the following error:
Failed to access the WSDL at: http://localhost:8080/OpenKM/OKMDocument?wsde. it failed with: Connection refused:Connect
I´m traing this on another workstation, not the OpenKM server, with a hp scanner. The scanning process is completed but the upload gives the above error. The problem is the URL how can I change the localhost reference?
Thanks
Re: Scan Problem
PostPosted:Fri Apr 16, 2010 3:47 pm
by yiannis
Hey there,
I have the same problem. What do we have to change to get remote clients use the right server address instead of localhost ??
cheers
yiannis
Re: Scan Problem
PostPosted:Sun Apr 18, 2010 6:01 pm
by jllort
Try setting in OpenKM.cfg
application.url=
http://localhost:8080/OpenKM/es.git.ope ... /index.jsp
REmember you mus restart jboss server after any OpenKM.cfg change
Tell me if it solves the problem
Re: Scan Problem
PostPosted:Sun Apr 18, 2010 10:43 pm
by jloureiro
Hi again,
In first place thank you for helping me.
I have placed you suggestion in the openkm.cfg (localhost to my-server-name) but keep getting the same result in the upload phase (Failed to access the WSDL at:
http://localhost:8080/OpenKM/OKMDocument?wsdl. it failed with: Connection refused:Connect).
here is the debugging extracted from the java console.
Code: Select allJarLib.load: Successfully loaded library [jar:http:// my-server-name:8080/OpenKM/scanner.jar!/uk/co/mmscomputing/device/twain/win32/jtwain.dll] from jar file location
18/Abr/2010 23:16:32 com.openkm.applet.Util uploadDocument
INFO: uploadDocument(10764044066723331112963186148821, /okm:root, teste, pdf, http://sechat.grupojrp.pt:8080/OpenKM, BufferedImage@958bb8: type = 5 ColorModel: #pixelBits = 24 numComponents = 3 color space = java.awt.color.ICC_ColorSpace@7f4ec transparency = 1 has alpha = false isAlphaPre = false ByteInterleavedRaster: width = 1275 height = 1755 #numDataElements 3 dataOff[0] = 2
18/Abr/2010 23:16:33 com.openkm.applet.ScannerManager update
SEVERE: WebServiceException: Failed to access the WSDL at: http:// my-server-name:8080/OpenKM/OKMDocument?wsdl. It failed with:
Connection refused: connect.
javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:8080/OpenKM/OKMDocument?wsdl. It failed with:
Connection refused: connect.
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unknown Source)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknown Source)
at javax.xml.ws.Service.<init>(Unknown Source)
at com.openkm.ws.client.OKMDocumentService.<init>(OKMDocumentService.java:46)
at com.openkm.applet.Util.uploadDocument(Util.java:60)
at com.openkm.applet.ScannerManager.update(ScannerManager.java:121)
at uk.co.mmscomputing.device.scanner.Scanner.fireListenerUpdate(Scanner.java:45)
at uk.co.mmscomputing.device.twain.TwainScanner.setImage(TwainScanner.java:75)
at uk.co.mmscomputing.device.twain.jtwain.transferNativeImage(jtwain.java:302)
at uk.co.mmscomputing.device.twain.TwainTransfer$NativeTransfer.finish(TwainTransfer.java:48)
at uk.co.mmscomputing.device.twain.TwainSource.transfer(TwainSource.java:315)
at uk.co.mmscomputing.device.twain.TwainSource.transferImage(TwainSource.java:354)
at uk.co.mmscomputing.device.twain.TwainSource.handleGetMessage(TwainSource.java:416)
at uk.co.mmscomputing.device.twain.jtwain.cbhandleGetMessage(jtwain.java:249)
at uk.co.mmscomputing.device.twain.jtwain.nstart(Native Method)
at uk.co.mmscomputing.device.twain.jtwain.access$200(jtwain.java:12)
at uk.co.mmscomputing.device.twain.jtwain$1.run(jtwain.java:339)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Unknown Source)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unknown Source)
... 20 more
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 6:21 am
by jllort
It's a problem accessing webservices, ok ... let's investigate the reason ?
1- Are you using the default OpenKM bundle downloaded in sourceforge or you've deployed OpenKM in a previous jboss application in your server ?
2- If you accesing to
http://localhost:8080/OpenKM/OKMDocument?wsdl runs well ?
3- Can you ping to my-server-name ( resolves well ? )
4- Theres some strange space in "http:// my-server-name" between // and my
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 10:13 am
by jloureiro
Hello,
1 - I´m using the last version of OpenKM (RC1) but, in the previous version I had the same problem. The difference is that I´m running JBOSS as a windows service (Windows server 2008 x64) JBOSS Application 5.0. And so far so good it works fine with AD integration and other function already tested (except the upload fase of the scanner and the pdf2swf it shows the object in OpKM but it shows me an always an empty page).
2 - It shows me a XML page and from a client machine when I change the localhost to my-server-name shows me the same page (OKMDocumentService). So I assume that's the correct beaver?
3- Yes very fast and well.
4 - My mistake when changing the real name of the server to a generic my-server-name.
Thank´s
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 11:18 am
by jllort
WE've got problems with webservices changing the jboss version, seems webservices to jboss 4.X are not totally compatible with 5.x ( it's a jboss upgrading application server problem ) ... could you try in jboss 4.x server ... or simply for testing purpose donwload actual sourceforge release and try in the same web server you've got actually deployed OpenKM.
Give me your feedback about it.
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 5:48 pm
by jloureiro
I made some testing with the scanner function in two different scenarios:
1 - In my-server-name (Windows server 2008 x64) the one with JBOSS Application 5.0 I attach to it a scanner a physical scanner and I was able to scan and upload the scanned file. When a tray to do this from a remote machine (client workstation) gives the already known error.
2 - I downloaded your latest version of OpenKM (4.1-RC1) and installed on a clean machine (Windows 7 pro) and the result was the same locally (localhost) all works well but from a remote machine don't.
From a remote machine he tries to access to the url
http://localhost:8080/OpenKM/OKMDocument?wsdl (self) but is not running that service. He recognize the scanner.jar located on my-server-name (passes the right url) but accessing the service OKMDocument he tries to access to local resources so it seems by the error message referring to the localhost. This URL is defined where?
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 9:22 pm
by pavila
Can you reproduce the issue in
http://demo.openkm.com ?
Re: Scan Problem
PostPosted:Tue Apr 20, 2010 10:44 pm
by jloureiro
I made the requested test with user05 on your demo page the name of the file to upload was teste_jloureiro.pdf (same error).
Remember my last post referring to the two scenarios? I was working from the windows 7 pro (for me client machine) and OpenKM JBOSS was running (used for the second scenario), didn’t notice, but I tried to make a scanning and upload to my-server-name (Windows Server 2008) and the process completed with a successful upload to this server. Then a stopped the local instance running on win 7 and repeated the process again this time with an error (the same).
Re: Scan Problem
PostPosted:Wed Apr 28, 2010 3:28 pm
by jloureiro
So no hope!
Re: Scan Problem
PostPosted:Wed Apr 28, 2010 8:10 pm
by pavila
Perhaps you have the old applet in the local cache. Delte it across Java Plugin Control Panel. Actually I can connect to
http://demo.openkm.com, run the applet and send a scanned document.
Re: Scan Problem
PostPosted:Mon May 03, 2010 8:35 am
by mmodrive
Hi, I've also confirmed this as a current problem. The application does not substitute the default url (
http://localhost:8080/OpenKM/OKMDocument?wsdl) to a configured one (e.g.
http://my-server-name:8080/OpenKM/OKMDocument?wsdl). Same behaviour witnessed at
http://demo.openkm.com/. Will there be a fix?
Re: Scan Problem
PostPosted:Mon May 03, 2010 3:23 pm
by pavila
Just fixed
I am uploading the new OpenKM 4.1 release which also include this fix. The
http://demo.openkm.com include also this fix. More news soon.