SandBox

import static stuff;

 

 

 

sadasd BOLD sdasd asd a

 

 

sadsda

sad

=========================================================================

 

  JBoss Bootstrap Environment

 

  JBOSS_HOME: /home/rhusar/as/jboss-as-7.1.1.Final-SNAPSHOT2/jboss-as-7.1.1.Final-SNAPSHOT

 

  JAVA: /home/rhusar/tools/jdk1.6.0/bin/java

 

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

 

=========================================================================

 

17:39:24,172 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

17:39:24,417 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

17:39:24,506 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" starting

17:39:25,670 INFO  [org.xnio] XNIO Version 3.0.3.GA

17:39:25,680 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

17:39:25,696 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

17:39:25,711 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.2.GA

17:39:25,775 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

17:39:25,780 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem

17:39:25,799 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.

17:39:25,852 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem

17:39:25,858 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem

17:39:25,858 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.6.final

17:39:25,865 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem

17:39:25,862 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.

17:39:25,905 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension

17:39:25,949 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)

17:39:26,041 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

17:39:26,076 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

17:39:26,088 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

17:39:26,180 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.1.GA

17:39:26,270 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--1%3A0%3A0%3A1%3A0%3A0%3A0%3A12%252-8080

17:39:26,277 INFO  [org.jboss.as.modcluster] (MSC service thread 1-4) JBAS011704: Mod_cluster uses default load balancer provider

17:39:26,337 INFO  [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final

17:39:26,389 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364

17:39:26,466 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:26,506 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:26,620 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /1:0:0:1:0:0:0:12%2:9999

17:39:26,623 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /1:0:0:1:0:0:0:12%2:4447

17:39:26,655 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/rhusar/as/jboss-as-7.1.1.Final-SNAPSHOT2/jboss-as-7.1.1.Final-SNAPSHOT/standalone/deployments

17:39:26,664 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

17:39:26,736 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "clusterbench-ee6.ear"

17:39:26,861 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "clusterbench-ee6-ejb.jar"

17:39:26,862 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "clusterbench-ee6-web.war"

17:39:26,989 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment clusterbench-ee6.ear

17:39:27,091 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment clusterbench-ee6-ejb.jar

17:39:27,093 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteSingletonSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

 

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

    java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

    java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

    java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

    java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

    java:jboss/exported/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

 

17:39:27,100 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteStatefulSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

 

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

    java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

    java:module/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

    java:jboss/exported/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl

    java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl

    java:module/RemoteStatefulSBImpl

 

17:39:27,101 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment clusterbench-ee6-web.war

17:39:27,107 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalStatefulSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

 

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

    java:app/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

    java:module/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB

    java:app/clusterbench-ee6-ejb/LocalStatefulSB

    java:module/LocalStatefulSB

 

17:39:27,109 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalSingletonSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

 

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

    java:app/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

    java:module/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

    java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB

    java:app/clusterbench-ee6-ejb/LocalSingletonSB

    java:module/LocalSingletonSB

 

17:39:27,119 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: clusterbench-ee6.ear

17:39:27,188 INFO  [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)

17:39:27,274 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment clusterbench-ee6.ear

17:39:27,740 INFO  [stdout] (pool-14-thread-1)

17:39:27,741 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

17:39:27,741 INFO  [stdout] (pool-14-thread-1) GMS: address=rhusar2/web, cluster=web, physical address=1:0:0:1:0:0:0:12:55200

17:39:27,741 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

17:39:27,758 INFO  [stdout] (pool-19-thread-1)

17:39:27,762 INFO  [stdout] (pool-19-thread-1) -------------------------------------------------------------------

17:39:27,762 INFO  [stdout] (pool-19-thread-1) GMS: address=rhusar2/ejb, cluster=ejb, physical address=1:0:0:1:0:0:0:12:55200

17:39:27,763 INFO  [stdout] (pool-19-thread-1) -------------------------------------------------------------------

17:39:27,931 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (MSC service thread 1-1) JBAS010206: Number of cluster members: 2

17:39:27,946 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.ejb] (MSC service thread 1-3) JBAS010206: Number of cluster members: 2

