Java Threads not being released after loggin off

Hello everyone,
We are seeing a weird problem in our PI 7.0 box.
Once I logout from the XI box (both ABAP and Java stck) my basis tem still sees Java threads aginst my id still open. Our system does not seem to be realeasing Java threads.
Is this a know problem? What are the remidition steps.

Hi,
Are there existing HTTP sessions only?
The following might be helpful.
http://help.sap.com/saphelp_nw73/helpdata/en/c7/5ee440ba994fa3b187ff2f050cfe7c/content.htm
http://wiki.sdn.sap.com/wiki/display/ERPHCM/Sessionnotendingafterlogoff
Regards,
Varun

Similar Messages

Pictures are not being delivered after saying delivered on iMessage.

Pictures are not being delivered after saying delivered on iMessage.
Txting through iMessage works fine. Pic's won't send.
I turned on and off everything and did all the necessary trouble shooting.
I'm on a Verizon 4S. and I'm sure Verizon has nothing to do with iMessage system, since it's on its on server.

bump

Jave is not coming up after SID refresh where as ABAP is Up

Recently I completed system refresh for Solution Manager 4.0 with DB SQL Server 2005 on Duel stack and Java is not coming up after SID refresh where as ABAP is Up.
Please advise where to check as i check Disp log and Java Dispatcher is not coming up and giving error DB connection.
Thanks
Sachin Sachdeva

How did you do the refresh? What method, export with SAPINST(both ABAP and Java)?
Post the DB connection error you are getting.
Can you connect to configtool?
Message was edited by:
Derek Galt

Is there a way of not being able to power off my phone when my phone is locked?

is there a way of somone not being able to power off my phone when it is locked?
i.e if it were stolen someone could just turn it off and i would not be able to track it via "find my iphone"
thanks

Sorry, no way to do that.

My new i phone 6 plus some time not connecting wifi after switching off it start and after some time gain its stop connection please advice

my new i phone 6 plus some time not connecting wifi after switching off it start and after some time gain its stop connection please advice

settings - general - reset - reset network settings.

HT4623 Hello! Answer Why do not open pictures after power-off at iphone 3? Thank you!

Hello! Answer Why do not open pictures after power-off at iphone 3G? Thank you!

This problem is already two years.

Applets and memory not being released by Java Plug-in

Hi.
I am experiencing a strange memory-management behavior of the Java Plug-in with Java Applets. The Java Plug-in seems not to release memory allocated for non-static member variables of the applet-derived class upon destroy() of the applet itself.
I have built a simple "TestMemory" applet, which allocates a 55-megabytes byte array upon init(). The byte array is a non-static member of the applet-derived class. With the standard Java Plug In configuration (64 MB of max JVM heap space), this applet executes correctly the first time, but it throws an OutOfMemoryException when pressing the "Reload / Refresh" browser button or if pressing the "Back" and then the "Forward" browser buttons. In my opionion, this is not an expected behavior. When the applet is destroyed, the non-static byte array member should be automatically invalidated and recollected. Isn't it?
Here is the complete applet code:
// ===================================================
import java.awt.*;
import javax.swing.*;
public class TestMemory extends JApplet
private JLabel label = null;
private byte[] testArray = null;
// Construct the applet
public TestMemory()
// Initialize the applet
public void init()
    try
      // Initialize the applet's GUI
      guiInit();
      // Instantiate a 55 MB array
      // WARNING: with the standard Java Plug-in configuration (i.e., 64 MB of
      // max JVM heap space) the following line of code runs fine the FIRST time the
      // applet is executed. Then, if I press the "Back" button on the web browser,
      // then press "Forward", an OutOfMemoryException is thrown. The same result
      // is obtained by pressing the "Reload / Refresh" browser button.
      // NOTE: the OutOfMemoryException is not thrown if I add "testArray = null;"
      // to the destroy() applet method.
      testArray = new byte[55 * 1024 * 1024];
      // Do something on the array...
      for (int i = 0; i < testArray.length; i++)
        testArray[i] = 1;
      System.out.println("Test Array Initialized!");
    catch (Exception e)
      e.printStackTrace();
