DriverManagerConnectionPoolConnection not closed

I am using the Oc4J connection pooling mechanism(data-source.xml) . I do a connection.close() everytime I am done with the Connection . But still I keep getting this "DriverManagerConnectionPoolConnection not closed, check your code!" all the time
Any clues whats going wrong

I already do that. But it does not help.
The problem probably comes from the fact that I use BLOBSo save some binary data :
[simplified version of my code:]
//Allocate a LOB using a stored proc (my prefered method, BLOB.createTemporary(...) throws a NullPointerException if used on a Pooled Connection)
OracleCallableStatement cs = (OracleCallableStatement)connection.prepareCall(
"{Call dbms_lob.createTemporary(?,false)}");
cs.registerOutParameter(1, Types.BLOB);
cs.executeUpdate();
BLOB myBlob = cs.getBLOB(1);
cs.close();
// fill the BLOB with some binary data
OutputStream outputStream = myBlob.getBinaryOutputStream();
outputStream.write(byteArray);
outputStream.flush();
outputStream.close();
// use it in an insert
preStatement = (OraclePreparedStatement)connection.prepareStatement(
INSERT_SQL);
preStatement.setBLOB(1, myBlob);
// execute the insert
preStatement.executeUpdate();
preStatement.close();
// free the BLOB
OracleCallableStatement cs2 = (OracleCallableStatement)connection.prepareCall(
"{Call dbms_lob.freetemporary(?)}");
cs2.setBLOB(1, myBlob);
cs2.executeUpdate();
cs2.close();
/// all this being enclosed try/finally very similar to the one in your sample
/// Also note that no Exception/Error are thrown (they are all caught and logged)
If the problem comes from the way Oracle Pooled connections manage BLOBs it there any other way I could use to save some binary data ?
Thanks for any answer,
Benoit

