Admin console lock&release button monitoring

Hi!
Need some help here.
Is there any way to log or trace when and by which IP lock-button was enabled in adminstration console?
Thanks.

I suppose access.log from .../domain/servers/AdminServer can be helpful for my case. Unfortunately it contains only certain logs:
#Version: 1.0
#Fields: time cs-method cs-uri sc-status c-ip cs-uri-stem cs-uri-query
#Software: WebLogic
#Start-Date: 2013-01-09 11:22:59
12:49:49 GET /bea_wls_deployment_internal/DeploymentService 200 x.x.x.38 /bea_wls_deployment_internal/DeploymentService -
12:55:28 GET / 404 10.7.62.38 / -
13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:19:25 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:21:52 GET /bea_wls_management_internal2/wl_management 200 x.x.x.163 /bea_wls_management_internal2/wl_management -
15:22:00 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:22:03 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:22:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:25:53 GET /favicon.ico 404 x.x.x.38 /favicon.ico -
15:26:03 GET /favicon.ico 404 x.x.x.38 /favicon.ico -
15:56:30 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
15:56:31 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
and no messages about logging in or something like that.
What should I do to see them?

Similar Messages

OAM admin console lock

Dear All,
I forgot Oracle access manager admin user password. How to reset it?
I appreciate your time
Maria

I do not think my Weblogic LDAP is configured properly. Please see result below...
wls:/oas_domain/serverConfig> displayUserIdentityStore('UserIdentityStore1')
Name : UserIdentityStore1, LDAP_URL : ldap://ldap-host:7001, SECURITY_PRINCIPAL : cn=Admin, SECURITY_CREDENTIAL : {AES}E8FC3D36BEAF0A3ADA78458E36102C70, USER_SEARCH_BASE : ou=people,ou=myrealm,dc=base_domain, GROUP_SEARCH_BASE : ou=groups,ou=myrealm,dc=base_domain, USER_NAME_ATTRIBUTE : uid, LDAP_PROVIDER : EMBEDDED_LDAP, UserIdentityProviderType : OracleUserRoleAPI, IsPrimary : false, IsSystem : false, ENABLE_PASSWORD_POLICY : true, Users : weblogic, Role Application Administrator : Operators, Role System Manager : Monitors

While I'm in BC Admin Console, the 'EDIT' button is not working.

Online editing is therefore not possible. How to resolve this?

Take the issue up with whomever replaced the device, whether that is Apple or another company.
There is nothing that we, your fellow users, in these user to user support forums can do for you.

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

Weblogic Admin Console Issue (Move and Copy buttons do not work)

Hi everyone!
We are using Weblogic portal 10.2. While using the administration console, some buttons are not working (exmple: copy and move buttons). When clicked, it gives the following errors:
weblogic.utils.NestedRuntimeException: Cannot parse POST parameters of request: '/PortalEARAdmin/xHttpReq'
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:1816)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:1703)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:1656)
at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:756)
at com.bea.jsptools.util.Utilities.isNewTreeMode(Utilities.java:1490)
Truncated. see log file for complete stacktrace
java.io.UnsupportedEncodingException: Unsupported Encoding UTF-8;charset:UTF-8
at weblogic.servlet.internal.ServletRequestImpl.setCharacterEncoding(ServletRequestImpl.java:384)
at weblogic.servlet.internal.ServletRequestImpl.initReader(ServletRequestImpl.java:1071)
at weblogic.servlet.internal.ServletRequestImpl.access$1100(ServletRequestImpl.java:68)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:1778)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:1703)
Truncated. see log file for complete stacktrace
I hope you could share your thoughts on this.
Thanks and have a nice day! :-)
Warm regards,
Rakie

Are you using FireFox 3 to access the WLP Admin Console? If so, unfortunately, this is sounds like a known issue with FireFox 3. See http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/relnotes/relnotes.html#wp1210315 is the note for the portal admin console. Also, the release note is for WLP 10.3, but it will actually affect other releases as well.
Try another browser, such as FireFox2 or IE6 or 7. If you want, you could initiate a support case, and ask to get a patch for bug 8159454.
Greg

HttpSessionDebug Not Working For Session Monitoring through Admin Console

Hi,
I want to Analyze the HttpSession Payload (Size) in the AdminConsole-->Diagnostics-->Log Files -->EventsDataArchive
I followed the Link http://jayesh-patel.blogspot.com/2008_04_01_archive.html
I am using "MyDiagnosticEar\META-INF\weblogic-diagnostics.xml" as following:
<?xml version="1.0" encoding="UTF-8"?>
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics">
<instrumentation>
<enabled>true</enabled>
<wldf-instrumentation-monitor>
<name>HttpSessionDebug</name>
<enabled>true</enabled>
</wldf-instrumentation-monitor>
</instrumentation>
</wldf-resource>
I am using a Simple JSP page to set Some Attribute inside the newly Created Session
MyDiagnosticEar\SimpleActionWebApp\index.jsp
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ page session="false" %>
<html>
<body>
<%
HttpSession session=request.getSession(true);
out.println("<h4>Session ID: "+session.getId());
session.setAttribute("AAAAAAAAA","BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB");
java.util.Vector v=new java.util.Vector();
v.add(new java.util.Date());
v.add(new java.util.ArrayList());
v.add("AAAAABBCCCC");
session.setAttribute("EEEEEEEEEEEEEE",v);
%>
Data is Set As an Attribute inside the HttpSession:
session.setAttribute("AAAAAAAAA","BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB");
session.setAttribute("EEEEEEEEEEEEEE",v);
<%
System.out.println((String)request.getSession().getAttribute("AAAAAAAAA"));
System.out.println(session.getAttribute("EEEEEEEEEEEEEE"));
%>
</body>
</html>
Please let me know if there is any thing missing.....I have tested it in All WLS9.2, WLS10MP1 and WLS10.3 versions ..But no Success...
I am not able to see anything After hitting the JSP...in AdminConsole-->Diagnostics-->Log Files -->EventsDataArchive
But i can see that the Diagnostic Module has been Picked up successfully...
AdminConsole--->Deployments--->MyDiagnosticEar -->Configuration--->Instrumentation page
Thanks
Jay SenSharma