// Component initialization
private void guiInit() throws Exception
    setSize(new Dimension(400, 300));
    getContentPane().setLayout(new BorderLayout());
    label = new JLabel("Test Memory Applet");
    getContentPane().add(label, BorderLayout.CENTER);
// Start the applet
public void start()
    // Do nothing
// Stop the applet
public void stop()
    // Do nothing
// Destroy the applet
public void destroy()
    // If the line below is uncommented, the OutOfMemoryException is NOT thrown
    // testArray = null;
//Get Applet information
public String getAppletInfo()
    return "Test Memory Applet";
// ===================================================Everything works fine if I set the byte array to "null" upon destroy(), but does this mean that I have to manually set to null all applet's member variables upon destroy()? I believe this should not be a requirement for non-static members...
I am able to reproduce this problem on the following PC configurations:
* Windows XP, both JRE v1.6.0 and JRE v1.5.0_11, both with MSIE and with Firefox
* Linux (Sun Java Desktop), JRE v1.6.0, Mozilla browser
* Mac OS X v10.4, JRE v1.5.0_06, Safari browser
Your comments would be really appreciated.
Thank you in advance for your feedback.
Regards,
Marco.

Hi Marco,
my guess as to why JPI would keep references around, if it does keep them, is that it propably is an implementation side effect. A lot of things are cached in the name of performance and it is easy to leave things laying around in your cache. Maybe the page with the associated images/applets is kept in the browser cache untill the browser needs some memory and if the browser memory manager is not co-operating with the JPI/JVM memory manager the browser is not out of memory, thus not releasing its caches but the JVM may be out of memory. Thus the browser indirectly keeps the reference that it realy does not need. This reference could be inderect through some 'applet context' or what ever the browser uses to interact with JPI, don't realy know any of these details, just imaging what must/could be going on there. Browser are amazingly complicated beast.
This behaviour that you are observing, weather the origin is something like I speculated or not, is not nice but I would not expect it to be fixed even if you filed a bug report. I guess we are left with relleasing all significatn memory structures in destroy. A simple way to code this is not to store anything in the member fields of the applet but in a separate class; then one has to do is to null that one reference from the applet to that class in the destroy method and everything will be relased when necessary. This way it is not easy to forget to release things.
Hey, here is a simple, imaginary, way in which the browser could cause this problem:
The browser, of course needs a reference to the applet, call it m_Applet here. Presume the following helper function:
Applet instantiateAndInit(Class appletClass) {
Applet applet=appletClass.newInstance();
applet.init();
return applet;
When the browser sees the applet tag it instantiates and inits the new applet as follows:
m_Applet=instantiateAndInit(appletClass);
As you can readily see, the second time the instantiation occurs, the m_Applet holds the reference to the old applet until after the new instance is created and initlized. This would not cause a memory leak but would require that twice the memory needed by the applet would be required to prevent OutOfMemory.I guess it is not fair to call this sort of thing a bug but it is questionable design.In real life this is propably not this blatant, but could happen You could try, if you like, by allocating less than 32 Megs in your init. If you then do not run out of memory it is an indication that there are at most two instances of your applet around and thus it could well be someting like I've speculated here.
br Kusti

Java is not coming up after deploying Cryptographic toolkit 1.4

Hi,
when i open the keystore service in visualadministrator, i got following issue.
Java.lang.NoClassDefFoundError.iaik/security/provider/IAIK
IAIK security library not found
after searching in SDN i got the following link :
http://help.sap.com/saphelp_nw04/helpdata/en/8d/cb71b8046e6e469bf3dd283104e65b/frameset.htm
After deploying Cryptographic toolkit 1.4 through SDM, i have restarted the system. java is not coming up. the system is ABAP+JAVA system.
Could you please tell how to undeploy the tc_sec_java_crypto_signed_fs_lib.sda component. i have tried through standalone mode also but i could not find that component. i could not able to login to the visual admin, configtool.
Regards,
Jagadish

I have pasted both server0 log and default trace.
please find the log which is pasted.
SERVER0 LOG
[Thr 6276] *************** SAP_STINIT3 ***************
[Thr 6276] SAP_STINIT3: my TP_name: >jlaunch<
[Thr 6276] SAP_STINIT3: new buffer state = BUFFER_EMPTY
[Thr 6276] SAP_STINIT3: GWHOST=localhost
[Thr 6276] SAP_STINIT3: GWSERV=sapgw22
[Thr 6276] SAP_STINIT3: PROTOCOL=I
[Thr 6276] GwIConnect: connect to gateway localhost / sapgw22 (timeout=60000)
[Thr 6276] NiHsLGetNodeAddr: found hostname 'localhost' in cache
[Thr 6276] NiIGetNodeAddr: hostname 'localhost' = addr
[Thr 6276] NiHsLGetServNo: found service name 'sapgw22' in cache
[Thr 6276] NiIGetServNo: servicename 'sapgw22' = port 0C.FA/3322
[Thr 6276] NiICreateHandle: hdl 11 state NI_INITIAL
[Thr 6276] NiIInitSocket: set default settings for new hdl 11 / sock 4656 (I4; ST)
[Thr 6276] NiIBlockMode: set blockmode for hdl 11 FALSE
[Thr 6272] *************** SAP_STINIT3 ***************
[Thr 6272] SAP_STINIT3: my TP_name: >jlaunch<
[Thr 6272] SAP_STINIT3: new buffer state = BUFFER_EMPTY
[Thr 6272] SAP_STINIT3: GWHOST=localhost
[Thr 6272] SAP_STINIT3: GWSERV=sapgw22
[Thr 6272] SAP_STINIT3: PROTOCOL=I
[Thr 6272] GwIConnect: connect to gateway localhost / sapgw22 (timeout=60000)
[Thr 6272] NiHsLGetNodeAddr: found hostname 'localhost' in cache
[Thr 6272] NiIGetNodeAddr: hostname 'localhost' = addr
[Thr 6272] NiHsLGetServNo: found service name 'sapgw22' in cache
[Thr 6272] NiIGetServNo: servicename 'sapgw22' = port 0C.FA/3322
[Thr 6272] NiICreateHandle: hdl 13 state NI_INITIAL
[Thr 6272] NiIInitSocket: set default settings for new hdl 13 / sock 4516 (I4; ST)
[Thr 6272] NiIBlockMode: set blockmode for hdl 13 FALSE
[Thr 2836] NiSelISelectInt: 0 handles selected (0 buffered)
[Thr 2836] SAP_CMLISTEN: timeout after 2000 msecs
[Thr 2836] *************** SAP_CMLISTEN ***************
[Thr 2836] SAP_CMLISTEN: timeout = 2000
[Thr 5584] Fri Feb 27 19:45:38 2009
[Thr 5584] JLaunchIShutdownCheck: check shutdown, 16 sec left to shutdown
[Thr 6276] NiHsLGetServName: found port number 0C.FA/3322 in cache
[Thr 6276] NiIGetServName: port 0C.FA/3322 = servicename 'sapgw22'
[Thr 6276] ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2764]
[Thr 6276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 11 / sock 4656
     (SI_ECONN_REFUSE; I4; ST; 127.0.0.1:3322) [nixxi.cpp    2764]
[Thr 6276] NiICloseHandle: closing initial hdl 11
[Thr 6276] *** ERROR => GwIConnect: GwConnect to localhost / sapgw22 failed (rc=NIECONN_REFUSED) [gwxx.c       294]
[Thr 6276] ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx.c       295]
[Thr 6276] ***LOG S0R=> GwIConnect, GwConnect () [gwxx.c       297]
[Thr 6276] ***LOG S0S=> GwIConnect, GwConnect (sapgw22) [gwxx.c       299]
[Thr 6276] ***LOG S90=> SAP_STINIT3, GwIConnect ( 236) [r3cpic.c     2006]
[Thr 6276]
[Thr 6276] * LOCATION    CPIC (TCP/IP) on local host with Unicode
[Thr 6276] * ERROR       partner '127.0.0.1:sapgw22' not reached
[Thr 6276] *
TIME        Fri Feb 27 19:45:38 2009
[Thr 6276] * RELEASE     700
[Thr 6276] * COMPONENT   NI (network interface)
[Thr 6276] * VERSION     38
[Thr 6276] * RC          -10
[Thr 6276] * MODULE      nixxi.cpp
[Thr 6276] * LINE        2764
[Thr 6276] * DETAIL      NiPConnect2
[Thr 6276] * SYSTEM CALL connect
[Thr 6276] * ERRNO       10061
[Thr 6276] * ERRNO TEXT WSAECONNREFUSED: Connection refused
[Thr 6276] * COUNTER     3
[Thr 6276] *
[Thr 6276] *****************************************************************************
[Thr 6272] NiHsLGetServName: found port number 0C.FA/3322 in cache
[Thr 6272] NiIGetServName: port 0C.FA/3322 = servicename 'sapgw22'
[Thr 6272] ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2764]
[Thr 6272] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 13 / sock 4516
     (SI_ECONN_REFUSE; I4; ST; 127.0.0.1:3322) [nixxi.cpp    2764]
