Lock & Edit Issue

Hi:
I am using Weblogic 9.2.
I am trying to unlocked my weblogic admin console, when I pressed "Lock & Edit" button there is a hour glass and and it goes on forever whithout unlocking the screen.
Is there a manual configuration file I can edit to fix this problem.
Yours,
Frustrate

Issue resolved..

Similar Messages

Since I've installed Mountain Lion, I am having lock up issues with multiple programs. MS Outlook has crashed and I've lost all my folders. HELP?

Since I've installed Mountain Lion, I am having lock up issues with multiple programs. MS Outlook has crashed and I've lost all my folders. HELP?

okay I've finally been able to get tor and all the other programs to work according to my plan the only thing that's still making problems is that iptables doesn't work as I want it to, when I start chromium without proxy settings privoxy doesn't seem to forward the information to polipo.. do I need to add another rule to iptables.rules in order for the program to know it has to reroute the information again or how can I get this to work? and is there any way to run rtorrent with proxy support?
anyway, problem 2 and 3 are still to be solved.
and does anybody know where i can get a good dansguardian blacklist that was not designed for 6 year old children and for which I don't need to subscribe? I'm still getting these partypoker popups -.-
//e: with iptables it's the same thing as described in the first post. https works, http doesnt. I get the output "Invalid header received from client." on http sites. still no idea why though.. (and the https-version of torcheck.xenubite says i'm tor unprotected while starting the browser with iptables)
Last edited by deF291 (2011-04-23 16:16:31)

Lock & Edit button not present in Change Center

Hi,
I installed Weblogic server 10.3. When i go to the administration console, the "Lock & Edit" button is not present in the Change Center. The Change Center is present and has the following text in there "Configuration editing is enabled. Future changes will automatically be activated as you modify, add or delete items in this domain".
Can someone please let me know if this is some issue that has to be fixed or is it because of any configurations this behaviour is seen.
Thanks,

Hi Jluis,
Thanks for guiding me, and changing the preferences the Change Center is now available as described in the documentation :)
Thanks,

No Lock & Edit button in WLS 10 Console

I don't have the Lock & Edit button in the WLS 10 Console. I know that this could be turned on and off in previous versions of WebLogic in the config.xml file, but I didn't find this anywhere in the documentation anymore.
Can anybody tell me how to make the Lock & Edit buton visible again in WebLogic 10.3a?
Thanx
Peter