Hi Raj,
Thanks for looking into this issue.
I tried to Configure DiagnosticModule as well from Admin Console but could not make it work...Can u Please elaborate more on this...It will be really helpful.
Below is the Diagnostic Module...Created using Admin Console....Diagnostics -> Diagnostics Modules.
<?xml version='1.0' encoding='UTF-8'?>
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/weblogic-diagnostics" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-diagnostics http://www.bea.com/ns/weblogic/weblogic-diagnostics/1.1/weblogic-diagnostics.xsd">
<name>Module-0</name>
<instrumentation>
<enabled>true</enabled>
<wldf-instrumentation-monitor>
<name>Connector_Around_Work</name>
<description></description>
</wldf-instrumentation-monitor>
</instrumentation>
<harvester>
<enabled>true</enabled>
<sample-period>3000</sample-period>
<harvested-type>
<name>weblogic.management.runtime.WebAppComponentRuntimeMBean</name>
<harvested-attribute>SessionMonitoringEnabled</harvested-attribute>
<harvested-instance>com.bea:ApplicationRuntime=TestDiagnosticsEAR,Name=AdminServer_/TestDiagnostics,ServerRuntime=AdminServer,Type=WebAppComponentRuntime</harvested-instance>
<namespace>ServerRuntime</namespace>
</harvested-type>
</harvester>
<watch-notification>
<watch>
<name>WatchA</name>
<enabled>true</enabled>
<rule-type>Harvester</rule-type>
<rule-expression>(${ServerRuntime//[weblogic.management.runtime.WebAppComponentRuntimeMBean]com.bea:ApplicationRuntime=TestDiagnosticsEAR,Name=AdminServer_/TestDiagnostics,ServerRuntime=AdminServer,Type=WebAppComponentRuntime//SessionMonitoringEnabled} = '')</rule-expression>
<alarm-type>AutomaticReset</alarm-type>
<alarm-reset-period>60000</alarm-reset-period>
</watch>
</watch-notification>
</wldf-resource>
TestDiagnostics
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 8, 2010 10:38 AM

Sun java system application server 8 custom realm lock the admin console up

Hi:
I implemented a custome realm. After I installed the custom realm to Sun App server 8 PE, I can get into the admin console any more. According to the log, the user is authenticated. However, this user isn't in write group to access the admin console. What would be the user group in a custom realm to access admin console?
In version 7, even you set up custom realm the admin console still not affected by the custom realm. Why is the admin console in version 8 picking up custom realm?
Thanks.

Previous reply was quite misleading - there is no such thing as default admin password for standalone installation of Application Server. Default values only apply to Application Server installation installed through Creator or NetBeans installer.
Otherwise, you have to specify admin user name and password at installation time. Admin username value is defaulted to "admin" so unless you changed it in your installation that should still apply. You had to enter explicit password values.
If you forgot those, you can either uninstall and reinstall or you can take a look at Troubleshooting Guide for instructions on reseting admin authentication:
http://docs.sun.com/source/817-6085/troubleshooting.html#1026910

Monitoring Weblogic Server statistics (Other than admin console)

          Hi,
          I am using WLS 5.1 SP 12 on AIX 5.1. I need to figure out how to provide weblogic
          server statistics dynamically (Such as active servlets, response times, session
          stats etc). I know this information is available on the weblogic admin console.
          But due to the complexity of the situation I would like to provide custom JSP
          pages or servlets wherein I can make some API calls (????) to provide the above
          statistics.
          Any help or ideas would be greatly appreciated.
          Thanks,
          Bala


Hello Nadar,
Tell me how are you starting server in the cluster, through nodemanager or commnadline.
Kuldeep

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

Admin Console browser problem

Hi,
This is a peculiar problem that I am facing. I am working with iPS3.0SP3 on solaris8. My installation went fine. But when I try to access Admin console(thru Netscape 4.7 or 4.75), I have the login screen displayed. But, after I provide User and Password and hit Submit button, the browser window vanishes. This has been happening with SP2 also. And my login to the portal desktop screen is successful. My browser window is available. The problem is only with the Admin Console.
Now when I tried to Login to the same portal server instance's Admin Console thru the local Web Browser on a different machine, its working fine. I mean, the windows doesnt close.
Any guess on what could be the problem.
Thanks & Regards.
shivaram.

Hi there Shivaram,
I have found a similar problem, when using iPS. If you have logged into the portal desktop and then wan't to log into the admin console, the admin console seems to fail when logging in. What I have found, is that after you logout of the desktop, and then go to the console login, it helps to just click the reload button in netscape, while on the admin console login screen. It seems that you need to clear the session cookie first, otherwise admin authentication fails. Alternatively you can start a seperate instance of Netscape from the command line, which then forces Netscape to create an alternative temporary store, and lock files. I'm not sure wheteher this will help, but this is what I have seend before.... comments welcome..

Weblogic 9.x admin console slowest and worst application ever

Does anyone else think the Weblogic 9.x admin console really sucks? Is there any place I can make improvement requests?
Things in Weblogic 8.x that took just a couple of minutes to accomplish routinely take a half-hour or more in the Weblogic 9.x console. I have recently discovered WLST and I have created a couple of scripts to script things I do quite often but quite honestly I don't have time to script everything I need to do in the console, especially since BEA should provide a usable admin console IMHO.
My specific complaints (not all inclusive as there is no way I could think of every annoyance I run into on a day to day basis):
1) It is crazy slow. We use the ssh node manager so every time it loads a page I guess it polls every managed instance via ssh and page loads take a couple of minutes. For example, getting the next page of Deployments takes around 3 minutes.
2) The deployment pagination is very annoying. Why is this limited to 10 deployments per page? This should just show me a list of all my deployments in alphabetical order. The pagination offers nothing. At the very least pagination length should be configurable. The pagination combined with problem 1 takes me many minutes to get to the app I need to do something with.
3) If BEA insists on pagination on the deployments list at least give me a link so I can immediately jump to a specific page! The link should have the letter range of the deployments on that page (like A-C, D-V, W-Z, or something like that).
4) After I stop an app it jumps back to page 1 instead of showing the page of deployments containing the app I just stopped. OMG!!! GRRR! Now I have to hit Next several times to get back to my app with 3 minutes between each page load. YOU HAVE GOT TO BE KIDDING ME!!!!
5) Why is there not a Redeploy button like there was in Weblogic 8.x? If I need to restart an application I have to go through the update procedure and not upload a new version. This is annoying, just give me a damn redeploy button.
6) After clicking the Lock button I have to wait 2-3 minutes for it to give me the Lock. Why does it take this long?
7) The whole locking mechanism is stupid. Why do I have to obtain a lock to make any changes? I never had a problem in Weblogic 8.x with walking on someone else. I can see how this could possibly be beneficial to some organizations (I suppose) so at the very least make obtaining the lock optional via configuration.
I am sure there are many more but I can't think of all of them now. I will start writing it down every time the console annoys the hell out of me. IMHO the Weblogic 9.x console broke the perfectly good Weblogic 8.x console.
It wouldn't be so annoying if it wasn't so MADDENINGLY SLOW.