[Thr 6272] NiICloseHandle: closing initial hdl 13
[Thr 6272] *** ERROR => GwIConnect: GwConnect to localhost / sapgw22 failed (rc=NIECONN_REFUSED) [gwxx.c       294]
[Thr 6272] ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx.c       295]
[Thr 6272] ***LOG S0R=> GwIConnect, GwConnect () [gwxx.c       297]
[Thr 6272] ***LOG S0S=> GwIConnect, GwConnect (sapgw22) [gwxx.c       299]
[Thr 6272] ***LOG S90=> SAP_STINIT3, GwIConnect ( 236) [r3cpic.c     2006]
[Thr 6272]
[Thr 6272] * LOCATION    CPIC (TCP/IP) on local host with Unicode
[Thr 6272] * ERROR       partner '127.0.0.1:sapgw22' not reached
[Thr 6272] *
TIME        Fri Feb 27 19:45:38 2009
[Thr 6272] * RELEASE     700
[Thr 6272] * COMPONENT   NI (network interface)
[Thr 6272] * VERSION     38
[Thr 6272] * RC          -10
[Thr 6272] * MODULE      nixxi.cpp
[Thr 6272] * LINE        2764
[Thr 6272] * DETAIL      NiPConnect2
[Thr 6272] * SYSTEM CALL connect
[Thr 6272] * ERRNO       10061
[Thr 6272] * ERRNO TEXT WSAECONNREFUSED: Connection refused
[Thr 6272] * COUNTER     2
[Thr 6272] *
[Thr 6272] *****************************************************************************
[Thr 2836] Fri Feb 27 19:45:39 2009
[Thr 2836] NiSelISelectInt: 0 handles selected (0 buffered)
[Thr 2836] SAP_CMLISTEN: timeout after 2000 msecs
[Thr 2836] *************** SAP_CMLISTEN ***************
[Thr 2836] SAP_CMLISTEN: timeout = 2000
[Thr 3508] ShmCache_nativeDelete (3)
[Thr 3508] ShmCache_nativeDelete (2)
[Thr 3508] ShmCache_nativeDelete (0)
[Thr 3508] ShmCache_nativeDelete (1)
[Thr 3508] Fri Feb 27 19:45:40 2009
[Thr 3508] JHVM_NativeSetState: set process state to 6
[Thr 3508] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 5584] JLaunchIShutdownCheck: check shutdown, 14 sec left to shutdown
[Thr 2836] Fri Feb 27 19:45:41 2009
[Thr 2836] NiSelISelectInt: 0 handles selected (0 buffered)
[Thr 2836] SAP_CMLISTEN: timeout after 2000 msecs
[Thr 2836] *************** SAP_CMLISTEN ***************
[Thr 2836] SAP_CMLISTEN: timeout = 2000
[Thr 5584] Fri Feb 27 19:45:42 2009
[Thr 5584] JLaunchIShutdownCheck: check shutdown, 12 sec left to shutdown
[Thr 2836] Fri Feb 27 19:45:43 2009
[Thr 2836] NiSelISelectInt: 0 handles selected (0 buffered)
[Thr 2836] SAP_CMLISTEN: timeout after 2000 msecs
[Thr 2836] *************** SAP_CMLISTEN ***************
[Thr 2836] SAP_CMLISTEN: timeout = 2000
[Thr 5584] Fri Feb 27 19:45:44 2009
[Thr 5584] JLaunchIShutdownCheck: check shutdown, 10 sec left to shutdown
[Thr 5840] Fri Feb 27 19:45:45 2009
[Thr 5840] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 5840] JsfCloseShm: JsfCloseShm() -> 0
[Thr 5840] JLaunchCloseProgram: good bye (exitcode = 0)
DEFAULT TRACE
#1.5#001143318A03002C00000186000015CC000463E71A6EB1E0#1235744138921#com.sap.engine.services.connector##com.sap.engine.services.connector#######SAPEngine_System_Thread[impl:5]_18##0#0#Error#1#/System/Server#Java#connector_0500##"ResourceObjectFactory" is closed. Possible reasons: the Connector Service is stopped or not started.#1#ResourceObjectFactory#
#1.5#001143318A03002C00000187000015CC000463E71A6EB538#1235744138921#com.sap.engine.services.connector##com.sap.engine.services.connector#######SAPEngine_System_Thread[impl:5]_18##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.connector.exceptions.BaseResourceException: "ResourceObjectFactory" is closed. Possible reasons: the Connector Service is stopped or not started.
     at com.sap.engine.services.connector.ResourceObjectFactory.removeConnectionFactory(ResourceObjectFactory.java:401)
     at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.clearAllResources(ContainerImpl.java:1677)
     at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.commitStop(ContainerImpl.java:768)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
     at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
     at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4244)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
     at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:243)
     at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#001143318A03003E0000000D000015CC000463E71A7BC7F1#1235744139781#com.sap.engine.services.deploy##com.sap.engine.services.deploy#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Plain###CACHE MAY BE NOT CLEARED, while stopping sap.com/crmmigrxcm application.#
