Vaadin with using Jetty Server -> ERROR: Jetty server existing - jetty

I recently started studying Vaadin. At the beginning I am using Vaadin 8 and have started a small Vaadin project in eclipse for practice purposes. I always started and opened this project via Jetty on my localhost:8080. That worked great for the first few days, but since yesterday
my localhost:8080 wants username and password at once and the application is no longer opening there.
The only difference is that the day before yesterday I installed an Oracle database (OracleXE 11 g) - could that have something to do with it?
Here is a snipppet if the error-message that I am getting:
Sep. 12, 2021 10:51:20 VORM. org.atmosphere.cpr.AtmosphereFramework addInterceptorToAllWrappers
INFORMATION: Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority BEFORE_DEFAULT
[INFO] Started o.e.j.m.p.JettyWebAppContext#60b616c8{/,file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/,AVAILABLE}{file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/}
[INFO] Jetty server exiting.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 42.520 s
[INFO] Finished at: 2021-09-12T10:51:20+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.3.9.v20160517:run (default-cli) on project VaadinFirstSteps: Failure: Address already in use: bind -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Anyone know how to get Vaadin up and running again? I am grateful fur any help,
Zrebna :)

"Failure: Address already in use: bind" means that you are trying to start web application server on localhost port 8080 while there is already web application server running and owning that port. Hence new one cannot be started.
You need to check you processes already running and kill the old one.

Related

Dataflow job fails due to inability to read ojdbc driver from the Google Cloud Storage

I have a working GCP account and trying to run a dataflow job which ingest data from on-prem oracle to BigQuery using cloud SDK. I have installed the versioned cloud SDK tool and configured my account. I want to use the JDBCToBigQuery template.
Tried executing:
mvn compile exec:java -Dexec.mainClass=com.google.cloud.teleport.templates.JdbcToBigQuery -Dexec.cleanupDaemonThreads=false -Dexec.args="--driverJars=gs://********/jars/ojdbc8-8.0.17.jar --driverClassName=oracle.jdbc.OracleDriver --connectionURL=***** --query='select * from schema.users' --outputTable= ***** --bigQueryLoadingTemporaryDirectory=***** --username=***** --password=****** --project=***** --runner=DirectRunner"
It throws this error:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:24 min
[INFO] Finished at: 2019-11-21T23:02:45-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project google-cloud-teleport-java: An exception occured while executing the Java class. org.apache.beam.sdk.util.UserCodeException: java.lang.RuntimeException: java.io.IOException: Error reading gs://********/jars/ojdbc8-8.0.17.jar: connect timed out -> [Help 1]
I am working behind the company's proxy but have taken care of that by incorporating proxy settings.
Trying to troubleshoot this error, can anyone help out in this?
P.S.: Newbie to google cloud services

WSO2 CLI tools Unable to connect to host

I'm just using WSO2 micro intregrator and having issue with CLI tools, mi: Unable to connect to host
i run the WSO2 Micro Integrator on a VM using command :
$micro-integrator.bat -DenableManagementApi
and i wanna Get information about one or more Carbon Apps using :
$mi show carbonapp --verbose
[INFO] Executed ManagementCLI (mi) on Thu, 25 Jul 2019 14:59:47 +07
[INFO] Show Carbon app called
[INFO] URL: https://localhost:9165/management/applications
$mi: Unable to connect to host
mi init --verbose
[INFO] Executed ManagementCLI (mi) on Thu, 25 Jul 2019 15:01:52 +07
[INFO] Init called
Enter following parameters to configure the cli
Host name(default localhost): localhost
Port number(default 9164): 9165
CLI configuration is successful
i expect Get information about one or more Carbon Apps
Can you check the port ManagementApi is running. By default it is 9164 since you have mentioned as 9165, is MI started with offset 11 ( default offset 10 )? Else you may find the offset in carbon.xml.
Following logs will be printed in console when MI is started with Management Api
[2019-07-28 21:05:05,318] [micro-integrator] INFO - PassThroughListeningIOReactorManager Pass-through EI_INTERNAL_HTTPS_INBOUND_ENDPOINT Listener started on 0.0.0.0:9164
Here "9164" is the port of it. Please make sure that it is started and the port it is started is same as what you define in init.

