6:51 a.m.
Hi,
I've just implemented https://jira.jboss.org/jira/browse/JBAS-5240 using
java.lang.management.RuntimeMXBean.getInputArguments();
Example:
13:44:43,226 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh
-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
-Djava.endorsed.dirs=/home/galder/jboss/code/as/trunk/build/output/jboss-6.0.0.Alpha1/lib/endorsed
This is a much better solution than the one originally suggested in the
jira. This is also a much needed information from a support point of
view and the fact that from now on it's logged in boot.log reduces the
pieces of information we need to get from customer (before we needed
either console output to see these options or for the customer to spell
it out for us).
Hence, the following line in all of our run scripts should be removed as
it's obsolete:
echo " JAVA_OPTS: $JAVA_OPTS"
Thoughts?
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
6:55 a.m.
Please reply to this and not the previous email.
Galder Zamarreno wrote:
Hi,
I've just implemented https://jira.jboss.org/jira/browse/JBAS-5240 using
java.lang.management.RuntimeMXBean.getInputArguments();
Example:
13:44:43,226 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh
-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
-Djava.endorsed.dirs=/home/galder/jboss/code/as/trunk/build/output/jboss-6.0.0.Alpha1/lib/endorsed
This is a much better solution than the one originally suggested in the
jira. This is also a much needed information from a support point of
view and the fact that from now on it's logged in boot.log reduces the
pieces of information we need to get from customer (before we needed
either console output to see these options or for the customer to spell
it out for us).
Hence, the following line in all of our run scripts should be removed as
it's obsolete:
echo " JAVA_OPTS: $JAVA_OPTS"
Thoughts?
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
7:15 a.m.
On Wednesday 18 February 2009 07:55:29 Galder Zamarreno wrote:
> Hence, the following line in all of our run scripts should be
removed as
> it's obsolete:
>
> echo " JAVA_OPTS: $JAVA_OPTS"
>
> Thoughts?
Look good, Galder :)
But I would say that we should keep the 'echo' statement - so you don't have
to look in the boot.log to verify your settings.
Just my $0.02
Best regards,
Jesper
7:25 a.m.
I agree, add the new feature but keep the echo command, as well.
Some VMs might return different results from the MXBean.
Jesper Pedersen wrote:
On Wednesday 18 February 2009 07:55:29 Galder Zamarreno wrote:
>> Hence, the following line in all of our run scripts should be removed as
>> it's obsolete:
>>
>> echo " JAVA_OPTS: $JAVA_OPTS"
>>
>> Thoughts?
Look good, Galder :)
But I would say that we should keep the 'echo' statement - so you don't have
to look in the boot.log to verify your settings.
Just my $0.02
Best regards,
Jesper
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
8:34 a.m.
Dimitris Andreadis wrote:
I agree, add the new feature but keep the echo command, as well.
Some VMs might return different results from the MXBean.
Good point. Let's leave it then.
Jesper Pedersen wrote:
> On Wednesday 18 February 2009 07:55:29 Galder Zamarreno wrote:
>>> Hence, the following line in all of our run scripts should be
>>> removed as
>>> it's obsolete:
>>>
>>> echo " JAVA_OPTS: $JAVA_OPTS"
>>>
>>> Thoughts?
>
> Look good, Galder :)
>
> But I would say that we should keep the 'echo' statement - so you
> don't have to look in the boot.log to verify your settings.
>
> Just my $0.02
>
> Best regards,
> Jesper
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
8:30 a.m.
Jesper Pedersen wrote:
On Wednesday 18 February 2009 07:55:29 Galder Zamarreno wrote:
>> Hence, the following line in all of our run scripts should be removed as
>> it's obsolete:
>>
>> echo " JAVA_OPTS: $JAVA_OPTS"
>>
>> Thoughts?
Look good, Galder :)
But I would say that we should keep the 'echo' statement - so you don't have
to look in the boot.log to verify your settings.
Well, what ServerInfo logs is the preRegister method is by default shown
already in:
- console
- server.log
- boot.log
So, echo " JAVA_OPTS: $JAVA_OPTS" is just a repetition of what will be
shown a few lines below in the console. Check out trunk and see :)
Just my $0.02
Best regards,
Jesper
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
8:40 a.m.
On Wed, 2009-02-18 at 15:30 +0100, Galder Zamarreno wrote:
Well, what ServerInfo logs is the preRegister method is by default
shown
already in:
- console
- server.log
- boot.log
So, echo " JAVA_OPTS: $JAVA_OPTS" is just a repetition of what will be
shown a few lines below in the console. Check out trunk and see :)
It isn't repetition if the changed JAVA_OPTS either:
* break the log4j configuration
* the failure is before it even does that logging
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:09 a.m.
Adrian Brock wrote:
On Wed, 2009-02-18 at 15:30 +0100, Galder Zamarreno wrote:
> Well, what ServerInfo logs is the preRegister method is by default shown
> already in:
> - console
> - server.log
> - boot.log
>
> So, echo " JAVA_OPTS: $JAVA_OPTS" is just a repetition of what will be
> shown a few lines below in the console. Check out trunk and see :)
It isn't repetition if the changed JAVA_OPTS either:
* break the log4j configuration
* the failure is before it even does that logging
Ok, ok, I give in :)
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
5810
days inactive
5810
days old
jboss-development@lists.jboss.org
7 comments
4 participants
participants (4)
-
Adrian Brock -
Dimitris Andreadis -
Galder Zamarreno -
Jesper Pedersen