I started WildFly 8.2. And can open http://localhost:8080/
Btw, on Ubuntu it was different port.
Anyway, I cant open localhost:8080/console or http://127.0.0.1:9990/console. Just nothing happen. I make same steps like on ubuntu. But on Win 7 I cant open admin page.
In console after start i see:
00:19:46,011 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-3) JBAS017519: Undertow HTTP listener default listening on
/127.0.0.1:8080
And...
00:19:46,344 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951:
Admin console listening on http://127.0.0.1:9990
What should i do?
Had the similar issue and it turns out that we tried to open admin console from IE8, which is the only browser was available on the server at the time. Looks like Wildfly 8.2 does not support IE8, which is make sense. Issue solved by using different browser.
Very often (in my practice) it happens because of one or both of the ports 8080 and 9990 are in use by other [java] processes.
Admin console is listening on port 9990, but it doesn't guarantee something else doesn't use it.
You can also use netstat -noa | find "port number" and then tasklist | findstr PID_of_process to check which process uses your ports.
To change port modify standalone.xml.
Related
So no idea why but tomcat7 seems to be just hanging. When I enter in localhost or my own ip that it's running on, it just sits there loading. And when doing 'startup' cmd in the tomcat directory, I get some random JSSE java error but then a log4J warning saying please initialize the log4j system properly.
Not sure why a WARN would prevent it from starting. I still see that tomcat service is listening on 443 and java is listening on 80.
Thanks.
We have a web application that's been running on Tomcat 7, we're moving to Tomcat 8 and are now depending on an internal microservice for the application as well. We use Netbeans.
I have made the necessary changes to configuration such that I can start the microservice app and then the web application on my machine from the command line. However, when I attempt to run the web app from within Netbeans, it tells me "Starting of Tomcat failed, the server port 8443 is already in use".
I don't know why that port is reported as in use when run from within Netbeans, but not if the same server with the same web application is run from the command line. Does anyone have any ideas on what to check?
A quick way to make progress is simply to use a port other than 8443. That won't necessarily resolve the problem you are experiencing, but it will circumvent it. To do that:
Stop Tomcat.
Pick a port other than 8443. I chose 8447.
Run the following command from the console to verify that port 8447 is not already being used:
netstat -aon | findstr 8447
That's the syntax for Windows - I think it is different on Linux. If nothing is displayed then 8447 is an available port. Otherwise keep picking different port numbers until you find one which is available.
Take a backup of server.xml which resides in directory {Tomcat dir}/conf (so you can regress if necessary).
Edit server.xml replacing all instances of 8443 with 8447, or whatever alternative port you chose, and save the file.
Start Tomcat. It will come up using port 8447 instead of 8443. You can verify that in Tomcat's log shown in NetBeans; look for the string https-openssl-apr-8447 to verify:
09-Jan-2018 02:07:26.279 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["http-nio-8080"] 09-Jan-2018 02:07:26.285 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["https-openssl-apr-8447"] 09-Jan-2018 02:07:26.290 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["ajp-nio-8009"] 09-Jan-2018 02:07:26.293 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in 2585 ms
You should now be able to test your web app. I just verified that this approach works using Tomcat 9 but I'm sure it would also work with Tomcat 8.
As a separate issue, once everything is working on port 8447, run netstat -aon | findstr 8443 to see if port 8443 is still being used while Tomcat is running. If so then (on Windows) get the PID of the process that is still using that port, and then lookup that PID on the Details tab of Task Manager. Here's a screenshot showing that in my case port 8447 was used by PID 2340 which was an instance of java.exe for Tomcat:
If none of that resolves anything:
Please advise which Operating System and which version of NetBeans are being used.
Add the relevant portion of Tomcat's log within NetBeans to your post.
I'm trying to run a dynamic web application from eclipse. I am using wildfly-10.0.0.Final as the server. I installed jboss tools.
As a test I created a dynamic web project called 'test', and added an index.html file in the WebContent directory with simply "hi" in p tags.
I start the server, which is running fine, hit 'Run On Server', and immediately get the error message:
http://localhost:8080/tester/index.html
Page load failed with error: The network connection was lost.
So far I have tried a full clean uninstall of eclipse, downloading wildly, adding jboss tools, and trying again, yet the same issue occurs. I have looked on the Eclipse forums, but they are of no help.
This problem occurred out of the blue.
wildfly admin works at the url:
http://127.0.0.1:9990/management
unable to access localhost:8080/
I tried this with intelliJ and am getting the same issue. Getting the error message from google:
The localhost page isn't working
localhost didn't send any data.
ERR_EMPTY_RESPONSE
03:49:12,347 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
03:49:12,671 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: /tester
03:49:12,688 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "tester.war" (runtime-name : "tester.war")
03:49:12,747 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
03:49:12,748 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
03:49:12,748 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 3163ms - Started 336 of 627 services (382 services are lazy, passive or on-demand)
Connected to server
Please check whether index.html is present in the list welcome file in web.xml
and right click the project name and select Run on server,
if u directly use run on server from index.html,it will try to run that page only not the entire application
i think that's it
Page load failed with error: The network connection was lost.
Your URL is pointing to the wrong port. You are saying that you are running Wildfly on port 9x. So you need to change the URL to point to 9080 instead of 8080. Go to the servers tab in Eclipse and change the HTTP port there to 9080.
I want to check some cli commands if they are valid from java. I cant use the config file I'm currently running on. Additionally I can't use a running Wildfly at all, since I would have to do reloads every now and then.
So I want to use offline-cli (cli with embedded server)
What I'm doing:
Connect to CLi using org.jboss.as.cli.scriptsupport.CLI
CLI cli = CLI.newInstance();
cli.connect("127.0.0.1",9990,"admin","admin".toCharArray());
starting an embedded server via cli.cmd
cli.cmd("embed-server --server-config=standalone.xml --std-out=discard");
But apart from me waiting forever for this command to finish (?) nothing happens.
One thing I noticed was, after deploying my application configuration-management.war to wildfly, state changes to "deployed". But then, a service fails to start. I did not pay much attention to it, because after that I can see an output from my application. Maybe this has something to do with it?
2016-06-29 15:59:55,333 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0021: Registered web context: /configuration
2016-06-29 15:59:55,364 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "configuration-management.war" with deployment "configuration-management.war"
2016-06-29 15:59:55,364 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."configuration-management.war".POST_MODULE
2016-06-29 16:00:29,530 INFO [stdout] (default task-1) this is mine!
All there is is just that little spinning wheel of death at the upper left corner of my mozilla firefox, indicating that I'm still waiting for a response.
Any hints?
When you start an embedded server it doesn't start any interfaces. This includes the management interface. It doesn't look like the script support allows for embedded CLI. You could file a feature request to support it though.
However you can use the CLI CommandContext API to achieve this.
final CommandContext commandContext = CommandContextFactory.getInstance().newCommandContext();
commandContext.handle("embed-server --jboss-home=/path/to/wildfly-10.0.0.Final");
commandContext.handle(":read-resource");
commandContext.handle("stop-embedded-server");
Do note some command, like module add, will require the jboss.home.dir system property to be set as well.
Hi I currently just setup JBOSS 6.3 EAP on AWS Ubuntu 14.04 Server. I also have Apache installed and running.
The AWS machine has all ports accessible for testing, and no firewall.
Lets say the public IP is: 2.2.2.2
Going to 2.2.2.2 on a web browser gets me to the Apache "It Works!" page.
In terms of JBoss, I run JBoss through standalone.sh.
I get the following lines in the output:
07:17:02,989 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://0.0.0.0:9990/management
07:17:02,990 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
07:17:02,990 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 3621ms - Started 151 of 189 services (56 services are lazy, passive or on-demand)
I try to visit 2.2.2.2:9990 and am met with a "Webpage not Available" prompt from chrome.
I tried running the command with the -b option: sudo standalone.sh -b 2.2.2.2
Then I get this error:
07:21:40,730 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72]
Does anyone know what I am doing wrong?
Try to bind on 0.0.0.0 instead of 2.2.2.2
The public IP addresses of EC2 instances are not visible on the instance itself. So, JBoss will not find the network interface with IP 2.2.2.2.
You can try this yourself by issuing the following command :
ifconfig -a
You must start your Jboss with
/opt/jboss/wildfly/bin/standalone.sh -b 0.0.0.0
Also, keep in mind that if you want to start the management console, you must
create an admin user
/opt/jboss/wildfly/bin/add-user.sh username password --silent
Start JBoss by telling him to start the management interface
/opt/jboss/wildfly/bin/standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0