17:39:28,214 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,218 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,246 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (pool-15-thread-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,377 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000078: Starting JGroups Channel

17:39:28,379 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (pool-15-thread-1) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@2c642c2e) but now it is being overridden

17:39:28,378 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000078: Starting JGroups Channel

17:39:28,380 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (pool-21-thread-1) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@649096c6) but now it is being overridden

17:39:28,381 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000094: Received new cluster view: [rhusar1/ejb|1] [rhusar1/ejb, rhusar2/ejb]

17:39:28,382 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000094: Received new cluster view: [rhusar1/web|1] [rhusar1/web, rhusar2/web]

17:39:28,384 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000079: Cache local address is rhusar2/web, physical addresses are [1:0:0:1:0:0:0:12:55200]

17:39:28,383 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000079: Cache local address is rhusar2/ejb, physical addresses are [1:0:0:1:0:0:0:12:55200]

17:39:28,393 INFO  [org.infinispan.factories.GlobalComponentRegistry] (pool-21-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.1.FINAL

17:39:28,426 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-21-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,445 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-20-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,446 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-15-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,575 INFO  [org.jboss.as.clustering.infinispan] (pool-15-thread-1) JBAS010281: Started repl cache from web container

17:39:28,576 INFO  [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010281: Started repl cache from ejb container

17:39:28,596 INFO  [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010281: Started remote-connector-client-mappings cache from ejb container

17:39:28,649 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,660 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,681 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-2) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,709 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) JBAS010281: Started //default-host//clusterbench cache from web container

17:39:28,723 INFO  [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-1) Added a new EJB receiver in cluster context ejb for node rhusar2. Total nodes in cluster context = 1

17:39:28,729 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,735 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

17:39:28,742 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,750 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server.

17:39:28,784 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010281: Started org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl cache from ejb container

17:39:28,788 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) JBAS010281: Started org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from ejb container

17:39:28,894 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/clusterbench'

17:39:29,553 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final

17:39:29,730 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /clusterbench

17:39:29,734 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015874: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" started in 5796ms - Started 324 of 452 services (127 services are passive or on-demand)

17:39:29,791 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "clusterbench-ee6.ear"

asd

asd

 

bdiuasdb asudbasud badbasuo aouds

is email pretty prented in here?

test = test <test@redhat.com>

 

 

raw htwm test = test@redhat.com

 

 

HOW DO I DOWNLOAD THIS WIKI ??-> see Issue https://issues.jboss.org/browse/ORG-1137

SandBox

Feel free to experiment with JBoss Wiki :-)

 

I'm just playing around....

 

 

 

{embedcontent:id=12993}

wawawewe

delete from dual;
commit;
import java.xml.*;

public class MyClass {

}

Testing codefatta

and here we go

 

<xml>
     <child>Ole</child>
</xml>

Test Edit JBoss.  How can I do inline code text???  ARGH!  I have to specify a fixed-width font???

 

Fine my account is working...

 

java code
more java code

 

So is this clearspace?

 

I'm part of a Wiki.  So am I!

 

 

Test test...

Hi I am part of Wiki, too!

 

nice

 

Link

 

Materials

-

 

This is a test

 

 


this

 

 

 


 

 

 

Examples of Syntax Highlighting:

SQL

 

XML

 

Java

 

Plain

testing

 

 

 

    This page last changed on Oct 02, 2008 by skittoli.

Response Times

Concepts

Response times denote the time it takes to serve a web request or a EJB method call. Unlike the numerical metrics, this is most of the time an array of data in the sense that the one metric you enable brings you  min/avg/max data for all methods of a Session Bean or all URLs of a web application.

Please refer to the Monitoring section for an overview of monitoring in JON.

Enabling Response Time measurement

Before response times can be gathered or displayed, they first need to be enabled

EJB call times

In order to gather EJB call times you need to go to the configure section of the Monitor tab and enable the collection of the call times:

Please refer to the Collection Schedules section on the general Monitoring page for more information about collection schedules and defaults.

 

 

 

    This page last changed on Oct 02, 2008 by skittoli.

Response Times

Concepts

Response times denote the time it takes to serve a web request or a EJB method call. Unlike the numerical metrics, this is most of the time an array of data in the sense that the one metric you enable brings you  min/avg/max data for all methods of a Session Bean or all URLs of a web application.