#1.5#001143318A0300740000004B000015CC000463E71A8A8DA4#1235744140750#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#0#####Thread[Thread-715,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_50]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]106a69b] with classloader [[email protected]be66@service:log_configurator]#
#1.5#001143318A0300740000004C000015CC000463E71A8B2DF0#1235744140781#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#0#####Thread[Thread-715,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_69]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.jms.client.connection.AsyncCloser | toString: com.sap.jms.client.connection.AsyncCloser@1a41c14] with classloader [[email protected]f854@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]

Java processes not coming up after WAS JAVA installation

Hi,
After installing WAS ABAP and WAS JAVA, the Java related processes are not being seen.
Under /usr/sap/<instance_name>/work, dev_jcontrol shows the following error:
ERROR => OS release OS/400 V5R4 M0 570 is not supported with this startup framework (640) [jstartxx_mt. 3883]
I had applied the SAPJ2EE patch but still I am having the same error.
What next I could do to bring the Java processes up?
Thanks
Kiran

Hi Kiran,
I do have in mind, that this is described in the installation notes. It is very easy. The CDs are built for V5R3 and not V5R4 - but you are running V5R4. So, you need to patch the J2EE engine to the latest level and then this problem will disappear as the latest patch for sure includes the V5R4 certification.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Java thread not working in windows 7

