Jump to

• Request
• Response

View This JMS Message Log File

get

/management/weblogic/{version}/domainConfig/resourceGroups/{name}/JMSServers/{name}/JMSMessageLogFile

View this JMS message log file.

Request

Path Parameters

• name: string
  The name property of the instance in the collection.
• version: string
  The version of the WebLogic REST interface.

Query Parameters

• excludeFields(optional): string
  The 'excludeFields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields whose name is not on the list will be returned. If not present, all fields are returned (unless the 'fields' query parameter is specified). Note: 'fields' must not be specified if 'excludeFields' is specified.
• excludeLinks(optional): string
  The 'excludeLinks' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links whose relationship name is not on the list will be returned. If not present, all links are returned (unless the 'links' query parameter is specified). Note: 'links' must not be specified if 'excludeLinks' is specified.
• fields(optional): string
  The 'fields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields with matching names are returned. If not present, all fields are returned (unless the 'excludeFields' query parameter is specified). Note: 'excludeFields' must not be specified if 'fields' is specified.
• links(optional): string
  The 'links' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links with matching relationship names are returned. If not present, all links are returned (unless the 'excludeLinks' query parameter is specified). Note: 'excludeLinks' must not be specified if 'links' is specified.

Security

• Admin: basic
  Type: basic

  Description: A user in the Admin security role.
• Deployer: basic
  Type: basic

  Description: A user in the Deployer security role.
• Monitor: basic
  Type: basic

  Description: A user in the Monitor security role.
• Operator: basic
  Type: basic

  Description: A user in the Operator security role.

Back to Top

Response

Supported Media Types

• application/json

200 Response

Returns this JMS message log file.

Body ()

Root Schema : JMS Message Log File

Type: object

Show Source

• bufferSizeKB(optional): integer(int32)
  Default Value: 8

  Gets the underlying log buffer size in kilobytes

• dateFormatPattern(optional): string

  The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the java.text.SimpleDateFormat class.

  Constraints

  • legal null
• dynamicallyCreated(optional): boolean
  Read Only: true

  Default Value: false

  Return whether the MBean was created dynamically or is persisted to config.xml

• fileCount(optional): integer(int32)
  Minimum Value: 1

  Maximum Value: 99999

  Default Value: 7

  The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)

  Constraints

  • production mode default : 100
• fileMinSize(optional): integer(int32)
  Minimum Value: 1

  Maximum Value: 2097150

  Default Value: 500

  The size (1 - 2097150 kilobytes) that triggers the server to move log messages to a separate file. The default is 500 kilobytes. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file as SERVER_NAME.lognnnnn and create a new one to store subsequent messages. (Requires that you specify a file rotation type of Size.)

  Constraints

  • production mode default : 5000
• fileName(optional): string

  The name of the file that stores current JMS server log messages. Usually it is a computed value based on the name of the parent of this MBean. For example, for a JMS server log, it is jmsserverName.log

  However, if the name of the parent cannot be obtained, the file name is weblogic.log. If you specify a relative pathname, it is interpreted as relative to the server's root directory.

  To include a time and date stamp in the file name when the log file is rotated, add java.text.SimpleDateFormat variables to the file name. Surround each variable with percentage () characters.

  For example, if the file name is defined to be myjmsserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file will be named myserver_yyyy_mm_dd_hh_mm.log

  When the log file is rotated, the rotated file name contains the date stamp. For example, if the log file is rotated on 2 April, 2005 at 10:05 AM, the log file that contains the old messages will be named myserver_2005_04_02_10_05.log

  If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example, myjmsserver.log00007

• fileTimeSpan(optional): integer(int32)
  Minimum Value: 1

  Default Value: 24

  The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of TIME.)

• id(optional): integer(int64)
  Read Only: true

  Return the unique id of this MBean instance

• logFileRotationDir(optional): string

  The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.

• name(optional): string
  Read Only: true

  The user-specified name of this MBean instance.

  This name is included as one of the key properties in the MBean's javax.management.ObjectName

  Name=user-specified-name

  Constraints

  • legal null
• notes(optional): string

  Optional information that you can include to describe this configuration.

  WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.

  Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

• numberOfFilesLimited(optional): boolean
  Default Value: true

  Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of SIZE or TIME.)

  After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.

  If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.

  Constraints

  • production mode default : true
• rotateLogOnStartup(optional): boolean
  Default Value: true

  Specifies whether a server rotates its log file during its startup cycle. The default value in production mode is false.

  Constraints

  • production mode default : false
• rotationTime(optional): string
  Default Value: 00:00

  Determines the start time (hour and minute) for a time-based rotation sequence.

  At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span.

  Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.

  Use the following format: H:mm, where

  • is Hour in day (0-23)

  • mm is the minute in hour

• rotationType(optional): string
  Default Value: bySize

  Allowed Values: [ "bySize", "byTime", "none", "bySizeOrTime" ]

  Criteria for moving old log messages to a separate file.

  • NONE Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.

  • SIZE When the log file reaches the size that you specify in FileMinSize, the server renames the file as SERVER_NAME.lognnnnn

  • TIME At each time interval that you specify in TimeSpan, the server renames the file as SERVER_NAME.lognnnnn

  After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.

• tags(optional): array Items
  Title: Items

  Return all tags on this Configuration MBean

• type(optional): string
  Read Only: true

  Returns the type of the MBean.

  Constraints

  • unharvestable

