JDBInsight 2.0 Released - True JDBC Transaction Analysis !!!

Check out the new product release and revised documentation at:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
PRESS RELEASE
=============
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
of J2EE performance management products from JInspired.
JDBInsight is the first product to effectively integrate Java profiling information
with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
analysis, cpu, blocking and waiting measurements at the transaction path level.
Clock measurements are adjusted for blocking, waiting and gc pauses. New features
in this release
- New console user interface: Many new informative visualizations of J2EE transactions
and performance execution profiles have been added. Including call stack graphs,
entry point tree maps, sequence diagrams, call stack and transaction transcripts.
Additional views included allow for navigation of the performance profile via
database table or column, Java package, class, or method, technology classification,
SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE
server administrators can now better understand the interaction of various Java
enterprise technologies with corporate databases. Classifications are available
for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way
to communicate with multiple servers without having to use a graphical user interface.
This facilitates the streamlined connection, activation and deactivation of profiles
on local or remote servers with the ability to control multiple servers from a
single terminal. The terminal environment provides a powerful environment to create
and schedule snapshot information, in order to monitor servers at regular intervals,
with the ability to store and retrieve snapshots from any mounted drive, as well
as providing a rich set of commands, that can be executed from saved scripts,
to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management
product to have the ability to detect and present resource transaction demarcations
- allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for
each JDBC interception point create a resource object. When a JDBC resource changes
state the allocation site counters are updated. This helps to pinpoint source
code locations where resource objects are created and not closed properly or freed
from memory. Because an interception is a combination of call stack and SQL the
view caters for generic J2EE application frameworks which create objects based
on application parameters and callers.
- Xml export: Various statistical measurements can be viewed in Xml format and
copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of
overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying
the performance tuning and testing of J2EE(tm) applications, which access data
through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
analysis can encompass transaction executions, from multiple J2EE(tm) containers.
JDBInsight captures timing and execution information for enterprise data accessed
by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
Entity Bean using a container's persistence engine. JDBInsight can also profile
non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management
tools on the market is that JDBInsight provides analysis from a sequence perspective
instead of simply showing a call tree. Inefficiencies in J2EE applications occur
mainly at the transaction level such as repeating the execution of a particular
SQL locally and globally. JDBInsight facilitates the recognition of database interaction
patterns that exhibit inefficiencies when viewed in terms of the sequential execution
of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
Application Performance Tuning and Testing that focuses directly on early identification
within the development and testing lifecycle. Jinspired offers sophisticated analytical
tools, that capture transactional behaviour and performance timing information,
across multiple containers in a single console, and presents this information
intuitively to the user "Visualizing the Invisible".

Check out the new product release and revised documentation at:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
PRESS RELEASE
=============
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
of J2EE performance management products from JInspired.
JDBInsight is the first product to effectively integrate Java profiling information
with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
analysis, cpu, blocking and waiting measurements at the transaction path level.
Clock measurements are adjusted for blocking, waiting and gc pauses. New features
in this release
- New console user interface: Many new informative visualizations of J2EE transactions
and performance execution profiles have been added. Including call stack graphs,
entry point tree maps, sequence diagrams, call stack and transaction transcripts.
Additional views included allow for navigation of the performance profile via
database table or column, Java package, class, or method, technology classification,
SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE
server administrators can now better understand the interaction of various Java
enterprise technologies with corporate databases. Classifications are available
for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way
to communicate with multiple servers without having to use a graphical user interface.
This facilitates the streamlined connection, activation and deactivation of profiles
on local or remote servers with the ability to control multiple servers from a
single terminal. The terminal environment provides a powerful environment to create
and schedule snapshot information, in order to monitor servers at regular intervals,
with the ability to store and retrieve snapshots from any mounted drive, as well
as providing a rich set of commands, that can be executed from saved scripts,
to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management
product to have the ability to detect and present resource transaction demarcations
- allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for
each JDBC interception point create a resource object. When a JDBC resource changes
state the allocation site counters are updated. This helps to pinpoint source
code locations where resource objects are created and not closed properly or freed
from memory. Because an interception is a combination of call stack and SQL the
view caters for generic J2EE application frameworks which create objects based
on application parameters and callers.
- Xml export: Various statistical measurements can be viewed in Xml format and
copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of
overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying
the performance tuning and testing of J2EE(tm) applications, which access data
through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
analysis can encompass transaction executions, from multiple J2EE(tm) containers.
JDBInsight captures timing and execution information for enterprise data accessed
by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
Entity Bean using a container's persistence engine. JDBInsight can also profile
non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management
tools on the market is that JDBInsight provides analysis from a sequence perspective
instead of simply showing a call tree. Inefficiencies in J2EE applications occur
mainly at the transaction level such as repeating the execution of a particular
SQL locally and globally. JDBInsight facilitates the recognition of database interaction
patterns that exhibit inefficiencies when viewed in terms of the sequential execution
of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
Application Performance Tuning and Testing that focuses directly on early identification
within the development and testing lifecycle. Jinspired offers sophisticated analytical
tools, that capture transactional behaviour and performance timing information,
across multiple containers in a single console, and presents this information
intuitively to the user "Visualizing the Invisible".

