What effect If not Close statement or resultSet

Hi
i in my project somewhere i did not close these thing is it necessary
If am not close any resultSet or statement/Preparedstatement
what problem can arise, will it is cause to make database conjection
is it automatically close
Thanks

I am creating connection in each JSp /Servlet so according to current synario at present is it better to close in every JSP.
is better to generate one time and pass it to context

Similar Messages

JDBC: Closing Connection does it close statement and resultset

In my application I am facing ORA-0100 Maximum open cursors exceeded problem. We are executing quite a few queries and stored procedures before we close the connection object. But in few places statements and resultsets are not closed. Can these be a problem? Shouldn't they be automatically closed when the connection is closed?
We are executing this block of code in a loop.

in few places statements and
resultsets are not closed. Can these be a problem?Yes.

Closing Statements and ResultSets

I just recently realized that you need to close Statements and ResultSets in order to avoid getting the "Too many cursors"-message.
My question is:
Do you need to close both Statements and ResultSets?
- not that it's a problem...
if so:
Does it matter which one you close first?

I usually place the stmt.close() code in my finally block, to ensure that the statement gets closed, even if a SQLException occurs during the query/update. The ResultSet does not explicitly have to be closed, ... it is automatically closed when the Statement is closed, or if a new query is run on the same statement.

FCP HD SOME EFFECTS NO NOT WORK

I HAVE SEVERAL LOCATIONS IN MY CURRENT PROJECT THAT HAVE EFFECTS INSTALLED AND THEY DO NOT OCCUR DURING PLAY BACK AND THEY ARE RENDERED. I HAVE TRIED TI 'JOIN THRU EDIT', THEN RECUT AND INSTALL THE EFFECT. THIS SEEMS TOOCCURE WHEN THERE IS A RED DIAMOND ON EITHER SIDE OF THE CUT.

Welcome the the forum Durward,
Please don't use ALL CAPS, it comes across as shouting.
What effects are not working?
What are your render settings?
What media format...DV, HDV, Grahics...etc.
Just need more info...
Kevan
EDIT - Have you tried trashing preferences, and repairing disk permissions?

What does "After Effects error: Not enough memory to initialize PSL. ( 83 :: 8 )" mean?

