3 answers
- 10-1
2019-08-07 15:11:30.770 DEBUG 523 --- [io-9191-exec-10] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header - this reminds me, would it be the same issue that you clicked so many times in CDT that caused the duplication in the header?
APPC-1676 - Not able execute tests under APPC CDT tool Closed
you can turn on the debugger in firefox, and check the header. I have submitted the fix for this.
- Frédéric Larocque
Hi Takamune Cho,
First, there is two problems. When I use firefox, the web page can't connect with APPC server.
This issue is related to cross origin request policy. So, I loaded the specific requested page in an another tab, then I trusted the certificate for this page. It solves this issue.
The second problem, is when I click on SYNCHRONIZE TEMPLATE PARAMETERS nothing happend.
I will look into that and give you more details.
Thanks
- Frédéric Larocque
Here is some details when I clicked on SYNCHRONIZE TEMPLATE PARAMETERS. The following message appear in the firefox debugger:
The script from “https://172.24.52.68:30289/node_modules/ace-builds/src-min/theme-chrome.js” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.
Loading failed for the <script> with source “https://172.24.52.68:30289/node_modules/ace-builds/src-min/mode-velocity.js”.
Maybe, this is not related ...
Does the SYNCHRONIZE TEMPLATE PARAMETERS button trigger a js script ?
Thanks,
- Takamune Cho
SYNCHRONIZE TEMPLATE PARAMETERS button triggers those js (link below) there is a node.js server running in CDT container - that takes care the SYNCHRONIZE TEMPLATE PARAMETERS click.
- Frédéric Larocque
Ok thank Takamune Cho for the information.
Here you can see, I got mutiple error when I try to access the template tab:
Should I open a Jira on this , or this is related to my environment ?
Thanks,
- Frédéric Larocque
I notice that if I upload the template using a file , the SYNCHRONIZE TEMPLATE PARAMETERS works ...
Add your comment... - 10-1
2019-08-07 15:11:30.770 DEBUG 523 --- [io-9191-exec-10] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
that reminds me. would that be the same issue on
Add your comment... - 10-1
I think it's a connectivity between CDT and APPC. In APPC docker, there is cdtproxy java application running. check the log to see what happened.
- Frédéric Larocque
I will look into : /opt/onap/appc/cdt-proxy-service/jar.log'
- Frédéric Larocque
Takamune Cho , I can't point out the root cause. Can you take a look when you will have time.
Thanks
- Takamune Cho
we can ignore that mode-velocity.js error. Did you see CDT POST request sending to CDTproxy, if so, then CDTproxy will compose a request then send to APPC.
- Frédéric Larocque
When I try to intereact with APPC using the CDT tool. Here is what happend in the jar.log. There is no trace of successul post request.
019-08-07 15:11:02.922 DEBUG 523 --- [nio-9191-exec-7] o.apache.tomcat.util.threads.LimitLatch : Counting down[https-jsse-nio-9191-exec-7] latch=1
2019-08-07 15:11:02.922 DEBUG 523 --- [nio-9191-exec-7] org.apache.tomcat.util.net.NioEndpoint : Socket: [org.apache.tomcat.util.net.SecureNioChannel@7cf73c83:java.nio.channels.SocketChannel[closed]] closed
2019-08-07 15:11:30.730 DEBUG 523 --- [9191-Acceptor-0] o.apache.tomcat.util.threads.LimitLatch : Counting up[https-jsse-nio-9191-Acceptor-0] latch=1
2019-08-07 15:11:30.732 DEBUG 523 --- [nio-9191-exec-8] o.a.tomcat.util.net.SecureNioChannel : The SNI host name extracted for connection [java.nio.channels.SocketChannel[connected local=/10.42.5.7:9191 remote=/10.42.6.0:58184]] was [null]
2019-08-07 15:11:30.770 DEBUG 523 --- [io-9191-exec-10] o.a.tomcat.util.net.SocketWrapperBase : Socket: [org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper@1d128707:org.apache.tomcat.util.net.SecureNioChannel@7cf73c83:java.nio.channels.SocketChannel[connected local=/10.42.5.7:9191 remote=/10.42.6.0:58184]], Read from buffer: [0]
2019-08-07 15:11:30.770 DEBUG 523 --- [io-9191-exec-10] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request headerjava.io.EOFException: null
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1206) ~[tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1140) ~[tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:731) ~[tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:352) ~[tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294) ~[tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:834) [tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415) [tomcat-embed-core-9.0.17.jar!/:9.0.17]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.17.jar!/:9.0.17]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_201]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.17.jar!/:9.0.17]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_201]2019-08-07 15:11:30.771 DEBUG 523 --- [io-9191-exec-10] o.apache.coyote.http11.Http11Processor : Socket: [org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper@1d128707:org.apache.tomcat.util.net.SecureNioChannel@7cf73c83:java.nio.channels.SocketChannel[connected local=/10.42.5.7:9191 remote=/10.42.6.0:58184]], Status in: [OPEN_READ], State out: [CLOSED]
- Frédéric Larocque
Takamune Cho , is there any workaround or action I can take to solve the problem ?
Thanks
- Frédéric Larocque
It seems that using chrome instead of firefox may works ... I will take a look into that
- Takamune Cho
would it be the same issue?
Add your comment...
Hi,
I'm trying to deploy the use case vFWDT following this tutorial :https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_vFWDT.html?highlight=vFWDT
At the step : Configuration of VNF in the APPC CDT tool. I'm facing this problem :
The CDT tool can't connect to APPC :
( In the bottom left corner, there is an APPC connection error)
When I click on the button below, nothing happened. I'm suspecting it is related to the APPC error:
How to troubleshoot this issue ?
Thanks,