Please refer to the Monitoring section for an overview of monitoring in JON.

Enabling Response Time measurement

Before response times can be gathered or displayed, they first need to be enabled

EJB call times

In order to gather EJB call times you need to go to the configure section of the Monitor tab and enable the collection of the call times:

Please refer to the Collection Schedules section on the general Monitoring page for more information about collection schedules and defaults.

Web application response times

In order to gather response times from web applications, you need to instrument the servlet container. This process is described on the Response Time Filter page.

Note: the JBossON server is already instrumented.

After the filter is installed, you need to open the inventory tab of the web application and specify the full path to the logfile:

There are two more properties that you can set:

  • URL Excludes: Specifies URLs that should not be taken into account for the response time metrics. Examples are e.g. static files like CSS files or images. Entries are regular expressions separated by spaces. For example to exclude gif, jpg, and png files, use:
    (?i)\.(jpg|gif)$
  • URL Transforms: If a page is called with a different parameter, you may decide to show them as separate URLs or as one URL only. The transform allows you to rewrite URLs to e.g. strip off those parameters. Entries are substitution expressions separated by spaces. A substitution expression has the syntax:
    |<regular expression>|<replacement text>|
    For example, to remove all query strings, use:
    |(.*)\?.*|$1|

    For WARs, the functioning of URL transforms depends on the settings of the Response Time Filter; particularly the chopQueryString parameter.

After this is done, you need to open the configure section of the Monitor tab and enable the collection of the response times:

Please refer to the c. Monitoring#Collection schedules section for more information.

Monitor Tab

For resources that can collect response times, you will see another subtab on the monitor tab named "Response time":

When you select it you will see two sections

  • on the left the raw data table with the resource, number of calls and times

  • on the right the call times visualized as bar diagrams

                      

 

 


 

 

This is text at size 10pt.

This is larger text at size 12 pt.

This is default size text.

This is text at size 14 pt.

This is text at size 18 pt.

This is header1 style.

This is header2 style.

This is syntaxt highlighting plain.

 

This is syntax highlighting java interface class

 

This is a quote

 

 

MORE HTML IMPORT TESTING

 

    This page last changed on Oct 07, 2008 by jshaughn.

JON Server Installation Guide - Version 2.0.1

It is recommended that you also read the JON Server section for more information about the JON Server.

Upgrading

If you are upgrading from an earlier JON 2.x GA release, you must follow the JON Server upgrade instructions, so that your inventory and metric data will be migrated from the previous installation.

Upgrading from JON 1.x or the JON 2.0 Beta or CR releases is not supported.

Preparation

OS, Java and Database Prerequisites

Before running the installer, you first must have a JDK 5 installed as well as an external database.  For instructions on how to install JDK 5, please read the Prerequisites section.

Once you have an installed database, determine the JDBC URL needed to connect to that database and make a note of it - you will need to specify the JDBC URL, database username and password in the installer.

Synchronize Machine Clocks

You must ensure that all platforms to be imported into your environment have their clocks in sync with each other and with the JBoss ON Server. If the times are not in syncg, measurements, availabilities and graphs will be skewed and problems will occur when you attempt to import resources into your inventory.  Please refer to NTP if you are unfamiliar with how you can ensure your clocks are in sync.

Monitoring the JON Server itself

You must decide if you want the JBoss ON server to monitor itself.  If you intend to have the JBoss ON server to monitor itself, you need to install a JON Agent on the same machine where your JON Server is installed.

The following options are available:

Using the embedded agent frees you from having to install and maintain a separate, standalone agent.  The embedded agent starts when the JON Server starts and will remain running as long as the JON Server is running. If you wish to use the embedded agent, you need to indicate in the installer that you want to start it along with the JON Server itself (see Embedded JON Agent).

Use of the embedded agent is meant for monitoring the JBoss ON Server itself. If you have another JBoss Application Server instance that you would like to monitor on the same machine as the JON Server then you should select the standalone agent option.

Running The Installer

