JMXServerManager could not create the RMI local registry java.rmi.server.ExportException: Port already in use: xxxxx; java.net.BindException:Address already in use

Have you ever faced a situation like this before ? Once you start an instance on a particular WSO2 product and it shows an error message

JMXServerManager could not create the RMI local registry java.rmi.server.ExportException: Port already in use: xxxxx; java.net.BindException:Address already in use

The reason for this is there's a server which is already running on your default port or the port with offet. Or may be a process is already running for the previous time you started the server.



April 15, 2019

Solution

Here I'm going to use the 'ps' command to check out the every process on the system matches with the keyword I'm defining ( wso2) using grep command

ps -ef|grep wso2

output in the console

Here you can see the process id's where the word 'wso2' has been used within the system. The number of process may be increased if you run multiple wso2 products on the same machine. So follow below command to destroy or kill the processes you want.

kill -9 4714 4741

(4714 and 4741 are the process id's of the currently running processes.)

It's not necessary to destroy the process with grep command ( the below stated process with 4838 id ) since it's the one we initiate to search the processes.

That's it. Not you can up the server. If you got the same error message again, make sure to adjust a port offset in carbon.xml or just follow this procedure.

ORA-01950: no privileges on tablespace 'USERS'

If you are using oracle as database for configuring wso2 carbon based product or other product, you might get the following kind of error.

ORA-01950: no privileges on tablespace 'USERS'

This is occurred because the created user doesn't specify the 'USERS' tablespace.

In oracle each database user should have a default tablespace. By default, a perticular user has no quota on any tablespace in the database. As a solution we can specify an unlimited quota or limiting the allocation space to store a particular user's objects within the specified tablespace ( in this case 'USERS' )

Solution 

Go to database ( better to use GUI tool like sqlplus or sqldeveloper) and execute following command to allow unlimited quota for a particular tablespace.

ALTER USER <user> quota unlimited on <tablespace name>;


Ex - ALTER USER mydb quota unlimited on USERS;


or you can just limit the space to store objects by specifying a quota like below,

Ex - ALTER USER mydb quota 100M on USERS;