Similar Messages

  • JDBInsight 2.0 Released - True J2EE/JDBC Resource Transaction Analysis !!

    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation of J2EE performance management products from JInspired.
    Downloads: http://www.jinspired.com/products/jdbinsight/downloads/index.html
    JDBInsight is the first product to effectively integrate Java profiling information with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived from its support of the Java VM Profiling Interface (JVMPI) such as Java call stack analysis, cpu, blocking and waiting measurements at the transaction path level. Clock measurements are adjusted for blocking, waiting and gc pauses. New features in this release
    - New console user interface: Many new informative visualizations of J2EE transactions and performance execution profiles have been added. Including call stack graphs, entry point tree maps, sequence diagrams, call stack and transaction transcripts. Additional views included allow for navigation of the performance profile via database table or column, Java package, class, or method, technology classification, SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE server administrators can now better understand the interaction of various Java enterprise technologies with corporate databases. Classifications are available for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets, JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way to communicate with multiple servers without having to use a graphical user interface. This facilitates the streamlined connection, activation and deactivation of profiles on local or remote servers with the ability to control multiple servers from a single terminal. The terminal environment provides a powerful environment to create and schedule snapshot information, in order to monitor servers at regular intervals, with the ability to store and retrieve snapshots from any mounted drive, as well as providing a rich set of commands, that can be executed from saved scripts, to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management product to have the ability to detect and present resource transaction demarcations - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for each JDBC interception point create a resource object. When a JDBC resource changes state the allocation site counters are updated. This helps to pinpoint source code locations where resource objects are created and not closed properly or freed from memory. Because an interception is a combination of call stack and SQL the view caters for generic J2EE application frameworks which create objects based on application parameters and callers.
    - Xml expor: Various statistical measurements can be viewed in Xml format and copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying the performance tuning and testing of J2EE(tm) applications, which access data through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the access of enterprise data by J2EE(tm) client-, web-, and bean containers. The analysis can encompass transaction executions, from multiple J2EE(tm) containers. JDBInsight captures timing and execution information for enterprise data accessed by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an Entity Bean using a container's persistence engine. JDBInsight can also profile non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management tools on the market is that JDBInsight provides analysis from a sequence perspective instead of simply showing a call tree. Inefficiencies in J2EE applications occur mainly at the transaction level such as repeating the execution of a particular SQL locally and globally. JDBInsight facilitates the recognition of database interaction patterns that exhibit inefficiencies when viewed in terms of the sequential execution of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for Application Performance Tuning and Testing that focuses directly on early identification within the development and testing lifecycle. Jinspired offers sophisticated analytical tools, that capture transactional behaviour and performance timing information, across multiple containers in a single console, and presents this information intuitively to the user "Visualizing the Invisible".

    any one

  • JDBInsight 2.0 Released - True Transaction Analysis !!!

    Check out the product and revised documentation at:
    http://www.jinspired.com/products/jdbinsight/downloads/index.html
    PRESS RELEASE
    =============
    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
    in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
    of J2EE performance management products from JInspired.
    JDBInsight is the first product to effectively integrate Java profiling information
    with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
    from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
    analysis, cpu, blocking and waiting measurements at the transaction path level.
    Clock measurements are adjusted for blocking, waiting and gc pauses. New features
    in this release
    - New console user interface: Many new informative visualizations of J2EE transactions
    and performance execution profiles have been added. Including call stack graphs,
    entry point tree maps, sequence diagrams, call stack and transaction transcripts.
    Additional views included allow for navigation of the performance profile via
    database table or column, Java package, class, or method, technology classification,
    SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE
    server administrators can now better understand the interaction of various Java
    enterprise technologies with corporate databases. Classifications are available
    for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
    JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way
    to communicate with multiple servers without having to use a graphical user interface.
    This facilitates the streamlined connection, activation and deactivation of profiles
    on local or remote servers with the ability to control multiple servers from a
    single terminal. The terminal environment provides a powerful environment to create
    and schedule snapshot information, in order to monitor servers at regular intervals,
    with the ability to store and retrieve snapshots from any mounted drive, as well
    as providing a rich set of commands, that can be executed from saved scripts,
    to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management
    product to have the ability to detect and present resource transaction demarcations
    - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for
    each JDBC interception point create a resource object. When a JDBC resource changes
    state the allocation site counters are updated. This helps to pinpoint source
    code locations where resource objects are created and not closed properly or freed
    from memory. Because an interception is a combination of call stack and SQL the
    view caters for generic J2EE application frameworks which create objects based
    on application parameters and callers.
    - Xml export: Various statistical measurements can be viewed in Xml format and
    copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of
    overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying
    the performance tuning and testing of J2EE(tm) applications, which access data
    through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
    access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
    analysis can encompass transaction executions, from multiple J2EE(tm) containers.
    JDBInsight captures timing and execution information for enterprise data accessed
    by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
    Entity Bean using a container's persistence engine. JDBInsight can also profile
    non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management
    tools on the market is that JDBInsight provides analysis from a sequence perspective
    instead of simply showing a call tree. Inefficiencies in J2EE applications occur
    mainly at the transaction level such as repeating the execution of a particular
    SQL locally and globally. JDBInsight facilitates the recognition of database interaction
    patterns that exhibit inefficiencies when viewed in terms of the sequential execution
    of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
    Application Performance Tuning and Testing that focuses directly on early identification
    within the development and testing lifecycle. Jinspired offers sophisticated analytical
    tools, that capture transactional behaviour and performance timing information,
    across multiple containers in a single console, and presents this information
    intuitively to the user "Visualizing the Invisible".

    Dear Friend...
    ur error concerning...
    "In default.properties, I changed {transaction/sessionbean}.timeout from 0 to 100. Sometime after this, error.log contained:
    "SQL Exception: Table or view 'Entity1BeanTable' already exists in
    schema 'APP'". "
    Ur XML file contains
    "<create-table-deploy>true</create-table-deploy>"
    The first time u deploy ur bean,table is created with the query specified.once u shutdown the server
    "<delete-table-undeploy>false</delete-table-undeploy>" property does not allow the app server to drop the table.
    This leaves u with the above mentioned error/exception when u start the server for the second time as ur server tries to create the table again.Moreover this will not hinder the starting process of the server.
    ganesh

  • IDOC should be created when PO RELEASED Using ME29N Transaction?

    Hi,
       Can anyone suggest me how to create ACCESS SEQUENCE,PROCESS ROUTINES,CONDITION RECORD and all steps in NACE Transaction.
    our requirement is that the IDOC Should get Created Only after Purchase Order is Released using ME29N transaction.
    Can anyone tell how to create IDOC and Send that IDOC to Receipient system for a Purchase Order that is already Released using ME29N transaction

    thank u

  • UserTransaction or JDBC transaction

    Hi,
    please give suggestions...
    We are using a application server with connection pooling
    jsp and servlets are used in project
    for transactions Is userTransaction is better or JDBC transaction is better
    userTransaction may be implemented like this
    try
    getUserTransaction
    transaction.begin
    execute queries
    transaction.commit
    catch()
    transaction.setRollbackOnly
    JDBC Transaction may be implemented like this
    connection.autoCommit=false
    try
    execute queries
    connection.commit
    catch()
    connection.rollback
    which is better for scalability and performance when we have to use transactins
    in jsp/servlets
    regards

    Hi,
    You are talking about using programmatic transactions in J2EE applications.
    When developing J2EE applications, you are recommended to use the transaction mechanism provided by the application servers.
    Sometimes, JDBC transaction can undertake the whole task. However, using JTA (Java Transaction APIs) is the better choice.
    Especially when you are going to develop a lot of components (JavaBeans/ EJBs).
    Imangine if a transaction is to be finished after the coroperation of serveral objects(JavaBean/ EJB instances).
    How can you control the begining and the ending of the transaction by puting codes in these programs?
    But it is very easy to input JTA codes (just like userTransaction etc.) to implement it.
    Therefore, to use JTA is more convinient.
    Additionally, J2EE specifications recommend to use declarative transactions in EJBs. Thus transaction management could be more flexible.
    Good luck.
    Gary Wang
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support/

  • Setting JDBC Transaction Isolation

    https://community.jboss.org/wiki/ConfigDataSources
    As explained in the above URL, with JBoss, you can set the JDBC transaction isolation level in the xml file that contains the JDBC connection information.
    I've been doing some googling, but I'm not clear on how this can be done with WebLogic. Is there some kind of external file where you can set the JDBC transaction isolation level as with JBoss, or is this some kind of change that can only be made in the application code or in some file contained within the application archive file (ear, war, etc.)?

    You can set the isolation in the deployment override weblogic-ejb-jar.xml
    - http://docs.oracle.com/cd/E21764_01/web.1111/e13719/ejb_jar_ref.htm#i1116237
    - http://docs.oracle.com/cd/E21764_01/web.1111/e13719/ejb_jar_ref.htm#i1219612

  • A jdbc transaction error occur

    Hi Everybody
    A jdbc transaction error occur when I deploy the application on the server .
    Below is the stack trace
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot initiate transaction from a connection of "YTSQLS2K" DataSource. Local or distributed transaction has already started.
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
    Any idea about it
    I use the jdbc version in datasource <jdbc-1.x>
    is there a need to replace it with <jdbc-2.0>
    Thank You
    Syed Saifuddin

    Hibernate allows you to choose transaction manager. As Nikolay pointed out, in a JEE envirnment it's prefferable to use JTA transactions. All you need to do is to configure hibernate to use a JTA transaction manager. It is all written in the Hibernate documentations. See
    http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#configuration-j2ee
    and
    http://www.hibernate.org/42.html#A5 .
    The relevant properties that need to be set in the configuration are:
    hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
    and
    hibernate.transaction.manager_lookup_class=<Class that knows how to lookup>
    You need to implement a class that knows how to lookup user transaction in SAP J2EE Egnine.
    The class must extend org.hibernate.transaction.JNDITransactionManagerLookup and only override its abstract method getName (simply returning the lookup string). Then provide the fully qualified name as value of the property and make sure that Hibernate can load the class.
    That should work.
    HTH
    -Georgi
    Message was edited by:
            Georgi Pavlov

  • Account Transaction Analysis query

    Hello,
    I want to create a GL Account Transactions Analysis Report. Can anybody help me with the tables needed for the query?
    Thanks

    Try looking at e.g. report $GL_TOP/reports/US/GLRJED.rdf - main tables are:
    gl_code_combinations cc,
    gl_je_lines jel,
    gl_je_headers jeh,
    gl_je_batches jeb,
    gl_je_categories cat,
    gl_je_sources src
    PS. gl_code_combinations_kfv has concatenated_segments which is very handy rather than dealing with the accounting key flexfield segments separately.
    Gareth
    Blog: http://garethroberts.blogspot.com
    Added PS.

  • Connections not being released from jdbc pool on WLS 5.1 sp8

    I am using WLS 5.1 on RedHat Linux kernel 2.4
    The database is oracle 8.1.6 and I am using the thin jdbc driver as shown in the config below.
    weblogic.jdbc.connectionPool.bobePool=\
    url=jdbc:oracle:thin:@localhost:1521:<sid>,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=10,\
    maxCapacity=22,\
    capacityIncrement=5,\
    allowShrinking=true,\
    shrinkPeriodMins=3,\
    testConnsOnReserve=true,\
    testTable=dual,\
    refreshTestMinutes=5,\
    props=user=<username>;password=<password>
    The problem I am facing is that some connections remain active
    after the SQL query has finished. The no. of open connections
    keep on piling up till the limit of 18 connections is reached and
    ultimately at that point weblogic hangs.
    Has someone else faced this problem...and found a solution??
    Regards,
    Anish Srivastava
    System Analyst
    Baazee.com

    Hi Caren,
    Weblogic doesn't close connections on "time-out". There are some reasons
    for this. The most important one is that even if you have such a
    functionality,
    in case of a connection leak all the available connections can be trashed in
    a matter of milliseconds, so it wouldn't help at all. Though, weblogic does
    close leaked connection when they are garbage collected, but it's easy to
    see
    that it doesn't help a lot, too.
    So you need to make sure that all the JDBC objects are closed properly,
    for example like in this code:
    try {
    } finally {
    try {resultSet.close();} catch (SQLException se) {}
    try {preparedStatement.close();} catch (SQLException se) {}
    try {connection.close();} catch (SQLException se) {}
    Also it's possible that you simply don't have enough connection.
    You could try to increase size of the pool.
    Regards,
    Slava Imeshev
    "Karen Law" <[email protected]> wrote in message
    news:[email protected]...
    Closing the DB connections is important. But is there any parameters to be
    set in the WebLogic configuration in order to release the connection whenit
    hasn't been closed for a long time? Say, setting the connection timeout?
    Many thx!
    Karen
    "Deyan D. Bektchiev" <[email protected]> wrote in message
    news:[email protected]...
    Do you close the DB connections in a finally block after you've finished
    using them?
    If not your application is leaking the connections and sometimes GC is
    not able or does not free those in a timely manner.
    --dejan
    Anish Srivastava wrote:
    I am using WLS 5.1 on RedHat Linux kernel 2.4
    The database is oracle 8.1.6 and I am using the thin jdbc driver as
    shown
    in the config below.
    weblogic.jdbc.connectionPool.bobePool=\
    url=jdbc:oracle:thin:@localhost:1521:<sid>,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=10,\
    maxCapacity=22,\
    capacityIncrement=5,\
    allowShrinking=true,\
    shrinkPeriodMins=3,\
    testConnsOnReserve=true,\
    testTable=dual,\
    refreshTestMinutes=5,\
    props=user=<username>;password=<password>
    The problem I am facing is that some connections remain active
    after the SQL query has finished. The no. of open connections
    keep on piling up till the limit of 18 connections is reached and
    ultimately at that point weblogic hangs.
    Has someone else faced this problem...and found a solution??
    Regards,
    Anish Srivastava
    System Analyst
    Baazee.com

  • JDBC  Transaction is no longer active - status: 'Marked rollback'

    I'm getting the folowing issue, we are not seeing this issue if we recycle the WLS
    Using WLS V10.3.3
    Can any one suggest on this issue, how to reslove this
    85417.772: [Full GC [PSYoungGen: 117504K->0K(234880K)] [PSOldGen: 662564K->665699K(700416K)] 780068K->665699K(935296K) [PSPermGen: 133284K->132438K(225280K)], 30.2876423 secs] [Times: user=31.23 sys=0.68, real=30.32 secs]
    java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 39 seconds
    BEA1-600C65F8B23E363DFDF0]'. No further JDBC access is allowed within this transaction.
    at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:193)
    at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:209)
    at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:99)
    at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
    at com.vzw.pos.cmw.ejb.service.UserProfileService.getNewUserId(Unknown Source)
    at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createUserProfileVO(Unknown Source)
    at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createRosterVO(Unknown Source)
    at com.vzw.pos.cmw.ejb.service.AdministrationBean.getRostersByUserId(Unknown Source)
    at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.__WL_invoke(Unknown Source)
    at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
    at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.getRostersByUserId(Unknown Source)
    at com.vzw.pos.cmw.action.CMWTopFrameAction.setUserRoleInSession(Unknown Source)
    at com.vzw.pos.cmw.action.CMWTopFrameAction.changeLocation(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
    at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at com.vzw.pos.cmw.filters.CMWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3710)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3676)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2272)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2178)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 298 internal data record unavailable (probable closure due idle timeout), event received -32>
    <Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>
    <Aug 23, 2013 10:41:56 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 299 internal data record unavailable (probable closure due idle timeout), event received -32>
    <Aug 23, 2013 10:42:51 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>

    Here is DS configuration
    Initial Capacity:                  75
    Maximum Capacity:                  75
    Capacity Increment:                    1
    Seconds to trust an idle pool connection:     10
    Shrink Frequency:                    900
    Enable Connection Leak Profiling:          False
    Enable Connection Profiling:               False
    Test Frequency:                         120 seconds
    Test Connections on Reserve:               True
    Connection Reserve Timeout:               10 seconds
    Connection Creation Retry Frequency:         1
    Inactive Connection Timeout:               60 second
    Maximum Waiting for Connection:               2147483647
    Statment Cache Type:     LRU
    Statment Cache Size:     10
    Connection Creation Relay Frequency:      1
    Remove Infected Connections Enabled:      True
    Wrap Data types:     True
    Ignore In-use connections:     True

  • Grouping JMS & JDBC transaction with JTA outside of an app server

    hi,
    Can anyone help me or direct me to some code/configuration that shows how to combine JDBC + JMS into one distributed transaction outside of an app server.
    thanks in advance
    michael

    Hi,
              Well, transaction guru's please correct what I say here, but from what I
              understand of your problem here goes:
              If you begin a user transaction your are going to be starting a distributed
              transaction. That's the point of doing it, and hence that's why you have an
              XA. You have more than once resource participating in a transaction, and
              that is what UserTransaction was created for. You can't do it with a local
              transaction, which is for one resource only. I hope that answers "why
              would I need a XA". Even if both resources are hosted by WebLogic, you have
              explicitly asked for a UserTransaction...WL will optimize it if both are on
              same server, but still.. In addition, if you have a true XA data source and
              connection pool, then I would imagine that WL would list the transaction
              system of the DB too....whcih won't be local.
              As for your other problem, it seems to me that you have a connection pool of
              connections that are not XA-aware. If you set the attribute in the
              datasource and enable emulation, then the datasource becomes XA aware, but
              only sort of. WL handles the XA behaviour of that resource, but with
              limitations (you can't have more than one resource with XA emulation in the
              same Tx). If you are using a connection factory with a different store that
              uses XA-emulation, as well as straight JDBC from yet another pool using XA
              emulation, then you will also get problems. Best is to use a real driver
              that supports XA.
              Regards,
              Jon
              

  • JDBC transactions in EJB 3.0

    We have an EJB 3.0 method that call some jdbc DAO methods. This DAO methods called from controller (servlet) works fine, but when called from EJB method raise the following exception:
    "java.sql.SQLException: Cannot call Connection.commit in distributed transaction. Transaction Manager will commit the resource manager when the distributed transaction is committed."
    I think it is a JTA related error. I don't want to use JTA because I can't modify DAO (its a third party library).
    I've tried annotation @TransactionAttribute(value=SUPPORTS) in the EJB method without success.
    There is anyway to say EJB 3.0 not use JTA?
    Thank's

    Frank, yes, I can modify if it is necessary the datasource but, how can I say in the xxxx-jdbc.xml not to use JTA transactions when this data source is called inside a ejb 3.0 method?
    I'm using Jdev11g and the integrated Web Logic Server.
    Thank's

  • How to ensure locks on objects are released after one transaction

    Hi,
    While a program is performing successive operations over the same object, there can be a scenario that after the first operation is completed it may still have a lock over the object. This would result that the object is not available for locking to proceed with the second operation. Hence, the entire record processing would end up in errors. So how we can ensure that after the first operation the locks are released ?
    Regards,
    Ratheesh

    Hi Bhaskaran,
    Please note the Implicit locks set by the system will be deleted whenever the system finds a commit or rollback actions either implicitly or explicitly.
    implicit release of locks takes place whenever there is a CALL SCREEN, LEAVE TO SCREEN,
    SUBMIT PROGRAM, LEAVE TO TRANSACTION, CALL FUNCTION etc.
    for more info Please go through the SAP LUW concept
    Regards
    Ramchander Rao.K

  • JMS and JDBC Transaction

    I have recently tried using the JMS interface for AQ and I have discovered that the queue connection is a separate JDBC connection even if you create a queue connection using an OracleConnection. Is there a workaround for this? It seems a bit strange to have two connections open to the database and be forced to use an XA session in order to get the commits synchronized. Any ideas ? Below is some sample code I am using:
    queueConnection = AQjmsQueueConnectionFactory.createQueueConnection((OracleConnection)connection);
    queueConnection.start();
    QueueSession queueSession = queueConnection.createQueueSession(true, Session.CLIENT_ACKNOWLEDGE);
    AQjmsSession aqs = (AQjmsSession)queueSession;
    Queue queue = aqs.getQueue("TEST_SCHEMA", "TEST_QUEUE");

    Hello,
    What version are you using of the jar files? What version of the database are you using?
    From what I recall the example in <Note:301434.1> successfully reused an existing JDBC connection.
    I would be interested to see a more complete code example if this is not helpful.
    Thanks
    Peter

  • Basic JDBC transactional question

    Hello all,
    I have (what I believe) is a basic transactional JDBC question.
    Here's what I want to do:
    begin transaction
    select a row from a table where (some condition).
    that row may or may not exist.
    if the row exists: update the row
    else if the row does not exist, insert a new row
    end transaction
    I want this entire thing to be atomic .. I don't want the select to complete, then have something else come in there before the update/insert takes place.
    I'm using MySQL .. I seem to remember hearing about some proprietary MySQL command which would do a SELECT + UPDATE atomically .. which would be fine, but I can't find it.
    Wrapping this with a row-level lock would be fine too .. I'm just not sure how to do that in JDBC.
    Thanks!
    -d

    By thte way, and not that it helps the orignal poster, who's using MySQL, but Oracle has a proprietary MERGE statement that does "insert or update" in one go. For example:
    MERGE INTO bonuses D
       USING (SELECT employee_id, salary, department_id FROM employees
       WHERE department_id = 80) S
       ON (D.employee_id = S.employee_id)
       WHEN MATCHED THEN UPDATE SET D.bonus = D.bonus + S.salary*.01
         DELETE WHERE (S.salary > 8000)
       WHEN NOT MATCHED THEN INSERT (D.employee_id, D.bonus)
         VALUES (S.employee_id, S.salary*0.1)
         WHERE (S.salary <= 8000);

