I have a problem starting a wildfly app-server (wildfly-21.0.1) on a Solaris server (computer). I have read a lot of similar posts, but my problem seems to be different.
First, I make an SSH-tunnel in PuTTY:
My home machine is Windows, I connect to a remote Solaris server. I write the address of the server in a "Host name" field.
After this I create an SSH tunnel on a port of the server (I tried different and rare ones), so I put the port of the server I am connecting to in "Source port" field and the port of my personal machine (localhost:port_number) in the "Destination".
I have configured standalone.xml by changing on
<interface name="public">
<any-address/>
</interface>
and
<socket-binding name="http" port="${jboss.http.port:14384}"/>
I have configured PATH and JAVA_HOME on the server.
I start the server by
bash wildfly-21.0.1.Final/bin/standalone.sh
command.
After this I get the following error:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use /0.0.0.0:14384
It happens with any ports I tried, and I am sure that they aren't in use.
How can I fix this? Are there any known bugs in Wildfly that can cause this? Is it somehow connected with tunneling?
The discussion with #AndrewHenle made me think of ports usage in a tunneling procedure so I changed "Remote" parameter in "Tunnels" section on "Local" (since the destination is localhost). All the other parameters and values were left the same. Now everything works correctly, and WildFly doesn't recognise 14384 as a taken port.
Related
I need to shutdown port 1099 in Wildfly 10.1. This port normally used for remote JNDI/RMI and in Wildfly 10.1, the remote naming system has a
[security vulnerability][1].
The straightforward solution will be to configure a firewall to not allow traffic on 1099 port, but this is not acceptable by our client. I thought it possible to configure WF to not use remote JNDI/RMI but can't figure out how to configure it.
The JBoss documentation on Remote JNDI Interface says that you can deactivate the remote JNDI interface by executing the following command via CLI interface:
/subsystem=naming/service=remote-naming:remove
and it seems really stopping the service, but once you do server 'reload' the Wildfly resumes connection on the port 1099.
My team needs to see a web page I have built that I am hosting temporarily on my local windows 10 laptop using Wildfly 11.
I have changed the configuration standalone.xml from commented value to this
<interface name="public">
<!-- <inet-address value="${jboss.bind.address:127.0.0.1}"/>-->
<inet-address value="${jboss.bind.address:xx.xx.xxx.xxx}"/>
</interface>
Where xxx is equal to my ip address as determined from my internet provider's control page. I can ping that address from any of my local machines and my co-workers can also ping the address.
However, when I go to run with this value in the xml, I get the error:
Failed to start service org.wildfly.network.interface.public: org.jboss.msc.service.StartException in service org.wildfly.network.interface.public: WFLYSRV0082: failed to resolve interface public
What else do I need to do to enable access to the port? Thank you in advance for your help.
If your "xx.xx.xxx.xxx" is not the IP number of an interface on your machine, then you won't be able to bind to it. You can only bind to an interface that is actually present on the host. Typically the IP number of your machine, as seen from the public Internet, will not be the same as an IP number on the machine itself. You need to bind your HTTP server to the machine's real IP number (not localhost, 127.0.0.1, but the IP corresponding to some real network connection -- Ethernet, Wifi, whatever) and you need to configure your Internet router to forward packets addressed to port 8080 to the IP number of your wildfly host.
I would think that, if your co-workers are on the same site as you, they would have access to your machine without going through the public Internet. In that case, all you need to do is to bind the port to the (non-localhost) IP number of your machine, and have your colleagues use that IP number. You might also need to configure any firewall you have -- either on your wildfly host or your router -- to allow access to port 8080.
I would recommend that you run Wildfly on the command line with something like:
bin\standalone.bat -b 0.0.0.0
This will have Wildfly bind to all available interfaces. For testing this should be safe - it should be ok to bind to more than on interface. You will not need any changes in standalone.xml.
It's my first time deploying apps into web, I've successfully configured ubuntu 14.04 on server, installed java, placed Jboss 8.1.0.Final there.
I'v made also wildfly service. But the problem is that I don't know how to set jboss to start on my default address. For example I have vps555111.ovh.net adress how can I make it to start on that address?
/edit I figured it out how to set it to start it on my address but there's another problem - I was fallowing this tutorial http://www.itbuzzpress.com/wildfly-8-administration/getting-started-with-wildfly-8.html
and when I'm starting it as service it starts on 127.0.0.1:8080 address, anyone?
You can edit you standalone.xml file find the public interface:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
And replace 127.0.0.1 with the IP Address you need or 0.0.0.0
Centos 6.5
JBoss 7.1.1.Final
starting jboss as ./standalone.sh
When I go to localhost:8080 there is jboss, nice and happy
When I go to 192.168.111.222:8080 I get a 404 page not found error
This is problematic.
I have looked at other questions here that have advocated the following
./standalone.sh -b 0.0.0.0
This gives an error. It says the address is already in use.
I have tried
./standalone.sh -b 192.168.111.222
This doesn't work either.Same error as above. I have checked each time to see if there is another jboss process running out there and the answer is no.
I have tried modifying the jboss/standalone/configuration/standalone.xml interfaces to accept all connections. That didn't work either
No matter what I do, it always says:
Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
and going to ipaddr:8080 doesn't work, but localhost:8080 does work.
I saw one thread recommend modifying your hosts file to point your ip address at local host: I already have an entry there pointing my ip address at a domain name (which also doesn't work)
Other services on my machine work just fine, able to reach addresses whether I use localhost or specify the IP address, so this seems to be a jboss specific problem.
How do I fix this? I haven't used jboss before and I'm starting to see why.
There is probably some other process listening on port 8080. Try to find the process by
netstat -tulpn | grep 8080
You can simply change the AS7 port numbers by setting port-offset. Start JBoss AS7 like this:
./standalone.sh -b 0.0.0.0 -Djboss.socket.binding.port-offset=150
The web port will be 8230 in this case. (i.e. you'll use 192.168.111.222:8230 in the browser).
This may have been addressed prior, but I don't see a question specifically from this problem.
I'm trying to run 3 separate instances of JBoss as5 on my Win7 box. After starting the initial server the subsequent server startups complain:
13:57:59,659 ERROR [RmiInitialization]
java.rmi.server.ExportException: Port already in use: 0; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
which would indicate to me that the JVM_Bind port is not getting configured so it's defaulting to 0 ?
If so, where/how should this be defined in the JBoss infrastructure?
Looks like you are using the same bind address. Please do an nslookup or lsof to check your address and port. You could also set a port offset since your instances are running on the same machine.
Try stopping services in services.msc particular to other application servers like IBM Websphere.