{
    "type":"object",
    "properties":{
        "bufferSizeKB":{
            "default":8,
            "type":"integer",
            "format":"int32",
            "description":"<p>Gets the underlying log buffer size in kilobytes</p>"
        },
        "dateFormatPattern":{
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The date format pattern used for rendering dates in the  log. The DateFormatPattern string conforms to the specification of the <code>java.text.SimpleDateFormat</code> class.</p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "dynamicallyCreated":{
            "readOnly":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Return whether the MBean was created dynamically or is persisted to config.xml</p>"
        },
        "fileCount":{
            "default":7,
            "x-weblogic-productionDefault":100,
            "minimum":1,
            "maximum":99999,
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)</p><p><h5>Constraints</h5></p><ul><li>production mode default : 100</li></ul>"
        },
        "fileMinSize":{
            "default":500,
            "x-weblogic-productionDefault":5000,
            "minimum":1,
            "maximum":2097150,
            "type":"integer",
            "format":"int32",
            "description":"<p>The size (1 - 2097150 kilobytes) that triggers the server to move log messages to a separate file. The default is 500 kilobytes. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file as <code><i>SERVER_NAME</i>.log<i>nnnnn</i></code> and create a new one to store subsequent messages. (Requires that you specify a file rotation type of <code>Size</code>.)</p><p><h5>Constraints</h5></p><ul><li>production mode default : 5000</li></ul>"
        },
        "fileName":{
            "type":"string",
            "description":"<p>The name of the file that stores current JMS server log messages. Usually it is a computed value based on the name of the parent of this MBean. For example, for a JMS server log, it is <code><i>jmsserverName</i>.log</code></p><p> However, if the name of the parent cannot be obtained, the file name is <code>weblogic.log</code>. If you specify a relative pathname, it is interpreted as relative to the server's root directory.</p><p>To include a time and date stamp in the file name when the log file is rotated, add <code>java.text.SimpleDateFormat</code> variables to the file name. Surround each variable with percentage (<code></code>) characters.</p><p>For example, if the file name is defined to be <code>myjmsserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log</code>, the log file will be named <code>myserver_yyyy_mm_dd_hh_mm.log</code></p><p>When the log file is rotated, the rotated file name contains the date stamp. For example, if the log file is rotated on 2 April, 2005 at 10:05 AM, the log file that contains the old messages will be named <code>myserver_2005_04_02_10_05.log</code></p><p>If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example, <code>myjmsserver.log00007</code></p>"
        },
        "fileTimeSpan":{
            "default":24,
            "minimum":1,
            "type":"integer",
            "format":"int32",
            "description":"<p>The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of <code>TIME</code>.)</p>"
        },
        "id":{
            "readOnly":true,
            "type":"integer",
            "format":"int64",
            "description":"<p>Return the unique id of this MBean instance</p>"
        },
        "logFileRotationDir":{
            "type":"string",
            "description":"<p>The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.</p>"
        },
        "name":{
            "readOnly":true,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The user-specified name of this MBean instance.</p><p>This name is included as one of the key properties in the MBean's <code>javax.management.ObjectName</code></p><p><code>Name=<i>user-specified-name</i></code></p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "notes":{
            "type":"string",
            "description":"<p>Optional information that you can include to describe this configuration.</p><p>WebLogic Server saves this note in the domain's configuration file (<code>config.xml</code>) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <code>&lt;</code>. Carriage returns/line feeds are preserved.</p><p>Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.</p>"
        },
        "numberOfFilesLimited":{
            "default":true,
            "x-weblogic-productionDefault":true,
            "type":"boolean",
            "description":"<p>Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of <code>SIZE</code> or <code>TIME</code>.)</p><p>After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.</p><p>If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.</p><p><h5>Constraints</h5></p><ul><li>production mode default : true</li></ul>"
        },
        "rotateLogOnStartup":{
            "default":true,
            "x-weblogic-productionDefault":false,
            "type":"boolean",
            "description":"<p>Specifies whether a server rotates its log file during its startup cycle. The default value in production mode is false.</p><p><h5>Constraints</h5></p><ul><li>production mode default : false</li></ul>"
        },
        "rotationTime":{
            "default":"00:00",
            "type":"string",
            "description":"<p>Determines the start time (hour and minute) for a time-based rotation sequence.</p><p>At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span.</p><p>Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.</p><p>Use the following format: <code>H:mm</code>, where</p><ul><li><p><code></code> is Hour in day (0-23)</p></li><li><p><code>mm</code> is the minute in hour</p></li></ul>"
        },
        "rotationType":{
            "default":"bySize",
            "enum":[
                "bySize",
                "byTime",
                "none",
                "bySizeOrTime"
            ],
            "type":"string",
            "description":"<p>Criteria for moving old log messages to a separate file.</p><ul><li><p><code>NONE</code> Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.</p></li><li><p><code>SIZE</code> When the log file reaches the size that you specify in <code>FileMinSize</code>, the server renames the file as <code><i>SERVER_NAME</i>.log<i>nnnnn</i></code></p></li><li><p><code>TIME</code> At each time interval that you specify in <code>TimeSpan</code>, the server renames the file as <code><i>SERVER_NAME</i>.log<i>nnnnn</i></code></p></li></ul><p>After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.</p>"
        },
        "tags":{
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>Return all tags on this Configuration MBean</p>"
        },
        "type":{
            "readOnly":true,
            "x-weblogic-unharvestable":true,
            "type":"string",
            "description":"<p>Returns the type of the MBean.</p><p><h5>Constraints</h5></p><ul><li>unharvestable</li></ul>"
        }
    },
    "description":""
}

Nested Schema : Items

Type: array

Title: Items

Return all tags on this Configuration MBean

Show Source

• Array of: string

{
    "title":"Items",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"<p>Return all tags on this Configuration MBean</p>"
}

Back to Top