This is not related to JBoss.
But I've a quick look into it but did not find such config.
You should visit the MyWMS documentation and if you did not find an answer there is a mail address at the page firstname.lastname@example.org where you can ask.
Thank you for your answer.
I couldnt find anything in the documentation I wrote the same question to email@example.com but I didn't get an answer.
So far no one is wiling to help and I bet it is something relatevly simple.
I found out that the client is seraching for the server at 127.0.0.0 (localhost), because when I use the -b 0.0.0.0 key to start jboss, che client cant find it.
Can I trick it somehow from the hosts file in System32 to redirect it?
One lead that I found in the document is this:
Modules of the LOS Rich Client:
- Login functionality, connection to the server application through JNDI lookup and remote method invocation, generic object browser
However I can't understand how this works.
Using -b 0.0.0.0 on your server was the correct thing to do.
However, on your client PC, you need to point it at the server's address. Therefore, on your server use the ipconfig command to discover it's network address and use this value on the client instead of 127.0.0.1 or localhost.
127.0.0.1 (aka localhost) is a special network address private to every computer which basically references itself. You should not touch the hosts file and attempt to change this because it will break many things.
Thank you for your answer. Thant is exactly what im trying to do, but I cant find where to change the 127.0.0.1(localhost) to my server IP which is 192.168.6.100 and one other thing shouldn't I point the port too because Jboss is accessable at 192.168.6.100:8080?
Here is a link with only the client in a .rar filе. If anyone can tell me in which file I should change I will be extremely gratefull (I can offer a few Bitcoins in gratitude).
The whole program is called myWms and can be found here:
I dont really understand what you mean....
As far as I know you can bind jboss to ip address in 3 ways : (I assume you use standalone)
1. run standalone with parameter -b ipadress
./standalone.sh -b 192.168.6.100
2. change your standalone.xml
but this way is not to recommended
3. add following lines in the configuration file in bin/standalone.conf property file
When you run standalone, there should be a line like the following on the console. What IP address is given on your output?
07:24:53,491 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--192.168.6.100-8080
Hope this can help you....
Finally, dudes you are GOLD! (Stephen Coy and Tan Mariani)
It is a combination of both your answers, I tryed changing the IP in the jndi.properties file a week ago but it didnt work, because I was starting the server with -b 0.0.0.0.
And you were right I shouldn't have cared about the port.
Now I don'y know to who should I give the corect answer, I'll leave that up to you!
Thank you dudes, you saved me tons of headaches.
I don't understant why -b 0.0.0.0 isn't working. If you start the server with this option check whether you can access via browser from a different machine with 192.168.6.100:8080 it should work.
If you start with the -b option you do not need to hide JBoss, the 8080 port is only for applications deployed on JBoss and your app is using RMI only right?
So you can't access the application via 8080.
The management http interface is available on port 9990 but as you don't change the interface (-bmanagement x.x.x.x) it should run on localhost and not accessible for others.
If you don't want the port 8080 opened you might remove all services listen on that port from your standalone.xml, but this is only possible if you do not need the http access.
The -b options works from 3.2.x up through 6.1.x. What we need to see is the console out, starting from the run command that was entered, to better determine what is going on. Also, what operating system are you ruinning on (my colleagues in the mainframe department had some issues with -b 0.0.0.0 not binding correctly, thought I don't recall the exact details)
I'm sorry for the late answer.
I am testing it on my PC so im using Windows7 64bit.
But wheather im using -b 0.0.0.0 or -b 184.108.40.206 doesn't really matter to me, I leave that yo tou JBOSS gurus I'm happy that now everything is working and hopefully the students will be able to use it next semester.
My only worry is security, our network is not accessable from the outside, but I still want to hide the JBOSS server from port 8080 оr any other port. Isn't there a way to set JBOSS so you can't access the contents visible on 8080 unless u have some pass and a user.