Here is my config.xml ( I guess I cannot just attach it):
<?xml version='1.0' encoding='UTF-8'?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
     <name>IOP5</name>
     <domain-version>10.3.0.0</domain-version>
     <security-configuration>
          <name>IOP5</name>
          <realm>
          
               <sec:auditor xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-auditorType">
                    <sec:name>CSRealmCSAuditor</sec:name>
                    <prov:audit-logger-name>@audit.WLSAuditChannel</prov:audit-logger-name>
                    <prov:use-wls-log-handler>false</prov:use-wls-log-handler>
                    <prov:providers-logs-enabled>false</prov:providers-logs-enabled>
               </sec:auditor>
               <sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
                    <sec:name>SAMLIdentityAsserter</sec:name>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xsi:type="prov:cssaml-authenticatorType" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xmlns:dom="http://www.bea.com/ns/WebLogic/920/domain" xmlns:xsi1="xsi">
                    <sec:name>CS SAML Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
               </sec:authentication-provider>


               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-identity-asserterType">
                    <sec:name>CS Identity Asserter</sec:name>
                    <prov:credentials-validators>X.509=com.csg.cs.security.wls.authentication.pki.ext.CSPKICredentialValidator</prov:credentials-validators>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-principal-authenticatorType">
                    <sec:name>CS Principal Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    <prov:credential-validator>com.csg.cs.security.wls.authentication.pki.ext.CSPrincipalCredentialValidator</prov:credential-validator>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:csb1-authenticatorType">
                    <sec:name>CS B1 Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authenticatorType">
                    <sec:name>CS Authentication Provider</sec:name>
                    <sec:control-flag>SUFFICIENT</sec:control-flag>
                    <prov:log-in-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:log-in-module-class-name>
                    <prov:assertion-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:assertion-module-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-internal-identity-asserterType">
                    <sec:name>CS Internal Identity Asserter</sec:name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-data-layer-providerType">
                    <sec:name>CS Data Layer Security Provider</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                                   <prov:key-alias>SYSTEM</prov:key-alias>
                                   <prov:key-store-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-store-pass-phrase-encrypted>
                                   <prov:key-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-pass-phrase-encrypted>
               </sec:authentication-provider>
               <sec:role-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-role-mapperType">
                    <sec:name>CS Role Mapper</sec:name>
                    <sec:role-deployment-enabled>true</sec:role-deployment-enabled>
                    <prov:is-debug>false</prov:is-debug>
                    <prov:application-role-mapper-class-name></prov:application-role-mapper-class-name>
               </sec:role-mapper>
               <sec:authorizer xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authorizerType">
                    <sec:name>CS Authorization Provider</sec:name>
               </sec:authorizer>
               <sec:credential-mapper xsi:type="sam:saml2-credential-mapperType" xmlns:sam="http://www.bea.com/ns/weblogic/90/security/saml2">
                    <sec:name>SAML2CredentialMapper</sec:name>
                    <sam:issuer-uri>http://www.credit-suisse.com</sam:issuer-uri>
                    <sam:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</sam:name-qualifier>
                    <sam:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAML2NameMapperImpl</sam:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers">
                    <sec:name>SAMLCredentialMapper</sec:name>
                    <wls:issuer-uri>http://www.credit-suisse.com</wls:issuer-uri>
                    <wls:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</wls:name-qualifier>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-credential-mapperType">
                    <sec:name>CSCredentialMapper</sec:name>
               </sec:credential-mapper>
               <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
               <sec:cert-path-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cert-path-providerType">
                    <sec:name>CS Certificate Path Provider</sec:name>
                    <prov:cert-path-validator-class-name>com.csg.cs.security.wls.authentication.cert.ext.CSPKICertPathValidator</prov:cert-path-validator-class-name>
               </sec:cert-path-provider>
               <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
               <sec:deploy-role-ignored>true</sec:deploy-role-ignored>
               <sec:deploy-policy-ignored>true</sec:deploy-policy-ignored>
               <sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
               <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
               <sec:security-dd-model>Advanced</sec:security-dd-model>
               <sec:name>CSRealm</sec:name>
               <sec:delegate-m-bean-authorization>true</sec:delegate-m-bean-authorization>
          </realm>
          <default-realm>CSRealm</default-realm>
          <anonymous-admin-lookup-enabled>true</anonymous-admin-lookup-enabled>
          <credential-encrypted>{3DES}Zk0PFQd/y2JbBwcVCkoTVA==</credential-encrypted>
          <connection-filter>com.csg.cs.security.wls.net.ConnectionFilterImpl</connection-filter>
          <connection-logger-enabled>true</connection-logger-enabled>
     </security-configuration>
     <server>
          <name>IOPWLS5</name>
          <reverse-dns-allowed>true</reverse-dns-allowed>
          <ssl>
               <use-java>true</use-java>
               <enabled>true</enabled>
               
               <ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
               <ciphersuite>TLS_RSA_WITH_3DES_EDE_CBC_SHA</ciphersuite>
               <cert-authenticator></cert-authenticator>
               <hostname-verifier>com.csg.cs.security.wls.net.SSL.ext.CSPKIHostNameVerifier</hostname-verifier>
               <hostname-verification-ignored>false</hostname-verification-ignored>
               <export-key-lifespan>500</export-key-lifespan>
               <client-certificate-enforced>false</client-certificate-enforced>
               <listen-port>7002</listen-port>
               <two-way-ssl-enabled>true</two-way-ssl-enabled>
               <server-private-key-alias>tipd.csintra.net</server-private-key-alias>
               <server-private-key-pass-phrase-encrypted>{3DES}mQrgg0qTDHAhuU+2FACgZQ==</server-private-key-pass-phrase-encrypted>
               <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
               <inbound-certificate-validation>BuiltinSSLValidationAndCertPathValidators</inbound-certificate-validation>
               <outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
          </ssl>
          <log>
               <rotate-log-on-startup>true</rotate-log-on-startup>
               <logger-severity>Notice</logger-severity>
               <stdout-severity>Notice</stdout-severity>
               <log-file-filter xsi:nil="true" />
               <stdout-filter xsi:nil="true" />
               <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
               <domain-log-broadcast-filter xsi:nil="true" />
               <memory-buffer-filter xsi:nil="true" />
               <redirect-stdout-to-server-log-enabled>true</redirect-stdout-to-server-log-enabled>
               <redirect-stderr-to-server-log-enabled>true</redirect-stderr-to-server-log-enabled>
          </log>
          <machine xsi:nil="true"></machine>
          <listen-port>7001</listen-port>
          <listen-port-enabled>true</listen-port-enabled>
          <cluster xsi:nil="true"></cluster>
          <web-server>


               <send-server-header-enabled>false</send-server-header-enabled>
          </web-server>
          <iiop-enabled>false</iiop-enabled>
          <listen-address>127.0.0.1</listen-address>
          <staging-directory-name>./stage</staging-directory-name>
          <classpath-servlet-disabled>true</classpath-servlet-disabled>
          <key-stores>CustomIdentityAndCommandLineTrust</key-stores>
          <custom-identity-key-store-file-name>./keystores/identity.properties</custom-identity-key-store-file-name>
          <custom-identity-key-store-type>CS_PKI</custom-identity-key-store-type>
          <custom-identity-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-identity-key-store-pass-phrase-encrypted>
          <custom-trust-key-store-file-name>./keystores/trustedca.properties</custom-trust-key-store-file-name>
          <custom-trust-key-store-type>CS_PKI</custom-trust-key-store-type>
          <custom-trust-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-trust-key-store-pass-phrase-encrypted>
     </server>
     <embedded-ldap>
          <name>IOP5</name>
          <credential-encrypted>{3DES}nQpvTCkYlf4h4+8bAEI7JH8pg2Zo4uqNrVEu9bfYSr8=</credential-encrypted>
     </embedded-ldap>
     <administration-port-enabled>true</administration-port-enabled>
     <administration-port>9999</administration-port>
     <configuration-version>10.3.0.0</configuration-version>
     <app-deployment>
          <name>IOPA_root</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/root.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPD_prsysmgmt</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPD/prsysmgmt.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPC_prhelp</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPC/prhelp.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPA_prpc_j2ee14</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/prpc_j2ee14.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPB_prdbutil</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPB/prdbutil.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>



     <library>
          <name>CSWSPolicySAML11#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\WSS11SAML1WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>
     <library>
          <name>CSWSPolicySAML20#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\SAML2WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>






     
     <jms-server>
          <name>PRJMS_Server</name>
          <target>IOPWLS5</target>
     </jms-server>
     <jmx>
          <management-ejb-enabled>false</management-ejb-enabled>
     </jmx>
     <shutdown-class>
          <name>CSServerLifeCycleShutdown</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycleShutdown</class-name>
     </shutdown-class>
     <startup-class>
          <name>CSServerLifeCycle</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycle</class-name>
          <failure-is-fatal>true</failure-is-fatal>
          <load-before-app-deployments>true</load-before-app-deployments>
          <load-before-app-activation>false</load-before-app-activation>
     </startup-class>

     <jms-system-resource>
          <name>PRJMS_Module</name>
          <target>IOPWLS5</target>
          <sub-deployment>
               <name>PRJMS_Subdeployment</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <sub-deployment>
               <name>PRJMS_Subdeployment_Topic</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <descriptor-file-name>jms/prjms_module-jms.xml</descriptor-file-name>
     </jms-system-resource>
     <admin-server-name>IOPWLS5</admin-server-name>
     <jdbc-system-resource>
          <name>pega-rules</name>
          <target>IOPWLS5</target>
          <descriptor-file-name>jdbc/pega-rules-jdbc.xml</descriptor-file-name>
     </jdbc-system-resource>

     

     <webservice-security>
          <name>default_wss</name>
          <webservice-token-handler>
               <name>CSTokenHandler</name>
               <class-name>com.csg.cs.security.wls.authentication.wsee.TokenHandler</class-name>
               <token-type>ut</token-type>
               <handling-order>0</handling-order>
          </webservice-token-handler>
     </webservice-security>