Similar Messages

  • DriverManagerConnectionPoolConnection not closed with TopLink cahce synch

    We're using TopLink in several JVMs and have configured cache synchronisation over JMS. The JMS topic runs on Oracle AQ. Every once in a while we get the follwoing error from OC4J:
    DriverManagerConnectionPoolConnection not closed, check your code!
    Now this could be some connection we forget to close, but we do use TopLink for all our databasecommunication. I also see that every time it shows up the last steps of the stacktrace involves the TopLink cache and the AQ classes:
    05/05/12 11:42:27 com.evermind.sql.DriverManagerConnectionPoolConnection@10e3c8c was Created at:
    05/05/12 11:42:27 java.lang.Throwable: DriverManagerConnectionPoolConnection created
    05/05/12 11:42:27      at com.evermind.sql.DriverManagerConnectionPoolConnection.<init>(DriverManagerConnectionPoolConnection.java:29)
    05/05/12 11:42:27      at com.evermind.sql.DriverManagerPooledConnection.getNewLogicalConnection(DriverManagerPooledConnection.java:375)
    05/05/12 11:42:27      at com.evermind.sql.DriverManagerPooledConnection.getConnection(DriverManagerPooledConnection.java:121)
    05/05/12 11:42:27      at com.evermind.sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:347)
    05/05/12 11:42:27      at com.evermind.sql.OrionCMTConnection.setConnection(OrionCMTConnection.java:191)
    05/05/12 11:42:27      at com.evermind.sql.OrionCMTConnection.intercept(OrionCMTConnection.java:141)
    05/05/12 11:42:27      at com.evermind.sql.OrionCMTConnection.setAutoCommit(OrionCMTConnection.java:479)
    05/05/12 11:42:27      at com.evermind.sql.ConnectionBCELProxy.setAutoCommit(ConnectionBCELProxy.java:105)
    05/05/12 11:42:27      at oracle.jms.AQjmsDBConnMgr.extraInit(AQjmsDBConnMgr.java:740)
    05/05/12 11:42:27      at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:568)
    05/05/12 11:42:27      at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:367)
    05/05/12 11:42:27      at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:246)
    05/05/12 11:42:27      at oracle.jms.AQjmsTopicConnectionFactory.createTopicConnection(AQjmsTopicConnectionFactory.java:214)
    05/05/12 11:42:27      at oracle.toplink.remote.jms.JMSClusteringService.createRemoteConnection(JMSClusteringService.java:67)
    05/05/12 11:42:27      at oracle.toplink.remote.jms.JMSClusteringService.retreiveRemoteSessions(JMSClusteringService.java:199)
    05/05/12 11:42:27      at oracle.toplink.remote.jms.JMSClusteringService.run(JMSClusteringService.java:177)
    05/05/12 11:42:27      at oracle.toplink.remote.jms.JMSClusteringService.initialize(JMSClusteringService.java:164)
    05/05/12 11:42:27      at oracle.toplink.remote.CacheSynchronizationManager.initialize(CacheSynchronizationManager.java:112)
    05/05/12 11:42:27      at oracle.toplink.publicinterface.DatabaseSession.login(DatabaseSession.java:534)
    05/05/12 11:42:27      at org.springframework.orm.toplink.SessionFactoryBean.afterPropertiesSet(Unknown Source)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1072)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:343)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:260)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:221)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveReference(AbstractAutowireCapableBeanFactory.java:980)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveValueIfNecessary(AbstractAutowireCapableBeanFactory.java:918)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:859)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:688)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:325)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:260)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:221)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveReference(AbstractAutowireCapableBeanFactory.java:980)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveValueIfNecessary(AbstractAutowireCapableBeanFactory.java:918)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveConstructorArguments(AbstractAutowireCapableBeanFactory.java:574)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:477)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:306)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:260)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:221)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveReference(AbstractAutowireCapableBeanFactory.java:980)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveValueIfNecessary(AbstractAutowireCapableBeanFactory.java:918)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveConstructorArguments(AbstractAutowireCapableBeanFactory.java:574)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:477)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:306)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:260)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:221)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
    05/05/12 11:42:27      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:291)
    05/05/12 11:42:27      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:317)
    05/05/12 11:42:27      at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:80)
    05/05/12 11:42:27      at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:65)
    05/05/12 11:42:27      at org.springframework.context.access.ContextJndiBeanFactoryLocator.createBeanFactory(ContextJndiBeanFactoryLocator.java:40)
    05/05/12 11:42:27      at org.springframework.beans.factory.access.JndiBeanFactoryLocator.useBeanFactory(JndiBeanFactoryLocator.java:68)
    05/05/12 11:42:27      at org.springframework.ejb.support.AbstractEnterpriseBean.loadBeanFactory(AbstractEnterpriseBean.java:115)
    05/05/12 11:42:27      at org.springframework.ejb.support.AbstractStatelessSessionBean.ejbCreate(AbstractStatelessSessionBean.java:63)
    For those of you familiar with the Spring Framework you'll notice I'm invoking an SLSB throug it, and that thet start of the stackrace is missing, but this error also shows up in other contexts. This is only one of them. They all have in common the AQ and Cache sync lines.
    Anyone have any ideas? Is it even tied to TopLink or might it be an AQ issue?
    Anders,

    What version of OC4J are you using?
    If you are using a 10.1.3 preview release, this may be an issue with OC4J connection pooling in that preview release.
    You could try using AS JMS and TopLink connection pooling to determine which is causing the issue.

  • OC4J AQ/JMS - Logging DriverManagerConnectionPoolConnection not closed

    Hi,
    Since I do not directly utilise JDBC resource, I cannot work out how I might investigate this supposed leak.
    Every now and then (and it does appear to happen sporadically - I cannot identify a pattern), I get the
    messages.
    DriverManagerConnectionPoolConnection not closed, check your code!
    I turned the logging on (using -Djdbc.connection.debug=true), and the following exceptions is thrown:
    Created at:
    java.lang.Throwable: DriverManagerConnectionPoolConnection created
    at com.evermind.sql.DriverManagerConnectionPoolConnection.<init>(DriverManagerConnectionPoolConnection.java:27)
    at com.evermind.sql.DriverManagerPooledConnection.getNewLogicalConnection(DriverManagerPooledConnection.java:341)
    at com.evermind.sql.DriverManagerPooledConnection.getConnection(DriverManagerPooledConnection.java:117)
    at com.evermind.sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:235)
    at com.evermind.sql.DriverManagerXADataSource.getNonAutoCommitConnection(DriverManagerXADataSource.java:285)
    at com.evermind.sql.DriverManagerXAConnection.start(DriverManagerXAConnection.java:101)
    at com.evermind.server.TransactionEnlistment.<init>(TransactionEnlistment.java:45)
    at com.evermind.server.ApplicationServerTransaction.enlistResource(ApplicationServerTransaction.java:247)
    at com.evermind.sql.OrionCMTConnection.tryToDelistEnlist(OrionCMTConnection.java:308)
    at com.evermind.sql.OrionCMTConnection.intercept(OrionCMTConnection.java:112)
    at com.evermind.sql.FilterConnection.getTypeMap(FilterConnection.java:135)
    at com.evermind.sql.FilterConnection.getTypeMap(FilterConnection.java:136)
    at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:1240)
    at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:981)
    at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:918)
    at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:834)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:905)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:797)
    at java.lang.Thread.run(Thread.java:479)
    Here is the ejb.jar sections of interest:
    <transaction-type>Container</transaction-type>
    <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
    <message-driven-destination>
    <destination-type>javax.jms.Queue</destination-type>
    </message-driven-destination>
    <resource-ref>
    <res-ref-name>jms/MessageQueueConnectionFactory</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Application</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/MessageSendQueue</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/MessageStatusQueue</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    Here is the orion-ejb.jar <enterprise-beans> definition:
    <enterprise-beans>
         <message-driven-deployment name="MessagingServer" destination-location="java:comp/resource/CallistaMessagingJMSContext/Queues/CORQ_MSG_SEND_QUEUE" connection-factory-location="java:comp/resource/CallistaMessagingJMSContext/QueueConnectionFactories/jmsFactory" max-instances="100">
         <resource-ref-mapping name="jms/MessageQueueConnectionFactory" location="java:comp/resource/CallistaMessagingJMSContext/QueueConnectionFactories/jmsFactory" />
         <resource-env-ref-mapping name="jms/MessageSendQueue" location="java:comp/resource/CallistaMessagingJMSContext/Queues/CORQ_MSG_SEND_QUEUE" />
         <resource-env-ref-mapping name="jms/MessageStatusQueue" location="java:comp/resource/CallistaMessagingJMSContext/Queues/CORQ_MSG_STATUS_QUEUE" />
         </message-driven-deployment>
    </enterprise-beans>
    The orion-application.xml has the following resource provider mapping for the OJMS Context:
    <resource-provider class="oracle.jms.OjmsContext" name="CallistaMessagingJMSContext">
    <description> OJMS/AQ </description>
    <property name="datasource" value="jdbc/ejb/CallistaMessageOwnerDS" />
    </resource-provider>
    Here is the matching 'jdbc/ejb/CallistaMessageOwnerDS' datasource definition for the JMS:
    <data-source
         class="com.evermind.sql.DriverManagerDataSource"
         name="CallistaMessageOwnerJDBCDatasource"
         location="jdbc/CallistaMessageOwnerCoreDS"
         xa-location="jdbc/xa/CallistaMessageOwnerXADS"
         ejb-location="jdbc/ejb/CallistaMessageOwnerDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
         username="*********"
         password="****"
              url="jdbc:oracle:thin:@myhost.com.au:1529:ORCL"
         inactivity-timeout="30"
    />
    I would appreciate any input into any mistakes I may have made (perhaps I need to use a different datasource, or define it in a different way)
    Any help - including an indication that this is an error I can safely ignore :-) would be appreciated.
    Thanks
    Jason

    I'm have the same issue. I'm currently trying to seen if the Oracle 9.2.0.5.0 patch corrects the issue (waiting for the file down load). There is a known issue in Oracle and cleaning up Inactive connections. I assuming the two are related ... I hope it works.

  • DriverManagerConnectionPoolConnection not closed, check your code!

    DriverManagerConnectionPoolConnection not closed, check your code!
    I keep getting these, both from custom jdbc calls (finally {close res, stmt, con} ALWAYS) as well as on CMP entity beans.... Not always, but periodicly! ... Running OC4J9.0.4.0.1 ...
    Suggestions ???

    Sorry Steven Button
    I did not mean to offend any one, but don't you go through some frustrating moments when you feel you have tried all possible combinations and u need help from other techies and they do not respond, Once again I am sorry if I have offended anybody.
    Here is my hardware/software in production
    1) IBM AIX
    2) Standalone OC4J 9.0.4.0.0
    3) JDK 1.4.2_07
    4) Database 10.1.0.2.0
    I have also set the following debug flags for the JVM,
    -Djdbc.connection.debug=true and
    -Ddatasource.verbose=true
    Yesterday one interesting thing happened
    For some reason our database server connection from application server went down for a few minutes.
    After the network connection was restored, in the admin console for OC4J I see more logical connections (Open JDBC Connections count(6) is more than initial pool size(5)).
    When I saw the log file I see the same "Check your code" message. But one more interesting thing got logged thanks to "-Ddatasource.verbose=true", this flag will log the pool size of the connection pool in the application log file.
    The number that got logged was the correct number of pool size(which is 5).
    Example
    My initial pool size was "5", the admin console showed the pool size after network failure as "6", which is wrong.
    But the -Ddatasource.verbose=true logged the pool size as "5" which is correct.
    Can anyone help me with respect to that?
    Message for Avi Abrami
    Here is the sample finally block we use through out the application code.
    try {
    } catch (Exception ex) {
    // we log the error in the application log file.
    } finally {
    try
    if (lobj_resultset != null)
    lobj_resultset.close();
    lobj_resultset = null;
    } catch (Exception exrs)
    try
    if (lobj_stmt != null)
    lobj_stmt.close();
    lobj_stmt = null;
    } catch (Exception exstmt)
    try
    if (lobj_conn != null)
    lobj_conn.close();
    lobj_conn = null;
    } catch (Exception exconn)
    As you can see the main catch block will log the appropriate errors encountered in the try block. Thanks for your suggestion, I will give it a try by not ignoring the catch block exceptions in the finally block.
    There is one more think,
    it is my understanding that if an 'Error' is raised like OutOfMemoryError rather than an Exception
    like 'SQLException' then that will not get caught since I am using catch (Exception ex) and not catch (Throwable throw).
    But even if I do not catch an 'Error', it is my belief that the finally block will still get executed.
    So say the try block for some reason raises an OutOfMemoryError , since in my code I use catch (Exception ex), my code execution will go to finally block and not the catch block, that still should release the connection back to the pool should it not?.
    Any help / advise is appreciated.
    I have also raised a TAR with oracle and will keep this forum posted with what happens with that.
    But, guys I really need help, suggestions, directions from u all.

  • DataSourceConnection was not closed!

    I'm developing with Jdev 9.0.3_1 testing with the embebed OC4J. I've some CMP EntityBeans and sometimes I get the following error message "DataSourceConnection was not closed! DriverManagerConnectionPoolConnection not closed, check your code! (Use -Djdbc.connection.debug=true to find out where the leaked connection was created)"
    I don't open or close connections explicitly.
    Any idea?
    Thanks in advance.
    Julio.

    This message is as a result of a bug in 9.0.3 with CMP/CMR without specifying a transaction attributes for entity bean methods. These are fixed in 9.0.4, please try this in 9.0.4 Developers preview
    regards
    Debu

  • SAP Production Order not closing

    Hi there,
    I am running the COHV with Complete parameter in the background, and it does pick up several TECO orders from the past, like say from 2009 which are not closed but it does not process them to CLSD status.
    I am seeing some entries in COHV, CO1P, COFC transactions - I picked a few randomly to check.
    The order qty is not always equal to the delivered qty - Again a random test
    The consumption qty on the components is not always equal to the required qty, which leaves reservation open - random check
    Is all the above causing my order not to close ? where do I see the error log, when I try to close the order. I wrote the above issues based on my random check.
    Thank you

    Hi SAP Process,
    When you run COHV to close the orders, you can see the log with the list of orders that have not been closed.
    To see in detail what has happened you will need to check order by order.
    Other option will we to evaluate each situation separatelly. You can check COGI, CO1P, see open reservations, check if you have TR or TO if you use WM, etc.. Once each situation is cleaned, you will be able to closed most of your production orders. It is quite common to create a custom report to make all these checks (COGI, TR/TOs, etc) and closed the orders.
    Kind Regards,
    Mariano

  • Firefox.exe*32 not closing down when i sutdown all open windows so I have to close it through taskmanager

    firefox.exe*32 not closing down when i sutdown all open windows so I have to close it through taskmanager so I can then start a new session.

    See:
    *"Hang at exit": http://kb.mozillazine.org/Firefox_hangs
    *"Firefox hangs when you quit it": https://support.mozilla.org/kb/Firefox+hangs

  • Cursors are not closed when using Ref Cursor Query in a report  ORA-01000

    Dear Experts
    Oracel database 11g,
    developer suite 10.1.2.0.2,
    application server 10.1.2.0.2,
    Windows xp platform
    For a long time, I'm hitting ORA-01000
    I have a 2 group report (master and detail) using Ref Cusor query, when this report is run, I found that it opens several cursors (should be only one cursor) for the detail query although it should not, I found that the number of these cursors is equal to the number of master records.
    Moreover, after the report is finished, these cursors are not closed, and they are increasing cumulatively each time I run the report, and finally the maximum number of open cursors is exceeded, and thus I get ORA-01000.
    I increased the open cursors parameter for the database to an unbeleivable value 30000, but of course it will be exceeded during the session because the cursors are increasing cumulatively.
    I Found that this problem is solved when using only one master Ref Cursor Query and create a breake group, the problem is solved also if we use SQL Query instead of Ref Query for the master and detail queries, but for some considerations, I should not use neither breake group nor SQL Query, I have to use REF Cursor queries.
    Is this an oracle bug , and how can I overcome ?
    Thanks
    Edited by: Mostafa Abolaynain on May 6, 2012 9:58 AM

    Thank you Inol for your answer, However
    Ref Cursor give me felxibility to control the query, for example see the following query :
    function QR_1RefCurDS return DEF_CURSORS.JOURHEAD_REFCUR is
    temp_JOURHEAD DEF_CURSORS.JOURHEAD_refcur;
              v_from_date DATE;
              v_to_date DATE;
              V_SERIAL_TYPE number;
    begin
    SELECT SERIAL_TYPE INTO V_SERIAL_TYPE
    FROM ACC_VOUCHER_TYPES
    where voucher_type='J'
    and IDENT_NO=:IDENT
    AND COMP_NO=TO_NUMBER(:COMPANY_NO);
         IF :no_date=1 then
                   IF V_SERIAL_TYPE =1 THEN     
                   open temp_JOURHEAD for select VOCH_NO, VOCH_DATE
                   FROM JOURHEAD
                   WHERE COMP_NO=TO_NUMBER(:COMPANY_NO)
                   AND IDENT=:IDENT
              AND ((TO_NUMBER(VOCH_NO)=:FROM_NO and :FROM_NO IS NOT NULL AND :TO_NO IS NULL)
              OR (TO_NUMBER(VOCH_NO) BETWEEN :FROM_NO AND :TO_NO and :FROM_NO IS NOT NULL AND :TO_NO IS NOT NULL )
              OR (TO_NUMBER(VOCH_NO)<=:TO_NO and :FROM_NO IS NULL AND :TO_NO IS NOT NULL )
              OR (:FROM_NO IS NULL AND :TO_NO IS NULL ))
                   ORDER BY TO_NUMBER(VOCH_NO);
                   ELSE
                   open temp_JOURHEAD for select VOCH_NO, VOCH_DATE
                   FROM JOURHEAD
                   WHERE COMP_NO=TO_NUMBER(:COMPANY_NO)
                   AND IDENT=:IDENT               
              AND ((VOCH_NO=:FROM_NO and :FROM_NO IS NOT NULL AND :TO_NO IS NULL)
              OR (VOCH_NO BETWEEN :FROM_NO AND :TO_NO and :FROM_NO IS NOT NULL AND :TO_NO IS NOT NULL )
              OR (VOCH_NO<=:TO_NO and :FROM_NO IS NULL AND :TO_NO IS NOT NULL )
              OR (:FROM_NO IS NULL AND :TO_NO IS NULL ))     
                   ORDER BY VOCH_NO;          
                   END IF;
         ELSE
                   v_from_date:=to_DATE(:from_date);
                   v_to_date:=to_DATE(:to_date);                         
              IF V_SERIAL_TYPE =1 THEN
                   open temp_JOURHEAD for select VOCH_NO, VOCH_DATE
                   FROM JOURHEAD
                   WHERE COMP_NO=TO_NUMBER(:COMPANY_NO)
              AND IDENT=:IDENT                         
                   AND ((voch_date between v_from_date and v_to_date and :from_date is not null and :to_date is not null)
                   OR (voch_date <= v_to_date and :from_date is null and :to_date is not null)
                   OR (voch_date = v_from_date and :from_date is not null and :to_date is null)
                   OR (:from_date is null and :to_date is null ))     
                   ORDER BY VOCH_DATE,TO_NUMBER(VOCH_NO);     
              ELSE
                   open temp_JOURHEAD for select VOCH_NO, VOCH_DATE
                   FROM JOURHEAD
                   WHERE COMP_NO=TO_NUMBER(:COMPANY_NO)
                   AND IDENT=:IDENT                         
              AND ((voch_date between v_from_date and v_to_date and :from_date is not null and :to_date is not null)
                   OR (voch_date <= v_to_date and :from_date is null and :to_date is not null)
                   OR (voch_date = v_from_date and :from_date is not null and :to_date is null)
                   OR (:from_date is null and :to_date is null ))     
                   ORDER BY VOCH_DATE,VOCH_NO;          
              END IF;
         END IF;               
         return temp_JOURHEAD;
    end;

  • Purchase Requsition is not closing automatically During ME59 PO creation

    Hi,
    We are using PO creation through ME59,
    In ME59 we have set the indicator 1 Set reqs. to "closed"
    In PR we have 1 qty and in PO was created for 1 qty. But the PR was not closed.
    When we check the F1 help for the filed it say it will work with respect to the rounding value. as for my concer the PR qty 1 was fulfilled by po with 1 qty creation.  I dont know why the PR was not set to Closed automatically.
    If we try 2 Set reqs. to "closed" It is working
    Can any once explaing why it is not wroking for indicator 1
    Regards
    Palani

    Is your order unit and requisition unit same ?

  • Hyperlinks not closing out in RH

    Here's another odd behavior:
    When I bring my FM book into RH, my hyperlinks are not closed
    out in the converted content in RH. In FM, the hyperlinks are
    correctly inserted using the gotolink and newlink Hypertext
    markers. Yet in RH, the rest of the sentence in which the hyperlink
    appears is also erroneously tagged as part of the hyperlink.
    Is this is a bug? Has anyone else seen this behavior and if
    so, how did you fix it?

    Hello Michael,
    This is not an issue, you'd always get the hyperlinks
    appearing corrcetly without any tagging in the Design view of RH.
    Just try to close and reopen the topic in the Design view or try to
    view it in preview - it shoudl appear correctly.
    Regards,
    Pooja

  • AS Java sessions are not closed until they time out

    Hello Experts,
    we have a SAP PI system to integrate SAP R/3 with external applications and recently we are facing a problem with inactive sessions. There's a new application we are setting up that consumes a webservice published by this SAP PI system. The scenario is SOAP --> PI --> PROXY. What we have noticed is that when the application sends loads of requests sometimes the system fails. This is because we are reaching the maximum number of open sessions in AS Java (1000). Investigating a bit more we found out that the sessions are not "closed" once the communication between the application and SAP PI has finished. Those sessions are open until they are automatically timed-out by the system after 1800 sec.
    We have found the notes below in SAPNet:
    Note 1363751 - ICM: Java Web sessions are not terminated
    Note 1307940 - New HTTP session opened for every web service call
    However, none of them are applicable to our system because it is more updated:
    SAP PI 7.1 EHP1 SP002
    Kernel Patch Level: 87
    We have tried to close connections from the application that consumes the webservice but with no success. The sessions remain in the server until they are timed-out. Could you please tell us if this is the normal behavior of an AS Java system? Is this the way it should work? If so, can you tell us how to decrease this timeout so the inactive sessions are cleaned faster? We tried to find it but we didn't manage. Is there any way to close the session once the communication has finished?
    Thank you in advance.
    Roger Allué i Vall

    Hi Roger,
    You can do the following things to help solving your issue:
    1. Decrease session timeout default value of the web container: Use the NetWeaver Administrator
    Open Application Modules plugin within NWA
    Configuration Management -> Infrastructure -> Application Modules
    Set the desired timeout web module you are using, in minutes.
    The default value 0 in the NWA means that the value is not modified
    and the default value of 30 minutes timeout will be used.
    2. Increase the max. no. of Sessions in Configtool
    The max. number of Sessions can be set in Configtool in the Expert
    mode. There is no limitation for the parameter.
    Thanks,
    Anderson

  • JMS session is not closed even after calling close()

    Hi All,
    I am using JMS to receive and publish topics for a process,in my java code i
    am creating new JMS Session on demand(ie., whenever a new topic is
    received) after processing the topic i am closing the session with close(),but
    still the session is not closed.In a period of time more sessions are created
    and FD leaks occurs which stops the process functionality.
    Later i moved the on demand session code to a static block, its working fine
    and no FD leak occurs.
    Is this a known behavior or any java bug is there to point this issue,please
    help me regarding this.
    Thanks,
    Ants Balajei

    You should try avoid creating sessions on demand but cache/pool them...
    http://activemq.apache.org/how-do-i-use-jms-efficiently.html
    James
    http://www.iona.com/
    Open Source the Enterprise Way

  • Why the photo app is not closing after i finish, when i take a picture accessing directly from home screen. the location is draining my battery if I'm not closing the app by double click home button. in iOS 6 was not like this

    When im taking a picture directly from home screen after im finished the application remain open. This app is ussing the location and if im not closing like other applications by doble click the home button the batery will finished fast. On the other IOS 5 and 6 was not neccesary to unblock the phone and bouble click the home bottom.

    Reinstalling OS X Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Reinstalling OS X Without Erasing the Drive
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list.  Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Alternatively, see:
    Reinstall OS X Without Erasing the Drive
    Choose the version you have installed now:
    OS X Yosemite- Reinstall OS X
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
    OS X Lion- Reinstall Mac OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • Outlook 2013 are not opening and showing pst files are not closed properly

    Hi
    Outlook 2007 has stopped working and showing close the program. Again,we re-started then outlook 2007 and it has opened and taken the backup of pst files in a separate hard drive.
    The pst file was repaired in scanpst.exe and again i have tried to put the pst file back in outlook 2007.It was hanging and suddenly i have uninstalled 2007 and started installing outlook 2013.
    2013 applications like word,excel,power point are opening and outlook 2013 are not able to open and showing pst files were not closed properly.
    Again i have un-installed and re-installed the outlook 2013.still we are not able to open the outlook.
    Need your support at the earliest to fix the issue.
    Thanks

    Hi,
    What's the .pst file used for? Archive? Or you set up a POP3 account and want to import the emails from the .pst file?
    Another question, you mentioned you installed Outlook 2013 and it didn't open either. Was this from the beginning right after you installed Outlook 2013, or after you did something such as create a new Profile, set up a new account and tried to import the
    .pst file?
    Kindly answer my questions so I can understand the situation better.
    I've seen some of this issue caused by the anti-malware software, check your anti-malware software to see if it's trying to interfere with Outlook - things like real time email checking can sometimes cause these kinds of problems. To troubleshoot, we can
    simply disable the anti-malware software temporarily to see the result.
    Regards,
    Melon Chen
    TechNet Community Support

  • Database connection not closing on time out

    Hi All,
    Not sure if this is the right place for this question but..
    I've moved my app (built using jdev10.1.2., adf bc's and jsp's) to an app server. For some reason, the database connection is not closing. I have 46 connections to the database and I''m the only one with the URL, not good.
    So can anyone shed any light on this? I thought it should disconnect after a time out but its not.
    Any ideas would be gratfully received.
    Thanks in advance

    or try this one..
    Go to the bottom of the tutorial, you will find the configuration...
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc9baf90-0201-0010-479a-b49b25598ebf

Maybe you are looking for