So, about a week ago I did a fresh install of 64-bit Windows 7 Ultimate on a new PC, and subscribed to the Adobe Creative Cloud, installing After Effects CS6 and Photoshop CS6 from the Adobe Application Manager, then doing all updates (and I just checked right now at 10:35PM on July 26th, I have the latest versions of everything).
After Effects was working completely normal, then just now, I tried to import a Photoshop .psd and I got the error message:
After Effects error: Not enough memory to initialize PSL.
( 83 :: 8 )
Then After Effects crashed. So now it opens up normally, but when I try to import a .psd or open an After Effects project saved from an earlier version of After Effects (CS3 to CS5) I get the same error and a crash, every single time.
Searching the forums, I see people talking about this error when importing .psds into CS5, and they say that getting the latest updates solved the issue for them (which obviously can't help me). I'm running all legit software on a brand new computer with 32 GB of RAM which has passed all my physical stress tests so I know it's not hardware related.
The one thing I saw people suggest is to hold down Ctrl-Alt-Shift when starting the program. When I do this, Windows asks if I want to allow After Effects to make changes to the system, and when I say yes, I can import .psds and open the older AE files. When I close After Effects and reopen it without holding down the Ctrl-Alt-Shift keys, it goes right back to crashing.
Obviously the smart-*** answer is "then hold down Ctrl-Alt-Shift, dummy", and I'll do that for now, but is there any clue what the problem is?
I feel like kind of a chump because I decided to stop using my student versions of Adobe software (I haven't been a student for about four years) and pay the full price for the cloud membership and the latest creative suite, and it's full of bugs.

Now, I get the same ( 83 :: 8 ) error listed above, followed by a new dialog window that reads:
After Effects error: Crash in progress. Last logged message was: <4488> <DynamicLink> <5> C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Then, when I click OK, I get:
After Effects can't continue: sorry, After Effects has crashed. For After Effects Help and Support, go to http://www.adobe.com/go/learn_ae_support. If you still can't resolve the issue, please contact Adobe Technical Support (2).
( 0 :: 42 )
Clicking OK to that gives me a chance to save the latest project, then the standard Windows 7 crash dialog window opens, the one that gives me the choice of "Check online for a solution and close the program" or just "Close the program" and lets me View problem details, which are:
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          AfterFX.exe
Application Version:          11.0.0.378
Application Timestamp:          4f6d63ab
Fault Module Name:          StackHash_a85b
Fault Module Version:          6.1.7601.17725
Fault Module Timestamp:          4ec4aa8e
Exception Code:          c0000374
Exception Offset:          00000000000c40f2
OS Version:          6.1.7601.2.1.0.256.1
Locale ID:          1033
Additional Information 1:          a85b
Additional Information 2:          a85ba096cc6b6acabe6eaf35bf34dc60
Additional Information 3:          f862
Additional Information 4:          f86227a9dfa15a47cdb6c94bb0d08360

Hello, what to do if a program crash? I was working in a power point presentation and suddenly the little rainbow circle appeared and can not close the program, thanks

Hello, what to do if a program crash? I was working in a power point presentation and suddenly the little rainbow circle appeared and can not close the program, thanks

Welcome to Apple Support Communities
Press Alt, Command and Esc keys, select the crashed app and force quit it. Then, open this app again.
If you didn't save this document, it's possible that you lost the changes you made unless you have OS X Lion or Mountain Lion and they saved your document automatically

What am i supposed to do when my mac says it's in the not charging state and says that the battery is holding a significantly lower charge than normal?

what am i supposed to do when my mac says it's in the not charging state and says that the battery is holding a significantly lower charge than normal?

Go to the Apple in the upper left corner and select About This Mac, then click on More Info (and then System Report if you are running 10.7 Lion or 10.8 Mountain Lion), then select Power from the left hand column of the System Profiler. Copy and paste the Battery Information from the top of the page back here.

I bought the production premium , cs6 , and I download it and registered with out any problem , I formatted my computer then I downloaded the collection , now everything else working only after effect is not working , what shall i do

I bought the production premium , cs6 , and I download it and registered with out any problem , I formatted my computer then I downloaded the collection , now everything else working only after effect is not working , what shall i do

did ae install without problem? check the install logs to be sure (Troubleshoot with install logs | CS5, CS5.5, CS6, CC)
if it did, what do you see when clicking the executable?

HT6114 I am trying to upgrade to Mavericks from 10.6.8. When it tells me to close all applications, Safari will not close and I cannot proceed. What to do?

I am trying to upgrade to Mavericks from 10.6.8. It tells me to close all open applications. However, Safari will not close and the installation cannot proceed. Any suggestions?

Either try to force quit Safari (press Command + Option + Escape keys and then choose force quit in the pop up window), or, you can also shut down the computer. Then boot up and open the app store application to download Mavericks - you don't need Safari for it.

How to close statement when calling in chain sequence

Hi all,
just have a look on below code:
java.sql.connection con =null;
//here getting connection
ResultSet rs= con.createStatement().executeQuery("sql");
its similer to chaining pattern. here I am having question,
with the line:
con.createStatement()
I am creating the statement and later using this object (which is implicit object as i m not having any futher reference of it, is it correct word which i used) i am executing query and getting result set object.
here statement object is implicit object.
is I need to close this object? As per me its too required and i can retrived statement object with the help of resultset object and can use close method.
but what does the java best pratice say? how they handle objects which are created in chain calling.
for example
//this.getPatternCode().getProperty().getName()
thanks,
Pax

In short : stop doing this, it's a bad idea.
You must always close all your resultsets, statements and connections._ Anyone who tells you anything different is wrong. End of story. Failure to properly close JDBC resources can lead to any number of problems including having your program crash and/or having the database crash.
So stop doing that.
There is only one correct practice and it is what is below.
Create the connection and keep a reference to it.
Create the statement (this can be a PreparedStatement or CallableStatement as well) using the connection and keep a reference to it (the statement).
Create the result set using the statement.
Process as needed.
Close the resultset in a finally block.
Close the statement in a finally block
Close the connection in a finally block.

Effects Panel not working correctly

I have Windows 7 64 bit, Home Premium and using PSE9. When I open PSE in Full Edit and go to the Effects Panel, the Filters work just fine, but the Layer Styles will not open (or show anything) and the Photo Effects will not open ( or show anything). I did rename the MediaDatabase.db3 file as MediaDatabase.old, following instructions given in a PSE9 class I am taking....but have done nothing else with that file, and then is now a new MediaDatabase.db3 file under the "old" listing....so two files there.
I have no idea what to do to correct this....and I did close everything and close PSE and also my PC...let them rest a while, and then restarted the PC and reopened PSE9, and still the Layer Styles and Photo effects did not work. I hope someone can understand my problem and help....in simple "baby steps". Thanks

Should I delete the file named mediaDatabase.old? I am a senior
"dummie" and just want to be sure what you are telling me.
I did delete the editor's pref files....I understand that one.
Thanks for your help.

FMS proxying HTTP does not close sockets correctly?

Hi,
So, after waiting for a while, we decided to upgrade our streamers to FMS 3.5.3 and set them up to proxy HTTP requests to a lighttpd server instead of the "built in" Apache. With the previous version 3.5 of FMS, we had problems of FMS hanging up after a while and stopping relaying requests, generally a few hours, even when it did not serve a lot of requests. With version 3.5.3, we had great hopes that this problem had disappeared as we had FMS running for more than a month on a test server. So we did the upgrade and we encounter another problem:
After less that one day of activity, our servers crashed for an unknown reason, almost at the same time. Analysing the logs, I saw out of memory messages, but how could two linux servers stop working in the same 5 minutes interval. I supposed there was a power failure of some sort. And I kept analysing because the sysadmins in the server room swore that they saw out of memory kernel panic on the consoles. After a bit of investigation, I found the reasons: the TCP connexions between FMS and the lighttpd server are stacking up and fill the OS network memory! Now, I don't know who is the culprit:
FMS code does not manage correctly HTTP proxy sessions?
lighttpd does not handle correctly HTTP proxying from FMS and does not close correctly the sessions?
Our Ubuntu linux network stack is not correctly configured to manage so many connexions?
Here are the details, any assistance is welcome!
The servers: linux Ubuntu 8.04 with 8 GB RAM.
FMS 3.5.3 proxying to lighttpd 1.4.19 listening on port 81. FMS and lighttpd are set up on the same server.
The streamer receives many (> 10/s) HTTP requests from iPhones which are proxied to lighttpd. iPhones request partial content and lighttpd is well suited for these type of requests.
Locking at the state of the TCP stack:
# netstat -st
IcmpMsg:
    InType3: 6
    InType8: 5501
    OutType0: 5501
    OutType3: 6
Tcp:
    101662 active connections openings
    1192680 passive connection openings
    33 failed connection attempts
    177391 connection resets received
    1653 connections established
    73559682 segments received
    70196072 segments send out
    165137 segments retransmited
    0 bad segments received.
    37219 resets sent
UdpLite:
TcpExt:
    22 resets received for embryonic SYN_RECV sockets
    141884 packets pruned from receive queue because of socket buffer overrun
    2052 packets pruned from receive queue
    40293 TCP sockets finished time wait in fast timer
    801 time wait sockets recycled by time stamp
    711318 delayed acks sent
    2401 delayed acks further delayed because of locked socket
    Quick ack mode was activated 535 times
    68554 packets directly queued to recvmsg prequeue.
    11705 bytes directly in process context from backlog
    341070 bytes directly received in process context from prequeue
    5114830 packet headers predicted
    22083 packets header predicted and directly queued to user
    32542120 acknowledgments not containing data payload received
    25289961 predicted acknowledgments
    9191 times recovered from packet loss due to fast retransmit
    6222 times recovered from packet loss by selective acknowledgements
    Detected reordering 7 times using FACK
    Detected reordering 1 times using SACK
    Detected reordering 7 times using reno fast retransmit
    Detected reordering 9 times using time stamp
    15 congestion windows fully recovered without slow start
    42 congestion windows partially recovered using Hoe heuristic
    17 congestion windows recovered without slow start by DSACK
    16517 congestion windows recovered without slow start after partial ack
    51 TCP data loss events
    3916 timeouts after reno fast retransmit
    3372 timeouts after SACK recovery
    10048 timeouts in loss state
    9157 fast retransmits
    6 forward retransmits
    28990 retransmits in slow start
    30176 other TCP timeouts
    7656 classic Reno fast retransmits failed
    95 SACK retransmits failed
    2738020 packets collapsed in receive queue due to low socket buffer
    52 DSACKs sent for old packets
    52 DSACKs received
    3 connections reset due to unexpected data
    74950 connections reset due to early user close
    2846 connections aborted due to timeout
    TCP ran low on memory 10 times
    TCPDSACKIgnoredOld: 41
IpExt:
The last red line can be visualised below; sometimes the server crashes in out of memory kernel panic...
And if you compare with previous behavior, you can tell when we did the upgrade to FMS 3.5.3...
A few words on our previous configuration with FMS 3.5. To be able to accept HTTP requests, we have a front load balancer which is able to route HTTP requests to lighttpd and RTMP requests to FMS. But with this configuration, we don't benefit from the ability of FMS to fallback to RTMPT for clients behind a proxy or proxy ol' HTTP requests... With the previous configuration, we never had so many connections active simultaneously: we change from 200 max to more than 7000 with FMS 3.5.3 in proxy!
Some figures on what exactly happens:
# netstat -tn | grep :81 | awk '{print $6}' | sort | uniq -c
     20 CLOSE_WAIT
   2245 ESTABLISHED
   1236 FIN_WAIT1
      5 TIME_WAIT
# netstat -tn
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0 275841 127.0.0.1:81            127.0.0.1:45088         FIN_WAIT1
tcp   562347      0 127.0.0.1:55150         127.0.0.1:81            ESTABLISHED
tcp        0 225152 127.0.0.1:81            127.0.0.1:34856         ESTABLISHED
tcp        0 238081 127.0.0.1:81            127.0.0.1:54310         FIN_WAIT1
tcp        0 114433 127.0.0.1:81            127.0.0.1:51810         FIN_WAIT1
tcp   670800      0 127.0.0.1:40746         127.0.0.1:81            ESTABLISHED
tcp   597444      0 127.0.0.1:40654         127.0.0.1:81            ESTABLISHED
tcp   592810      0 127.0.0.1:40669         127.0.0.1:81            ESTABLISHED
tcp        0 103168 127.0.0.1:81            127.0.0.1:54544         ESTABLISHED
tcp        0 201344 127.0.0.1:81            127.0.0.1:40567         ESTABLISHED
tcp        0      0 10.1.74.30:1935         10.1.74.2:60372         ESTABLISHED
tcp   665360      0 127.0.0.1:45282         127.0.0.1:81            ESTABLISHED
tcp        0 210432 127.0.0.1:81            127.0.0.1:40662         ESTABLISHED
tcp        0 207361 127.0.0.1:81            127.0.0.1:44895         FIN_WAIT1
tcp        0 109825 127.0.0.1:81            127.0.0.1:52144         FIN_WAIT1
tcp        0 221825 127.0.0.1:81            127.0.0.1:54844         FIN_WAIT1
tcp        0 103168 127.0.0.1:81            127.0.0.1:40791         ESTABLISHED
tcp   782301      0 127.0.0.1:55074         127.0.0.1:81            ESTABLISHED
tcp        0 219137 127.0.0.1:81            127.0.0.1:45040         FIN_WAIT1
tcp        0 209921 127.0.0.1:81            127.0.0.1:44837         FIN_WAIT1
tcp   574170      0 127.0.0.1:45275         127.0.0.1:81            ESTABLISHED
tcp        0 252033 127.0.0.1:81            127.0.0.1:54907         FIN_WAIT1
tcp        0 254977 127.0.0.1:81            127.0.0.1:54515         FIN_WAIT1
tcp        0 142977 127.0.0.1:81            127.0.0.1:52129         FIN_WAIT1
In case this is needed, FMS configuration is almost out of the box:
_defaultRoot_/Adaptor.xml:
<HTTPTunnel>
                <Enable>true</Enable>
                <NodeID></NodeID>
                <IdlePostInterval>512</IdlePostInterval>
                <IdleAckInterval>512</IdleAckInterval>
                <IdleTimeout>60</IdleTimeout>
                <MimeType>application/x-fcs</MimeType>
                <WriteBufferSize>16</WriteBufferSize>
                <SetCookie>true</SetCookie>
                <Redirect enable="false" maxbuf="16384">
                        <Host port="80">:8080</Host>
                        <Host port="443">:8443</Host>
                </Redirect>
                <HttpProxy enable="true" maxbuf="16384">
                        <Host port="80">${HTTPPROXY.HOST}</Host>
                </HttpProxy>
                <NeedClose>true</NeedClose>
                <MaxWriteDelay>20</MaxWriteDelay>
                <MinWriteDelay>12</MinWriteDelay>
                <MaxHeaderLineLength>1024</MaxHeaderLineLength>
</HTTPTunnel>
I've tried changing lighttpd configuration to handle KeepAlive session or not, it has no influence on the behaviour.
If you spot a configuration mistake or have any idea, I'm ready to test it as soon as possible... Asa?
Thanks

Has this been fixed? What was done?
We have been having the same issue. We worked on it with Adobe support and thought it might have been fixed with a "patched" version of FMS that was created to solve the problem. However, we still see the issue (recently we had a huge increase in load due to an annual event).
Over time, when we run netstat, we see Apache connections (127.0.0.1:88134) stuck in a FIN_WAIT_1 state while the corresponding FMS processes (127.0.0.1:1025 to 5000) are in an ESTABLISHED state. It appears as though the connection is closed from the http proxy side while FMS doesn't acknowledge the close.
We notice this behavior seems related to load. High load = connections getting hung more frequently. The only fix seems to be restarting the FMS service which restarts the embedded apache as well.
I'm curious if you found a fix or even a workaround to help you cope with these connections. Even something to close them periodically would be a huge help. So far, we're resorting to an automatic restart of the server ever 2 days which is hardly a proper production solution.
I would really appreciate any information you could provide with regards to your particular problem and whether or not it's been solved.
An example (just a snippet) of the netstat monitor we have running each hour on the half-hour:
Proto Local Address          Foreign Address        State
<snip FMS to Apache>
TCP    127.0.0.1:2847         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2848         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2849         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2850         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2851         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2853         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2854         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2855         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2856         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2857         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2858         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2859         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2860         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2861         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2862         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2863         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2864         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2865         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2866         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2867         127.0.0.1:8134         ESTABLISHED
TCP    127.0.0.1:2868         127.0.0.1:8134         ESTABLISHED
</snip FMS to Apache>
<snip Apache to FMS (corresponding entries)>
TCP    127.0.0.1:8134         127.0.0.1:2847         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2848         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2849         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2850         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2851         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2853         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2854         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2855         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2856         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2857         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2858         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2859         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2860         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2861         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2862         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2863         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2864         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2865         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2866         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2867         FIN_WAIT_1
TCP    127.0.0.1:8134         127.0.0.1:2868         FIN_WAIT_1
</snip Apache to FMS>
This particular log shows all ports between 1024 and 5000 in the same state as above. A restart resets all the connections and the process starts over. From my investigation, Apache seems to be acting properly. It tries to be a 'good citizen' and issue a graceful close that goes unacknowledged by FMS. Unfortunately, Apache doesn't go back to check a connection it considers closed, so they connection remains half-closed.
Please, please let me know if you found anything out. Information on the web is scarce and I'm at my wit's end!

One Statement - Many ResultSets??

Hey Folks,
how good of an idea is it to use just one DB Statement and than make many queries on it ending up in different resultsets:
Like this:
try
               Class.forName("com.mysql.jdbc.Driver").newInstance ();
               con = DriverManager.getConnection (url, benutzer, passwort);
               stmt = verbindung.createStatement();
          catch (Exception e)
               e.printStackTrace();
ResultSet rs7 = null;
          try {
               rs7 = stmt.executeQuery("SELECT * FROM artikel WHERE `artikel_nr` = " + artikelnr);
               while ( rs7.next() ) {
                    level = rs7.getInt("persopreislevel");
          } catch (SQLException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
rs7.close();
ResultSet rs8 = null;
          try {
               rs8 = stmt.executeQuery("SELECT * FROM artikel WHERE `artikel_nr` = " + artikelnr);
               while ( rs8.next() ) {
                    level = rs8.getInt("persopreislevel");
          } catch (SQLException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
rs8.close();Or would I have to create one Statement per ResultSet?? How do I avoid creating to many Objects??
My Problem is that i get NoOperationAllowed after ResultSet closed Errors once in a while, even though I am using different Resultsets but JDBC Api says 1 ResultSet per Statement right?
Best regards
Edited by: eCashier on Apr 1, 2008 7:26 AM

Why not use a prepared statement and then a loop iterating through the parameters that you want to supply to the query instead of hardcoding eight queries that do essentially the same thing?
But no, there's no profound overhead from opening multiple resultsets in sequence as long as you close them when you're done with them. You should close them in a finally block. The overhead from the result set objects is unlikely to be significant as long as they're closed.

Sgd client does not close after logging out of sgd on windows vista

Hi,
I have a scenario wherein I find that the sgd client in the system tray does not close even after logging out of sgd (using the browser).
We are using sgd 4.3.1
Is this a known issue.
Thanks,

Well, after searching every where, somewhere (not sure where now) I saw the suggestion to turn off bluetooth and NFC. I turned off both and it *seems* like the issue may be corrected. But what if I want touse a BT device, I guess I am stuck?
As to your questions, I my have changed to a larger mouse cursor, either that or the default cursor.
I think I may have had "mouse trails" clicked, not sure if that it the same as a mouse shadow? Neither ofthese options seem to make a difference.
I had a standard Windows provided background for use, no personal photos.
Hopefully this partial fix (turning off the other settings) helps someone else. It seems to have fixed the problem for me, at least in the last 3-4 days since switching I have not noted a return of the problem.
Dragon-Fur wrote:
I wish I were writing with a fix. I, too, have a new X2 -- I like it very much. I have not seen what you describe.
Instead, I have more questions; I am intrigued. I wonder if the way in which you have the system set is having an affect on the way it is behaving.
Do you see the problem regardless of which mouse pointer you set?
There are a variety of choices -- I use an extra large white arrow most of the time; sometimes I switch to a black cursor just for grins. You can change the selectors, too. Right-Click on the Background Screen and click Personalize ...
Are you using the entirely useless, but oh-so-pretty "mouse shadow"?
I am wondering if changing the pointer has had any effect on the disappearing act.
What about the background? Are you using a personal photo? Lots of colors? Does changing the background make any difference?

Report window does not close properly when using openDocument

XI R2 InfoView
Windows 2003 server
IIS
IE7
We have been experimenting with the use of openDocument and have managed to achieve what we wanted but have one small problem. When the document is retrieved it is opened in a new browser window. When Close is selected from the drop-down Document menu the document is closed but the window shrinks to approx 8.5cm x 6 cm and remains open.
A similar thing happens when we use the Preview button to view a document in the CMC, except in that case the document does not close and closing the browser window leaves a button on the Windows taskbar. There doesn't appear to be a related window as it cannot be restored but you have to right click and select Close to get rid of it.
Any ideas what is causing these problems and how we can get round them?

Anne,
There are some parameters in opendocument (for ex. sWindow) that can help control certain things, have you tried employing anything like that? What I find frustrating is the behavior of opendocument based on whether you're running Infoview or WebI -- each product, using the same exact opendocument syntax yields different results. Based on the sample code below, what I'm seeing with Infoview is the same browser instance is used for calling the child report, however, in WebI, a new browser instance is started and the child report is rendered in Infoview. In my case, when running within WebI and getting a new browser instance in Infoview, and then using the "Document", "close" workflow, the second instance is exiting and I'm back to the previous browser. Staying within Infoview entirely through the process, when closing the child report I get brought back to the folder list page. Who's to know?
="<a href=https://<server>/businessobjects/enterprise115/InfoView/scripts/opendocument.aspx?
idocid=100798&lsSInput_Pos_Nbr="+[Position Number Tracking]+">"+[Position Number Tracking]
+"</a>"
(double spaced on purpose)
Thanks,
John

What effect If not Close statement or resultSet

Similar Messages

Maybe you are looking for