Page 1 of 1

404 Not Found errors when Oxygen installed

Posted: Thu Jul 19, 2007 8:07 pm
by declan_flynn
Hi,
We have a set of plugins that are used to write and test web-services. As part of the testing process we have a web service tester which sends requests to our server. This all works fine on its own but when we add in Oxygen we started getting 404 errors.

After searching through the error logs we found that the 404 error seems to coming from some obfuscated Oxygen code.

Code: Select all


The 404 exception stack:

!ENTRY com.capeclear.wtp.server.publisher 4 0 2007-07-13 13:52:35.687
!MESSAGE Publish to Cape Clear Server failed: Error during send-receive; nested exception is:
com.capeclear.capeconnect.transport.TransportException: An I/O error occurred sending to http://localhost:8080/ccx/cc-authenticate: 404 Not Found for: http://localhost:8080/ccx/cc-authenticate
!STACK 0
java.rmi.RemoteException: Error during send-receive; nested exception is:
com.capeclear.capeconnect.transport.TransportException: An I/O error occurred sending to http://localhost:8080/ccx/cc-authenticate: 404 Not Found for: http://localhost:8080/ccx/cc-authenticate
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.$_doSend(BaseWSProxy.java:1366)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.$_processSoapMessage(BaseWSProxy.java:873)
at com.capeclear.capeconnect.soap.proxy.backend.impl.DefaultBackendExecutor.execute(DefaultBackendExecutor.java:57)
at com.capeclear.capeconnect.soap.proxy.backend.impl.DefaultBackendExecutor.execute(DefaultBackendExecutor.java:40)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.$_processRequest(BaseWSProxy.java:826)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy$JavaArgRequestInvoker.invoke(BaseWSProxy.java:187)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.$_doInvokeRequest(BaseWSProxy.java:770)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy$1.run(BaseWSProxy.java:591)
at java.security.AccessController.doPrivileged(Native Method)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.invokeRequest(BaseWSProxy.java:588)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.invokeRequest(BaseWSProxy.java:557)
at com.capeclear.capeconnect.soap.proxy.dynamic.DynSoapProxyHandler.invokeRequest(DynSoapProxyHandler.java:81)
at com.capeclear.capeconnect.soap.proxy.dynamic.ServiceInvocationHandler.invokeOperation(ServiceInvocationHandler.java:392)
at com.capeclear.capeconnect.soap.proxy.dynamic.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:154)
at $Proxy0.login(Unknown Source)
at com.capeclear.wtp.server.core.ServerProxyHelper.<init>(Unknown Source)
at com.capeclear.wtp.server.publisher.CcWsSoapPublisher.initProxies(Unknown Source)
at com.capeclear.wtp.server.publisher.CcWsSoapPublisher.publish(Unknown Source)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:91)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:676)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:756)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:611)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:865)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:853)
at org.eclipse.wst.server.core.internal.ServerWorkingCopy.publish(ServerWorkingCopy.java:627)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:142)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: com.capeclear.capeconnect.transport.TransportException: An I/O error occurred sending to http://localhost:8080/ccx/cc-authenticate: 404 Not Found for: http://localhost:8080/ccx/cc-authenticate
at com.capeclear.capeconnect.transport.http.client.HttpTransport.sendWithRetry(HttpTransport.java:212)
at com.capeclear.capeconnect.transport.http.client.HttpTransport.sendAndReceive(HttpTransport.java:130)
at com.capeclear.capeconnect.transport.http.client.SoapHttpTransport.doSendOrSendAndReceive(SoapHttpTransport.java:124)
at com.capeclear.capeconnect.transport.http.client.SoapHttpTransport.sendAndReceive(SoapHttpTransport.java:59)
at com.capeclear.capeconnect.soap.proxy.BaseWSProxy.$_doSend(BaseWSProxy.java:1351)
... 26 more
Caused by: org.apache.commons.httpclient.HttpException: 404 Not Found for: http://localhost:8080/ccx/cc-authenticate
at ro.sync.V.A.A.A.A(Unknown Source)
at ro.sync.V.A.A.A.A(Unknown Source)
at ro.sync.V.A.A.C.getInputStream(Unknown Source)
at ro.sync.V.A.A.C.getResponseCode(Unknown Source)
at com.capeclear.capeconnect.transport.http.client.HttpURLConnectionWrapper.checkStatus(HttpURLConnectionWrapper.java:183)
at com.capeclear.capeconnect.transport.http.client.HttpTransport.sendImpl(HttpTransport.java:248)
at com.capeclear.capeconnect.transport.http.client.HttpTransport.sendWithRetry(HttpTransport.java:172)
... 30 more
Line 183 in HttpURLConnectionWrapper is simply calling getResponseCode() on a java.net.HttpURLConnection object.

Earlien in the logs we also see

Code: Select all

!ENTRY org.eclipse.osgi 4 0 2007-07-12 17:14:39.937
!MESSAGE While loading class "ro.sync.exml.H", thread "main" timed out waiting (5000ms) for thread "Worker-2" to finish starting bundle "com.oxygenxml.editor". To avoid deadlock, thread "main" is proceeding but "ro.sync.exml.H" may not be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
The server is running, everything is available as normal. If we remove the Oxygen plugins everything works again. Is Oxygen registering anything or doing anything with HTTP that may have caused it to lock up? Has anyone seen this happen before or have any idea what can be causing it?

Thanks,
Declan

Posted: Mon Jul 23, 2007 11:50 am
by sorin_ristache
Hello,

Do you use Eclipse 3.2? What is the build number of the oXygen plugin in Window - Preferences - oXygen? If it is not the latest build available on the Download page (2007062605) please try with that. It should not register something on HTTP.


Regards,
Sorin

Posted: Mon Jul 23, 2007 2:53 pm
by declan_flynn
We are using Eclipse 3.2.2 and Oxygen 8.2 build 2007062605

Posted: Mon Jul 23, 2007 5:08 pm
by sorin_ristache
Hello,

It was a problem with the HTTP proxy settings of the oXygen plugin which sets the HTTP proxy for all the plugins. We fixed the problem for the next version of the plugin. In the current build you can test the web service if you set the correct proxy settings for your web service in Window -> Preferences -> oXygen -> HTTP/FTP/Proxy Configuration.


Regards,
Sorin

Posted: Tue Jul 24, 2007 11:01 am
by zoreander
I had this same problem but i simply reinstaled Eclipse and now work's fine.

Regards

Posted: Tue Jul 24, 2007 11:46 am
by declan_flynn
Great :-)

Thank you. We'll test that now. Do you know when the next version of the plugin will be released?

Thanks,
Declan

Posted: Tue Jul 24, 2007 12:33 pm
by sorin_ristache
The next version of the plugin will be released before the end of the year but the exact date was not planned.


Regards,
Sorin