</domain>
Regards
Peter

Bit locker security issues (easy to crack) disk encryption?

Bit locker security issues (easy to crack) disk encryption?
Problem 1: When the PC run I think its too easy to get malicious users (with usb pendrive) or spyware to get the encryption key (fast and easy)
youtube.com/watch?v=0npTlOq6q_0
Problem2:not resistant with bruteforce attacks
youtube.com/watch?v=zvaJxnvbGic
Problem 3: not resistant with boot hacking
Im using DriveCrypt plus pack and searched security issues in bit locker.The bit locker allow you the bruteforce/dic attack easy.I think It would be much safer 1. (I think the keys stored somewhere that is easily read) 2. Do not just be enough password
need a password+file combination to decrypt the disk. DriveCrypt plus pack use a file+password combination if you know the password but you wont have the file you can not decrypt the disk (protect with bruteforce attack).On system boot protected bruteforce
attak you can crash the (boot).If the boot system crash you can not decrypt the disk just the password you need the file+password combination plus to decrypt it. I am not a programmer but I see the BitLocker ( easy security catches to crack the disk encryption).Im
tested DriveCrypt and I can not get the key that easy (Problem 1). I have not tested it in greater depth just trying to (catches to crack software encryption).

Where is your question, sir?
If the question were "is it easy to crack", the answer is "no". Your videos make use of several assumptions and ingredients and permissions that a normal attacker does not have.
"Problem 3" is not clear, please describe what scenario you are talking about.

Locked thread issue

We encountered the following locked thread issue. Refer to the thread dump logs.
Any idea on the root cause of the issue? It seens to us that it is the weblogic app server codes that are causing the locked threads.
Will appreciate any advise.
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=22 idx=0x50 tid=329 prio=5 alive, in native, blocked, daemon
-- Blocked trying to get lock: java/lang/String@0x9a73910[fat lock]
at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)
at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674)[optimized]
at jrockit/vm/Locks.lockFat(Locks.java:1775)[optimized]
at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311)[optimized]
at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258)[optimized]
at jrockit/vm/Locks.monitorEnter(Locks.java:2455)[optimized]
at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=24 idx=0x58 tid=331 prio=5 alive, in native, blocked, daemon
-- Blocked trying to get lock: java/lang/String@0x9a73910[fat lock]
at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)
at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674)[optimized]
at jrockit/vm/Locks.lockFat(Locks.java:1775)[optimized]
at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311)[optimized]
at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258)[optimized]
at jrockit/vm/Locks.monitorEnter(Locks.java:2455)[optimized]
at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=23 idx=0x54 tid=330 prio=5 alive, in native, daemon
at jrockit/ext/epoll/EPoll.epollWait0(IIII)I(Native Method)
at jrockit/ext/epoll/EPoll.epollWait(EPoll.java:103)
at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:156)
^-- Holding lock: java/lang/String@0x9a73910[fat lock]
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace

This is standard behavior for the socket muxer threads. Only one of the epoll muxer threads is actually holding the lock at any one time. Here is the output of part of my thread dump on Linux with WLS 10.3.4 on JRockit on startup. The server is not hung up at all. Make a request on the server and take another thread dump and you'll see the lock change.
1st dump with ExecuteThread 1 waiting to get the lock from ExecuteThread 2
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=25 idx=0x58 tid=26836 prio=5 alive, blocked, native_blocked, daemon
    -- Blocked trying to get lock: java/lang/String@0xe82d6ec0[thin lock]
    at jrockit/vm/Threads.sleep(I)V(Native Method)
    at jrockit/vm/Locks.waitForThinRelease(Locks.java:955)
    at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1083)
    at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1005)
    at jrockit/vm/Locks.monitorEnter(Locks.java:2179)
    at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=26 idx=0x5c tid=26837 prio=5 alive, in native, daemon
    at jrockit/ext/epoll/EPoll.epollWait0(ILjava/nio/ByteBuffer;II)I(Native Method)
    at jrockit/ext/epoll/EPoll.epollWait(EPoll.java:115)
    at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:156)
    ^-- Holding lock: java/lang/String@0xe82d6ec0[thin lock]
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace2nd dump after the server servers a request with ExecuteThread 2 waiting to get the lock from ExecuteThread 1
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=25 idx=0x58 tid=26836 prio=5 alive, in native, daemon
    at jrockit/ext/epoll/EPoll.epollWait0(ILjava/nio/ByteBuffer;II)I(Native Method)
    at jrockit/ext/epoll/EPoll.epollWait(EPoll.java:115)
    at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:156)
    ^-- Holding lock: java/lang/String@0xe82d6ec0[fat lock]
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=26 idx=0x5c tid=26837 prio=5 alive, blocked, native_blocked, daemon
    -- Blocked trying to get lock: java/lang/String@0xe82d6ec0[fat lock]
    at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)
    at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1411)
    at jrockit/vm/Locks.lockFat(Locks.java:1512)
    at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1054)
    at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1005)
    at jrockit/vm/Locks.monitorEnter(Locks.java:2179)
    at weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of traceHere is a blog on this topic: http://jojovedder.blogspot.com/2009/05/weblogic-socket-muxers-are-not-stuck.html

Why iCal cancel of event edits issue is still not fixed after over 2 years?

Why iCal "cancel of event edits" issue is still not fixed after over 2 years?
I have been in the software engineering industry for over 14 years, but I have never seen a large corporation being so slow at addressing major issues like these.
What would it take for Apple to start working on this issue?

Yup. This is fully ridiculous that you can't cancel your updates once you start. I love the tool but this is on pretty significant issue.
Sometimes I accidentally move a mtg or make some edit while viewing and you can't back you!!
If you feel the same way, you should post a note here:
http://www.apple.com/feedback/ical.html
Message was edited by: SteveMc10123

Citrix Netscaler AppXpert with Sharepoint 2010 Page Edit Issue

Posting this as a questions and discussion point.
The issue is in using Citrix Netscaler with AppXpert with SharePoint 2010. I've seen this issue for two customers.
Configurations:
- Citrix Netscaler as the load Balancer
- Netscaler AppXpert for SharePoint deployed on Netscaler (using either AppXpert version 1.1 or 2.0)
- SharePoint 2010 Standard or Enterprise editions
Issue:
A SharePoint user with appropriate rights go to a SharePoint page. They choose Edit page, make changes and want to save changes. At this point all SharePoint ribbon options on the top are greyed out. End result, users are not able to make changes to their
site pages. Issue happens for everyone including Farm Admins.
Cases:
a. The users are able to edit and save SharePoint wiki pages if I point user's PC to the SharePoint web server WFE by changing their local host file.
b. On Citrix Netscaler, if I use the traditional load balancing i.e. without Citrix AppXpert, then the users are able to edit and save the pages. That is an option if the customer is using SharePoint 2010 Standard. That is not an option if a customer is
using InfoPath forms. InfoPath is a feature of SharePoint 2010 Enterprise edition. Citrix AppXpert for SharePoint is needed to make the InfoPath work. Else the users get session errors when they use InfoPath Web forms.
c. The issue happens on almost all combination of OS and browser. XP, vista, Win 7, Win8, Win8.1, IE8, 9, 10, 11 and other browsers like chrome etc as well.
Please share your ideas and suggestions.

