I recently had to reinstall IntelliJ IDEA, and ever since then, I've been unable to run this one app that runs on Payara. I have Payara 5.2022.3 (full) installed and the project is using java 11.
This is the server log:
Artifact my_project-ear:ear exploded: Waiting for server connection to start artifact deployment…
Detected server admin port: 4848
Detected server http port: 8080
And then nothing happens.
And if I terminate the process I get a message:
Application Server was not connected before run configuration stop, reason: Unable to ping server at localhost:4848
Based on my observation it seems like a process starts running on port 4848 for a few seconds but then stops abruptly.
I checked the CrashDumps and here is the .dpm file in question.
https://drive.google.com/file/d/1AyLU2HOyXKxREjaDNyIU9eRYMnzaBspw/view?usp=sharing
I'd already tried:
Running it on a different port./ Checking if there was not a process blocking used ports.
"Renewing" the domain.xml in case it was corrupted somehow.
Using different JDK.
Reinstalling Windows
I'm positive there is no problem with the app's code (seen a friend run it on his computer today) and I also think no changes happened to the run/debug configuration or the payara and domain configuration ever since it was working before the IDEA reinstall.
(I'm also very new to payara, and software development in general, so I'm not quite as skilled in solving this kind of problem.)
Thank you for all your answers.
It looks like a bug in the Java version/vendor you are using which is causing the crash of the process. Updating to a more recent Java build or to a different JVM vendor should help.
I am trying to start a phantomjs node on a virtual machine to connect to my own computer which hosts the hub. I have gotten a generic node set up externally (5 instances of firefox, chrome and one instance of IE). When I try and set up a phantomjs node however, it registers fine from the command prompt, but when I go to the grid console, the following message is displayed:
DefaultRemoteProxy unknown version,Connect to failed: [myIp] Connection refused: connect
Does anyone have any experience with this?
Connection refused when phantomjs is run on different machine than selenium hub
Referenced this question... Basically had to add the IP of my node machine to the --webdriver param in the command line...
I am new to Mesos and just finished setting up mesos and along with zookeeper on my test server.
Unfortunately I keep getting this error message on my mesos console indicating i am unable to connect to mesos on port 5050 and can't seem to figure out why.
I have included the error in the screen shot below
The mesos log files doesn't point to why the error is showing either.
I resolved the problem by this:
./bin/mesos-master.sh --ip=x.x.x.x --work_dir=/var/lib/mesos --hostname=x.x.x.x
We can avoid this problem by starting mesos-master with following option:
--ip=xx.xx.xx.xx --hostname_lookup=false
I have resolved this problem. Open the web page in Chrome, and open the developer tool, you will see the chrome is accessing the web site with domain, in my case the domain name is "mesosphere", as there is no mesosphere in dns, so the accessing was failed.
I solved the problem by adding the mesosphere in the hosts file, C:/windows/system32/etc/hosts/
If you use the domain name for the Mesos cluster you must set the domain name in windows hosts.
There can be multiple issues here.
Is your mesos-master running and healthy ?
Has leader election process completed, if all is good.
Check if you are able to do
ping leader.mesos
If above ping doesn't work, that means leader has not been elected. First fix that.
I had this problem also. Luckily, I have a running mesos server also. So, I can compare the different between my demo and the running mesos server. I captured the packets between client and server in my demo. I found the explorer didn`t resend fresh request, only some keepalive packets.
but, when I catch the packets in the running mesos server, I found the explorer send get request frequently. like the image
I think, if you run some task or add some agent, maybe it will activate the explore to send request frequently. Then the "Failed to connect" will disappeared.
I was having the same issues and what fixed it for me was the zookeeper configuration. In my case I was using the EC2 public IP Address rather than the private one. Once I changed the /etc/mesos/zk file to zk://<private IP>:2181/mesos I was able to connect without the constant error messages. In other words, zookeeper was reporting to be running in one IP and mesos-master was trying to connect using a different IP.
My configuration was correct as suggested. But failed to start mesos-master service. But There is alternative way to start mesos-master node with exact same configuration. Commands to start mesos-master
$ cd /usr/sbin [or mesos_installation directory/bin]
$sudo ./mesos-master --work_dir=/var/lib/mesos --log_dir=/home/rajeev/logs/mesos/
Its start mesos-master service successfully for me.
I am new to Hadoop. Oracle VM with Hortonworks sandbox (OS Red Hat 64bit) with HDP 2.3.2 is up and running. When i am trying to test via http://192.168.56.101 i get the 502 proxy error.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server
I have done the same installation and configuration on both my pc and mac and i get the same error. I have tried the test from IE and chrome as well.
I also got same issue when I try it in another browser it worked, so you can try in different browser. And also increase your VMware allocated memory for hortonworks VM.
Click on machine tab of Horton sandbox virtual box running instance and click Reset. It worked for me.
Usually it happens when the Ambari is restarting or shutting down. Just wait for a few seconds and it should resolve.
You can also try to open it in incognito mode or clear the cookies.
To clear the cookies, for the chrome browser:
Click on i icon which is at the left side of URL
Click on Cookies
Remove all cookies one-by-one
It should solve.
I am running a small selenium project using grid setup. All is fine when I run locally which has the hub and the node running in the same machine. What I did next was kept the hub running in my local machine and tried running the test through teamcity. I presume that the test will run in one of the build agents. When I kick start the build job, I got the following exception. Not sure what the issue is.
Test(s) failed. System.Net.WebException : Unable to connect to the remote server ---->
System.Net.Sockets.SocketException : A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed
because connected host has failed to respond 192.168.6.121:80 at
System.Net.HttpWebRequest.GetResponse()
Also, the team city build agent IP is 192.168.7.132 whereas I am getting a message that it is unable to contact 192.168.6.121
Is there something happening which I am not aware of.
The selenium server is up and running in my local machine. and all is fine at the server end.
Any pointers will be much helpful