Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spline Web UI- "ERROR Server returned code: 0. Http failure response for http://spline:9090/consumer/execution-events" #744

Closed
ankit302 opened this issue Jun 29, 2020 · 10 comments · Fixed by #745

Comments

@ankit302
Copy link

Describe the bug

While accessing Spline web UI - getting server retured code:0 https failure response.

Versions

spline version 0.5.3 ( Docker latest image tag )
arnagoDb version 3.5.1 ( Docker latest image tag )

Components State

  • [ Yes ] ArangoDB running without errors
  • [ Yes] ArangoDB spline database initialized
  • Rest Gateway running and
    • [YES ] connects to ArangoDB
    • [ YES] there are no errors in logs
  • Spline UI running and
    • [NO ] connects to Rest Gateway consumer
    • [YES ] there are no errors in logs

To Reproduce

Steps to reproduce the behavior OR commands run:

Accessing spline webui on brower

Expected behaviour

Should be able to view the spline webUI page

Screenshots

Attached the error of spline webUI:
Capture

Desktop (please complete the following information):

  • OS: [Ubuntu]
  • Browser [Chrome]
  • Version [Latest]

Additional context

Add any other context about the problem here.

spline service file:-

apiVersion: v1
kind: Service
metadata:
annotations:
kompose.cmd: kompose convert
kompose.version: 1.21.0 (992df58d8)
creationTimestamp: null
labels:
io.kompose.service: spline
name: spline
namespace: dataservice
spec:
ports:

service file spline-ui:-

name: "9090"
port: 9090
targetPort: 8080
selector:
io.kompose.service: spline
status:
loadBalancer: {}
apiVersion: v1
kind: Service
metadata:
annotations:
kompose.cmd: kompose convert
kompose.version: 1.21.0 (992df58d8)
creationTimestamp: null
labels:
io.kompose.service: ui
name: spline-ui
namespace: dataservice
spec:
ports:

name: "8080"
port: 8080
targetPort: 8080
selector:
io.kompose.service: ui
status:
loadBalancer: {}

@ankit302 ankit302 added the bug label Jun 29, 2020
@wajda
Copy link
Contributor

wajda commented Jun 29, 2020

Answered here - #743 (comment)

@wajda wajda closed this as completed Jun 29, 2020
@wajda wajda removed the bug label Jun 29, 2020
@ankit302
Copy link
Author

ankit302 commented Jun 29, 2020

Hi @wajda ,

when i'm trying to access the endpoint (http://spline:9090/consumer), getting below logs in spline gateway rest-server;

13:26:06.868 [http-nio-8080-exec-1] INFO  o.s.web.servlet.DispatcherServlet - Completed initialization in 94 ms
13:43:10.968 [http-nio-8080-exec-3] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:44:43.722 [http-nio-8080-exec-4] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:44:55.475 [http-nio-8080-exec-5] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:45:19.750 [http-nio-8080-exec-6] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:45:58.540 [http-nio-8080-exec-7] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:48:46.892 [http-nio-8080-exec-8] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:48:55.867 [http-nio-8080-exec-10] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:49:25.673 [http-nio-8080-exec-1] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:49:44.723 [http-nio-8080-exec-3] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:50:10.287 [http-nio-8080-exec-4] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /producer
13:50:48.994 [http-nio-8080-exec-6] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer

how i can verify that jsp of consumer & producer is present in spline gateway rest-server

Logs of spline gatewat rest server:-

Init DB ....
DONE
29-Jun-2020 06:24:00.932 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.27
29-Jun-2020 06:24:00.942 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Oct 7 2019 09:57:22 UTC
29-Jun-2020 06:24:00.942 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.27.0
29-Jun-2020 06:24:00.943 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
29-Jun-2020 06:24:00.943 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            4.15.0-1083-azure
29-Jun-2020 06:24:00.944 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
29-Jun-2020 06:24:00.945 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-1.8.0-amazon-corretto/jre
29-Jun-2020 06:24:00.945 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_232-b09
29-Jun-2020 06:24:00.945 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Amazon.com Inc.
29-Jun-2020 06:24:00.945 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /usr/local/tomcat
29-Jun-2020 06:24:00.946 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /usr/local/tomcat
29-Jun-2020 06:24:00.947 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties
29-Jun-2020 06:24:00.947 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
29-Jun-2020 06:24:00.948 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
29-Jun-2020 06:24:00.949 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
29-Jun-2020 06:24:00.950 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
29-Jun-2020 06:24:00.950 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsecurerandom.source=file:/dev/./urandom
29-Jun-2020 06:24:00.950 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.security.egd=file:/dev/./urandom
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/usr/local/tomcat
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/usr/local/tomcat
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/usr/local/tomcat/temp
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3].
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
29-Jun-2020 06:24:00.951 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
29-Jun-2020 06:24:00.956 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
29-Jun-2020 06:24:01.218 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
29-Jun-2020 06:24:01.237 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
29-Jun-2020 06:24:01.241 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [500] milliseconds
29-Jun-2020 06:24:01.263 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
29-Jun-2020 06:24:01.263 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.27]
29-Jun-2020 06:24:01.285 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/ROOT.war]
29-Jun-2020 06:24:07.140 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
06:24:07.148 [main] INFO  o.s.web.context.ContextLoader - Root WebApplicationContext: initialization started
06:24:07.788 [main] INFO  z.c.a.s.p.ArangoRepoConfig$$EnhancerBySpringCGLIB$$cd2ea4ca - Connecting to arangodb://arangodb:8529/spline
06:24:08.146 [main] INFO  o.s.web.context.ContextLoader - Root WebApplicationContext initialized in 995 ms
06:24:08.160 [main] INFO  o.s.web.servlet.DispatcherServlet - Initializing Servlet 'producerDispatcher'
06:24:08.297 [main] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'producerRESTConfig' of type [za.co.absa.spline.producer.rest.ProducerRESTConfig$$EnhancerBySpringCGLIB$$adeb6747] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
06:24:09.438 [main] INFO  o.s.web.servlet.DispatcherServlet - Completed initialization in 1277 ms
06:24:09.438 [main] INFO  o.s.web.servlet.DispatcherServlet - Initializing Servlet 'consumerDispatcher'
06:24:09.473 [main] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'consumerRESTConfig' of type [za.co.absa.spline.consumer.rest.ConsumerRESTConfig$$EnhancerBySpringCGLIB$$1052080f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
06:24:09.584 [main] INFO  o.s.web.servlet.DispatcherServlet - Completed initialization in 146 ms
29-Jun-2020 06:24:09.596 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/usr/local/tomcat/webapps/ROOT.war] has finished in [8,311] ms
29-Jun-2020 06:24:09.599 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
29-Jun-2020 06:24:09.627 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
29-Jun-2020 06:24:09.639 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [8,398] milliseconds
13:26:06.773 [http-nio-8080-exec-1] INFO  o.s.web.servlet.DispatcherServlet - Initializing Servlet 'RootDispatcher'
13:26:06.868 [http-nio-8080-exec-1] INFO  o.s.web.servlet.DispatcherServlet - Completed initialization in 94 ms
**13:43:10.968 [http-nio-8080-exec-3] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:44:43.722 [http-nio-8080-exec-4] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:44:55.475 [http-nio-8080-exec-5] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:45:19.750 [http-nio-8080-exec-6] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:45:58.540 [http-nio-8080-exec-7] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:48:46.892 [http-nio-8080-exec-8] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:48:55.867 [http-nio-8080-exec-10] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:49:25.673 [http-nio-8080-exec-1] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:49:44.723 [http-nio-8080-exec-3] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
13:50:10.287 [http-nio-8080-exec-4] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /producer
13:50:48.994 [http-nio-8080-exec-6] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer
14:11:05.963 [http-nio-8080-exec-1] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /consumer**

