-
1. Re: Fresh install throws startup error
peterj Oct 9, 2006 11:59 AM (in response to stevetee)This class is located in the jboss-remoting.jar file, which should be in server/default/lib.
How did you install JBoss? Via the installer jar file, or download and unzip the zip file? -
2. Re: Fresh install throws startup error
stevetee Oct 10, 2006 8:05 AM (in response to stevetee)I downloaded the installer zip file and unzipped into a local directory ( c:\app\jboss404).
I checked for jboss-remoting.jar and it is not located in the specified directory. There is a version of the jar in c:\app\jboss404\client however. Perhaps I have selected incorrect options during the install process.
Should I reinstall from scratch and specify some paticular option or can I copy the jar from /client to /server/default/lib.
Steve -
3. Re: Fresh install throws startup error
peterj Oct 10, 2006 10:53 AM (in response to stevetee)I once again downloaded the jboss-4.0.4.GA.zip file from the download site, and looked at and it contains the jboss-remoting.jar file in the server/all/lib and server/default/lib directories.
Should I reinstall from scratch and specify some paticular option or can I copy the jar from /client to /server/default/lib.
Uh, there are no installation options available when unzipping a zip file. -
4. Re: Fresh install throws startup error
stevetee Oct 10, 2006 12:51 PM (in response to stevetee)Mea Culpa.I had initially downloaded jboss-4.0.4.GA.zip and unzipped it into place before I saw the "patch1" label on the binary version. I deleted the install, downloaded jboss-4.0.4.GA-Patch1-installer.jar and ran the installer to completion. Only the zip version is left on my box hence the error.
The installer options I refer to are listed in InstallerSummary.html in the root directory.
I've uninstalled the offending copy and reinstalled again using the installer jar. I now have a jar file called in jboss-remoting-int.jar in server/default/lib.
The server boots without error and I can connect to the console. My install options were on both occasions : default, no isolation/call-by-value, full security on JMX/Web interfaces.
Thanks for the finger...