The Experts below are selected from a list of 102831 Experts worldwide ranked by ideXlab platform

Paolo Romano - One of the best experts on this subject based on the ideXlab platform.

  • ensuring e transaction with asynchronous and uncoordinated Application Server replicas
    IEEE Transactions on Parallel and Distributed Systems, 2007
    Co-Authors: Francesco Quaglia, Paolo Romano
    Abstract:

    A recently proposed abstraction, called e-transaction (exactly-once transaction), specifies a set of properties capturing end-to-end reliability aspects for three-tier Web-based systems. In this paper we propose a distributed protocol ensuring the e-transaction properties for the general case of multiple, autonomous back-end databases. The key idea underlying our proposal consists in distributing, across the back-end tier, some recovery information reflecting the transaction processing state. This information is manipulated at low cost via local operations at the database side, with no need for any form of coordination among asynchronous replicas of the Application Server within the middle-tier. Compared to existing solutions, our protocol has therefore the distinguishing features of being both very light and highly scalable. The latter aspect makes our proposal particularly attractive for the case of very high degree of replication of the Application access point, with distribution of the replicas within infrastructures geographically spread on public networks over the Internet (e.g., Application delivery networks), namely, a configuration that also provides the advantages of reduced user perceived latency and increased system availability

  • reliability in three tier systems without Application Server coordination and persistent message queues
    ACM Symposium on Applied Computing, 2005
    Co-Authors: Francesco Quaglia, Paolo Romano
    Abstract:

    When dealing with fault tolerance in three-tier systems, two major problems need to be addressed, that is how to prevent duplicate transaction executions when classical timeout based retransmission logics are employed, and how to ensure the agreement among the back-end databases despite failures (a transaction needs to be aborted or committed at all the involved databases independently of the failure scenario). In this paper we address these problems by proposing a fault tolerant protocol that, unlike previous solutions, (i) avoids the additional phase of storing the client request into a persistent message queue and (ii) avoids explicit coordination of middle tier Application Servers (during both normal behavior and fail-over). Our protocol reduces therefore the overhead imposed on the end-to-end interaction, thus improving user perceived responsiveness, and provides better scalability.

  • ensuring e transaction through a lightweight protocol for centralized back end database
    International Symposium on Parallel and Distributed Processing and Applications, 2004
    Co-Authors: Paolo Romano, Francesco Quaglia, Bruno Ciciani
    Abstract:

    A reasonable end-to-end reliability guarantee for three-tier systems, called e-Transaction (exactly-once Transaction), has been recently proposed. This work presents a lightweight e-Transaction protocol for centralized back-end database. Our protocol does not require coordination among the replicas of the Application Server and does not rely on any assumption for what concerns the processing order of messages exchanged among processes, as instead required by some existing solution.

Carla Sadtler - One of the best experts on this subject based on the ideXlab platform.

  • ibm websphere Application Server express v5 0 2 developer handbook
    2003
    Co-Authors: Carla Sadtler, Justin Bogers, Shailen Borkar, Andri Firtiyan
    Abstract:

    Use WebSphere Application Server - Express to develop Applications Test and deploy Applications Learn by example This IBM Redbook introduces IBM WebSphere Application Server - Express V5 , an IBM offering that provides a comprehensive development tool and a single-Server Application Server environment designed for small and medium business customers who want to have a Web presence for their business. This publication shows how to use WebSphere Application Server - Express to build, test, and deploy Web Applications. It will help you install the product, build a simple Web Application, and deploy that Application to the Server. This publication is applicable to the Linux and Windows platforms.

  • websphere Application Server express v5 0 2 administrator handbook
    2003
    Co-Authors: Carla Sadtler
    Abstract:

    Configure the Server environment Deploy Applications Problem determination tips Beginning with WebSphere Application Server - Express V5.0.1, the recommended way to administer production Servers is through the Web-based administrative console. This IBM Redbook describes the installation planning and administration of WebSphere Application Server - Express on Windows and UNIX in a production environment. It includes information about development and production topologies, configuring and securing the Server, problem determination, and deploying Applications. IBM WebSphere Application Server - Express V5.02 now includes the Web Server plugin feature for customers who choose to use an external Web Server for security purposes. This redbook has been updated to include the Web Server plugin. Application developers should continue to use IBM WebSphere Application Server - Express V5.0.2 Developer Handbook. The Server administration for test environments is still available through the Studio Site Developer tool. iSeries users should use WebSphere Application Server - Express V5.0 for iSeries, REDP3624 for supplemental information specific to iSeries.

