Three questions:
1. Typically, we bring up the application server and eyeball the output for
obvious errors, which are one of three typically:
- Cannot bind to the required port, usually because a jboss instance
is already running
- Cannot create one or more db pools, usually because the database
is down
- One or more errors deploying the beans, including verifier
problems.
If we see an error, we fix it and restart. However, in production, we want
to automatically bring up the server, detect problems, and exit with an
error code. Is there a straightforward way of doing this?2. Logging with log4j. Log4j on its own is easy. However, I'm still frustrated getting my beans to log using log4j with jboss. Scanning the forum, it seems there are a LOT of people having the same problem. We are probably all doing the same thing wrong, but it's not clear exactly what the remedy is. Can someone please tell me? I would think I could get the latest log4j and log4-core jars, put them in the classpath, and roll, but this is not the case. Please let me know what I need to do? 3. We have a couple of system properties (-D flag) as well as classpath extensions to make when running jboss. We currently have hacked run.bat, but I don't think this is a great solution. What is the sanctioned way in jboss for dealing with this? Thanks Eric Kaplan Armanta, Inc. 55 Madison Ave. Morristown, NJ 07960 Phone: (973) 326-9600
winmail.dat
Description: application/ms-tnef