Unlike JBoss ON 1.x, there is no longer a standalone installer.  You should have a JON Server distribution file (jon-server-2.X.zip).

  1. Unzip the Server distribution to the directory within which it will be executed from, e.g.:
    cd /opt
    unzip jon-server-2.0.1.GA.zip

    The directory structure within the zipfile will ensure the Server has a version-specific installation directory name (e.g. the above commands will create a directory named /opt/jon-server-2.0.1.GA).

    Windows Installation

    On Windows, do not install the JON Server into a directory with a path longer than 19 characters (e.g. use C:\Program Files\ rather than C:\Documents and Settings\myusername\ ), as this will cause errors during execution of the server.

  2. ( Version 2.0.0 Only) If you are running Linux/Unix you need to make the start scripts executable. Execute the following command from the directory into which you unpacked the server ZIP file:
    chmod +x bin/*.sh jbossas/bin/*.sh
  3. Run the JON Server:
    For UNIX, execute the following from the command line:
    bin/rhq-server.sh start

    For Windows, execute the following from the command line:

    bin\rhq-server-console.bat start
  4. Point your browser to http://localhost:7080/ – This will display the JON Server Installer web application.
  5. Click the "Click here to continue the installation" link
  6. Database Installation      
    1. Set your database connection properties.
      Update the default values as necessary.
    2. If necessary, create a new database.
      If you have installed your database server but not yet created the necessary database or role for use with JON, click on the "Create Database" button. Do not perform this step if you have already created the RHQ database and rhqadmin role.             
      • On Oracle, if you select the 'overwrite tables' option but there is nothing to overwrite (Because this is a first-time installation), you may see some message in your server log.  These can be safely ignored: ERROR [DBSetup] {DBSetup.dropped-table-error}Failed to drop table [SOME_RHQ_TABLE] or one of its sequences. Cause: ErrorCode=[2289]; SQLState=[42000]; Message=[ORA-02289: sequence does not exist]; Type=[java.sql.SQLException]
    3. Test your database connection:
      Click the "Test Connection" button. If this test fails check your connection properties for mistakes and/or ensure your database server is running.
    4. Existing Database options
      If an existing JON Server schema is discovered (e.g. from a previous JON installation) the installer will give you the choice of either upgrading it to the latest schema version or overwriting it and losing all existing data. Please select the upgrade option unless you are sure that you want to lose all previous JON data. If any errors occur during the DB schema installation, please open the logs directory and check the logs.             
      The JBoss ON 1.x database schema is incompatible with the JBoss ON 2.0 schema and you cannot upgrade a 1.x schema to a 2.0 schema.
  7. Server Settings
    You have the choice of using the basic installer or showing advanced settings.      
    1. Basic Installation
      Basic installation presents the settings typically needed to install JON.  Default values are usually appropriate for most basic and all advanced settings. If necessary, any server setting can be modified at a later time by editing the <jon-server-home>/bin/rhq-server.properties file.             

      If you bind the server to an address other than 0.0.0.0 you must also edit the <jon-server-home>/bin/rhq-server.properties file. Enable the java.rmi.server.hostname property, setting it to the same address to which the server is bound.

      SMTP settings must be set correctly to enable e-mail notification of alerts. You can update these settings if your SMTP server is not on the same machine as the JON server.
      ( Version 2.0.0), You must check the "Show Advanced Settings" checkbox to view these settings.
      ( Version 2.0.1), These are now basic settings.

      Embedded Agent Enabled : "No" if not monitoring the JON Server or if using the standalone agent; "Yes" otherwise (see Embedded JON Agent)

    2. Advanced Installation
      To use the Advanced Installation, check the "Show Advanced Settings" checkbox.
      All the settings listed in the Advanced Installation are explained in detail on the Startup Properties page.
Keep in mind that if any startup properties that indicate 'a restart is required' are changed, the server will not correctly function until it is restarted. It is recommended to restart immediately after the installation is completed to work with the server.

After you have clicked "Install JON Server" you will see an intermediate screen.  Once the installation has completed the message "Starting up, please wait..." will be displayed.  Once done, click the "Done! Click here to get started." link to begin using your JON server.

Some browsers - most notably Safari and Opera - will not display the login page, but show the last page. If this happens, press the refresh button of your browser and click on the link again.

Install errors on Postgres

There have been some cases where the installation of PostgreSQL failed with an error "Relation RHQ_Principal" does not exist. Please refer to the Postgres Preparation page for a workaround.

Installing as a Boot-Time Service

You can install the JON Server to run when your computer boots up. On Windows, this means installing the JON Server to start as a Windows Service.  On UNIX, it means installing the JON Server startup script as an init.d startup script.

To install as a boot-time service on either Windows or UNIX, please read the instructions found here: Running the JON Server.

Upgrading the JON Server - Version 2.0.1

Upgrading from JON 1.x, the JON 2.0 Beta or CR releases is not supported.

Loss of Data

Loss of minimal monitoring data is inevitable given the down-time involved in shutting down instances of the Agents during the upgrade process.

If you have a Resource in inventory corresponding to the JON Server itself, upgrading JON will entail the loss of all monitoring data for that Resource.

Please follow the steps outlined below to upgrade your JON Server:

1. Remove Obsolete Alert Definitions

Before upgrading JON you must remove alert definitions with conditions for obsolete metrics. Please remove alert definitions, including alert templates, for the following metrics:

ResourceType  Metric
Postgres ServerUser Time

Kernel Time

Physical Memory

Virtual Memory

The alert definitions are not easy to remove after the upgrade.

2. Remove no longer wanted platforms from the inventory

If you plan to put platforms that are in the inventory out of service, do this before upgrading.

3. Stop the Server and all Agents.

Stop all of the JON Agents and then the JON Server. Do not stop the JON Database.

The JON Server must be upgraded before any Agents are upgraded. Please shut down all agents and wait until all agents show red availability in the GUI before shutting down the server.

4. Unzip the new version of the JON Server.

Unzip the new Server distribution to the directory within which it will be executed from, e.g.:

cd /opt
unzip jon-server-2.0.1.GA.zip

Note, the directory structure within the zipfile will ensure the new Server has a version-specific installation directory name (e.g. the above commands will create a directory named /opt/jon-server-2.0.1.GA). The new Server installation should not be copied on top of the original Server installation.

If you have made modifications to your original Server's Startup Properties (e.g. enabling SSL, SMTP), either when first installing or through the ./bin/rhq-server.properties file, merge these changes into the new Server's rhq-server.properties file.

Merging Startup Properties

If you prefer not to edit the new Server's ./bin/rhq-server.properties file, you can merge your changed values during installation via the "advanced installation" checkbox.

If you are running the Server on Windows and installed the original Server as a Windows service, uninstall the Windows service:

cd <old-server-install-dir>/bin
./rhq-server.bat remove

Then install a Windows service for the new Server:

cd <new-server-install-dir>/bin
./rhq-server.bat install

5. Setup the JON Server.

Backup Your Database

You should consider backing up your database prior to proceeding. In case problems arise during the database upgrade, having a backup will allow you to restore to your previous state.

Locate Your License

You will need to register your license with the new version of JON. Your existing license file is located in <old-server-install-dir>/jbossas/server/default/deploy/rhq.ear/license/license.xml.  If necessary copy this to a safe location and re-use it during the upgrade process.

Follow the JON Server installation instructions to install the Server. Once you've entered your database connection info, the installer should detect that there is an existing JON database and display the following prompt:

"A database schema already exists. What do you want to do?"

Choose "Keep and, if necessary, upgrade it". Do not choose "Overwrite it (and lose existing data)", otherwise all of the existing inventory, metric, and history data from your original JON installation will be lost.

During the upgrade you may see error messages similar to the following in the console. These error messages are harmless.

14:19:36,540 ERROR [ClientCommandSenderTask] {ClientCommandSenderTask.send-failed}Failed to send 
command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.timeout=1000,
rhq.send-throttle=true}]; params=[{targetInterfaceName=org.rhq.enterprise.communications.Ping,
invocation=NameBasedInvocation[ping]}]]. Cause: org.jboss.remoting.CannotConnectException:[.....]

6. Install the new version of the JON Agent to each Agent machine.

Follow the Agent upgrade instructions.

7. Start up the new Server and Agents.

8. Open the JON GUI.

  1. If a JON JBossAS Server Resource corresponding to your old Server installation is in the inventory, please remove it from the inventory.
  2. (optional) If desired, import the new JON JBossAS Server Resource into the inventory. If you do import it, its metric schedules and alert definitions will need to be configured.
                                
             

 

中文显示如何?