Maybe you are looking for

  • Using JPA Entity-Objects defined in other EJB-Development Component

    Hello Community, I'm working on a Java-Application on NW CE 7.1, using JEE5 Beans in the Business-Logic-Layer and WebDynpro/Java in the UI-Layer. I designed a Bean for working with data, stored in a database-table of the system-database. For that add

  • Purchase Order Net Price not editable after GR/IR

    Hi Friends! I am facing a problem that, I want the price of the Purchase Order document should not be changed after the GR or IR is posted for this document. I have checked that making the net price field as display or M/06 is not the solution of the

  • In-place upgrade of Windows Server 2012 RDS to R2 fails

    Hi All I have a Server 2012 Standard RDS virtual machine (vmware) on which I have tried doing an in-place upgrade to 2012 R2 but it constantly fails. It sits at the "Collecting files, settings and applications" process for quite a while - always on 0

  • Lens correction for EOS 60D...

    More than a question is a little missing detail in CS6 beta The Canon EOS 60D and the EF-S 18-55 mm IS II in Lens correction filter doesn't exist. It's not a new camera model, it's from 2010. Thanks

  • Invalid UTF8 encoding when including XML page in XSQL

    Hello I'm creating an XSQL page that includes an XML page generated using PSP <?xml version="1.0" encoding="ISO-8859-1"?> <page xmlns:xsql="urn:oracle-xsql" connection="sgvrt"> <xsql:include-xml href="http://epdesccs.pdvsa.com:7777/pls/sgvrt/xml_indi