We have upgraded our WebLogic from 8.1 to 9.2 along with our PeopleSoft 9.0 upgrade and boy-oh-boy, has the WebLogicAdmin console slowed down.
It used to open in about 10 seconds.
Now it opens in roughly 1 minute and 30 seconds.
The heap size settings are the same as they were in the WebLogic 8.1
Even restarting the WebLogicAdmin and associated PeopleSoft PIA's is the worst I have ever seen.
Windows 2003 SP3
Here's the startup command line;
-Xms256m -Xmx256m -XX:MaxPermSize=128m -classpath ";D:/psft/hr849\webserv\hdev\lib\ps_patch.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PSIGW\WEB-INF\lib\mail.jar;D:/psft/hr849\webserv\hdev\lib\portlet-api-1.0.jar;D:/psft/hr849\webserv\hdev\lib\pluto-1.0.1.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\saaj.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\xml-apis.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\xercesImpl.jar;;d:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\bea\jdk150_12\lib\tools.jar;d:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\bea\WEBLOG~1\server\lib\weblogic.jar" -Djava.util.logging.config.file=D:\psft\hr849\webserv\hdev\applications\peoplesoft\logging.properties -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Dweblogic.Name=WebLogicAdmin -Dweblogic.management.username=operator -Dweblogic.ProductionModeEnabled=true -Dps_vault=D:\psft\hr849\webserv\hdev\psvault -Djava.security.policy="d:\bea\WEBLOG~1\server\lib\weblogic.policy" -Dssl.debug=false -Dps_home=D:/psft/hr849 weblogic.Server
Regards,
Tom

WLS 10.0 cannot get Admin Console to start

