ok, so the jdk 1.4.1 i was using did cause a number of those issues it looks like. i've upgraded to 1.5.0_05 and now it looks a little better, but i'm still getting some exceptions.
the first exception deals with the port 8083 address being already used. it appears that it doesn't attempt to change ports in the event of this exception--how does one go about changing the server port setting? soon thereafter, i get a warning message: "15:48:16,345 WARN [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used." is this something that must be setup explicitly by me or is this a sign of a deeper problem? i get another port already in use exception for the rmi portion i believe, as it complains about port 1098. however, as indicated in my original post, the port is definitely -not- in use before nor after i execute run.sh. how is this to be resolved? that does it for the exceptions, but this is clearly a crippled startup and not usable. thanks for your input. cheers, jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907292#3907292 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907292 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
