Port 1098 is taken

[kannaiyanbalaji]

Hi,

JBoss while starting looks for this rmi port. But in netstat it shows that 1098 connection is already established? Because of this server is not starting up at all... The exact message I get is:

java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

Can somebody help to fix this?

Thanks
Balaji

[nlsurfman]

On Windows XP type on a prompt: netstat -a -n -o
The output will include the Process ID. Use the task manager to find out what process that is....

[plnarayana]

How I tell Jboss server to use a different port
Thanks
LN

[subhash_bhushan]

Hi,

I too am a newbie to JBoss, but came across the answer to your question.

jboss-service.xml file, present in the conf directory of your server mode (Ex. default), has a section called JNDI. The ports have been specified there. You probably will be able to change the ports there.

Here is the listing that I have in jboss-service.xml:

<!-- ==================================================================== -->
 <!-- JNDI -->
 <!-- ==================================================================== -->

 <mbean code="org.jboss.naming.NamingService"
 name="jboss:service=Naming"
 xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
 <!-- The call by value mode. true if all lookups are unmarshalled using
 the caller's TCL, false if in VM lookups return the value by reference.
 -->
 <attribute name="CallByValue">false</attribute>
 <!-- The listening port for the bootstrap JNP service. Set this to -1
 to run the NamingService without the JNP invoker listening port.
 -->
 <attribute name="Port">1099</attribute>
 <!-- The bootstrap JNP server bind address. This also sets the default
 RMI service bind address. Empty == all addresses
 -->
 <attribute name="BindAddress">${jboss.bind.address}</attribute>
 <!-- The port of the RMI naming service, 0 == anonymous -->
 <attribute name="RmiPort">1098</attribute>
 <!-- The RMI service bind address. Empty == all addresses
 -->
 <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
 <!-- The thread pool service used to control the bootstrap lookups -->
 <depends optional-attribute-name="LookupPool"
 proxy-type="attribute">jboss.system:service=ThreadPool</depends>
 </mbean>

 <mbean code="org.jboss.naming.JNDIView"
 name="jboss:service=JNDIView"
 xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
 </mbean>

Regards,
Subhash Bhushan.

[rgrantitt]

Often Outlook will take this port prior to starting jboss. Shutdown Outlook, or reboot your computer without Outlook running on startup, start your jboss server first then start Outlook. If you are not running outlook on the same machine then I can't help you.

But I have run into this issue with outlook

[subhash_bhushan]

I encountered the same problem on my machine, and found that Oracle services were using the port 1098.
If you are using Oracle, then try stopping those services, and restarting jboss.

Regards,
Subhash Bhushan.

[ntableman]

I am having the problem as well in Windows 2000 pro and XP

here is my chain of events

I start JBoss

1098 is in use, by JBoss

I stop JBoss

1098 is NOT IN USE

I start JBoss, it fails telling me 109 is in use.

When I move it to 10098, it then get 8083 in use errors.

JBoss isnt cleaning this up.

[drhok]

"kannaiyanbalaji" wrote:

java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

You don't need to move JBoss to a different port. It is sufficient and maybe even better to reserve some ports using regedit. It is described here (in the reply by fbiaggi):

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=64248

Port range 1098-1099 works for me.

[anilit99]

There is a very quick solution to this.
In the server/xxx/conf directory there is jboss-service.xml
Search for the tag: ServiceBindingManager.
Now Uncomment the whole mbean. Opposite to serverName you can find ports-01. In most of the cases it can remain the same.

Just restart the server. If you are interested you can open and see the sample-bindings.xml where all the ports are configured. This is a fail proof way to get over the ports problem.

thanks
Anil.

[jasonlevinsohn]

Hello everyone,

This would be my first post, but I found a solution I don't think anyone has tried yet.  For me the problem was that there was another process called alg.exe running using port 1098. It is a windows program which allows other clients needing ports to be able to have one dynamically in windows or something like that.  If you have that process running check the TCPViewer to see if it using that port and shut that thang down.  I hope this helps someone.

Cheers,

jason

[akayender]

Hi Everyone,

With EAP 5,  editing conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml file with respect to following element:

            <bean class="org.jboss.services.binding.ServiceBindingMetadata">

               <property name="serviceName">jboss:service=Naming</property>

               <property name="bindingName">RmiPort</property>

               <property name="port">1112</property>

               <property name="description">Socket Naming service uses to receive RMI requests from client proxies</property>

            </bean>

is the neat solution that I found. Bold number is what you need to change.

[wdfink]

Hi,

lot of answers... but

First what JBoss do you use,

JBoss4 => you need to activate the ServiceBindingManager within the server/.../conf/jboss-service.xml

you can use ports-0? configuration

JBoss5 => there is a active configuration you can use it, it will shift the ports wit an offset.

You should read http://community.jboss.org/wiki/ServiceBindingManager for detailed information.

[mcc99]

Just want to mention that the jboss-service.xml file needing editing in conf\ is in install_path\server\default\conf\  Be forewarned that port 1099 is also used by JNP.  Basically, search on '1099' in the file and then replace it with some port like '2000'.  Then find '1098' and replace it with a port like '2001'.  Doing exactly this worked for me, cleared up all my startup problems in one fell swoop.

[wdfink]

I recommend to use the binding manager, here all ports are changed with one configuration.

Editing different files will mess up and you have to edit the files each time if you install a newer JBoss version.