I have a Java app that runs just fine on Windows XP. However, on Windows 7 there is a problem related to a job being done via a Java thread.
Background: The app spawns a separate job via a Java thread and continues on while the spawned job executes. In other words, 2 things happen at once.
Problem: On Windows 7, when the app spawns the job, Windows sits and waits for the spawned job to complete before it continues on. In other words, 2 things DO NOT happen at once.
It's as if Java threading does not work in Windows 7. Any input would be greatly appreciated. Thanks.

l_sleven wrote:
Thanks for the input, guys. From now on I'll be sure to include a SSCCE.
I'm beginning to believe this is actually my ignorance of threading in SWT, and XP was more forgiving than 7.
I would include a SSCCE, but of the 4 different ways I tried to get this to work I wouldn't know which to include since all failed to fix the problem.
If you want to identify a link to a web page identifying 'best practices' for SWT threading, that would be great. Be aware though that there's a good chance I've already googled the page.
A programmer smarter than me once said, "The road to best practices is a bumpy ride".[Concurrency in Swing|http://download.oracle.com/javase/tutorial/uiswing/concurrency/index.html]

Rules in Mail not being applied after Mavericks update

Hi everyone, I know there are a lot of threads already discussing similar issues, but so far I've been unable to find one that helps resolve my particular issue. Ever since upgrading to Mavericks my rules are not being applied in Mail. I will give you a screenshot of one of my rules:
I have about five rules that follow the same pattern: search for particular string in the FROM field and mark it with a color if the string is present. These rules all worked fine in Snow Leopard. All of my rules are still present after the upgrade and all checked as active. When I "select all" messages in my inbox and press Option-Cmd-L the rules are applied properly. However, the rules are not applying themselves when new mail comes in. As far as I can tell this does not have anything to do with the mail not being recognizes “as a new message” like, for example, because the mail was already read on my phone. It happens even if my other devices are offline and the only thing I am using to check mail is my laptop.
I am using a MacBook Pro 2.3 GHz Intel Core Duo with OS X 10.9.1, in case that matters.
Thanks for any advice!

I think I've found at least a partial solution to the Mail - Rules Don't Work problem:
In "Mail" go to the menu Mailbox and click on Rebuild.
If you have a lot of stuff, this will take several minutes to finish.
I also reviewed all my rules and made a few minor changes.
Mixed results: I found that running "Apply Rules" didn't work on email already received; but new mail did. I don't quite understand that, but I call it a partial success.

Memory does not get released after encrypting/ decrypting files.

I am using javax.crypto package to encypt/decrypt files but the problem is that once a big file (around 100- 700 mb) is encrypted there is spike in memory of 70 Mb (first time) and whole of this memory is not released after execution is finished. I have kept my application run for days but this memory do not come down.
Interesting thing is if I encrpyt/ decrypt the same file again and again the memory do not rise by 70 Mb, but for first 3-4 iterations 5-8 Mb of memory is released in each iteration and after that memory starts increasing again in chunk of 2-5 Mb and after few iteration some memory get released but in all the memory always increases. The code to encrypt file is simple
Cipher c = Cipher.getInstance("AES/CBC/PKCS5Padding");
byte[] salt = generateRandomBytes(16);
Rfc2898DeriveBytes rfc = new Rfc2898DeriveBytes("123456", salt, 1000);
SecretKey key = new SecretKeySpec(rfc.getBytes(32), "AES");
c.init(Cipher.ENCRYPT_MODE, key );
FileOutputStream fos = new FileOutputStream(encryptedFile);
CipherOutputStream cos = new CipherOutputStream(fos);
FileInputStream fis = new FileInputStream(largeInputFile);
int len = 0;
byte[] buf = new byte[1024 * 128];
while((len = fis.read(buf)) != -1) {
cos.write(buf, 0, len);
cos.close();
fis.close();
This is simple observation I have seen in my program:
I am using Windows 7 64 bit with 16 GB RAM Intel Core 2 Duo 3.00 GHz and file encrypted was 700 MB size
Explanation
Memory Usage (As shown in Windows Task Manager Private Working Set column)
When program starts
9924 K
After first iteration of encryption
81,180 K
Second Iteration
78,254 K
3 Iteration
74,614 K
4 Iteration
69,523 K
5 Iteration
72,256 K
6 Iteration
70,152 K
7 Iteration
83,327 K
8 Iteration
85,613 K
9 Iteration
95,124 K
10 Iteration
92,698 K
11 Iteration
94,670 K
I kept the iteration on for 2000 iteration, the same pattern was observed and at the end memory usage 184,951 K, this memory was not released after calling System.gc() also.
What could be the possible problem, is it the CipherOutputStream or Cipher class having some memory leak or I am doing something wrong here?

ash wrote:
We are using WebLogic Server 7.0 runing on Solaris 2.7.
We are experiencing a problem where the memory does not seem to be released after
the application has been shut down.What do you mean by "application has been shut down"? Is the server
process running or not? Is it a zombie?
The
Unix 'top' command reports that memory has not been reclaimed by the O/S. What exactly has it reported? If the process is gone, then I'm pretty
sure your O/S has reclaimed the memory. What exactly are you looking at
in top?
-- Rob
> Continue
restarting it will forces us to reboot the server as there will be more and more
memory lost when restarting the WebLogic.
Advice to fix the problem is much appreciated. Thanks.

Seagate portable drive not being recognized after OSX10.9.2

After I installed the 9.2 update, my Seagate portable external drive is not being recognized - doesnt show up in Finder, or Disk Utility, but I know the drive is live, as I can feel it vibrating
Someone please help, all my time machine backup is on that

I had the same issue - the Seagate drive is in a format that will recognize both Windows and Mac formats and there seems to be a flaw with Seagate. After working on this for five hours and finally calling Apple, I found out why. If you reformat to Mac OS extended journaled then they usually start working properly.
When I contacted Seagate they said it was best if you are just using a mac to just use the Mac formatting.
Hope this helps and good luck. Hope there wasn't any valuable data on the drive.

Batteries not being recognised after update!!

My OS seems to be messed up! I updated my battery while running on 10.4.3, and it asked me to remove battery and plug it back in and restart.
I did that, but now my battery is simply not recognised??? I tried plugging in the other battery but that too is not being recognised! Though both batteries run and I am able to use laptop without powerchord.. but once the battery runs out, i need to plug in powerchord and this does NOT charge the battery.
This is bad, as now I have 2 batteries which are not recognised after the update!?? I even tried updating to 10.4.4. Doesn't help!

Got it.
Try running the firmware update for the battery again.
The first couple of times I tried the firmware update failed. With the firmware update window open but in the "didn't work" mode, remove the battery and replace it and then hit the update button again. Took a couple of times but I got it to work, the computer recognized the battery and all is smiles again.
Jim
Two, 15" pb's
Two, 17" pb's
G5
Imac

HT3131 Clamshell mode not working even after powering off and reconnecting display; external monitor goes black anyway

After connecting an external monitor (non-Mac) to my MacBook (Mac OSX 10.6.6) w/proper adaptor, setting up to use clamshell mode as per manual, the external still goes black even after putting MacBook to sleep, disconnecting and reconnecting external and powering up again as suggested in Support. Displays are set to Mirror. Also, when I open Displays in System preferences, 2 different windows for Resolution settings appear. Where have I gone wrong? This monitor (Viewsonic) came with it's own software for setup on a Windows PC, but of course it is not being used on the MacBook.
Any help would be appreciated!

Hi Mike,
Yes I followed all the procedueres....except for waking the computer using a keyboard click. For obvious reasons one is just inclined to open the top of the MacBook to wake it when the external goes dark...I did that twice, until I realized that very last step was needed to 'wake' it. It worked. Something so simple, easy to overlook I guess.
I did leave the monitors mirrored, fyi, if I don't then all I can access from the external are the resolution settings. This Viewsonic comes pre-loaded with Windows software of it's own and doesn't quite behanve the way my previous external did, but I got it figured out.
Thanks for your response, tho!

Java Threads not being released after loggin off

Similar Messages

Maybe you are looking for