Hi Faisal,
As I understand, the issue will be solved when end users directly connect to SharePoint WFE servers. Since the issue is related to third party products, I'd recommend you contact their support engineer for sufficient resource and assistance. For your convenience:
http://discussions.citrix.com/forum/150-support-forums/
Should you need more assistance, let me know. Thanks for the understanding.
Regards,
Rebecca Tu
TechNet Community Support

How Do I Lock Editing?

I was wondering if there was a way I could lock editing in iTunes? It's very easy to accidentally mess up file information. Anyway to fix this?

Just click back to the editor and close the image there. Either use the close button on the right or left of the image window or tab, or press Ctrl+W/Cmd+W.

Lock & Edit button is not visible

Hi All,
Whenever I create a WL 10.3 domain in Windows XP box I am not able to see "Lock & Edit" button and instead of that I see "Activate Changes". Once I click on "Activate Changes" still it doesn't release the configuration so I am unable to make any further change.
Restarted the domain clearing all cache,tmp folder still no luck.
Thanks a lot in advance.
~Pradeep

Hi Pradeep,
Typically, this is solved by going to the "Preferences" link of the admin console and changing the "Automatically Acquire Lock and Activate Changes" Checkbox on the new displayed screen.
However, if this doesn't solve your problem, then I would suggest you to check the forum thread at No Lock & Edit button in WLS 10 Console
Thanks,
Cris

Credits & lock box issues in SAP XI

Hi All,
what is the credits & lock box issues in SAP XI....? can any body explain me in detail and how to solve all these credits and lockbox issues...
Thanks
Sudheer

Sudheer,
I dont think you have any issues with these files. These files are sent to the Bank. Just google for help on these files. If you are expecting in detail explanation then I think you should give us few inputs.
Regards,
---Satish

Weblogic 9.2 disable the 'lock & edit'

I am developing locally and i have to keep clicking, lock & edit, activate changes, etc,....every time i make a change. is there a way i can just disable this feature and perform the actual changes without having to lock & edit them?

Hi,
The *"Lock & Edit"* feature was introduced from WLS9.x onwards...And It was very Time consuming (But Safe)...So based on recommendation of Many Admins...we provided a new feature in WLS10.3 to Enable/Disable this feature from Admin Console....based on our comfort.
But unfortunately there is no way to get rid of it in WLS9.x and WLS10.1.
In WLS10.3 if you want to Enable or Disable it ..then Login to AdminConsole and then search for *"preferences"* Link just beside *"logout"* button at the Center top fo AdminConsole...After clicking on *"Preferences"* link...New Page will open...You will find *"Automatically Acquire Lock and Activate Change"* Check Box.... The Lock&Edit Button will disappear.
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (Once Oracle Always Oracle)

Locking up issue?

On two occasions since upgrading to Lion, my IMac24 has locked up. Although it's a weird locking up issue because I can still move the mouse around, but nothing else actually works. No apps work. CMD+ALT+ESC doesn't work. The only solution is to reboot. Very frustrating.

I had the same thing happening on my new 27" iMac after installing Lion. I narrowed it down to the Flash plugin a few days ago. I found this third party app that disable flash, ClickToFlash.
http://hoyois.github.com/safariextensions/clicktoplugin/
If a web site uses HTML 5 a h.264 video will be used instead of the Flash video. For example YouTube, Facebook and Vimeo… If a webpage uses Flash video only, you can double click to play the Flash video. No locking up for a few days now.
I have also read that if you uncheck 'enable hardware acceleration' in the Flash settings, this should fix the freezing up too. Right click on a Flash video while it is playing…. pick Settings from the menu… uncheck 'enable hardware acceleration'. I also did this and still no freezing up on my iMac!!!
iMac 27", 3.4GHz Quad-Core Intel Core i7, 16GB 1333MHz DDR3, 2TB HD + 256GB SSD, AMD Radeon HD 6970M 2GB GDDR5 • FCS 3 • OS X 10.7 (Lion) • iPad 1&2 • Apple Tv 2

