Skip to main content

Tomcat fails to start due to Oracle XE blocking port 8080

Hi!

I have ran across many instances that during Java development, that the engineers cannot startup their Tomcat server because the port 8080 is used by some other resource.
It has been noticed that if Oracle XE was installed prior to tomcat, this has occurred.

Possible Options to resolve

1) Change the connector port from 8080 to some other available port in Tomcat
2) Changing the Oracle APEX port from 8080 to some other.

Method
Please note that you may use either of these 2 options but only one option is required to resolve this issue.
Most of the time it is very important to keep Tomcat port as 8080 so if that is the case you may use the 2 nd option.

Option 1) Changing Tomcat Port

go to "apache-tomcat-5.5.26\conf" inside tomcat installation folder.

Edit "server.xml" file

find Connector port="8080"
you may change 8080 with some other available port number.

Restart your tomcat.









Option 2) Changing Oracle APEX port

Logon to your XE database using sqlplus as system user

to check the existing port execute the following sql query

select dbms_xdb.gethttpport from dual;



you may see the result something similar

gethttpport

8080



Now let’s assume we are to change the port to 8081. Execute the following pl/sql anonymous block.



BEGIN

dbms_xdb.sethttpport('8081');
END;



You may check to verify the changes have been affected by:

select dbms_xdb.gethttpport from dual;
Labels:

Comments

Post a Comment

Popular posts from this blog

Oracle Enterprice Management Console

Hi - I got some useful tips regarding the management console. Speciall I used these commands when there was a requirement in changing my Server name. RECREATE EM REPOSITORY ====================== ################################################################################ # warning: 1. emca put database into quiesced mode, only DBA transaction # continues,the other waits, on production db there must be downtime # # 2. if some emca process fails, make a manual check and clean # - check OS processes,is java app running emca, RepManagerand,kill # # - is database in quiesced mode? # => SQL> select active_state from v$instance # => you can send # SQL> ALTER SYSTEM UNQUIESCED; # ################################################################################ emca help - see full syntax emctl stop dbconsole #To Drop emca -deconfig dbcontrol d...
Post a Comment
Read more
  RMAN Crosscheck commands derived  from different Oracle sources: To crosscheck all backups use: RMAN> CROSSCHECK BACKUP; To list any expired backups detected by the CROSSCHECK command use: RMAN> LIST EXPIRED BACKUP; To delete any expired backups detected by the CROSSCHECK command use: RMAN> DELETE EXPIRED BACKUP; To crosscheck all archive logs use: RMAN> CROSSCHECK ARCHIVELOG ALL; To list all expired archive logs detected by the CROSSCHECK command use: RMAN> LIST EXPIRED ARCHIVELOG ALL; To delete all expired archive logs detected by the CROSSCHECK command use: RMAN> DELETE EXPIRED ARCHIVELOG ALL; To crosscheck all datafile image copies use: RMAN> CROSSCHECK DATAFILECOPY ALL; To list expired datafile copies use: RMAN> LIST EXPIRED DATAFILECOPY ALL; To delete expired datafile copies use: RMAN> DELETE EXPIRED DATAFILECOPY ALL; To crosscheck all backups of the USERS tablespace use: RMAN> CROSSCHECK BACKUP OF TABLESPACE USERS; To list expired backups...
Post a Comment
Read more

Changing redo log Size

Redo logs cannot be resized on the fly we must drop and recreate them.This is the only method known to resize at the time this post is written. A database requires at least two groups of redo log files,regardless the number of the members. We cannot drop the redo log file if it's status is current or active. Initially the status need to be changed "inactive" before dropping the redo log member. Soon after a redo log member is drooped the file doesn't remove from the file system, instead it need to be separately removed from the file system. Step 1 : Check the Status of Redo Logfile    SQL>   select group#,sequence#,bytes,archived,status from v$log;      GROUP#        SEQUENCE#      BYTES    ARC STATUS ----------  ----------   ----------    -----  -------------          1          5  ...
Post a Comment
Read more