@wajda
Copy link
Contributor

wajda commented Jun 29, 2020

@ankit302
Copy link
Author

Hi @wajda ,

I even tried to setup on docker environment, with the latest version of spline, arangodb image from docker hub, But issue persist.

It appears to be an issue with the image;

Used docker compose file from github;
https://raw.githubusercontent.com/AbsaOSS/spline/develop/docker-compose.yml.

ankit@dockervm:~$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
27010ecc9c61 absaoss/spline-web-client "catalina.sh run" 3 hours ago Up 3 hours 8009/tcp, 0.0.0.0:8080->8080/tcp ankit_ui_1
99c0a5d6108d absaoss/spline-rest-server "bash -c '\n until c…" 3 hours ago Up 3 hours 8009/tcp, 0.0.0.0:9090->8080/tcp ankit_spline_1
8c3c24d580de arangodb "/entrypoint.sh aran…" 3 hours ago Up 3 hours 0.0.0.0:8529->8529/tcp ankit_arangodb_1

When tried to access the spline.consumer.url using curl (curl http://localhost:8080/consumer)

29-Jun-2020 15:14:14.089 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
29-Jun-2020 15:14:14.101 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
29-Jun-2020 15:14:14.104 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [7,848] milliseconds
15:18:07.787 [http-nio-8080-exec-1] WARN o.s.web.servlet.PageNotFound - No mapping for GET /consumer
15:26:00.464 [http-nio-8080-exec-2] WARN o.s.web.servlet.PageNotFound - No mapping for GET /producer

@wajda
Copy link
Contributor

wajda commented Jun 30, 2020

You are trying a wrong URL

http://localhost:8080/consumer -- this resource does not exist
http://localhost:9090/consumer/execution-events -- this one does

@dhiraj-raj
Copy link

Hi @wajda we tried this URL also i.e. http://localhost:9090/consumer/execution-events , but Spline-UI shows same error message as indicated above.

@wajda
Copy link
Contributor

wajda commented Jun 30, 2020

I have answered it about 3 times already - the consumer REST API URL has to be accessible from the client browser. If Spine UI says "Code 0" it mean it cannot connect to that URL. Please double check your Spline setup.

@ankit302
Copy link
Author

HI Wajda,

i understand that, URL is not accessible from splineUI.

we have used same Dockercompose file to run spline WebUI, rest server & arangodb without any modification.
https://raw.githubusercontent.com/AbsaOSS/spline/develop/docker-compose.yml

Do you see ant issue with config parameters in docker compose file ?

Does any one else facing similar issue ?

@wajda
Copy link
Contributor

wajda commented Jun 30, 2020

Ah, that's a new piece of info. Seems like an issue with the Docker. Just tried our docker-compose.yml and the 'spline' container appeared to have connection issues. Re-opening the issue, although I have doubts that it's related to Spline, rather to a Docker network config.

@wajda
Copy link
Contributor

wajda commented Jul 1, 2020

I have just confirmed that it is indeed a particular docker setup issue that has nothing to do with Spline.
I've tested it on three PCs running Fedora, Ubuntu and MacOS, the same Dcoker version 19.03.8. Only on my Fedora PC I have this issue, on the other two laptops docker-compose run Spline with no issue, straight out of the box.
So please check your docker network configuration and consult with the Docker support.
I consider this issue closed.

@wajda wajda closed this as completed Jul 1, 2020
@wajda wajda added this to the 0.6.0 milestone Jul 1, 2020
wajda added a commit that referenced this issue Jul 1, 2020
* spline #744 Upgrade Spline version to 0.5.3

* spline #744 Add more logs to the docker-compose.yml
@zacayd zacayd mentioned this issue Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants