Abstract: A computer receives a first trace output, generated during a first execution of a first program, that is annotated with an indication of a first pattern of logged events and one or more second programs that identify additional logged events. The computer identifies the first pattern of logged events in a second trace output, which is generated during a second execution of the first program. The computer executes the one or more second programs to identify one or more additional logged events that are discoverable during the second execution of the first program, wherein the one or more additional logged events are not included in the first trace output. The computer determines that the end first pattern of logged events in the second trace output has been reached. The computer ceases execution of the one or more second programs.

Abstract: A computer identifies a first trace output, generated during a first execution of a first program, that is annotated with an indication of a first pattern of logged events and one or more second programs that identify additional logged events. The computer identifies the first pattern of logged events in a second trace output, which is generated during a second execution of the first program. The computer executes the one or more second programs to gather one or more additional logged events that are discoverable during the second execution of the first program, wherein the one or more additional logged events are not included in the first trace output.

Abstract: Systems and methods of managing problem determination (PD) data provide for obtaining PD data from a plurality of data sources via an input/output (I/O) interface of a data management device and storing the PD data to a memory of the data management device. In addition, an automated diagnostic analysis of the PD data may be conducted on the data management device. An automated discovery manager may provide the ability to find new sources of PD data and to either reconfigure remote systems to send data to the data management device or to automatically retrieve data from remote systems on a configurable schedule. Dynamically updateable database of symptom information can also be used, wherein the data management device may include a dynamically updateable set of analysis modules with which to conduct analysis on the PD data.

Abstract: A computer identifies a first trace output, generated during a first execution of a first program, that is annotated with an indication of a first pattern of logged events and one or more second programs that identify additional logged events. The computer identifies the first pattern of logged events in a second trace output, which is generated during a second execution of the first program. The computer executes the one or more second programs to gather one or more additional logged events that are discoverable during the second execution of the first program, wherein the one or more additional logged events are not included in the first trace output.

Abstract: A computer receives a first trace output, generated during a first execution of a first program, that is annotated with an indication of a first pattern of logged events and one or more second programs that identify additional logged events. The computer identifies the first pattern of logged events in a second trace output, which is generated during a second execution of the first program. The computer executes the one or more second programs to identify one or more additional logged events that are discoverable during the second execution of the first program, wherein the one or more additional logged events are not included in the first trace output. The computer determines that the end first pattern of logged events in the second trace output has been reached. The computer ceases execution of the one or more second programs.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth. In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: Systems and methods of managing problem determination (PD) data provide for obtaining PD data from a plurality of data sources via an input/output (I/O) interface of a data management device and storing the PD data to a memory of the data management device. In addition, an automated diagnostic analysis of the PD data may be conducted on the data management device. An automated discovery manager may provide the ability to find new sources of PD data and to either reconfigure remote systems to send data to the data management device or to automatically retrieve data from remote systems on a configurable schedule. Dynamically updateable database of symptom information can also be used, wherein the data management device may include a dynamically updateable set of analysis modules with which to conduct analysis on the PD data.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth. In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth. In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: Problem diagnostics may be obtained from components that log messages using a unique component identifier which is provided within each message so as to enable routing of callbacks to the component that originated the message. Similarly, problem diagnostics may be obtained from components that generate alerts, where the alerts contain the unique identifier of the component that generated the alert. Each component supports a diagnostic provider interface comprising operations which may be dynamically invoked, for example to solicit information from the component such as its configuration data, its state information, to execute self-diagnostic tests, and so forth In addition or instead, operations may be provided that can be invoked to cause the component to alter its configuration data (such as notifying the component to change its level of message logging) or its behavior.

Abstract: A secure method and system for accessing a cache for web session is provided using web browser cookies. The cache for the web session data uses an encoded identifier, determined using for example the Keyed-Hash Message Authentication Code, based on information identifying a client. The client communication is accompanied by a cookie (persistent state object) that also includes the identifier encoded in the same manner. This encoded identifier in the received cookie is used for accessing the cached data. Where a secure communication channel is available, such as a secure socket layer (SSL connection), a second cookie which is only transmitted over SSL is used as a signature for the first cookie.

Abstract: A data processing system comprising a cache memory, wherein a cache entry containing data is stored in the cache memory. A cache coordinator, wherein the cache coordinator invalidates one or more cache entries in response to a signal. An ID-based invalidation process, wherein a cache entry is associated with an ID that uniquely identifies the cache entry and can optionally be associated with one or more data ids that represent the underlying data contained in the cache entry, and the ID-based invalidation process sends a signal to the cache coordinator to invalidate all cache entries that either have that cache entry ID or have been associated with a data ID when the data that the ID represents changes. A time-limit-based invalidation process, wherein a cache entry can be associated with a time limit, and the time-limit-based invalidation process sends a signal to the cache coordinator to invalidate a cache entry whose time limit has expired.

Abstract: A secure method and system for accessing a cache for web session is provided using web browser cookies. The cache for the web session data uses an encoded identifier, determined using for example the Keyed-Hash Message Authentication Code, based on information identifying a client. The client communication is accompanied by a cookie (persistent state object) that also includes the identifier encoded in the same manner. This encoded identifier in the received cookie is used for accessing the cached data. Where a secure communication channel is available, such as a secure socket layer (SSL connection), a second cookie which is only transmitted over SSL is used as a signature for the first cookie.

Abstract: A data processing system comprising a cache memory, wherein a cache entry containing data is stored in the cache memory. A cache coordinator, wherein the cache coordinator invalidates one or more cache entries in response to a signal. An ID-based invalidation process, wherein a cache entry is associated with an ID that uniquely identifies the cache entry and can optionally be associated with one or more data ids that represent the underlying data contained in the cache entry, and the ID-based invalidation process sends a signal to the cache coordinator to invalidate all cache entries that either have that cache entry ID or have been associated with a data ID when the data that the ID represents changes. A time-limit-based invalidation process, wherein a cache entry can be associated with a time limit, and the time-limit-based invalidation process sends a signal to the cache coordinator to invalidate a cache entry whose time limit has expired.

Abstract: A data processing system comprising a cache memory, wherein a cache entry containing data is stored in the cache memory. A cache coordinator, wherein the cache coordinator invalidates one or more cache entries in response to a signal. An ID-based invalidation process, wherein a cache entry is associated with an ID that uniquely identifies the cache entry and can optionally be associated with one or more data ids that represent the underlying data contained in the cache entry, and the ID-based invalidation process sends a signal to the cache coordinator to invalidate all cache entries that either have that cache entry ID or have been associated with a data ID when the data that the ID represents changes. A time-limit-based invalidation process, wherein a cache entry can be associated with a time limit, and the time-limit-based invalidation process sends a signal to the cache coordinator to invalidate a cache entry whose time limit has expired.

Abstract: Toner compositions comprise (a) a toner particulate including resin, magnetic component and charge control agent, and (b) an extra-particulate additive comprising a first hydrophobic additive having negative tribocharging properties and a second hydrophobic additive having positive tribocharging properties.