;t work for all properties. I think some
are only checked by the JVM at start-up.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] logging and admininstration
>Date: Tue, 19 Feb 2002 07:10:47 -0500
>
>
.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.ja
>va:513)
> at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
> at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
> at org.jboss.Main.(Main.java:182)
> at o
.jar in lib/ext?
Don't put it in the classpath, it can't see the rest of the
system from there, hence the other errors you report.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>CC: <[EMAIL PROTECTED]>
>Subject: RE:
rian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Monday, February 18, 2002 1:43 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] logging and admininstration
>
>
>Here's some short answers.
>
>1) Stop on error
>JBoss is designed to host many service
> > 2) Log4j
> > The best way to do logging for a bean (at the moment)
> > private static final Category log = Category.newInstance(MyClass.class);
> >
>
>The following accomplishes the same thing, and can be cut and pasted from
>one source to the next.
>
>private static final Category log =
>
[Guy Rouillier]
> > 2) Log4j
> > The best way to do logging for a bean (at the moment)
> > private static final Category log = Category.newInstance(MyClass.class);
> >
>
> The following accomplishes the same thing, and can be cut and pasted from
> one source to the next.
>
>private static fi
> 2) Log4j
> The best way to do logging for a bean (at the moment)
> private static final Category log = Category.newInstance(MyClass.class);
>
The following accomplishes the same thing, and can be cut and pasted from
one source to the next.
private static final Category log =
Category.getIns
here is no jar to
copy to lib/ext. what should we do in this case?
thanks
eric
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:43 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] logging and admininstration
H
ce
for this?
Thanks
Eric
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:43 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] logging and admininstration
Here's some short answers.
1) Stop on error
JBoss i
by developers when they should have been using jboss.jcml for
configuration.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: [JBoss-user] logging and admininstration
>Date: Mon, 18 Feb 2002 12:25:27 -0500
>
>Thre
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 beca
11 matches
Mail list logo