Hi,
We have WLS 10.0 with Jrocket on a Windows Server.
We have two domains and they have been working fine for well over a year until this morning. I cannot bring up the Admin Console for the 2 domains. The domains are setup to start up automatically and they get stopped and started every Saturday. This week the restart seems to have failed, The services were showing as started but we could not login into the WLS Admin Console or the web applications that the domains host.
As far as i know nothing should have changed with the server.
Event viewer is not showing any issues.
I tried to start the WLS for the 'da' domain from the cmd line and am now seeing the following in the AdminServer.log (FYI, the domain log is not being created). I have had to remove some lines to make the post :
========================================================================
####<Feb 14, 2010 2:20:15 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <> <Main Thread> <> <> <> <1266142815354> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
D:\bea10\wlserver_10.0\platform\lib\p13n\p13n-schemas.jar;D:\bea10\wlserver_10.0\platform\lib\p13n\p13n_common.jar;D:\bea10\wlserver_10.0\platform\lib\p13n\p13n_system.jar;D:\bea10\wlserver_10.0\platform\lib\wlp\netuix_common.jar;D:\bea10\wlserver_10.0\platform\lib\wlp\netuix_schemas.jar;D:\bea10\wlserver_10.0\platform\lib\wlp\netuix_system.jar;D:\bea10\wlserver_10.0\platform\lib\wlp\wsrp-client.jar;D:\bea10\wlserver_10.0\platform\lib\wlp\wsrp-common.jar>
####<Feb 14, 2010 2:20:15 PM GST> <Info> <WebLogicServer> <ePIMSEDMS2> <> <Main Thread> <> <> <> <1266142815870> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R26.4.0-63_CR302700-72606-1.5.0_06-20061127-1108-win-ia32 from BEA Systems, Inc.>
####<Feb 14, 2010 2:20:16 PM GST> <Info> <Management> <ePIMSEDMS2> <> <Main Thread> <> <> <> <1266142816183> <BEA-141107> <Version: WebLogic Server 10.0 Wed May 9 18:10:27 EDT 2007 933139 >
####<Feb 14, 2010 2:20:17 PM GST> <Info> <WebLogicServer> <ePIMSEDMS2> <> <Main Thread> <> <> <> <1266142817511> <BEA-000215> <Loaded License : D:\bea10\license.bea>
####<Feb 14, 2010 2:20:17 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <> <Main Thread> <> <> <> <1266142817526> <BEA-000365> <Server state changed to STARTING>
####<Feb 14, 2010 2:20:23 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1266142823995> <BEA-000365> <Server state changed to STANDBY>
####<Feb 14, 2010 2:20:24 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1266142824011> <BEA-000365> <Server state changed to STARTING>
####<Feb 14, 2010 2:20:24 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142824026> <BEA-149209> <Resuming.>
####<Feb 14, 2010 2:20:24 PM GST> <Info> <WorkManager> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142824183> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<Feb 14, 2010 2:20:24 PM GST> <Info> <J2EE> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142824292> <BEA-160192> <While upgrading weblogic.xml, encountered "debug" param "jsp-param". This param is unknown and will be removed>
####<Feb 14, 2010 2:20:24 PM GST> <Info> <J2EE> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142824698> <BEA-160192> <While upgrading weblogic.xml, encountered "debug" param "jsp-param". This param is unknown and will be removed>
####<Feb 14, 2010 2:20:25 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142825011> <BEA-149059> <Module da.war of application da is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
####<Feb 14, 2010 2:20:25 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142825354> <BEA-149060> <Module da.war of application da successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
####<Feb 14, 2010 2:20:25 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142825370> <BEA-149059> <Module da.war of application da is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<Feb 14, 2010 2:20:25 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142825370> <BEA-149060> <Module da.war of application da successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<Feb 14, 2010 2:20:37 PM GST> <Info> <netuix> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142837729> <BEA-423101> <[console] Initializing the NetUIx container>
####<Feb 14, 2010 2:20:39 PM GST> <Info> <netuix> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266142839433> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [webapp]. Classifications functionality not enabled.>
####<Feb 14, 2010 2:36:43 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803604> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Feb 14, 2010 2:36:43 PM GST> <Alert> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803620> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Feb 14, 2010 2:36:43 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803620> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <JMX> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803683> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://10.113.202.96:8101/jndi/weblogic.management.mbeanservers.edit .>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <JMX> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803683> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://10.113.202.96:8101/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <WebService> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803683> <BEA-220028> <Web Service reliable agents are suspended.>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <WebService> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803683> <BEA-220029> <Web Service reliable agents are shut down.>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <SAFService> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803698> <BEA-281004> <SAF Service has been suspended.>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <SAFService> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803698> <BEA-281005> <SAF Service has been shut down.>
####<Feb 14, 2010 2:36:43 PM GST> <Info> <Deployer> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <> <> <1266143803714> <BEA-149059> <Module da.war of application da is transitioning from STATE_ADMIN to STATE_NEW on server AdminServer.>
####<Feb 14, 2010 2:36:49 PM GST> <Info> <Management> <ePIMSEDMS2> <AdminServer> <ApplicationFilePoller-consoleapp> <<anonymous>> <> <> <1266143809277> <BEA-400411> <ApplicationFilePoller exiting. Further application file updates will not be seen.>
####<Feb 14, 2010 2:37:13 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Thread-19> <<WLS Kernel>> <> <> <1266143833624> <BEA-000378> <Server failed to shutdown within the configured timeout of 30 seconds. The server process will exit now.>
####<Feb 14, 2010 2:37:13 PM GST> <Error> <> <ePIMSEDMS2> <AdminServer> <Thread-19> <<WLS Kernel>> <> <> <1266143833640> <BEA-000000> <
===== FULL THREAD DUMP ===============
Sun Feb 14 14:37:13 2010
BEA JRockit(R) R26.4.0-63_CR302700-72606-1.5.0_06-20061127-1108-win-ia32
"Main Thread" id=1 idx=0x2 tid=8140 prio=5 alive, in native, blocked
-- Blocked trying to get lock: java/lang/Class@0x00DB5430[thin lock]
at jrockit/vm/Threads.sleep(I)V(Native Method)
at jrockit/vm/Locks.waitForThinRelease(Ljava/lang/Object;I)I(Unknown Source)
at jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown Source)
at jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at java/lang/Shutdown.exit(I)V(Unknown Source)
at java/lang/Runtime.exit(I)V(Runtime.java:90)
at java/lang/System.exit(I)V(Unknown Source)
at weblogic/Server.main([Ljava/lang/String;)V(Server.java:87)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x4 tid=1196 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/t3/srvr/T3Srvr$2@0x00DEDF70[fat lock]
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Thread.join(J)V(Unknown Source)
^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr$2@0x00DEDF70[fat lock]
at java/lang/Thread.join()V(Unknown Source)
at java/lang/Shutdown.runHooks()V(Unknown Source)
at java/lang/Shutdown.sequence()V(Unknown Source)
at java/lang/Shutdown.exit(I)V(Unknown Source)
^-- Holding lock: java/lang/Class@0x00DB5430[thin lock]
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"(Code Generation Thread 1)" id=3 idx=0x6 tid=1736 prio=5 alive, in native, native_waiting, daemon
"(Code Optimization Thread 1)" id=4 idx=0x8 tid=436 prio=5 alive, in native, native_waiting, daemon
"(GC Main Thread)" id=5 idx=0xa tid=3404 prio=5 alive, in native, daemon
"(GC Worker Thread 1)" id=? idx=0xc tid=7548 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 2)" id=? idx=0xe tid=8164 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 3)" id=? idx=0x10 tid=6716 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 4)" id=? idx=0x12 tid=5452 prio=5 alive, native_waiting, daemon
"(VM Periodic Task)" id=6 idx=0x14 tid=4496 prio=10 alive, in native, daemon
"Timer-0" id=11 idx=0x1a tid=7536 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: java/util/TaskQueue@0x00CB5758[fat lock]
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at jrockit/vm/Locks.wait(Ljava/lang/Object;J)V(Unknown Source)
at java/lang/Object.wait()V(Native Method)
at java/util/TimerThread.mainLoop()V(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x00CB5758[fat lock]
at java/util/TimerThread.run()V(Timer.java:462)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"Timer-1" id=12 idx=0x1c tid=5060 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: java/util/TaskQueue@0x04F27760[fat lock]
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop()V(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0x04F27760[fat lock]
at java/util/TimerThread.run()V(Timer.java:462)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=13 idx=0x1e tid=732 prio=5 alive, in native, daemon
at sun/nio/ch/SocketDispatcher.read0(Ljava/io/FileDescriptor;JI)I(Native Method)
at sun/nio/ch/SocketDispatcher.read(Ljava/io/FileDescriptor;JI)I(SocketDispatcher.java:25)
at sun/nio/ch/IOUtil.readIntoNativeBuffer(Ljava/io/FileDescriptor;Ljava/nio/ByteBuffer;JLsun/nio/ch/NativeDispatcher;Ljava/lang/Object;)I(IOUtil.java:233)
at sun/nio/ch/IOUtil.read0(Ljava/io/FileDescriptor;Ljava/nio/ByteBuffer;JLsun/nio/ch/NativeDispatcher;Ljava/lang/Object;)I(IOUtil.java:200)
at sun/nio/ch/IOUtil.read(Ljava/io/FileDescriptor;Ljava/nio/ByteBuffer;JLsun/nio/ch/NativeDispatcher;Ljava/lang/Object;)I(Unknown Source)
at sun/nio/ch/SocketChannelImpl.read(Ljava/nio/ByteBuffer;)I(SocketChannelImpl.java:207)
^-- Holding lock: java/lang/Object@0x0707C800[thin lock]
at com/documentum/fc/impl/util/io/MessageChannel.readSocket(Ljava/nio/ByteBuffer;I)V(MessageChannel.java:123)
at com/documentum/fc/impl/util/io/MessageChannel.readLength()I(MessageChannel.java:100)
at com/documentum/fc/impl/util/io/MessageChannel.getIncomingMessageLength()I(MessageChannel.java:92)
at com/documentum/fc/impl/util/io/MessageChannel.read(Ljava/nio/ByteBuffer;)I(MessageChannel.java:77)
^-- Holding lock: com/documentum/fc/impl/util/io/MessageChannel@0x07088B80[thin lock]
at com/documentum/fc/client/impl/connection/netwise/AbstractNetwiseRpcClient.receiveMessage(Ljava/nio/ByteBuffer;)V(AbstractNetwiseRpcClient.java:167)
at com/documentum/fc/client/impl/connection/docbase/netwise/NetwiseDocbaseRpcClient.applyForStringInternal(Ljava/lang/String;Lcom/documentum/fc/common/IDfId;Lcom/documentum/fc/client/impl/typeddata/ITypedData;ZZ)Ljava/lang/String;(NetwiseDocbaseRpcClient.java:746)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/netwise/NetwiseDocbaseRpcClient@0x07088C18[recursive]
at com/documentum/fc/client/impl/connection/docbase/netwise/NetwiseDocbaseRpcClient.fetchTypeViaApply(Ljava/lang/String;I)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(NetwiseDocbaseRpcClient.java:894)
at com/documentum/fc/client/impl/connection/docbase/netwise/NetwiseDocbaseRpcClient.fetchType(Ljava/lang/String;I)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(NetwiseDocbaseRpcClient.java:821)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/netwise/NetwiseDocbaseRpcClient@0x07088C18[thin lock]
at com/documentum/fc/client/impl/connection/docbase/DocbaseConnection$11.evaluate()Ljava/lang/Object;(DocbaseConnection.java:1309)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/DocbaseConnection@0x06E11D48[recursive]
at com/documentum/fc/client/impl/connection/docbase/DocbaseConnection.evaluateRpc(Lcom/documentum/fc/impl/util/Functor;Z)Ljava/lang/Object;(DocbaseConnection.java:1014)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/DocbaseConnection@0x06E11D48[recursive]
at com/documentum/fc/client/impl/connection/docbase/DocbaseConnection.fetchType(Ljava/lang/String;Z)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(DocbaseConnection.java:1302)
at com/documentum/fc/client/impl/connection/LiteTypeManager.getRawType(Ljava/lang/String;Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(LiteTypeManager.java:104)
at com/documentum/fc/client/impl/connection/LiteTypeManager.getType(Ljava/lang/String;Ljava/util/List;Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(LiteTypeManager.java:78)
at com/documentum/fc/client/impl/connection/LiteTypeManager.getType(Ljava/lang/String;Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(LiteTypeManager.java:61)
at com/documentum/fc/client/impl/connection/docbase/DocbaseConnection.getLiteType(Ljava/lang/String;)Lcom/documentum/fc/client/impl/typeddata/ILiteType;(DocbaseConnection.java:1421)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/DocbaseConnection@0x06E11D48[recursive]
at com/documentum/fc/client/impl/Docbase.typeExists(Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;Ljava/lang/String;)Z(Docbase.java:143)
at com/documentum/fc/client/impl/Docbase.determineBof2Support(Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;)V(Docbase.java:133)
at com/documentum/fc/client/impl/Docbase.<init>(Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;Lcom/documentum/fc/client/impl/Server;)V(Docbase.java:90)
at com/documentum/fc/client/impl/Docbase.getInstance(Lcom/documentum/fc/client/impl/connection/docbase/IDocbaseConnection;Lcom/documentum/fc/client/impl/Server;)Lcom/documentum/fc/client/impl/Docbase;(Docbase.java:58)
^-- Holding lock: java/util/HashMap@0x091A3598[thin lock]
at com/documentum/fc/client/impl/connection/docbase/DocbaseConnection.getDocbase()Lcom/documentum/fc/client/impl/Docbase;(DocbaseConnection.java:1553)
^-- Holding lock: com/documentum/fc/client/impl/connection/docbase/DocbaseConnection@0x06E11D48[thin lock]
at com/documentum/fc/client/impl/session/Session.getDocbase()Lcom/documentum/fc/client/impl/Docbase;(Session.java:3113)
at com/documentum/fc/client/impl/session/Session.getObjectManager(Lcom/documentum/fc/common/IDfId;)Lcom/documentum/fc/client/impl/objectmanager/PersistentObjectManager;(Session.java:775)
at com/documentum/fc/client/impl/session/Session.getObject(Lcom/documentum/fc/common/IDfId;)Lcom/documentum/fc/client/IDfPersistentObject;(Session.java:834)
at com/documentum/fc/client/impl/session/SessionHandle.getObject(Lcom/documentum/fc/common/IDfId;)Lcom/documentum/fc/client/IDfPersistentObject;(SessionHandle.java:580)
at com/documentum/fc/client/security/impl/IpAndRcHelper.getRegistration(Lcom/documentum/fc/client/security/internal/IPublicIdentity;Lcom/documentum/fc/client/IDfSession;)Lcom/documentum/fc/client/privilege/internal/IClientRegistration;(IpAndRcHelper.java:472)
at com/documentum/fc/client/security/impl/DfcIdentityPublisher.getRegistration(Lcom/documentum/fc/client/security/internal/IPublicIdentity;Lcom/documentum/fc/client/IDfSession;)Lcom/documentum/fc/client/privilege/internal/IClientRegistration;(DfcIdentityPublisher.java:469)
at com/documentum/fc/client/security/impl/DfcIdentityPublisher.isRegistration(Lcom/documentum/fc/client/security/internal/IPublicIdentity;Lcom/documentum/fc/client/IDfSession;)Z(DfcIdentityPublisher.java:446)
at com/documentum/fc/client/security/impl/DfcIdentityPublisher.publish(Z)V(DfcIdentityPublisher.java:134)
^-- Holding lock: java/lang/Object@0x03E097F0[thin lock]
at com/documentum/fc/client/security/impl/DfcIdentityPublisher.publish()V(DfcIdentityPublisher.java:102)
at com/documentum/fc/client/security/internal/RegistrationMgr.register()Z(RegistrationMgr.java:34)
at com/documentum/fc/impl/RuntimeContext.<clinit>()V(RuntimeContext.java:191)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
at jrockit/vm/RNI.generateFixedCode(I)I(Native Method)
at com/documentum/fc/impl/RuntimeContext.getInstance()Lcom/documentum/fc/impl/RuntimeContext;(RuntimeContext.java:0)
at com/documentum/fc/client/DfClient.<clinit>()V(DfClient.java:700)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
at jrockit/vm/RNI.generateFixedCode(I)I(Native Method)
at com/documentum/fc/client/DfClient.getLocalClient()Lcom/documentum/fc/client/IDfClient;(DfClient.java:0)
at com/documentum/com/DfClientX.getLocalClient()Lcom/documentum/fc/client/IDfClient;(DfClientX.java:43)
at com/documentum/web/env/NotificationManager.contextInitialized(Ljavax/servlet/ServletContextEvent;)V(NotificationManager.java:101)
at weblogic/servlet/internal/EventsManager$FireContextListenerAction.run()Ljava/lang/Object;(EventsManager.java:458)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(AuthenticatedSubject.java:321)
at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Unknown Source)
at weblogic/servlet/internal/EventsManager.notifyContextCreatedEvent()V(EventsManager.java:168)
at weblogic/servlet/internal/WebAppServletContext.preloadResources()V(WebAppServletContext.java:1721)
^-- Holding lock: weblogic/servlet/internal/WebAppServletContext@0x0E953B38[thin lock]
at weblogic/servlet/internal/WebAppServletContext.start()V(WebAppServletContext.java:2890)
at weblogic/servlet/internal/WebAppModule.startContexts()V(WebAppModule.java:948)
at weblogic/servlet/internal/WebAppModule.start()V(WebAppModule.java:353)
at weblogic/application/internal/flow/ModuleStateDriver$3.next(Ljava/lang/Object;)V(ModuleStateDriver.java:204)
at weblogic/application/utils/StateMachineDriver.nextState(Lweblogic/application/utils/StateChange;[Ljava/lang/Object;)V(StateMachineDriver.java:26)
at weblogic/application/internal/flow/ModuleStateDriver.start([Lweblogic/application/Module;)V(ModuleStateDriver.java:60)
at weblogic/application/internal/flow/ScopedModuleDriver.start()V(ScopedModuleDriver.java:200)
at weblogic/application/internal/flow/ModuleListenerInvoker.start()V(ModuleListenerInvoker.java:117)
at weblogic/application/internal/flow/ModuleStateDriver$3.next(Ljava/lang/Object;)V(ModuleStateDriver.java:204)
at weblogic/application/utils/StateMachineDriver.nextState(Lweblogic/application/utils/StateChange;[Ljava/lang/Object;)V(StateMachineDriver.java:26)
at weblogic/application/internal/flow/ModuleStateDriver.start([Lweblogic/application/Module;)V(ModuleStateDriver.java:60)
at weblogic/application/internal/flow/StartModulesFlow.activate()V(StartModulesFlow.java:26)
at weblogic/application/internal/BaseDeployment$2.next(Ljava/lang/Object;)V(BaseDeployment.java:635)
at weblogic/application/utils/StateMachineDriver.nextState(Lweblogic/application/utils/StateChange;[Ljava/lang/Object;)V(StateMachineDriver.java:26)
at weblogic/application/internal/BaseDeployment.activate(Lweblogic/deploy/container/DeploymentContext;)V(BaseDeployment.java:212)
at weblogic/application/internal/DeploymentStateChecker.activate(Lweblogic/deploy/container/DeploymentContext;)V(DeploymentStateChecker.java:154)
at weblogic/deploy/internal/targetserver/AppContainerInvoker.activate(Lweblogic/deploy/container/DeploymentContext;)V(AppContainerInvoker.java:80)
at weblogic/deploy/internal/targetserver/BasicDeployment.activate(Lweblogic/deploy/container/DeploymentContext;)V(BasicDeployment.java:182)
at weblogic/deploy/internal/targetserver/BasicDeployment.activateFromServerLifecycle()V(BasicDeployment.java:359)
at weblogic/management/deploy/internal/DeploymentAdapter$1.doActivate(Ljava/lang/Object;)V(DeploymentAdapter.java:51)
at weblogic/management/deploy/internal/DeploymentAdapter.activate(Ljava/lang/Object;)V(DeploymentAdapter.java:196)
at weblogic/management/deploy/internal/AppTransition$2.transitionApp(Lweblogic/management/deploy/internal/DeploymentAdapter;Ljava/lang/Object;)V(AppTransition.java:30)
at weblogic/management/deploy/internal/ConfiguredDeployments.transitionApps(Lweblogic/management/deploy/internal/AppTransition;)V(ConfiguredDeployments.java:233)
at weblogic/management/deploy/internal/ConfiguredDeployments.activate()V(ConfiguredDeployments.java:169)
at weblogic/management/deploy/internal/ConfiguredDeployments.deploy()V(ConfiguredDeployments.java:123)
at weblogic/management/deploy/internal/DeploymentServerService.resume()V(DeploymentServerService.java:173)
at weblogic/management/deploy/internal/DeploymentServerService.start()V(DeploymentServerService.java:89)
at weblogic/t3/srvr/SubsystemRequest.run()V(SubsystemRequest.java:64)
at weblogic/work/ExecuteThread.execute(Ljava/lang/Runnable;)V(ExecuteThread.java:200)
at weblogic/work/ExecuteThread.run()V(ExecuteThread.java:172)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
Open lock chains
================
Chain 1:
"Main Thread" id=1 idx=0x2 tid=8140 waiting for java/lang/Class@0x00DB5430 held by:
"(Signal Handler)" id=2 idx=0x4 tid=1196 (waiting on notification)
Chain 2:
"Thread-1" id=10 idx=0x54 tid=1624 waiting for weblogic/servlet/internal/WebAppServletContext@0x0E953B38 held by:
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=13 idx=0x1e tid=732 (active)
===== END OF THREAD DUMP ===============
>
There is enough memory, and the CPU usaage does not get too high.
I have searched the forums and cant find what could be causing the blocking.
The startup hangs at the following line :
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
doing a Ctrl-C to stop the startup then produces the dump entries in the adminserver.log file :
There is no error or warning in the adminserver.log file.
What should I be checking to find out what is going on ? is this a known issue ?
Thanks.

Hi
1. Looking carefully at the following 3 lines in server statup logs, after 2:20:39 PM GST, server waited like for 16 mts like 2:36:43 and invoked the Force Shutdown. Possible reasons I gave below.
####<Feb 14, 2010 2:20:37 PM GST> <Info> <netuix> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1266142837729> <BEA-423101> <[console] Initializing the NetUIx container>
####<Feb 14, 2010 2:20:39 PM GST> <Info> <netuix> <ePIMSEDMS2> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1266142839433> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [webapp]. Classifications functionality not enabled.>
####<Feb 14, 2010 2:36:43 PM GST> <Notice> <WebLogicServer> <ePIMSEDMS2> <AdminServer> <Thread-1> <<WLS Kernel>> <1266143803604> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
2. Since you mentioned this worked fine and nothing else is changed over a year, the possible cause may be like this. Looks like you have some Documentum stuff (or webapp or modules) loaded on this server. I am not much familiar with EMC Documentum stuff, except that we use that as external Content Management repository for Portal Applications. Looking at the full thread dump for thread 0, looks like documentum code is trying to publish something or interact with its documentum server and may be it is not getting the response back. So make sure if any external systems that this WLS interacts are all up and running.
HTH
Ravi Jegga

Weblogic 10, WLST and Admin Console Classpath Exceptions

I've been deploying an application to Weblogic 10 (not 10.3 from Oracle, the last version under the BEA logo) for a few weeks now without a problem. We're going to upgrade to 10.3 from Oracle in our development environment and play around with that hopefully today but I can't imagine a dot-version being much different so I figured I'd post the issue anyway.
Recently, we've been having some issues with the WLST script we use to deploy/redeploy the application. It seems to have just started happening randomly which is odd because the script has not been modified since the get-go. What's happening is the application is compiled, staged and then the WLST script kicks off, log into the application server, looks to see if the app is already deployed, if it is, it redploys it with the latest code and then starts it up and then exits. Every now and again, the next time we go to deploy the application, the WLST fails saying that someone currently has a lock on the admin console. When we log in to the admin console, we see that the user the WLST script uses to log into the admin console currently has a lock on the console and we have the option to take the lock from this user.
When we click the button to take the lock, we get a HUGE exception in the lefthand panel where the Lock & Edit button typically is that says something along the lines of:
Error opening ...
The source of this error is javax.servlet.ServletException: javax.xml.transform.TransformerFactoryConfigurationError: Provider net.sf.saxon.TransformerFactoryImpl not found at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:324) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551) at ...
If I click on the 'Home' button along the upper righthand corner to go back to the home page of the admin console, the error goes away, the 'Activate Changes' button reappears, and then I click that and the Lock & Edit button reappears, then if I go back to my WLST script and run it, it runs successfully. If I log back into the admin console, everything appears normally. This happens intermittently and I'm not sure why it's happening some times and not others. If my WLST script is incorrect I would assume it would behave this way EVERY time.
I also don't get why the xml transformer factory SOMETIMES throws the exception and sometimes it doesn't. It also happens when I try to click on a JDBC data source. Same exact exception is thrown on the default configuration tab, if I click on any of the other tabs available after clicking on my JDBC data source, those all appear fine, just the initial default Configuration > General tab shows this huge exception. If I stop and restart the application server, these exceptions magically go away...the odd thing is this exception being thrown seems to be referencing libraries made available by my deployed application (the whole net.sf.saxon.TransformerFactoryImpl class is in a library we deploy with our application). These jar files containing these libraries should ONLY be available to the deployed application, I'm not putting these files on the classpath of the application server, so why the application server's admin console have any knowledge of these libraries? Could these be mucking with the overall functionality of the admin server's behavior?
Here is my WLST script I use the deploy the application. If you see something wrong with it, any feedback would be greatly appreciated. Any thoughts on the whole classpath of my application being used by the Weblogic Admin console would be helpful too.
WLST Script:
connect("merlin", "merlin595")
# check to see if the apb data source exists and if so, make sure it's targeting the AdminServer
try:
     # Either deploy or redeploy application
     try:
          print 'Checking for the existence of the APB application.'
          cd('/AppDeployments/apbEar')
          print 'The APB application will be redeployed.'
          progress=redeploy('apbEar')
          print 'Status of redeployment: ' + progress.getState()
     except WLSTException:
          print 'The APB application has not yet been deployed to this server, so application will be deployed for the first time now.'
          progress=deploy(appName='apbEar', path='/opt/weblogic/merlinpb/merlinpbEar/apbEar', targets='AdminServer')
          print 'Status of initial deployment: ' + progress.getState()
     # Start application
     try:
          print 'Starting APB application'
          startApplication(appName='apbEar')
     except WLSTException:
          pass
     disconnect()
     print 'End of script, exiting WLST...'
     exit()
except WLSTException:
     print 'Could not deploy apb. Please log into the admin console and attempt the deployment manually.'
Oh, one final thing I've noticed when I use this script. The last thing the script says WHEN it actually runs successfully is:
<Nov 13, 2008 10:57:13 AM EST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>
Why does it say that? What does that mean? Is my script mot structure correctly above?
Any help is greatly appreciated. Thanks again!
Rob

Hey Mike,
The problem I was experiencing was that we had code that was applying an XSL stylesheet against XML we are getting from the database. In order for this stylesheet to work, we had to set code that does the following:
System.setProperty("javax.xml.transform.TransformerFactory", "net.sf.saxon.TransformerFactoryImpl");
Now the first time this code was called, and someone subsequently went to the Weblogic admin console, the screens would be completely unreachable...we were experiencing loads of compilation errors. So I did some digging and tried various other ways to set the TransformerFactory class that wouldn't affect the system as a whole. I found, by sheer luck, the fact that you can set this parameter in the weblogic-application.xml file located in the META-INF directory of your root EAR folder. The very first element in the XML of my weblogic-application.xml file is now:
<wls:xml>
     <wls:parser-factory>
          <wls:transformer-factory>net.sf.saxon.TransformerFactoryImpl</wls:transformer-factory>
     </wls:parser-factory>
</wls:xml>
I now deploy the application with this and my reports are transformed properly and the admin console and command-line WLST scripts are all working uninterrupted as well without any adverse side-effects. Hope that helps. Just an aside, in preparation for the upgrade to WLS10, I restructured our application to a split development directory structure...this structure in combination with Workshop 10 really has made development and deployment much easier.
Best of luck. Cheers!
Rob

Missing tabs from WebLogic Server Admin console

I am extremely new to WebLogic. It came with a vendor package we bought, and we do not have support. I have been using ASK to search for answers to my questions/problems. It has become obvious that either I don't know what I am doing :-) or that our installation is less robust than other peoples.
On our Weblogic Server Admin console, there is no such thing as a "Change Center". If I go to Services -> JDBC -> Connection Pools, there is no tab for Testing. The only tabs I have are Configuration and Monitoring. Monitoring only has text on it - no button to push. Do I always have to "configure a new JDBC connection pool" in order to somehow find a TEST tab?
Have we done something wrong during installation? Thank you, anyone, for help and advice.
Bonnie

Can you please share the error logs/standard output snippet here. It seems to be an issue with the classpath that the system classloader is reading.
Cheers!!
AJ

BO 5.1.7 admin console hangs

Hi All,
We are running BO 5.1.7. The issue is we have imaged the working environment to a new enviornment, this is on unix environment. Infoview works fine on the old server as well as the new imaged server, but when we launch admin console it just hangs after entering username and password.Restarted all the servers but the issue still persists.
Could anyone of you please suggest your thoughts...
Thanks...

It's been a long time since this version but is your OSAgent running on the new machine on a different port from the old machine? If not, make sure it is. It should be in the range of 1024-65535. You could use osfind to determine if another is listening on the port as well.
Check these as well:
1202038 - How do you have the server Administrator Tool connect to a different cluster manager or change the OSAGENT_PORT and Broadcast Agent's IP address from the client Console and Administrator Tool?
Version   1     Validity: 08/23/2000 - active
Language   English
Edit Show change log Show Internal Memos
Content:    Summary   |   Header Data   |   Product   |   Other Properties
Symptom
You want the Server Administrator Tool to connect to another cluster.
Console and Administrator Tool installed on a client machine: You have these modules installed on a client machine for administration purposes and want to change the OSAGENT_PORT and IP address to monitor and administer another Broadcast Agent Server.
Resolution
****CONFIGURATION*****
Broadcast Agent version 5.1
*********RESOLUTION*****
Here are the steps to follow:
1. Open the "ORBDesktop.ini" file for editing. It is located under the following directory:
Business Objects\Server\System 2.5\Bin
2. Specify the new ORBagentAddr and ORBagentPort parameter values under the [COMMON] section.
Keywords
5244 ,
Header Data
Released on 11/27/2000 20:55:47 by Lineu Reis (I817971)
Release Status Released to Customer
Component BOJ-BIP
Responsible Lineu Reis ( I817971 )
Processor Lineu Reis ( I817971 )
1204280 - How do you check CORBA conflicts with the Osfind tool?
Version   1     Validity: 06/26/2001 - active
Language   English
Edit Show change log Show Internal Memos
Content:    Summary   |   Header Data   |   Product   |   Other Properties
Symptom
On a WebIntelligence server, there are several causes of conflicts with CORBA products including:
- PC Anywhere
- Tivoli server management software
- If you have a Compaq server, the "Surveyor" service may not be disabled
- You do not have a dedicated server
- The Oracle database is not installed on the same server as the WebIntelligence Server
In the cases of "PC Anywhere" and "Tivoli", you must you must disable these products and/or any other third party software that use the CORBA architecture.
You can visit the manufacturer websites to determine if an application uses CORBA.
Resolution
****CONFIGURATION*****
WebIntelligence version 2.x
Windows NT
*********RESOLUTION*****
To use the osfind tool, you must launch a DOS command prompt.
Type the following line at the command prompt to generate a "*.txt" file called "osfind":
"C:\Business Objects\Server\ORB 2.5\Bin osfind > osfind.txt"
The file will contain entries similar to the following lines:
osfind: Found one agent at port 14742
HOST: lab12.uk.businessobjects.com
osfind: Found 1 OADs in your domain
HOST: lab12.uk.businessobjects.com
osfind: Following are the list of Implementations registered with OADs.
HOST: lab12.uk.businessobjects.com...................................................................................................................................................................................
Note: It is important to check this file for the number of ports and the port number(s).
You can also have different OADs in your domain if you have a server manager and a node.
*********MORE**************
See resolution entry # 7559 for more information on testing CORBA conflicts.
Keywords
7558 ,
Header Data
Released on 07/13/2001 14:30:53 by Support SAP (SUPPORT)
Release Status Released to Customer
Component BOJ-ERQ-WBI
Responsible Support SAP ( SUPPORT )
Processor Support SAP ( SUPPORT )
Category How To

Admin console lock&release button monitoring

Similar Messages

Maybe you are looking for