1 Reply Latest reply on Nov 16, 2005 8:26 PM by Adrian Brock

    initial startup issues

    Jason Oh Newbie

      hi folks,
      i'm attempting to install and run the default configuration of jboss 4.0.3SP1 but am running into issues that i've explained in my other post in the "beginner's corner" (to which i've not received any satisfactory answer and hence my presence here).

      to start, i'm running jdk 1.5.0_05 on suse linux 2.4.21. after unpacking and installing the specified release, with no configuration changes, i execute bin/run.sh with no arguments. it begins, but almost immediately throws an Exception, specifically that port 8083 is already in use. fine, it is in use by another application but that fact cannot be changed. how can one force jboss to run on another port? i've looked at the documentation and the forums, but see no workaround for this.

      next, after binding the mail service, i get an ExportException, specifically, another port in use exception, this time 1098. that port, 1098, is neither in use before nor after i execute the run.sh script (verified by netstat), so i have no idea what this is truly complaining about. i see on
      http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossInstallation
      , subsection "Notes on default ports for JBoss 4.0.3 (applies to others)", that it mentions port 1098, but it definitely doesn't fit the bill (there are no messaging services running on this server). in addition, i've seen that there have been several other indications of similar problems ( http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67937 ) but none of the solutions apply or are simply invalid for this current release.

      after the script finishes running, the deployment is crippled and the jmx-console obviously not accessible.

      any insight into this problem would be greatly appreciated. i believe i've stated the problem clearly enough, but if i haven't, let me know what other details you might require.