Tracing in weblogic

How can i enable tracing in weblogic 9.2 MP2.
We have JMS(Java Method server) deployed we want to know that its processing the request.

Hi,
You can use the below Mentioned JMX code to Trace the JMS system of your Server...
http://jaysensharma.wordpress.com/jmx_weblogic/
It's a very siimple JMX code which provides all the JMS system related informations in a Tabular format.
Step1). open a Command Window (or Shell prompt)
Step2). Run the "setWLSEnv.sh" or "setWLSEnv.cmd" whcich comes along with WebLogic installation in following Location: C:\bea103\wlserver_10.3\server\bin
Step 2 we need to run Just to Set JAVA_HOME and to Set CLASSPATH....usually "weblogic.jar" is required in the Classpath
Step3). Compile the Program ...and then Run it...by providing your own values in the JAVA Code. Like AdminServer URL, UserName & Passwords...
Thanks
Jay SenSharma

Similar Messages

  • Forms 11.1.1.2.1 troubleshooting with debug or trace

    Can DEBUG be configured for more info:
    If I add &config=debug to the end of the forms URL.. then the formsapp-diagnostic.log basically shows the clients IP, HOSTNAME, and Java Version..
    nothing really usefull.. Is it possible to configure what debug info is written..
    How do I Fix TRACING:
    in weblogic console, forms, user sessions.. if I click on enable trace.. then later disable trace.. then view the trace.. All I get is:
                                            FRM-93240: Multiple Forms applications cannot share an HTTP session.

    First, the FRM-93240 problem is a known issue that has been corrected in an upcoming patch.  For current versions (11.1.1.7 and 11.1.2.1) a tempory patch is available.  Contact Support and refer to Bug 16567961
    The second part of the issue is that adding "DEBUG" to the url will only enable servlet diagnostics.  In most cases, this is of little value unless you are trying to troubleshoot a networking issue or session handling issue, or maybe a performance issue.  The tracing which is found in EM can provide granular diagnostic information about a running form.  This is not the same as servlet debugging.  Refer to the document for details.
    http://docs.oracle.com/cd/E38115_01/doc.111210/e24477/tracing.htm

  • Tracing weblogic EJB routing

    Hi,
    we are using replica-aware clustered EJBs. We are curreclty experimenting with custom load balancing mechanism offered by weblogic via callRouter interface. However we experimenced some kind of wierdnes regarding JNDI tree corruption. We would like to get some visibility (tracability/debug) into weblogic routing/loadbalancing mechanism. I tried DebugRouting from servers/debug - default settings but I didn't see what I would expect. May be I was looking into the wrong location (server logs).
    Does anybody have any idea?
    Thanks

    weblogic-ejb-jar.xml jndi-name (instead of local-jndi-name) is with JDeveloper version 10.1.2 & 10.1.3

  • Error while starting Integrated Weblogic Server - Jdeveloper 11.1.1.4

    I installed Jdevloper 11.1.1.4, and getting the below error while starting Integrated Weblogic Server:
    [Waiting for the domain to finish building...]
    [05:13:34 PM] Creating Integrated Weblogic domain...
    The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
    [05:14:53 PM] Error processing Integrated Weblogic domain:
    I've checked for log files under my "C:\Documents and Settings\pramod.gujjeti\Application Data\JDeveloper\system11.1.1.4.37.59.23" directory but no error/exception is traced.
    Then I tried the below:
    Run from command line:
    F:\Oracle\Middleware\oracle_common\common\bin\wlst.cmd "C:\Documents and Settings\pramod.gujjeti\Application Data\JDeveloper\system11.1.1.4.37.59.23\o.j2ee.adrs\CreateDefaultDomain.py"
    " from DOS prompt I got "Error: ADRS_DOMAIN_PASSWORD environment variable not set."
    After I set ADRS_DOMAIN_PASSWORD environment variable (value is weblogic1) the command line is throwing:
    C:\Documents and Settings\pramod.gujjeti>F:\Oracle\Middleware\oracle_common\common\bin\wlst.cmd "C:\Documents and Settings\pramod.gujjeti\Application Data\JDeveloper\sy
    stem11.1.1.4.37.59.23\o.j2ee.adrs\CreateDefaultDomain.py"
    CLASSPATH=F:\Oracle\Middleware\patch_wls1034\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\Oracle\Middleware\patch_jdev1111\profiles\default\sys_manifes
    t_classpath\weblogic_patch.jar;F:\Oracle\Middleware\jdk160_21\lib\tools.jar;F:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic_sp.jar;F:\Oracle\Middleware\wlserver_
    10.3\server\lib\weblogic.jar;F:\Oracle\Middleware\modules\features\weblogic.server.modules_10.3.4.0.jar;F:\Oracle\Middleware\wlserver_10.3\server\lib\webservices.jar;F:
    \Oracle\Middleware\modules\org.apache.ant_1.7.1/lib/ant-all.jar;F:\Oracle\Middleware\modules\net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar;;F:\Oracle\Middleware\o
    racle_common/modules/oracle.jrf_11.1.1/jrf-wlstman.jar;F:\Oracle\Middleware\oracle_common\common\wlst\lib\adf-share-mbeans-wlst.jar;F:\Oracle\Middleware\oracle_common\c
    ommon\wlst\lib\adfscripting.jar;F:\Oracle\Middleware\oracle_common\common\wlst\lib\mdswlst.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\auditwlst.jar;F:
    \Oracle\Middleware\oracle_common\common\wlst\resources\igfwlsthelp.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\jps-wlst.jar;F:\Oracle\Middleware\oracle
    _common\common\wlst\resources\jrf-wlst.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\oamap_help.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resour
    ces\oamAuthnProvider.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\ossoiap.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\ossoiap_help.jar;
    F:\Oracle\Middleware\oracle_common\common\wlst\resources\ovdwlsthelp.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\sslconfigwlst.jar;F:\Oracle\Middleware
    \oracle_common\common\wlst\resources\wsm-wlst.jar
    PATH=F:\Oracle\Middleware\patch_wls1034\profiles\default\native;F:\Oracle\Middleware\patch_jdev1111\profiles\default\native;F:\Oracle\Middleware\wlserver_10.3\server\na
    tive\win\32;F:\Oracle\Middleware\wlserver_10.3\server\bin;F:\Oracle\Middleware\modules\org.apache.ant_1.7.1\bin;F:\Oracle\Middleware\jdk160_21\jre\bin;F:\Oracle\Middlew
    are\jdk160_21\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\Oracle\Middleware\wlserver_10.3\server\native\win\32\oci920_8
    Your environment has been set.
    CLASSPATH=F:\Oracle\Middleware\patch_wls1034\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\Oracle\Middleware\patch_jdev1111\profiles\default\sys_manifes
    t_classpath\weblogic_patch.jar;F:\Oracle\Middleware\jdk160_21\lib\tools.jar;F:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic_sp.jar;F:\Oracle\Middleware\wlserver_
    10.3\server\lib\weblogic.jar;F:\Oracle\Middleware\modules\features\weblogic.server.modules_10.3.4.0.jar;F:\Oracle\Middleware\wlserver_10.3\server\lib\webservices.jar;F:
    \Oracle\Middleware\modules\org.apache.ant_1.7.1/lib/ant-all.jar;F:\Oracle\Middleware\modules\net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar;;F:\Oracle\Middleware\o
    racle_common/modules/oracle.jrf_11.1.1/jrf-wlstman.jar;F:\Oracle\Middleware\oracle_common\common\wlst\lib\adf-share-mbeans-wlst.jar;F:\Oracle\Middleware\oracle_common\c
    ommon\wlst\lib\adfscripting.jar;F:\Oracle\Middleware\oracle_common\common\wlst\lib\mdswlst.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\auditwlst.jar;F:
    \Oracle\Middleware\oracle_common\common\wlst\resources\igfwlsthelp.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\jps-wlst.jar;F:\Oracle\Middleware\oracle
    _common\common\wlst\resources\jrf-wlst.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\oamap_help.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resour
    ces\oamAuthnProvider.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\ossoiap.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\ossoiap_help.jar;
    F:\Oracle\Middleware\oracle_common\common\wlst\resources\ovdwlsthelp.jar;F:\Oracle\Middleware\oracle_common\common\wlst\resources\sslconfigwlst.jar;F:\Oracle\Middleware
    \oracle_common\common\wlst\resources\wsm-wlst.jar;F:\Oracle\Middleware\utils\config\10.3\config-launch.jar;F:\Oracle\Middleware\wlserver_10.3\common\derby\lib\derbynet.
    jar;F:\Oracle\Middleware\wlserver_10.3\common\derby\lib\derbyclient.jar;F:\Oracle\Middleware\wlserver_10.3\common\derby\lib\derbytools.jar;;
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Creating Default Domain
    Reading template: /F:/Oracle/Middleware/wlserver_10.3/common/templates/domains/wls.jar
    Setting Name to 'DefaultServer'
    Setting ListenAddress to ''
    Setting ListenPort to 7101
    Setting domain administrator to 'weblogic'
    Setting domain password.
    Writing domain: /C:/Documents and Settings/pramod.gujjeti/Application Data/JDeveloper/system11.1.1.4.37.59.23/DefaultDomain/
    Closing template.
    Reading domain: /C:/Documents and Settings/pramod.gujjeti/Application Data/JDeveloper/system11.1.1.4.37.59.23/DefaultDomain/
    Adding domain extension template: /F:/Oracle/Middleware/jdeveloper/common/templates/jdeveloper/adrs_template.jar
    Adding domain extension template: /F:/Oracle/Middleware/jdeveloper/common/templates/domains/jsf_template_1.2.9.0.jar
    Adding domain extension template: /F:/Oracle/Middleware/oracle_common/common/templates/applications/jrf_template_11.1.1.jar
    Error: addTemplate() failed. Do dumpStack() to see details.
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Documents and Settings\pramod.gujjeti\Application Data\JDeveloper\system11.1.1.4.37.59.23\o.j2ee.adrs\CreateDefaultDomain.py", line 100, in ?
    File "C:\Documents and Settings\pramod.gujjeti\Local Settings\Temp\WLSTOfflineIni5328235009276840957.py", line 89, in addTemplate
    at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
    at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)
    at com.oracle.cie.domain.script.jython.WLScriptContext.addTemplate(WLScriptContext.java:420)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: com.oracle.cie.domai
    n.ConfigGroupsException: Multiple definitions of server-group JRF-ADMIN-SVR are not allowed
    C:\Documents and Settings\pramod.gujjeti>
    Appreciate your help in advance!
    Thanks,
    Pramod Gujjeti

    I could see no helpful resolution of the issue in the mentioned thread. Please let me know if I'm missing anything!

  • OIM API portablity issue  with OIM 9.1 / Weblogic 10.3

    Hi , We have a existing piece of code which does some User Mutation through OIM API.
    [I am not well versed with OIM ]
    The code was running fine with Weblogic 8.3 and previous OIM version.
    Here is the piece of code.
    logger.info("Initializing OIM Params from config location:" oimConfigFileUtil.getOIMConfigBase());+*
    +          System.setProperty("XL.HomeDir", oimConfigFileUtil.getOIMConfigBase().getAbsolutePath());+
    +          System.setProperty("java.security.auth.login.config", oimConfigFileUtil.getOIMAuthWLFile().getAbsolutePath());+
    +          ConfigurationClient.ComplexSetting configClient = ConfigurationClient.getComplexSettingByPath("Discovery.CoreServer");+
    +          env = configClient.getAllSettings();+
    *+          try {+*
    +               oimAccessFactory = new tcUtilityFactory(env, oimConfigFileUtil.getUserID(), oimConfigFileUtil.getPassword());+
    I traced all the dependecy's for this piece of code.
    If I run this with Weblogic.jar[8.1] it gives me
    java.io.InvalidClassException: com.thortech.xl.dataaccess.tcDataSet; local class incompatible: stream classdesc serialVersionUID = -5446056666465114187, local class serialVersionUID = -8857647322544023100*
    With the compatablity issue I substituted with weblogic.jar:10.3 , now its giving me all classpath issues.
    Can someone layout the exact jars that are required for this to work?
    Thanks
    Vignesh

    Installl a Design Console. Copy any files that are required. Then take the class paths that are listed in the classpath and basecp files and put those into your application classpath files.
    -Kevin

  • Getting error while hitting weblogic server from EBS client instance

    Hi,
    We are trying to hit weblogic server from EBS client instance.
    Steps Done from our side :-
    1. Created a self signed key store and certificate (.cer file) with server host name and used it for SSL enabling on weblogic server.
    2. Created a self signed key store and certificate (.cer file) with client host name and used it for SSL enabling on oracle EBS client.
    3. Imported client certificate .cer file in Server Side Trust Store.
    4. Used Server keystore for client side verification.
    We are getting these logs from Client Side (Oracle EBS AS) :-
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    javax.net.ssl.SSLKeyException: [Security:090542]Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
    at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
    at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:158)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:363)
    at oracle.apps.nmc.filetransmission.DigitalSigner.sendSignedFileToBank(DigitalSigner.java:532)
    at oracle.apps.nmc.filetransmission.DigitalSigner.signXmlFile(DigitalSigner.java:330)
    at oracle.apps.nmc.filetransmission.DigitalSigner.invokerInit(DigitalSigner.java:437)
    at oracle.apps.nmc.filetransmission.DigitalSigner.runProgram(DigitalSigner.java:390)
    at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
    We are getting these logs from Server Side (Weblogic server) :-
    <Nov 9, 2012 10:34:51 AM AST> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from whjed-apstest3.nmc.com - 192.168.100.246. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Kindly suggest on this.
    Regards
    Deepak Gupta

    Hi;
    Please make a search BEA-090482 Check the peer to determine why it rejected at metalink. There are 8 docs avaliable, please review them
    Regard
    Helios

  • Weblogic halting while starting Admin Server

    I've created a SIP cluster. My understanding is you run startWebLogic.sh to start the admin server. I'm getting the following error (no matter how I create the domain).
    Can anyone help explain what I'm doing wrong?
    Thanks in advance for your help
    Bill Goss
    &lt;Mar 16, 2009 12:59:41 PM MDT&gt; &lt;Info&gt; &lt;Management&gt; &lt;BEA-141107&gt; &lt;Version: WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
    WebLogic SIP Server 3.1 at 668557 built on: 2007/06/30
    WebLogic Diameter 3.1 at 668557 built on 2007/06/30
    WebLogic SCTP 3.1 at 665356 built on 06/04/2007 03:12:47 PDT&gt;
    &lt;Mar 16, 2009 12:59:52 PM MDT&gt; &lt;Critical&gt; &lt;WebLogicServer&gt; &lt;BEA-000362&gt; &lt;Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141266|http://forums.oracle.com/forums/]Parsing Failure in config.xml: WorkManagerMBean 'wlss.transport' refers to a constraint or request class 'wlss.transport.fsrc' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast one server in common.
    at weblogic.management.provider.internal.RuntimeAccessImpl.&lt;init&gt;(RuntimeAccessImpl.java:122)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:67)
    Caused by: java.lang.IllegalArgumentException: WorkManagerMBean 'wlss.transport' refers to a constraint or request class 'wlss.transport.fsrc' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast one server in common.
    at weblogic.management.configuration.WorkManagerLegalHelper.validateTargets(WorkManagerLegalHelper.java:66)
    at weblogic.management.configuration.WorkManagerMBeanImpl.setFairShareRequestClass(WorkManagerMBeanImpl.java:138)
    at weblogic.management.configuration.WorkManagerMBeanImpl$1.resolveReference(WorkManagerMBeanImpl.java:120)
    at weblogic.descriptor.internal.ReferenceManager$UnresolvedReference.resolve(ReferenceManager.java:369)
    at weblogic.descriptor.internal.ReferenceManager.resolveReferences(ReferenceManager.java:271)
    at weblogic.descriptor.internal.DescriptorImpl.validate(DescriptorImpl.java:289)
    at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:289)
    at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:52)
    at weblogic.management.provider.internal.RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:599)
    at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:230)
    at weblogic.management.provider.internal.RuntimeAccessImpl.&lt;init&gt;(RuntimeAccessImpl.java:110)
    ... 7 more
    config.xml:
    &lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain
    [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"&gt;
    &lt;name&gt;sipcluster&lt;/name&gt;
    &lt;domain-version&gt;9.2.1.0&lt;/domain-version&gt;
    &lt;security-configuration xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml"&gt;
    &lt;name&gt;sipcluster&lt;/name&gt;
    &lt;realm&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-authenticatorType"/&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-identity-asserterType"&gt;
    &lt;sec:active-type&gt;AuthenticatedUser&lt;/sec:active-type&gt;
    &lt;/sec:authentication-provider&gt;
    &lt;sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/&gt;
    &lt;sec:authorizer xsi:type="xacml:xacml-authorizerType"/&gt;
    &lt;sec:adjudicator xsi:type="wls:default-adjudicatorType"/&gt;
    &lt;sec:credential-mapper xsi:type="wls:default-credential-mapperType"/&gt;
    &lt;sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/&gt;
    &lt;sec:cert-path-builder&gt;WebLogicCertPathProvider&lt;/sec:cert-path-builder&gt;
    &lt;sec:name&gt;myrealm&lt;/sec:name&gt;
    &lt;/realm&gt;
    &lt;default-realm&gt;myrealm&lt;/default-realm&gt;
    &lt;credential-encrypted&gt;{3DES}tDGHUzjR++h5UL7aQTrTUlWU9GPhPYOBWqkI4rxcfALZLiaI9f2cHBubx1NryS8quhnEs3VFHeHraeOQSdHb5ViTduPNpMYy&lt;/credential-encrypted&gt;
    &lt;node-manager-username&gt;weblogic&lt;/node-manager-username&gt;
    &lt;node-manager-password-encrypted&gt;{3DES}+UMAJUjFbF6d0IAm1HcG3g==&lt;/node-manager-password-encrypted&gt;
    &lt;/security-configuration&gt;
    &lt;server&gt;
    &lt;name&gt;AdminServer&lt;/name&gt;
    &lt;machine&gt;UnixMachine&lt;/machine&gt;
    &lt;listen-address/&gt;
    &lt;network-access-point&gt;
    &lt;name&gt;sip&lt;/name&gt;
    &lt;protocol&gt;sip&lt;/protocol&gt;
    &lt;listen-port&gt;5060&lt;/listen-port&gt;
    &lt;public-port&gt;5060&lt;/public-port&gt;
    &lt;http-enabled-for-this-protocol&gt;false&lt;/http-enabled-for-this-protocol&gt;
    &lt;tunneling-enabled&gt;false&lt;/tunneling-enabled&gt;
    &lt;outbound-enabled&gt;true&lt;/outbound-enabled&gt;
    &lt;enabled&gt;true&lt;/enabled&gt;
    &lt;two-way-ssl-enabled&gt;false&lt;/two-way-ssl-enabled&gt;
    &lt;client-certificate-enforced&gt;false&lt;/client-certificate-enforced&gt;
    &lt;/network-access-point&gt;
    &lt;/server&gt;
    &lt;server&gt;
    &lt;name&gt;ManagedServer&lt;/name&gt;
    &lt;machine&gt;UnixMachine&lt;/machine&gt;
    &lt;cluster&gt;SipCluster&lt;/cluster&gt;
    &lt;listen-address/&gt;
    &lt;/server&gt;
    &lt;cluster&gt;
    &lt;name&gt;SipCluster&lt;/name&gt;
    &lt;multicast-address&gt;239.192.0.0&lt;/multicast-address&gt;
    &lt;multicast-port&gt;17001&lt;/multicast-port&gt;
    &lt;/cluster&gt;
    &lt;embedded-ldap&gt;
    &lt;name&gt;sipcluster&lt;/name&gt;
    &lt;credential-encrypted&gt;{3DES}H0kJUtaBQ6gon62RYVhluFVRx6+AIgqzkQ4qoTEcrp4=&lt;/credential-encrypted&gt;
    &lt;/embedded-ldap&gt;
    &lt;configuration-version&gt;9.2.1.0&lt;/configuration-version&gt;
    &lt;machine xsi:type="unix-machineType"&gt;
    &lt;name&gt;UnixMachine&lt;/name&gt;
    &lt;node-manager&gt;
    &lt;name&gt;UnixMachine&lt;/name&gt;
    &lt;listen-address/&gt;
    &lt;/node-manager&gt;
    &lt;/machine&gt;
    &lt;migratable-target&gt;
    &lt;name&gt;ManagedServer (migratable)&lt;/name&gt;
    &lt;user-preferred-server&gt;ManagedServer&lt;/user-preferred-server&gt;
    &lt;cluster&gt;SipCluster&lt;/cluster&gt;
    &lt;/migratable-target&gt;
    &lt;self-tuning&gt;
    &lt;fair-share-request-class&gt;
    &lt;name&gt;wlss.transport.fsrc&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;fair-share&gt;50&lt;/fair-share&gt;
    &lt;/fair-share-request-class&gt;
    &lt;fair-share-request-class&gt;
    &lt;name&gt;wlss.timer.fsrc&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;fair-share&gt;100&lt;/fair-share&gt;
    &lt;/fair-share-request-class&gt;
    &lt;fair-share-request-class&gt;
    &lt;name&gt;wlss.tracing.fsrc&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;fair-share&gt;50&lt;/fair-share&gt;
    &lt;/fair-share-request-class&gt;
    &lt;min-threads-constraint&gt;
    &lt;name&gt;wlss.tracing.minthreads&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;count&gt;1&lt;/count&gt;
    &lt;/min-threads-constraint&gt;
    &lt;max-threads-constraint&gt;
    &lt;name&gt;wlss.timer.maxthreads&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;count&gt;16&lt;/count&gt;
    &lt;connection-pool-name/&gt;
    &lt;/max-threads-constraint&gt;
    &lt;max-threads-constraint&gt;
    &lt;name&gt;wlss.tracing.maxthreads&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;count&gt;1&lt;/count&gt;
    &lt;connection-pool-name/&gt;
    &lt;/max-threads-constraint&gt;
    &lt;capacity&gt;
    &lt;name&gt;wlss.transport.capacity&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;count&gt;400&lt;/count&gt;
    &lt;/capacity&gt;
    &lt;capacity&gt;
    &lt;name&gt;wlss.timer.capacity&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;count&gt;256&lt;/count&gt;
    &lt;/capacity&gt;
    &lt;work-manager&gt;
    &lt;name&gt;wlss.transport&lt;/name&gt;
    &lt;target&gt;SipCluster&lt;/target&gt;
    &lt;fair-share-request-class&gt;wlss.transport.fsrc&lt;/fair-share-request-class&gt;
    &lt;response-time-request-class xsi:nil="true"/&gt;
    &lt;context-request-class xsi:nil="true"/&gt;
    &lt;capacity&gt;wlss.transport.capacity&lt;/capacity&gt;
    &lt;ignore-stuck-threads&gt;false&lt;/ignore-stuck-threads&gt;
    &lt;/work-manager&gt;
    &lt;work-manager&gt;
    &lt;name&gt;wlss.timer&lt;/name&gt;
    &lt;target&gt;SipCluster&lt;/target&gt;
    &lt;fair-share-request-class&gt;wlss.timer.fsrc&lt;/fair-share-request-class&gt;
    &lt;response-time-request-class xsi:nil="true"/&gt;
    &lt;context-request-class xsi:nil="true"/&gt;
    &lt;max-threads-constraint&gt;wlss.timer.maxthreads&lt;/max-threads-constraint&gt;
    &lt;capacity&gt;wlss.timer.capacity&lt;/capacity&gt;
    &lt;ignore-stuck-threads&gt;false&lt;/ignore-stuck-threads&gt;
    &lt;/work-manager&gt;
    &lt;work-manager&gt;
    &lt;name&gt;wlss.tracing.domain&lt;/name&gt;
    &lt;target&gt;SipCluster&lt;/target&gt;
    &lt;fair-share-request-class&gt;wlss.tracing.fsrc&lt;/fair-share-request-class&gt;
    &lt;min-threads-constraint&gt;wlss.tracing.minthreads&lt;/min-threads-constraint&gt;
    &lt;max-threads-constraint&gt;wlss.tracing.maxthreads&lt;/max-threads-constraint&gt;
    &lt;ignore-stuck-threads&gt;false&lt;/ignore-stuck-threads&gt;
    &lt;/work-manager&gt;
    &lt;work-manager&gt;
    &lt;name&gt;wlss.tracing.local&lt;/name&gt;
    &lt;target&gt;SipCluster&lt;/target&gt;
    &lt;fair-share-request-class&gt;wlss.tracing.fsrc&lt;/fair-share-request-class&gt;
    &lt;response-time-request-class xsi:nil="true"/&gt;
    &lt;context-request-class xsi:nil="true"/&gt;
    &lt;min-threads-constraint&gt;wlss.tracing.minthreads&lt;/min-threads-constraint&gt;
    &lt;max-threads-constraint&gt;wlss.tracing.maxthreads&lt;/max-threads-constraint&gt;
    &lt;ignore-stuck-threads&gt;false&lt;/ignore-stuck-threads&gt;
    &lt;/work-manager&gt;
    &lt;/self-tuning&gt;
    &lt;custom-resource&gt;
    &lt;name&gt;sipserver&lt;/name&gt;
    &lt;target&gt;AdminServer&lt;/target&gt;
    &lt;descriptor-file-name&gt;custom/sipserver.xml&lt;/descriptor-file-name&gt;
    &lt;resource-class&gt;com.bea.wcp.sip.management.descriptor.resource.SipServerResource&lt;/resource-class&gt;
    &lt;descriptor-bean-class&gt;com.bea.wcp.sip.management.descriptor.beans.SipServerBean&lt;/descriptor-bean-class&gt;
    &lt;/custom-resource&gt;
    &lt;admin-server-name&gt;AdminServer&lt;/admin-server-name&gt;
    &lt;/domain&gt;

    There looks to be some problem with the Work Manager, which is causing the server to fail during the startup. Try to disable or delete the Work Manager and restart the server instance.
    - - Tarun

  • Getting error in log after sending https requiest to weblogic server.

    Hi,
    I am using weblogic 10.3 in production have three manage server in a single cluster, all the request at coming to the manage server from RADWARE WST load balancer, previously i am using appxcel device from radware for ssl encryption / decryption, not I remove this appxcel and the https request are directly coming to my weblogic manage server,
    Now following error i am gettion in my log file.
    ####<Apr 28, 2010 10:35:33 AM GMT+05:30> <Debug> <SecuritySSL> <newows> <Owstest> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1272431133354> <BEA-000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
    at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:202)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:100)
    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)
    Any one has the solution of this error, and why this error is coming.
    Edited by: user9286345 on Apr 27, 2010 10:10 PM

    this message i m receiving in server.out file. kindly tell me what is the reason for that??
    <Apr 28, 2010 8:10:37 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 122.163.3.36 - 122.163.3.36. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    Bcast compressor object created
    <Apr 28, 2010 8:10:45 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 122.163.3.36 - 122.163.3.36. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    <Apr 28, 2010 8:10:46 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 122.163.3.36 - 122.163.3.36. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    Bcast compressor object created
    <Apr 28, 2010 8:11:15 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 115.118.217.64 - 115.118.217.64. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    <Apr 28, 2010 8:11:16 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 117.197.52.98 - 117.197.52.98. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    Bcast compressor object created
    <Apr 28, 2010 8:11:22 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 117.197.52.98 - 117.197.52.98. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    <Apr 28, 2010 8:11:23 AM GMT+05:30> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from SYSTEM - 172.17.1.116. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    <Apr 28, 2010 8:11:26 AM GMT+05:30> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from 117.197.52.98 - 117.197.52.98. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>

  • Oracle Portal returns 500 error running under Weblogic 11g server

    I've got Oracle Portal set up under Weblogic 11g.
    SSO running, talking to OID 11g, also running under the same Weblogic 11g server. Tested SSO, it is working well.
    After the install (no errors or issue on install), I go to http://<server>:8090/portal/pls/portal and geta Error 500 - Internal Server Error.
    I traced down the problem to OHS - in ohs1.log:
    [2009-08-04T10:09:15.0512-05:00] [OHS] [ERROR:32] [OHS-9999] [odl_log.c] [host_id: <server>] [host_addr: 127.0.0.1] [tid: 1320139072] [user: oracle] [ecid: 004S594zs25Fw000jzwkno0002740001NK] [rid: 0] [VirtualHost: main] Request Failed for : /portal/pls/portal, Resp Code : [500]
    [2009-08-04T10:09:15.1212-05:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: <server> [host_addr: 127.0.0.1] [tid: 1330628928] [user: oracle] [ecid: 004S5953tHhFw000jzwkno0002740001NL] [rid: 0] [VirtualHost: main] File does not exist: /opt/oracle/Middleware/asinst_2/config/OHS/ohs1/htdocs/favicon.ico
    So the problem is favicon.ico is missing, which I confirmed. Does this mean a bad deployment of an .EAR file? What should I do?

    Yes, it seems you are correct....this is from WLS_PORTAL-diagnostic.log
    Looks like the real problem is ERROR: Failed to load C shared library in RepositoryGateway after calling RepositoryGatewayJNI.load:
    [2009-08-05T08:32:08.333-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBekbL6Fw000jzwkno1AU3uT000001,0] [APP: portal] Portal Servlet Context Listener destroy started
    [2009-08-05T08:34:14.191-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Initializing Portal Servlet Context Listener
    [2009-08-05T08:34:14.534-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Creating Repository Service
    [2009-08-05T08:34:14.540-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryService.constructor(<3 args>), PLSQL_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_plsql.conf[[args: serverInfo=WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 , contextRoot=/portal, logMode=error]]
    [2009-08-05T08:34:14.578-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryServiceConfig, DAD_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_dads.conf, CACHE_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_cache.conf
    [2009-08-05T08:34:14.582-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryServiceConfig, dadRetriever = oracle.webdb.repository.service.DadFileConfigRetriever@26d4835, cacheRetriever = [email protected]7
    [2009-08-05T08:34:14.622-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Calling RepositoryGatewayJNI.load ...
    **ERROR STARTS HERE
    [2009-08-05T08:34:14.637-05:00] [WLS_PORTAL] [ERROR] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] ERROR: Failed to load C shared library in RepositoryGateway!
    [2009-08-05T08:34:14.665-05:00] [WLS_PORTAL] [ERROR] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:
    <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] ERROR: Repository Service creation failed. Please check previous log entries for possible cause.
    [2009-08-05T08:34:14.911-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal.config.modplsql.mbeans.DadManagerMXBeanImpl] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] **** Inside Reloaded, NOW Register mbean = : /pls/portal
    [2009-08-05T08:34:14.915-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal.config.modplsql.mbeans.DadManagerMXBeanImpl] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] **** Inside RegisterBean, global beanName = : oracle.portal.config:subtype=DADs,name=/pls/portal,type=PortalConfig,Application=portal
    [2009-08-05T08:36:16.717-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portlet.server.wsrp.mbean.WSRPTransientConfigMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000IBelXi4Fw000jzwkno1ARF2b0004Zm,1:5002] [APP: wsrp-tools] Found WLS AppDeployment MBean com.bea:Name=portalTools#11.1.1.1.0,Type=AppDeployment

  • Problem in weblogic sip server 3.1 ( Giving ssl exception )

    Hi All ,
    I am facing some issue while trying to run weblogic server it is saying "WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from" , I also tried the options -Dweblogic.security.TrustKeyStore=DemoTrust but nothing is helping , Below are the logs please help.
    wls:/offline> wls:/offline> Launching NodeManager ...
    Properties: {NodeManagerHome=/opt/bea/sipserver311/common/nodemanager,}
    Command: /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/bin/java -classpath /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/rt.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/i18n.jar:/opt/bea/patch_weblogic311/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/lib/tools.jar:/opt/bea/sipserver311/server/lib/weblogic_sp.jar:/opt/bea/sipserver311/server/lib/weblogic.jar:/opt/bea/sipserver311/server/lib/wlss/sipservlet.jar:/opt/bea/sipserver311/server/lib/wlss/wlss.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/profile-service-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-mbeaninfo.jar:/opt/bea/sipserver311/server/lib/wlss/wlss_i18n.jar:/opt/bea/sipserver311/server/lib/wlss/wlssechosvr.jar:/opt/bea/sipserver311/server/lib/wlss/wlssdiameter.jar:/opt/bea/sipserver311/server/lib/wlss/sctp.jar:/opt/bea/sipserver311/server/lib/webservices.jar weblogic.NodeManager
    NMProcess: <Apr 8, 2009 3:19:40 AM> <INFO> <Loading domains file: /opt/bea/sipserver311/common/nodemanager/nodemanager.domains>
    NMProcess: <Apr 8, 2009 3:19:43 AM> <INFO> <Loading identity key store: FileName=/opt/saurabh.jks, Type=jks, PassPhraseUsed=true>
    NMProcess: <Apr 8, 2009 3:19:44 AM> <INFO> <Loaded node manager configuration properties from '/opt/bea/sipserver311/common/nodemanager/nodemanager.properties'>
    NMProcess: <Apr 8, 2009 3:19:46 AM> <INFO> <Secure socket listener started on port 5556, host ari23bems>
    Successfully launched the Node Manager.
    The Node Manager process is running independent of the WLST process.
    Exiting WLST will not stop the Node Manager process. Please refer
    to the Node Manager logs for more information.
    The Node Manager logs will be under /opt/bea/sipserver311/common/nodemanager
    wls:/offline> Connecting to Node Manager ...
    <Apr 8, 2009 3:19:53 AM CDT> <Warning> <Security> <BEA-090542> <Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1379, in nmConnect
    WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client. Use dumpStack() to view the full stacktrace'
    wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM CDT> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Not connected to Node Manager
    wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    NMProcess: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
    NMProcess: at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
    NMProcess: at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    NMProcess: at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    NMProcess: at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    NMProcess: at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
    NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
    NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
    NMProcess: at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
    NMProcess: at java.io.InputStreamReader.read(InputStreamReader.java:167)
    NMProcess: at java.io.BufferedReader.fill(BufferedReader.java:136)
    NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:299)
    NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:362)
    NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    NMProcess: at java.lang.Thread.run(Thread.java:595)
    NMProcess:
    Connecting to t3s://ari23bems:7002 with userid saurabhAdmin ...
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 22, in connect
    WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3s://ari23bems:7002 Use dumpStack() to view the full stacktrace'
    wls:/offline> Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
    wls:/offline> Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
    wls:/offline>
    Exiting WebLogic Scripting Tool.

    Hi All ,
    I am facing some issue while trying to run weblogic server it is saying "WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from" , I also tried the options -Dweblogic.security.TrustKeyStore=DemoTrust but nothing is helping , Below are the logs please help.
    wls:/offline> wls:/offline> Launching NodeManager ...
    Properties: {NodeManagerHome=/opt/bea/sipserver311/common/nodemanager,}
    Command: /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/bin/java -classpath /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/rt.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/i18n.jar:/opt/bea/patch_weblogic311/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/lib/tools.jar:/opt/bea/sipserver311/server/lib/weblogic_sp.jar:/opt/bea/sipserver311/server/lib/weblogic.jar:/opt/bea/sipserver311/server/lib/wlss/sipservlet.jar:/opt/bea/sipserver311/server/lib/wlss/wlss.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/profile-service-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-mbeaninfo.jar:/opt/bea/sipserver311/server/lib/wlss/wlss_i18n.jar:/opt/bea/sipserver311/server/lib/wlss/wlssechosvr.jar:/opt/bea/sipserver311/server/lib/wlss/wlssdiameter.jar:/opt/bea/sipserver311/server/lib/wlss/sctp.jar:/opt/bea/sipserver311/server/lib/webservices.jar weblogic.NodeManager
    NMProcess: <Apr 8, 2009 3:19:40 AM> <INFO> <Loading domains file: /opt/bea/sipserver311/common/nodemanager/nodemanager.domains>
    NMProcess: <Apr 8, 2009 3:19:43 AM> <INFO> <Loading identity key store: FileName=/opt/saurabh.jks, Type=jks, PassPhraseUsed=true>
    NMProcess: <Apr 8, 2009 3:19:44 AM> <INFO> <Loaded node manager configuration properties from '/opt/bea/sipserver311/common/nodemanager/nodemanager.properties'>
    NMProcess: <Apr 8, 2009 3:19:46 AM> <INFO> <Secure socket listener started on port 5556, host ari23bems>
    Successfully launched the Node Manager.
    The Node Manager process is running independent of the WLST process.
    Exiting WLST will not stop the Node Manager process. Please refer
    to the Node Manager logs for more information.
    The Node Manager logs will be under /opt/bea/sipserver311/common/nodemanager
    wls:/offline> Connecting to Node Manager ...
    <Apr 8, 2009 3:19:53 AM CDT> <Warning> <Security> <BEA-090542> <Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1379, in nmConnect
    WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client. Use dumpStack() to view the full stacktrace'
    wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM CDT> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Not connected to Node Manager
    wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    NMProcess: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
    NMProcess: at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
    NMProcess: at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    NMProcess: at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    NMProcess: at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    NMProcess: at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    NMProcess: at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
    NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
    NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
    NMProcess: at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
    NMProcess: at java.io.InputStreamReader.read(InputStreamReader.java:167)
    NMProcess: at java.io.BufferedReader.fill(BufferedReader.java:136)
    NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:299)
    NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:362)
    NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    NMProcess: at java.lang.Thread.run(Thread.java:595)
    NMProcess:
    Connecting to t3s://ari23bems:7002 with userid saurabhAdmin ...
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 22, in connect
    WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3s://ari23bems:7002 Use dumpStack() to view the full stacktrace'
    wls:/offline> Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
    wls:/offline> Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
    wls:/offline>
    Exiting WebLogic Scripting Tool.

  • Weblogic certificate is not being authenticated in Oracle HTTP Server

    I am using Oracle HTTP Server with SSL and mod_proxy set up trying to pass a url through to the weblogic server. I start with my OHS url in the browser and the proxy is switches to the url to weblogic but I get the following error on the OHS side:
    [2011-12-22T18:40:09.4683-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-2077] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] nzos proxy handshake error, nzos_Handshake returned 29024(server social.us.oracle.com:443, client 10.139.164.191)
    [2011-12-22T18:40:09.4683-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-2171] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] NZ Library Error: Invalid X509 certificate chain [Hint: the client probably doesn't provide a valid client certificate]
    [2011-12-22T18:40:09.4685-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] (20014)Internal error: proxy: pass request body failed to 10.139.164.191:7001 (denovm11-1.us.oracle.com)
    [2011-12-22T18:40:09.4685-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] proxy: pass request body failed to 10.139.164.191:7001 (denovm11-1.us.oracle.com) from 10.139.164.196 ()
    And the following error on the weblogic side:
    ####<Dec 22, 2011 6:40:10 PM MST> <Warning> <Security> <denovm11-1> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8e6c6502a1af117a:4eeee51e:13466bb040d:-8000-000000000000a764> <1324604410502> <BEA-090482> <BAD_CERTIFICATE alert was received from denovm11-6.us.oracle.com - 10.139.164.196. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Here is my ssl.conf from OHS:
    # Oracle HTTP Server mod_ossl configuration file: ssl.conf #
    # OHS Listen Port
    Listen 443
    <IfModule ossl_module>
    ## SSL Global Context
    ## All SSL configuration in this context applies both to
    ## the main server and all SSL-enabled virtual hosts.
    # Some MIME-types for downloading Certificates and CRLs
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl .crl
    # Pass Phrase Dialog:
    # Configure the pass phrase gathering process.
    # The filtering dialog program (`builtin' is a internal
    # terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog builtin
    # Inter-Process Session Cache:
    # Configure the SSL Session Cache: First the mechanism
    # to use and second the expiring timeout (in seconds).
    SSLSessionCache "shmcb:${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}/ssl_scache(512000)"
    SSLSessionCacheTimeout 300
    # Semaphore:
    # Configure the path to the mutual exclusion semaphore the
    # SSL engine uses internally for inter-process synchronization.
    <IfModule mpm_winnt_module>
    SSLMutex "none"
    </IfModule>
    <IfModule !mpm_winnt_module>
    SSLMutex pthread
    </IfModule>
    ## SSL Virtual Host Context
    <VirtualHost *:443>
    <IfModule ossl_module>
    # SSL Engine Switch:
    # Enable/Disable SSL for this virtual host.
    SSLEngine on
    # Client Authentication (Type):
    # Client certificate verification type and depth. Types are
    # none, optional and require.
    SSLVerifyClient none
    # SSL Cipher Suite:
    # List the ciphers that the client is permitted to negotiate.
    SSLCipherSuite SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_DES_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA
    # SSL Certificate Revocation List Check
    # Valid values are On and Off
    SSLCRLCheck Off
    #Path to the wallet
    SSLWallet "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default"
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/cgi-bin">
    SSLOptions +StdEnvVars
    </Directory>
    BrowserMatch ".*MSIE.*" \
    nokeepalive ssl-unclean-shutdown \
    downgrade-1.0 force-response-1.0
    </IfModule>
    <IfModule proxy_module>
    ProxyRequests Off
    <Proxy *>
    Order deny,allow
    Allow from all
    </Proxy>
    # Path to the wallet
    SSLProxyWallet "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default"
    SSLProxyEngine on
    SSLProxyVerify none
    # ottest : denovm11-1
    ProxyPass /test https://abc.us.oracle.com:7001/test
    ProxyPassReverse /test https://abc.us.oracle.com:7001/test
    </IfModule>
    </VirtualHost>
    </IfModule>
    On the OHS side I have all the certificates needed so SSL is working properly. The weblogic environment is currently working fine with other webgates, but those are apache and we are trying to switch to OHS.
    Can OHS use mod_proxy to connect to weblogic or do I need to use mod_wl_ohs?
    Does anyone see anything wrong in my ssl.conf file in regards to the proxy section.
    Thanks in advance.

    In summary:
    You need to create a new wallet with CSR (certificate signing req)
    Send this to your certificate authority and get the signed server certificate.
    Now import the signed server cert and the trusted root cert in to the wallet that you created newly.
    Modify ssl.conf to point to the new wallet location.
    To create wallet refer to : http://docs.oracle.com/cd/E25054_01/core.1111/e10105/wallets.htm#CHDGIJDC
    Further reference: http://docs.oracle.com/cd/E25054_01/core.1111/e10105/sslconfig.htm#CBDGIJDF
    Dont mind if this doc is 500 pages ;)

  • Quotes in attributes in a custom tag are failing in weblogic 5.1

    This seems to be on and off behaviour but when my tags are failing I
              have traced it down to the fact that my attributes have quotes in
              them. (By the way I'm running weblogic 5.1 with service pack 10)
              ie:
              <a:foo bar="<%=req.getParemeter("biz")%>">. Escaping the internal
              quotes doesn't seem to help the matter at all.
              After many hours of racking my brain to try and figure out why the
              tags were failing I found a message somewhere in this group which said
              they had the same issue and worked around it by using single qoutes
              around any attribute with a qoute in it ie: <a:foo
              bar='<%=req.getParemeter("biz")%>'>. This work around worked for me as
              well but leaves me with 2 important questions.
              a) According to weblogic this is issue (and I quote from their
              website) "CR 34389: Escaping Quotes was not working in the value tag
              for JSP params; The JSP spec says that quotations (") are to be
              escaped with \" . Fixed quoting problems for double and single quotes.
              " This was supposedly fixed in service pack 9, I'm running service
              pack 10 so what gives???
              b) Since this single qoute thing is not in the JSP spec if I keep it
              like this to get my tags working under my current setup and then we
              eventually migrate to weblogic 6x is there a risk all my tags will
              break?
              

    This seems to be on and off behaviour but when my tags are failing I
              have traced it down to the fact that my attributes have quotes in
              them. (By the way I'm running weblogic 5.1 with service pack 10)
              ie:
              <a:foo bar="<%=req.getParemeter("biz")%>">. Escaping the internal
              quotes doesn't seem to help the matter at all.
              After many hours of racking my brain to try and figure out why the
              tags were failing I found a message somewhere in this group which said
              they had the same issue and worked around it by using single qoutes
              around any attribute with a qoute in it ie: <a:foo
              bar='<%=req.getParemeter("biz")%>'>. This work around worked for me as
              well but leaves me with 2 important questions.
              a) According to weblogic this is issue (and I quote from their
              website) "CR 34389: Escaping Quotes was not working in the value tag
              for JSP params; The JSP spec says that quotations (") are to be
              escaped with \" . Fixed quoting problems for double and single quotes.
              " This was supposedly fixed in service pack 9, I'm running service
              pack 10 so what gives???
              b) Since this single qoute thing is not in the JSP spec if I keep it
              like this to get my tags working under my current setup and then we
              eventually migrate to weblogic 6x is there a risk all my tags will
              break?
              

  • Patch 19591087 unable to apply weblogic 12.1.3

    I am unable to apply patch 19591087 in weblogic 12.1.3
    getting below error logs
    Environment:
       OPatch.ORACLE_HOME=/apps/wlserver/12.1.3
       oracle.installer.invPtrLoc=/apps/wlserver/12.1.3/oraInst.loc
       oracle.installer.oui_loc=/apps/wlserver/12.1.3/oui
       oracle.installer.library_loc=/apps/wlserver/12.1.3/oui/lib/linux64
       oracle.installer.startup_location=/apps/wlserver/12.1.3/oui
       OPatch.PLATFORM_ID=
       os.name=Linux
       OPatch.NO_FUSER=
       OPatch.SKIP_VERIFY=null
       OPatch.SKIP_VERIFY_SPACE=null
       oracle.installer.clusterEnabled=false
       TRACING.ENABLED=null
       TRACING.LEVEL=null
       OPatch.DEBUG=false
       OPATCH_VERSION=13.2.0.0.0
       Bundled OPatch Property File=properties
       Minimum OUI version: 10.2
       OPatch.PATH=/opt/boksm/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/novell/zenworks/bin
       OPatch.MW_HOME=/apps/wlserver/12.1.3
       OPatch.WL_HOME=
       OPatch.COMMON_COMPONENTS_HOME=
    Oracle Home       : /apps/wlserver/12.1.3
    Central Inventory : /opt/home/mwswls/oraInventory
       from           : /apps/wlserver/12.1.3/oraInst.loc
    OPatch version    : 13.2.0.0.0
    OUI version       : 13.2.0.0.0
    Log file location : /apps/wlserver/12.1.3/cfgtoollogs/opatch/opatch2014-12-19_04-35-15AM_1.log
    OPatch detects the Middleware Home as "/apps/wlserver/12.1.3"
    Dec 19, 2014 4:35:23 AM oracle.sysman.oii.oiii.OiiiInstallAreaControl initAreaControl
    INFO: Install area Control created with access level  0
    Bugs fixed by this patch 19591087:
       18820382: Fix for Bug 18820382
    Applying interim patch '19591087' to OH '/apps/wlserver/12.1.3'
    Verifying environment and performing prerequisite checks...
    Running prerequisite check "CheckMinimumOPatchVersion" ...
    All patches can be applied using this OPatch.
    Prerequisite check "CheckMinimumOPatchVersion" passed.
    Running prerequisite check "CheckPatchingModel" ...
    Prerequisite check "CheckPatchingModel" passed.
    Running prerequisite check "CheckForIdenticalPatchInOracleHome" ...
    Prerequisite check "CheckForIdenticalPatchInOracleHome" passed.
    Patch "19591087" is ignored as it is not a "Fusion Applications patch".
    Prerequisite check "CheckFileVersionFormat" passed.
    Check if patch "19591087"  is a no-op patch.
    We have required comps greater than zero, so returning false for no-op patch "19591087"
    None of the selected patches are no-op. patches..
    There are some (or) all patches that are not no-ops.
    Running prerequisite check "CheckFusionAppsCompatible" ...
    OPatch is compatible with OUI for Fusion Apps patching.
    Running prerequisite check "CheckForInputValues" ...
    Input values is present for the all the actions of the given patches.
    Running prerequisite check "CheckSystemSpace" ...
    Finding the total space needed...
    Total space needed for the patches are: 4663474
    Checking if enough space is present on the disk...
    Required amount of space is availale on the disk.
    Enough system space is available.
    Running prerequisite check "CheckSystemCommandAvailable" ...
    All the required commands are available.
    All the required system commands are present.
    Running prerequisite check "CheckPatchApplicableOnCurrentPlatform" ...
    Genereic Platform ID 0is specified for patch : 19591087
    All the given patches are applicable on the current platform.
    Running prerequisite check "CheckApplicable" ...
    Prerequisite check "CheckApplicable" failed.
    The details are:
    Patch 19591087: Required component(s) missing : [ oracle.jrf.adfrt, 12.1.3.0.0 ] , [ oracle.jrf.adfrt, 12.1.3.0.0 ]
    Log file location: /apps/wlserver/12.1.3/cfgtoollogs/opatch/opatch2014-12-19_04-35-15AM_1.log
    Recommended actions: This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.
    OPatch failed with error code 39
    Package/s not installed. Please verify the patch logs.

    Hi Mike,
    Could you please guide which one exactly from the below link. I have installed generic Oracle WebLogic Server and Oracle Coherence 12.1.3
    http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
    Thanks

  • Logging JDBC Statements in Weblogic 8.1

    Hi,
    I am using Weblogic 8.1.I want to see the JDBC logs and right now I am getting
    "Oracle Jdbc tracing is not avaliable in a non-debug zip/jar file" error. Can
    any one help me with how to turn the JDBC Logging on? I am facing a wierd situation
    that one of my queries(it's from a Message Driven Bean) updates the Oracle database
    with junk values every time(the junk value differs each time) and so I want to
    see the exact SQL query which does this update.
    Thanks
    Jay

    Jay Balasubramanian wrote:
    Hi,
    I am using Weblogic 8.1.I want to see the JDBC logs and right now I am getting
    "Oracle Jdbc tracing is not avaliable in a non-debug zip/jar file" error. Can
    any one help me with how to turn the JDBC Logging on? I am facing a wierd situation
    that one of my queries(it's from a Message Driven Bean) updates the Oracle database
    with junk values every time(the junk value differs each time) and so I want to
    see the exact SQL query which does this update.
    Thanks
    JayHi. When we turn on jdbc logging, oracle's thin driver prints this out. There
    are two separate versions of the thin driver. We ship the regular one. The
    other one is a debug version. The best course is to download oracle's
    latest appropriate thin driver and put the debug version ahead of all weblogic
    jars in the classpath constructed for the server. Then when you turn on jdbc
    logging, you will get copious debug output.
    Joe

  • Weblogic proxy plugin closes keep-alive connections to clients randomly

    In short we have following arhitecture:
    clients ---> wl proxy plugin 1 ----> weblogic 1
    clients ---> wl proxy plugin 2 ----> weblogic 2
    Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
    Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
    Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
    As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
    We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
    Trace (replaced sensitive information):
    Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
    Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
    Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
    Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
    Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
    Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
    Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
    !!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
    WL proxy plugin conf params are:
    WebLogicCluster $IP$:$PORT$
    DynamicServerList OFF
    KeepAliveTimeout 90
    MaxKeepAliveRequests 0
    KeepAliveSecs 55
    Apache worker configuration is:
    <IfModule mpm_worker_module>
    PidFile var/run/httpd-worker.pid
    LockFile var/run/accept-worker.lock
    StartServers 2
    MinSpareThreads 25
    MaxSpareThreads 75
    ThreadLimit 200
    ThreadsPerChild 200
    MaxClients 2000
    MaxRequestsPerChild 0
    AcceptMutex pthread
    </IfModule>
    Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
    Any help?

    If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
    MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
    Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
    See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
    You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
    On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

Maybe you are looking for

  • ITunes ID Not Being Recognized by iTunes Program

    Hello, I have signed up for iTunes and gone through all the required steps.  I've created my Apple ID (it works perfectly), verified my email, I have chosen my payment option (PayPal), etc.  The iTunes program itself takes me to my browser to my PayP

  • Show standard texts on document

    Hi all, Our customers have the need to show some text on the bottom of some documents (invoice, order confirmation). Normally, I would use SO10 for the text. No problem there. In general, those texts have a limited time in which they should be printe

  • Fast wi-fi but extremely slow wired broadband

    Bit of a strange one here. Forthe last 24 hours have had ridiculously slow connection via a wired ethernet connection on my PC, yet my wi-fi connection on my laptop, phone etc is still working at top speed. Any ideas why this might be and what I can

  • (SOLVED) hal and automounting

    Hallo. I am e newbie of Arch. Two months ago I installed Arch on pc without problem and with a very few customisation. I tryed to do the same with my laptop. Installation with the last set was found on web was ok, but now ... I am unable to see hotpl

  • Access work PC from home iMac

    I expect delivery of my first iMac today . Need to communicate with my work desktop PC . Have been using a VPN client at my home PC and Remote Desktop in Windows on my work PC. How do I connect my home iMac to my work PC?