Django API returns 404 error but only 30% of the time. How to identify error in Docker setup?

I have a script that hits a simple API on all my servers every hour to ensure they are functioning properly. My newest server isn't using my normal stack, so I suspect I've configured it improperly. It is currently returning occasional 404 errors to the logging script.
Server Config
Ubuntu, Nginx, PostgreSQL, Supervisor;
Running a Docker container with Django/Wagtail and Gunicorn.
Looks fine when I visit in webbrowser, but my script logged four 404s in the last 12 hours.
My supervisor log shows the 404s but doesn't provide any additional useful information:
[2018-07-16 20:22:35 +0000] [9] [INFO] Booting worker with pid: 9
[2018-07-16 20:22:35 +0000] [10] [INFO] Booting worker with pid: 10
[2018-07-16 20:22:35 +0000] [11] [INFO] Booting worker with pid: 11
Not Found: /_server_health/
Not Found: /_server_health/
Not Found: /_server_health/
There is no relevant information captured in the Nginx log.
Can anyone recommend any steps I can take to gather further information? Or does this fit the pattern of any known problematic server configs?
Edit: It looks like Wagtail is sometimes causing the 404: "Raised by: wagtail.core.views.serve"
Maybe a problem in my urls.py? Should this be configured differently for Wagtail?
url(r'^_server_health$', status_api),

Teamcity Build Error

When I run my Automation test script locally its working absolutely fine without any error message. But when I run on server, I can see that its working fine, but at the end, instead of Pass status, it shows test failure.
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 282.662 sec <<<
FAILURE!
allNumbersEditorsDraws(NumbersEditor.TestSuiteAdmin) Time elapsed: 0.047 sec <
<< FAILURE!
org.openqa.selenium.remote.SessionNotFoundException: Session ID is null. Using WebDriver after calling quit()?
Build info: version: '2.53.1', revision: 'a36b8b1cd5757287168e54b817830adce9b0158d', time: '2016-06-30 19:26:09'
System info: host: 'W-SL-DEVBUILD1', ip: '10.130.32.68', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_131'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:134)
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:82)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:644)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:363)
at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:500)
at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:355)
at NumbersEditor.LoginPage.loginAdmin(LoginPage.java:32)
at NumbersEditor.TestSuiteAdmin.allNumbersEditorsDraws(TestSuiteAdmin.java:18)
Results :
Failed tests: allNumbersEditorsDraws(NumbersEditor.TestSuiteAdmin): Session ID is null. Using WebDriver after calling quit()?(..)
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:50 min
[INFO] Finished at: 2017-06-26T10:41:18+01:00
[INFO] Final Memory: 13M/328M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
12.4:test (default-test) on project NumbersEditor: There are test failures.
[ERROR]
[ERROR] Please refer to C:\BuildAgent\work\f3b21200f1a5caf2\Automation\target\su
refire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
This is a common issue when you are doing UI test with Selenium on virtual machines.
When you run your tests, your session should be active. So, if you are connected in remote desktop on the VM, the current script is working, but, if you exit, the current session disapear.
In order to make it works, you should leave the current remote session with a script :
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (
%windir%\System32\tscon.exe %%s /dest:console
)

hue installation error on AWS EC2

Hello I am trying to install Hue on AWS EC2 instance.
Following below link.
https://github.com/cloudera/hue
While doing step make apps I am getting below error.
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message:
Detected JDK Version: 1.6.0-30 is not in the allowed range [1.7.0,1.7.1000].
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.717s
[INFO] Finished at: Sun Mar 09 13:18:59 EDT 2014
[INFO] Final Memory: 5M/25M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce (default) on project hue-parent: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I have java version
java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Additional information can be provided. Thanks for your help.
You can also remove the JDK 7 check by editing:
vim maven/pom.xml
And replacing the '7' by '6':
<javaVersion>1.7</javaVersion>
<sourceJavaVersion>1.7</sourceJavaVersion>
<targetJavaVersion>1.7</targetJavaVersion>
(obviously you should it might be better to make sure Java 7 is the default if you plan to use 7)
It looks like you have another Java version in your system too. Based on what your installation says:
Detected JDK Version: 1.6.0-30
Make sure your JAVA_HOME variable points to the home of your Java 1.7 installation.