I'll answer my own post since I figured it out. Our server admin had installed latest Covalent ERS 2.4 on server since my prototyping last year. This apache 2.0 implementation has Tomcat bundled and part of this implementation was sitting on one of the ports that JMS/Jboss uses.
Strangely enough no error messages showed when the jboss was started on this server running Covalent. I guess it is a JMS binding that happens when the message queue is accessed, fired up through a jboss message on 1099 or something. I disabled the java stuff on the Covalent server and started jboss-3.2.3, using jboss's tomcat instead of covalent's, and everything started working. So if you see a "No Resource Manager found for xxx" message, connected with some JBoss network service, it may be due to a port binding that JBoss uses, taken by something else. My code still worked fine, and I wasn't quite as rusty at configuring jboss as I had thought. This port did not show up when I probed the ports so I am still not sure which one it was. This may be due to the fact that covalent is a type of "secure" server so may not answer port probes because of some security restriction. I apologize for the space I wasted with my original post. thx, neil View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849485#3849485 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849485 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
