366 results about "Event queue" patented technology

A method and controller for implementing storage adapter performance optimization with chained hardware operations minimizing hardware and firmware interactions, and a design structure on which the subject controller circuit resides are provided. The controller includes a plurality of hardware engines; and one or more processors. An event queue is coupled to at least one processor notifying the processor of a plurality of predefined events. A control block is designed to control an operation in one of the plurality of hardware engines including the hardware engine writing an event queue entry. A plurality of the control blocks are selectively arranged in a predefined chain to minimize the hardware engine writing event queue entries to the processor.

The present invention relates to a method, system, computer program product, or apparatus that schedules and executes events within a network in real-time. An event processor contacts one or more event schedulers, and it receives back from them event schedule updates. It then calculates the time when each event is to occur from information contained in the received scheduling information for each event. Next, it places event scheduling information contained in the received scheduling information for each event, plus the calculated occurrence time of the corresponding event, into an event queue. Finally, at the time when each event is to occur, as indicated by examination of the calculated times in the event queue, the event processor sends out event firing messages to event processors that are named in the received scheduling information for each event.

A computer program is provided for developing component based software capable of handling insurance-related tasks. The program includes a data component that stores, retrieves and manipulates data utilizing a plurality of functions. Also provided is a client component which includes an adapter component that transmits and receives data to / from the data component. The client component also includes a business component that serves as a data cache and includes logic for manipulating the data. A controller component is also included which is adapted to handle events generated by a user utilizing the business component to cache data and the adapter component to ultimately persist data to a data repository. In use, the client component allows a user to define tasks that achieve an insurance-related goal upon completion. In addition, the user is able to input rules which dictate which tasks should be selected based on a set of predetermined events. Events are then received from any source, such as a common event queue. Finally, tasks are selected and outputted based on the received events.

A method and system are provided for managing application programs with non-responsive user interfaces, possibly due to a bottleneck in handling events / messages. The method and system make an apparently frozen application user interface responsive so as to permit alternative tasks be executed or close the hung application. This is enabled by implementing routines to (a) detect if an application is hung, (b) replace the user interface for the hung application with a ghost interface, implemented by a separate thread, that permits system functionality such as sizing, minimization and closing of the application, and (c) destroying the ghost interface if the hung application becomes responsive again along with restoring the application's user interface along with updated event queues. Furthermore, creation of the ghost user interface is accompanied by placing a high priority special event in the hung application's queue to detect renewed responsiveness without requiring explicit monitoring.

A system and method for enabling multiple processes to efficiently log events is described. A client executable module that needs to log an event may interface with a module or component referred to as a “client-side logging component”, passing various types of information regarding the event, such as an associated event level, one or more event associated event categories, an informational message, etc. The client-side logging component may maintain event logging criteria specifying which types of events should be logged. If the event should be logged, the client-side logging component may queue the event information and return execution control the client module. The event information may then be asynchronously retrieved from the event queue and sent to a server-side logging component. The server-side logging component may persistently log the event information in any of various ways, e.g., by storing it in a file, a database, etc. Processes running on multiple computers may call the server-side logging component to log events, via a client-side logging component instance associated with the process. A logging administration tool may be utilized in order to set event logging criteria. In response to being configured with new event logging criteria information, the server-side logging component may automatically propagate the logging criteria information to each of the client-side logging components. The client-side logging components may then being using the new logging criteria, dynamically changing the filtering of events that are sent to the server-side logging component.

A system for operating multiple independent terminals of grouped, locally connected input and output devices through a single graphical user interface layer running on a computer comprising an event queue module for receiving each input command from each input device; an event handler module for receiving the input commands from the event queue module and directing input commands from specific input devices via corresponding socket / listeners of the single graphical user interface layer to corresponding ones of multiple pointers, focuses and client applications based on predetermined associations between grouped devices and respective ones of the socket / listeners; and an output module for directing output commands from each socket / listener to respective ones of the output devices based on the predetermined associations. A system for creating multiple independent terminals of grouped input and output devices connected to and for operation by a single computer comprising a configuration module for simultaneously providing unique output commands to ungrouped output devices to cause the output devices to respectively provide a unique input directive to a user; the configuration module also for receiving unique input commands from individual ungrouped input devices, each unique input command corresponding to a respective one of the unique output directives; and an association module for, in response to the receiving, commonly associating with a unique group identifier each of corresponding input and output devices and respective ones of multiple pointers and focuses.

A method, system, program product and computer data structure for providing for two levels of server virtualization. A first hypervisor enables multiple logical partitions to share a set of resources and provides a first level of virtualization. A second hypervisor enables multiple, independent virtual machines to share the resources that are assigned to a single logical partition and provides a second level of virtualization. All events for all of the virtual machines within said single logical partition are grouped into a single partition-owned event queue for receiving event notifications from the shared resources for that single logical partition. A request for an interrupt is signaled for the grouped events from the partition-owned event queue for the demultiplexing of grouped events, by the machine, from the partition-owned event queue into individual, virtualized event queues that are allocated on a per virtual machine basis.

Web-based event / state-driven mechanisms and methods for simplifying communication between networked multifunction devices, such as copiers, printers, facsimile machines and multifunction devices using a networked database for the creation and presentation of device metrics and status data. Web-based multifunction performance metrics and calculations themselves are created within concurrent (multiple instances) of Web objects, wherein a Web object is a self-contained entity with data and a state machine lifecycle. State changes inside and outside the Web object are made by sending events to event queues and routing them to other state machines within other Web objects or instances of the same Web object. Data and events between Web objects are formed into a regular event syntax providing a simpler method of communication than those of procedural programming approaches. The arguments of the events are processed by specific instances of state machines that compose each Web object to perform an appropriate action. The metrics displays and corresponding calculations within the Web object's state machine are highly self-contained and concurrent, hiding networked database contention and database locking, and enforcing atomicity with it's runtime software. Calculations are performed and displayed from within a very small context within each Web object's state minimizing external communications and further simplifying software application development efforts.

Techniques are disclosed for communicating to remote devices information about change events related to changes in access to an enterprise system. A device access management system may facilitate communication about a change event to the remote devices. Information about a change event may be stored in a change event object based on the type of change event (e.g., a policy change, an application change, and a settings change). A change event queue may persistently store information corresponding to change events. One or more computing nodes may be scheduled to execute an action process for each change event based on the type of the change event. A computing node may communicate information (e.g., an instruction to implement adjust access) about a change event to remote devices. A change event may persist on the queue until all remote devices are notified about the change event.

One embodiment of an event management system, operating on a computer system having event producers and event consumers, includes an initial event handler program and an event queue having a first event. The initial event handler program retrieves the first event from the event queue for event processing. This event processing returns a first response to the initial event handler program, wherein the initial event handler program manages the first event on the event queue based on the first response.

Aspects of a method and system for an operating system (OS) virtualization-aware network interface card (NIC) are provided. A NIC may provide direct I / O capabilities for each of a plurality of concurrent guest operating systems (GOSs) in a host system. The NIC may comprise a GOS queue for each of the GOSs, where each GOS queue may comprise a transmit (TX) queue, a receive (RX) queue, and an event queue. The NIC may communicate data with a GOS via a corresponding TX queue and RX queue. The NIC may notify a GOS of events such as down link, up link, packet transmission, and packet reception via the corresponding event queue. The NIC may also support unicast, broadcast, and / or multicast communication between GOSs. The NIC may also validate a buffered address when the address corresponds to one of the GOSs operating in the host system.

Dynamic administration of event pools for relevant event and alert analysis during event storms including receiving, by an events analyzer from an events queue, a plurality of events from one or more components of the distributed processing system, each event including an occurred time and a logged time; creating, by the event analyzer, an events pool; determining whether an arrival rate of the events from the components of the distributed processing system is greater than a predetermined threshold; if the arrival rate is greater than the predetermined threshold, assigning, by the events analyzer, a plurality of events to the events pool in dependence upon their occurred time; and if the arrival rate is not greater than the predetermined threshold, assigning, by the events analyzer, a plurality of events to the events pool in dependence upon their logged time.

Relevant alert delivery including determining, by an events listener associated with an event queue, whether one or more events in an events queue have not been assigned to any events pool by any event analyzer; and if one or more events in the events queue have not been assigned to any events pool, identifying by the events listener in dependence upon the event analysis rules one or more alerts; sending by the event listener to an alerts queue all the alerts identified by the event listener; the alerts queue having an associated alerts listener; determining whether one or more alerts in the alerts queue have not been assigned to any alert pool; if one or more alerts in the alerts queue have not been assigned to any alerts pool, and determining in dependence upon alert analysis rules whether to suppress the alerts; and transmitting the unsuppressed alerts.

Method of managing interaction between a host subsystem and a peripheral device. Roughly described, the peripheral device writes an event into an individual event queue, and in conjunction therewith, also writes a wakeup event into an intermediary event queue. The wakeup event identifies the individual event queue. The host subsystem, in response to retrieval of the wakeup event from the intermediary event queue, activates an individual event handler to consume events from the individual event queue.

Methods, systems and products are provided for dynamic administration of component event reporting in a distributed processing system including receiving, by an events analyzer from an events queue, a plurality of events from one or more components of the distributed processing system; determining, by the events analyzer in dependence upon the received events and one or more event analysis rules, to change the event reporting rules of one or more components; and instructing, by the events analyzer, the one or more components to change the event reporting rules.

An information processing system is provided which includes an interrupt table including a plurality of entries relating to interrupts requested by entries in a plurality of event queues. The entries of the interrupt table reference identifiers, and the identifiers are assigned to events from a pool of identifiers in accordance with an order in which the events occur.

A system for providing power substation event data to one or more master stations including: a plurality of intelligent electronic devices (IEDs) monitoring electrical power systems in a power substation, wherein each IED collects event data regarding conditions of a monitored electrical power system and queues the event data for transmission; a data concentrator in data communication with the IEDs, the concentrator including a database for storing IED event data transmitted from the event data queued in the IEDs and event queues in the concentrator for buffering IED event data from the database, and at least one master station in data communication with the concentrator, wherein the master station reads IED event data from event queues in the concentrator, and further the concentrator clears the event queues after the data is read by the master station.

Methods, systems, and computer program products for restarting event and alert analysis after a shutdown in a distributed processing system are provided. Embodiments include identifying, by an incident analyzer, a shutdown condition of the distributed processing system, the incident analyzer including a plurality of event analyzers and a monitor that monitors the plurality of event analyzers; and determining, by the incident analyzer, whether the shutdown was a planned shutdown or an unplanned shutdown; if the shutdown was planned, storing, by the incident analyzer, an identification of the last event in an event log that was injected in an event queue at the time of the planned shutdown and restarting, by the incident analyzer, event and alert analysis using the next event identified in the event log; and if the shutdown was unplanned, for each event analyzer, identifying the last event included in the last event pool that the event analyzer closed; and restarting, by the incident analyzer, event and alert analysis at the event analyzer using the next event received by the event analyzer after the identified last event.

A method and system for event publication and subscription with an event channel from user level and kernel level are disclosed. The system comprises an event channel. The event channel includes an event queue for an event sent by a publisher. Additionally, the event channel has a plurality of subscriber-based queues each corresponding to a subscriber. If the corresponding subscriber has subscribed to receive delivery of the event, the subscriber-based queue includes the event. Moreover, the event channel further comprises a dispatcher for dispatching based on filtering criteria the event to the subscriber-based queue if the corresponding subscriber has subscribed to receive delivery of the event, and a delivery mechanism for delivering the event from the subscriber-based queue to the corresponding subscriber. The publisher can be a user level publisher or a kernel level publisher. The subscriber can be a user level subscriber or a kernel level subscriber.

Methods, systems, and computer program products for restarting event and alert analysis after a shutdown in a distributed processing system are provided. Embodiments include identifying, by an incident analyzer, a shutdown condition of the distributed processing system; and determining, by the incident analyzer, whether the shutdown was a planned shutdown or an unplanned shutdown; if the shutdown was planned, storing, by the incident analyzer, an identification of the last event in an event log that was injected in an event queue at the time of the planned shutdown and restarting, by the incident analyzer, event and alert analysis using the next event identified in the event log; if the shutdown was unplanned, identifying, by the incident analyzer, a previously configured restart mode; selecting, by the incident analyzer, an identification of a restart event in the event log according to the previously configured restart mode; and restarting, by the incident analyzer, event and alert analysis using the restart event identified in the event log.

An Event Manager receives events requiring action. The events are parsed into event action types which are placed in an Event Queue. Program agents in a pool of agents are dynamicly instantiated and retired from the pool based on the number of queued events by type. Program agents, when available, initiate a search for a work entry on the Event Queue that is of a type that the agent can handle. When an agent finds work, the corresponding Event Queue entry is marked as assigned to the agent and the agent performs the action associated with the work entry.

An information processing system is provided which includes a plurality of system resources, and an event queue having a maximum number of entries. An event recording mechanism of the information processing system is operable to make entries regarding events in the event queue, wherein the entries are limited to a predetermined number of active entries in the event queue per each type of event per each of the system resources. In a particular embodiment, the number of entries per each type of event for each of the system resources is limited to one.

A system for operating multiple independent terminals of grouped, locally connected input and output devices through a single graphical user interface layer running on a computer comprising an event queue module for receiving each input command from each input device; an event handler module for receiving the input commands from the event queue module and directing input commands from specific input devices via corresponding socket / listeners of the single graphical user interface layer to corresponding ones of multiple pointers, focuses and client applications based on predetermined associations between grouped devices and respective ones of the socket / listeners; and an output module for directing output commands from each socket / listener to respective ones of the output devices based on the predetermined associations. A system for creating multiple independent terminals of grouped input and output devices connected to and for operation by a single computer comprising a configuration module for simultaneously providing unique output commands to ungrouped output devices to cause the output devices to respectively provide a unique input directive to a user; the configuration module also for receiving unique input commands from individual ungrouped input devices, each unique input command corresponding to a respective one of the unique output directives; and an association module for, in response to the receiving, commonly associating with a unique group identifier each of corresponding input and output devices and respective ones of multiple pointers and focuses.

Methods and systems for application framework development for wireless devices are provided herein. Aspects of the method may include acquiring an MMI event from an MMI event queue within the MMI wireless framework. An identity of the acquired MMI event may be determined and the acquired MMI event may be dispatched to an event handler based on the determined identity of the acquired event. If the acquired MMI event comprises a timing event, the acquired MMI event may be dispatched to an MMI event owner within the MMI wireless framework. If the acquired MMI event comprises a keypad event, the acquired MMI event may be dispatched to a currently active MMI view within the MMI wireless framework. If the acquired MMI event comprises an addressed event, the acquired MMI event may be dispatched to a destination handler within the MMI wireless framework.

Systems and Methods are provided for coordinating computing functions to accomplish a task. The system includes a plurality of standardized executable application modules (SEAMs), each of which is configured to execute on a processor to provide a unique function and to generate an event associated with its unique function. The system includes a configuration file that comprises a dynamic data store (DDS) and a static data store (SDS). The DDS includes an event queue and one or more response queues. The SDS includes a persistent software object that is configured to map a specific event from the event queue to a predefined response record and to indicate a response queue into which the predefined response record is to be placed. The system further includes a workflow service module, the work flow service module being configured to direct communication between the SDS, the DDS and each of the plurality of SEAMs.

The present invention relates to systems, apparatus, and methods for utilizing user interface (UI) snooping to optimize network connections. The method includes accessing, by a client proxy running on a client system, a UI events queue. The UI events queue is stored on the client system. The method further includes identifying events within the UI events queue. The identifying includes filtering the events for events to be optimized. The method further includes, based on the identified events, determining at least one command, and optimizing the at least one command, and executing the optimized command.

A method and system are provided for managing application programs with non-responsive user interfaces, possibly due to a bottleneck in handling events / messages. The method and system make an apparently frozen application user interface responsive so as to permit alternative tasks be executed or close the hung application. This is enabled by implementing routines to (a) detect if an application is hung, (b) replace the user interface for the hung application with a ghost interface, implemented by a separate thread, that permits system functionality such as sizing, minimization and closing of the application, and (c) destroying the ghost interface if the hung application becomes responsive again along with restoring the application's user interface along with updated event queues. Furthermore, creation of the ghost user interface is accompanied by placing a high priority special event in the hung application's queue to detect renewed responsiveness without requiring explicit monitoring.

A message signaled interrupt (MSI) specifying an input / output (I / O) address in I / O address space is received. In response to receipt of the MSI, a translation data structure is accessed and the I / O address is translated into a physical memory address by reference to the translation data structure. The MSI is then enqueued in an event queue at the physical memory address for subsequent servicing.

A platform for socializing devices includes a knowledge database, a rules database, an event processor, an event queue, an advocate message processor, and an advocate message queue. A plurality of software advocates, each corresponding to a respective one of the devices, resides on the advocate message processor. The knowledge database includes a plurality of private social graphs, each corresponding to a respective one of the advocates. A policy database includes rules governing the relationships between and among the advocates and devices. The event processor is configured to process incoming payloads based on the knowledge database and the policy database.

The present invention is a method, system and apparatus for event notification framework in a system of dynamically aggregated logical components. In accordance with the present invention, an event notification and management system can include one or more logical components coupled to corresponding dynamic proxies. An event notification service can be communicatively linked to one or more subscribing processes. Finally, an event queue can be disposed between the dynamic proxies and the event notification service.