I often find that, when I select files and use the Explorer menu "WinZip/Add to somefile.zip", the somefile.zip remains opened by "some" process (Windows doesn't bother to tell you which one). Using ProcessExplorer doesn't help identifying the process.
The only workaround I found so far is restarting the Explorer.exe process.
Windows is a pathetic piece of piecemeal spaghetti disaster and WinZip is not better. I normally use 7Zip.
Thursday, February 25, 2016
Monday, February 22, 2016
Notepad++ : all the accessories you need for it
Notepad++ is a really great tool, but you need a couple of plugins to make it a truly joyful war machine:
TextFX https://sourceforge.net/projects/npp-plugins/files/TextFX/
Xml Tools https://sourceforge.net/projects/npp-plugins/files/XML%20Tools/
They are both priceless!
For installation instructions, I leave you to google
TextFX https://sourceforge.net/projects/npp-plugins/files/TextFX/
Xml Tools https://sourceforge.net/projects/npp-plugins/files/XML%20Tools/
They are both priceless!
For installation instructions, I leave you to google
Labels:
notepad++
Friday, February 19, 2016
weblogic.security.subject.SubjectManager.getSubjectManager hangs when using wrong JDK
Trying to connect from Eclipse to a WLS, Java client for EJB, using 2 way SSL and t3s, we get a stuck thread on this:
The issue was solved changing JDK
"main" #1 prio=5 os_prio=0 tid=0x000000000263f000 nid=0x12900 in Object.wait() [0x0000000002a6d000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000d8d00d00> (a java.lang.Object) at java.lang.Object.wait(Object.java:502) at weblogic.security.subject.SubjectManager.getSubjectManager(SubjectManager.java:277) - locked <0x00000000d8d00d00> (a java.lang.Object) at weblogic.security.subject.SubjectManager$GetKernelIdentityAction.run(SubjectManager.java:440) at weblogic.security.service.SecurityManager.getKernelIdentity(SecurityManager.java:164) at weblogic.security.service.GetKernelIdentityAction.run(GetKernelIdentityAction.java:25) at java.security.AccessController.doPrivileged(Native Method) at weblogic.jndi.WLSJNDIEnvironmentImpl.(WLSJNDIEnvironmentImpl.java:57) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at weblogic.jndi.internal.JNDIEnvironment.getJNDIEnvironment(JNDIEnvironment.java:37) at weblogic.jndi.Environment. (Environment.java:92) ...
The issue was solved changing JDK
Subscribe to:
Posts (Atom)