I got an issue with my environment I guess.
I use Eclipse Photon and WildFly 11 for Maven Projects.
The issue is when I start my WildFly server on Eclipse. I wait few seconds then I have the following message :
19:46:06,398 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) started in 24044ms - Started 674 of 900 services (355 services are lazy, passive or on-demand)
But my server seems to not work correctly. I'll explain:
After I start the server and the message is displayed, I can access to localhost:8080/myproject but, when the timeout setting to start server is reach (450 seconds by default) the server stops. Like it wasn't fully started.
Furthermore, if I go to -> Servers -> WildFly 11 -> Server Details, I see the mention Not Connected and nothing else while I should get some folder like Attributes, Core Services, Deployments, etc.
I tried reinstall Eclipse, WildFly 11 and 13, and I tried with project in the server and with an empty server, with a new workspace... The issue is still there.
Has anyone ever had this concern or has any leads to solve it?
Related
Recently I've got a strange Wildfly bug where I can't start my server properly.
When I start the server empty I've got:
[org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full
14.0.0.Final (WildFly Core 6.0.1.Final) started in 3430ms - Started 306 of 527
services (321 services are lazy, passive or on-demand)
Which is pretty standard but even tho it says started in 3430ms when I go on my servers tab the server says [Starting, Synchronized] and the only option I have is to terminate it rather than restarting it. It also don't update my WEB content directly and I have to restart the server every single time when I make a slight change which is extremely time-consuming. I've tried so far:
deleted .eclipse, deleted eclipse-workplace, install new eclipse ide, install new JBoss tool (4.9 final), using new/different Wildfly.
And none of these solved the problem.
the only option I have is to terminate it rather than restarting it
This feature was removed from Jboss Tools at version 4.5 when the direct toolbar buttons were removed. See https://issues.jboss.org/browse/JBIDE-24528
You can try to downgrade Jboss Tools
It also don't update my WEB content directly and I have to restart the
server every single time when I make a slight change
Check you have added the resources on the server. Right click on server -> Add and remove...
Once a resource is added wildfly should update automatically your changes, also you can right click on the resource and do a manual incremental or full publish.
Hope it helps.
After fixing "Port Offset" it works. Instead of offset 0 the field had the port number 8080. I had to recreate the server configuration in the server view (New / Server).
I have written an application on REST API's and deployed that on tomcat 8.0.36. When I start the application from eclipse it gives me a timeout message after 45 seconds "Server Tomcat v8.0 Server at localhost was unable to start within 45 seconds. If the server requires more time, try increasing the timeout in the server editor."
I have done all the troubleshooting stuff:
1) Deleted the server from the server perspective and re-added the server and tried to re-deploy it
2) get the same message as above.
3) I have tried by launching the tomcat without the application deployed it starts .
Regards
Vilas
To increase the tomcat boot time, you must follow the following steps:
Launch Eclipse
On Servers view, double click on you tomcat server configuration
Find the option Timeouts, this is in the top right of editor
Increase the time, for example 120.
Everytime i create new JBoss EAP7 with MySQL Persistent Type Applications, i'm always receiving Error Deployment Failed for the MySQL Pod. the log says like this
--> Scaling xxx-mysql-2 to 1
--> Waiting up to 10m0s for pods in deployment xxx-mysql-2 to become ready
W0326 15:34:23.420524 1 reflector.go:330] github.com/openshift/origin/pkg/deploy/strategy/support/lifecycle.go:468:
watch of *api.Pod ended with: too old resource version: 1042923611 (1042946447)
error: update acceptor rejected xxx-mysql-2: pods for deployment "xxx-mysql-2" took longer than 600 seconds to become ready
Is this openshift bugs or Perhaps i have made mistakes?
I have an application that successfully deploys to Weblogic Server. I've configured cluster and wanted to start this application on a cluster, but sometimes I am facing such a situation.
1st node - application runs and there isn't any errors.
2st node - shows me 404 error.
How is that possible that 1 application can successfully work on 1 node and show 404 error on the second one?
Sorry for late answer and thanks to #Kyouma.
The problem was in JMS server.
I had such a configuration:
1 Machine that has 2 servers united in a cluster.
JMS Server that was targeted to 1 server from the cluster.
JMS Module that was targeted to the same server.
The problem was, that I had *.war file configured to both servers in a cluster.
When the first server was starting - everything was fine, because during Topic bean creation he could find those topics. But the second server couldn't find them, because JMS server in general was not in Running state.
So the solution is:
1. Have no *.war files in the Deployment menu.
2. Start all servers in a cluster.
3. Install *.war file in the Deployment menu.
E.R. Application have been deployed.
I am trying to deploy the hawtio-default-offline-1.3.1.war (into JBoss EAP 6.2) and I see this message in the logs:
10:16:07,988 WARN [io.hawt.jvm.local.JVMList] (ServerService Thread Pool -- 65) Local JVM discovery disabled as this JVM cannot access com.sun.tools.attach.VirtualMachine due to: com/sun/tools/attach/VirtualMachine
So I don't have a local tab when I start up hawtio. Is this OK? This is my local Windows laptop and I am deploying the hawtio WAR alongside my app WAR and I am launching it using the JBoss bat file. I do a jps and I can see the JBoss server running.
Appreciate any pointers, thanks!
Yes this is okay, the WARNING is only about the connect plugin, not being able to use the local discovery. You can always use remote discovery, also to connect to local.
But if you only need that hawtio application deployed in your EAP to manage and monitor whats running in the same JVM then this is no problem.
There is also a FAQ at hawtio about related to this.
http://hawt.io/faq/