Chatta subito con l'assistenza
Chat con il supporto

Foglight for Java EE Technologies 5.9.7.5 - Application Servers User Guide

Monitoring Application Servers Monitoring Systems Monitoring Servers Monitoring Applications Monitoring Requests Managing Traces Using Object Tracking to Locate a Memory Leak Monitoring Methods Application Servers Monitor Views
JVM view Method Groups view Request Types view Entity EJBs view Message Driven EJBs view Stateful Session EJBs view Stateless Session EJBs view Deployed Applications view JSPs/Servlets components view Resource Adapters components view Web Applications components view Web Services components view .NET views JBoss Services views Oracle Services views Tomcat Services views WebLogic Services views WebSphere Services views JMX Administration dashboard JMX Explorer dashboard
Appendix: Regular Expressions

MBean Property summary view

In the JMX Explorer Available MBeans view, select an MBean. In the MBean Properties view, click the value of an attribute.
Edit Configuration. Opens the Attribute - Topology Property Configuration dialog box, which allows you to edit the name, storage type, and metric derivations (if applicable).

Java Virtual Machine (JVM) dashboard

On the JMX Explorer dashboard, click the JVM name. The JVM Summary view popup opens. Click the Heap Usage chart to open the JVM dashboard.
Table 85. JVM details

Appendix: Regular Expressions

Regular expressions employ metacharacters. A metacharacter is a character with special meaning. It does not denote a normal letter, but instead affects the interpretation of other characters in a regular expression. Metacharacters only occur inside a regular expression; for example, an asterisk (*) in a data string is not a metacharacter. There are only a few metacharacters in the regular expression language, but their effect can be quite powerful.
For example: the regular expression ‘White *space’ matches ‘Whitespace’, or ‘White space’, or ‘White@@any number of space characters@@space’, but not ‘White *space’ (the string containing a literal asterisk).
NOTE: ‘nexus*’ does NOT match ‘nexus.bat’, or ‘nexusconfig’. Path name-style matching (file globbing) is not the same as regular expression syntax.
The regular expression ‘HTTP1[.]0’ matches HTTP1.0. Placing the period in a character class removes its metacharacter status.
The regular expression ‘HTTP1.0’ matches ‘HTTP1.0’ (the string containing the literal period), or ‘HTTP1A0’ or ‘HTTP110’, but not ‘HTTP1.x or ‘HTTP1..x’.
The combination ‘.*’ (dot-star) matches any string of characters. It is an idiom for ‘the rest of the characters’ in a string, but not including the end of line character.
For example: the regular expression ‘HTTP.*’ matches ‘HTTP1.0’, or
‘HTTP1://www.example.com/index.html’.
CAUTION: The regular expression ‘mayb.com.*’ matches ‘maybecompletely wrong!’. The dot in the regular expression matches any character, in this case an ‘e’.
NOTE: Because the dot is a metacharacter, use the character class [.] to match a literal dot in a string. It is more robust than attempting to protect the dot with a backslash (\.).
For example: the regular expression ‘i?www’ matches ‘www’ or ‘iwww’. The regular expression ‘(ab)?cd’ matches ‘abcd’ and ‘cd’.
For example: the regular expression ‘i+www’ matches ‘iwww’ or ‘iiwww’, but not ‘www’.
For example: the regular expression ‘[bcp]at’ matches ‘bat’, ‘cat’, or ‘pat’, but not ‘mat’.
For example: the regular expression ‘[b-h]at’ matches ‘bat’, or ‘cat’, or ‘fat’, or ‘hat’, but not ‘mat’.
The regular expression ‘^abc’ matches ‘abcxyz’ but not ‘xyzabc’.
The regular expression ‘[^cpt]at’ matches ‘hat’, or ‘mat’, or any three-letter combination ending in ‘at’ that does not begin with the letters ‘c’, ‘p’, or ‘b’.
For example: the regular expression ‘foo|bar’ matches ‘foo’ or ‘bar’, but not ‘foobar’.
For example: the regular expression ‘myhost\.com’ matches ‘myhost.com’, but not ‘myhostcom’.
For example: the regular expression ‘http://(my|our)host\.com’ matches ‘http://myhost.com’ or ‘http://ourhost.com’.

How regular expressions are scanned

If a regular expression contains “|” operators, the left most matching sub-expression is chosen. Example: if the regular expression is ‘(cat|dog)’ and the target string is ‘cats and dogs’, the match succeeds with ‘cat’ after the first three letters have been scanned.
In “*”, “+”, and “?” constructs, longer matches are chosen in preference to shorter ones. Example: if the regular expression is ‘^He’s ba*’ and the target string is ‘He’s baaaaack!’, the match succeeds with ‘He’s baaaaa’ after the full list of contiguous a’s have been scanned.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione