会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 3. 发明授权
    • Methods, systems and computer program products for synchronization of queue-to-queue communications
    • 用于队列到队列通信同步的方法,系统和计算机程序产品
    • US06401136B1
    • 2002-06-04
    • US09191637
    • 1998-11-13
    • Kathryn H. BrittonAndrew P. CitronBarron C. Housel, IIIAjamu Akinwunmi Wesley
    • Kathryn H. BrittonAndrew P. CitronBarron C. Housel, IIIAjamu Akinwunmi Wesley
    • G66F946
    • G06F9/546
    • Methods, systems, and computer program products are provided for communicating between a source device and a destination device over an external communication link by transmitting a message stored in a source persistent queue at the source device over the external communication link to the destination device. The transmitted message has transmitted with it an associated sequence identifier which identifies the message stored in the source persistent queue. The transmitted message and the associated sequence identifier are received at the destination device and stored in a destination persistent queue at the destination device. Occasionally, a commit message is transmitted to the source device from the destination device which identifies a sequence identifier associated with received message which has been persistently stored in the destination persistent queue. The persistently stored message in the destination persistent queue is made available to users of the destination device independent of whether a commit message identifying the message has been transmitted to the source device.
    • 提供方法,系统和计算机程序产品,用于通过外部通信链路通过外部通信链路发送存储在源设备的源持久队列中的消息,在源设备和目的地设备之间进行通信。 发送的消息已经与其一起发送了相关联的序列标识符,其标识存储在源持久队列中的消息。 发送的消息和相关联的序列标识符在目的地设备处被接收并存储在目的地设备的目的地持续队列中。 有时候,从目的地设备向源设备发送提交消息,该目的设备标识与已经持久存储在目的地持续队列中的接收到的消息相关联的序列标识符。 目的地持续队列中持续存储的消息对于目标设备的用户是可用的,而与标识消息的提交消息是否已经被发送到源设备无关。
    • 4. 发明授权
    • System for managing unit-of-work identifiers when a chained,
distributed, two phase commit transaction system is severed
    • 当链接,分布式,两阶段提交事务系统被切断时,用于管理工作标识符的系统
    • US5371886A
    • 1994-12-06
    • US164656
    • 1993-12-09
    • Kathryn H. BrittonAndrew P. CitronBruce G. Lindsay
    • Kathryn H. BrittonAndrew P. CitronBruce G. Lindsay
    • G06F12/00G06F11/14G06F15/40
    • G06F11/1402Y10S707/99953
    • A method of managing unit-of-work identifiers in a chained distributed database transaction system. The system has a plurality of processing nodes which are logically connected to form a tree. Normally, each node automatically increments its present identifier at the end of processing each transaction to derive the next transaction identifier. However, in response to a failure condition which results in a severed tree, the distributed database that now reside in the first and second subtrees that result from the severance are forced to consistent states. The transaction identifier is incremented in each of the nodes of the first subtree. Transaction work in the first subtree then proceeds with the incremented identifier. The second subtree is dismantled. In response to a nonfailure condition which results in a severed tree, the distributed database in the first and second subtrees that result from the nonfailure severance is committed to a permanent state. The transaction identifier in each of the nodes of the first subtree is incremented. Transaction work in the first subtree then proceeds with the incremented identifier. A new transaction identifier is generated and propagated to all nodes of the second subtree. Transaction work in the second subtree then proceeds with the new identifier.
    • 一种在链式分布式数据库事务系统中管理工作单元标识符的方法。 系统具有多个处理节点,逻辑上连接以形成一个树。 通常,每个节点在处理每个事务结束时自动递增其当前标识符以导出下一个事务标识符。 然而,响应于导致切断的树的故障条件,现在驻留在由切断导致的第一和第二子树中的分布式数据库被强制为一致的状态。 交易标识符在第一个子树的每个节点中递增。 然后在第一个子树中进行事务处理,然后继续增加标识符。 第二个子树被拆除。 响应导致切断的树的非失败条件,由非故障中断导致的第一和第二子树中的分布式数据库被承诺为永久状态。 第一个子树的每个节点中的事务标识符递增。 然后在第一个子树中进行事务处理,然后继续增加标识符。 生成新的事务标识符并将其传播到第二个子树的所有节点。 然后,第二个子树中的事务工作继续使用新的标识符。
    • 6. 发明授权
    • Method and apparatus for improving database reliability and response
time in a distributed transaction processing system
    • 在分布式事务处理系统中提高数据库可靠性和响应时间的方法和装置
    • US5432926A
    • 1995-07-11
    • US985391
    • 1992-12-04
    • Andrew P. CitronJames P. Gray
    • Andrew P. CitronJames P. Gray
    • G06F12/00G06F11/14G06F17/30G06F11/00
    • G06F17/30371
    • A transaction network in which, in appropriate cases, a transaction is allowed to complete at each node and new work to commence, before all transaction resources at the node actually complete a syncpoint operation. This desirable result is obtained without the risk of unreported database corruption. At each node in response to a prepare to commit syncpoint command from a parent node, the node in question determines if it or any of its descendant nodes can make a unilateral heuristic decision to commit or backout the transaction irrespective of whether or not the final syncpoint command is to commit or backout. Each node informs its parent node that it is reliable or unreliable. Reliable means that neither this node nor any of its descendant nodes can make a unilateral heuristic decision. Unreliable means that this node or one or more of the descendant nodes may make such a unilateral decision. If a node is reliable, the transaction is released at the node after receiving and propagating to descendant nodes the final commit or backout command and before completion or acknowledgement of completion of the commit or backout command by the node or any of its descendant nodes. If the node is unreliable, then it waits for acknowledgement of completion of the commit or backout syncpoint operation at all unreliable nodes, including itself, before releasing the transaction at the node.
    • 一种交易网络,在适当的情况下,允许交易在每个节点完成并且新工作开始,在节点的所有事务资源实际完成同步点操作之前。 获得这个理想的结果,而不会导致未报告的数据库损坏。 在每个节点响应于准备从父节点提交syncpoint命令时,所讨论的节点确定其或其任何后代节点是否可进行单边启发式决定来提交或退回该事务,而不管最终同步点是否 命令是提交或退出。 每个节点通知其父节点它是可靠的或不可靠的。 可靠的意味着这个节点和它的任何后代节点都不能进行单边启发式决策。 不可靠意味着该节点或一个或多个后代节点可以进行单方面决策。 如果一个节点是可靠的,则在节点或其后代节点完成或完成提交或退出命令之后,在接收到传播到后代节点的最后提交或退出命令之后,该节点被释放。 如果节点不可靠,则在释放节点处的事务之前,它将等待所有不可靠节点(包括其自身)完成提交或退出同步点操作的确认。