S K Shrivastava - One of the best experts on this subject based on the ideXlab platform.

  • transaction manager failover a case study using jboss Application Server
    International Conference on Move to Meaningful Internet Systems, 2006
    Co-Authors: Achmad Imam Kistijantoro, Graham Morgan, S K Shrivastava
    Abstract:

    This paper describes, for the case of Enterprise Java Bean components and JBoss Application Server, how replication for availability can be supported to tolerate Application Server/transaction manager failures Replicating the state associated with the progression of a transaction (i.e., which phase of two-phase commit is enacted and the transactional resources involved) provides an opportunity to continue a transaction using a backup transaction manager if the transaction manager of the primary fails Existing Application Servers do not support this functionality The paper discusses the technical issues involved and shows how a solution can be engineered.

  • Transaction Manager Failover: A Case Study Using JBOSS Application Server
    2006
    Co-Authors: Achmad Imam Kistijantoro, Graham Morgan, S K Shrivastava
    Abstract:

    The extension of object-oriented middleware to component-oriented middleware is now commonplace, with many distributed Applications structured as remote clients invoking services constructed from components. An advantage components offer over objects is that only the business logic of an Application needs to be addressed by a programmer. An Application Server hosts components, managing supporting services to provide the execution environment for components. A transaction manager within an Application Server assumes responsibility for managing the execution of transactions. Failure of an Application Server instance could result in abortion of ongoing transactions that are being managed by the transaction manager on that Server. This paper describes, for the case of Enterprise Java Bean components and JBoss Application Server, how replication for availability can be supported to tolerate Application Server/transaction manager failures. Replicating the state associated with the progression of a transaction (i.e., which phase of two-phase commit is enacted and the transactional resources involved) provides an opportunity to continue a transaction using a backup transaction manager if the transaction manager of the primary fails

Francesco Quaglia - One of the best experts on this subject based on the ideXlab platform.

  • ensuring e transaction with asynchronous and uncoordinated Application Server replicas
    IEEE Transactions on Parallel and Distributed Systems, 2007
    Co-Authors: Francesco Quaglia, Paolo Romano
    Abstract:

    A recently proposed abstraction, called e-transaction (exactly-once transaction), specifies a set of properties capturing end-to-end reliability aspects for three-tier Web-based systems. In this paper we propose a distributed protocol ensuring the e-transaction properties for the general case of multiple, autonomous back-end databases. The key idea underlying our proposal consists in distributing, across the back-end tier, some recovery information reflecting the transaction processing state. This information is manipulated at low cost via local operations at the database side, with no need for any form of coordination among asynchronous replicas of the Application Server within the middle-tier. Compared to existing solutions, our protocol has therefore the distinguishing features of being both very light and highly scalable. The latter aspect makes our proposal particularly attractive for the case of very high degree of replication of the Application access point, with distribution of the replicas within infrastructures geographically spread on public networks over the Internet (e.g., Application delivery networks), namely, a configuration that also provides the advantages of reduced user perceived latency and increased system availability

  • reliability in three tier systems without Application Server coordination and persistent message queues
    ACM Symposium on Applied Computing, 2005
    Co-Authors: Francesco Quaglia, Paolo Romano
    Abstract:

    When dealing with fault tolerance in three-tier systems, two major problems need to be addressed, that is how to prevent duplicate transaction executions when classical timeout based retransmission logics are employed, and how to ensure the agreement among the back-end databases despite failures (a transaction needs to be aborted or committed at all the involved databases independently of the failure scenario). In this paper we address these problems by proposing a fault tolerant protocol that, unlike previous solutions, (i) avoids the additional phase of storing the client request into a persistent message queue and (ii) avoids explicit coordination of middle tier Application Servers (during both normal behavior and fail-over). Our protocol reduces therefore the overhead imposed on the end-to-end interaction, thus improving user perceived responsiveness, and provides better scalability.

  • ensuring e transaction through a lightweight protocol for centralized back end database
    International Symposium on Parallel and Distributed Processing and Applications, 2004
    Co-Authors: Paolo Romano, Francesco Quaglia, Bruno Ciciani
    Abstract:

    A reasonable end-to-end reliability guarantee for three-tier systems, called e-Transaction (exactly-once Transaction), has been recently proposed. This work presents a lightweight e-Transaction protocol for centralized back-end database. Our protocol does not require coordination among the replicas of the Application Server and does not rely on any assumption for what concerns the processing order of messages exchanged among processes, as instead required by some existing solution.

Remy Maucherat - One of the best experts on this subject based on the ideXlab platform.

  • network performance of the jboss Application Server
    Local Computer Networks, 2013
    Co-Authors: Nabil Benothman, Jean-frederic Clere, Eryk Schiller, Peter Kropf, Remy Maucherat
    Abstract:

    JBoss Application Server (AS) uses java.io and the Apache Portable Runtime (APR) project to provide its HTTP connectors. Due to new features of upcoming specifications of the Java Enterprise Edition (Java EE), the existing connectors shall be replaced by modern non blocking Input/Outputs (I/Os). In this study, we review some modern I/O frameworks such as NIO.2 introduced by Java SE 7 and XNIO3 developed by JBoss. We compare their network performance by running a series of stress tests on client-Server Applications of limited functionality. As a result, we select NIO.2 as the most appropriate framework to specify and implement a new JBoss connector. Finally, we compare our newly implemented Java connector against the existing APR-based one by means of network performance measures.