Labview lock-up issue, Dr. Watson Hard Error...?

We sometimes run our software vi a library with Diagrams. Sometimes this library can be as large as 50Meg. Our problem seems to occur when we accumulate files in the library over approx 370 or so. When we run the software, no memory leakage or usage issue seems to be present but the software will stop running and we'll get a Dr. Watsons error and the only way to recover is to turn off the PC and reboot. Is there a limitation to the size off a library with diagrams..? We found that if we remove some of the vi's internal to the library (say we reduce the number of vi's down to 325 or so) the lock-up issue goes away...?

Hello Dave M,
Thank you for contacting National Instruments.
Saving to and reading from large library files is very memory intensive. This is most likely leading to your error.
Please refer to the LabVIEW User Manual (Chapter 7, pp. 12-13) at the following link:
http://www.ni.com/pdf/manuals/320999e.pdf
The following Knowledge Base is also useful:
http://digital.ni.com/public.nsf/websearch/D5662AF762385C1A862566C2007FE40F?OpenDocument
The recommended limit of VIs in a library is 255. This number can vary depending on you memory capacity. It is also recommended that your libraries not exceed 1 MB in size.
To avoid this error, you might want to consider dividing your library into multiple libraries. Put your high-level VIs in one library and
group other VIs by function.
Alternatively, you can save your VIs in a Development Distribution directory by selecting File >> Save with Options... and selecting the Development Distribution option.
Let me know if you need any more help.
Sean C.
Applications Engineer
National Instruments

[SOLVED] KDE Plasma 5 | Lock Screen Issues

Everytime my computer locks - whether it be manually or automaticly, I get this lock menu with 3 options. The first option has my username and my avatar, which prompts me for my password. Everytime I type in the correct password, the screen turns black and then reloads the lock screen. Which makes it impossible for me to log back into my session leaving me unable to leave my computer on ever. I can create a new Session from the same menu but when ever I do create a new Session after being locked out, not a single app will launch. And I know I am putting in the correct password because when I purposly put in an incorrect password; the screen doesn't turn black, it just gives me a diffrent prompt. Another issue I am facing with KDE at the moment is about 80% of the time when I shut down my computer, I get a crash report from most of the applications running, for expamle kwin. I'm only saying this incase it is relevant, it is annoying but at least it doesn't prevent me from getting work done. Also, I used KDE's suggested SDDM for login.
System Specs:
-`
.o+` tsteinholz@Yuri
`ooo/ OS: Arch Linux
`+oooo: Kernel: x86_64 Linux 4.0.4-2-ARCH
`+oooooo: Uptime: 9m
-+oooooo+: Packages: 1299
`/:-:++oooo+: Shell: bash 4.3.39
`/++++/+++++++: Resolution: 1920x1080
`/++++++++++++++: DE: KDE5
`/+++ooooooooooooo/` WM: KWin
./ooosssso++osssssso+` GTK Theme: Raleigh [GTK2], Default [GTK3]
.oossssso-````/ossssss+` Icon Theme: breeze
-osssssso. :ssssssso. Font: Oxygen-Sans Sans-Book
:osssssss/ osssso+++. CPU: Intel Core i7-4770 CPU @ 3.9GHz
/ossssssss/ +ssssooo/- GPU: GeForce GTX 650 Ti
`/ossssso+/:- -:/+osssso+- RAM: 1615MB / 15990MB
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/
Last edited by tsteinholz0 (2015-05-25 17:42:34)

arojas wrote:Latest nvidia driver is known to break KDE screen locker. Either downgrade nvidia or switch to nouveau
https://bugs.kde.org/show_bug.cgi?id=346938
Oh, that really sucks, I like to use Arch for gaming on Linux so i dont think either of those sound preferable, but I think I will just try to downgrade nvidia then. Gnome atcually has worse issues with the latest nvidia drivers which sucks as well. Thank you for finding this.

Lock & Edit Issue

Similar Messages

Maybe you are looking for