Javax.naming.NameNoteFoundException on admin server startup

On a WLS6.1+SP1 installation, I've created an Admin server and a Managed
Server. Of a sudden, I'm noticing a naming exception in the beans deployed
in the managed server. So, backtracking the problem, I bring up my admin
server (managed server is down) and see the following when I open up a
browser page for the admin server's JNDI tree and click on the java.comp
link:
javax.naming.NameNotFoundException: Unable to resolve comp. Resolved: ''
Unresolved:'comp' ; remaining name ''
     <>
Current Date
Mon Mar 18 10:08:45 CST 2002
Console Release Build
Console Build
Server Release Build
6.1.1.0
Server Build
WebLogic Temporary Patch for CR064232 01/15/2002 06:32:18
All Server Product Versions
WebLogic Temporary Patch for CR064232 01/15/2002 06:32:18
WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716
WebLogic XML Module 6.1 SP1 09/18/2001 14:43:02 #138716
Server System Properties
awt.toolkit = sun.awt.windows.WToolkit bea.home = e:/bea file.encoding =
Cp1252 file.encoding.pkg = sun.io file.separator = \ java.awt.fonts =
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment java.awt.printerjob
= sun.awt.windows.WPrinterJob java.class.path =
.;.\lib\CR058838_61sp1.jar;.\lib\CR064232_61sp1.jar;.\lib\weblogic_sp.jar;.\
lib\weblogic.jar java.class.version = 47.0 java.ext.dirs =
e:\bea\jdk131\jre\lib\ext java.home = e:\bea\jdk131\jre java.io.tmpdir =
E:\DOCUME~1\ewhite\LOCALS~1\Temp\ java.library.path =
e:\bea\jdk131\bin;.;E:\WINNT\System32;E:\WINNT;.\bin;e:/bea/jdk131/bin;.\;d:
\java\jdk1.3.1_02\bin;D:\Java\Jikes-1.15\bin;d:\java\jdk1.3.1_02\jre\bin;d:\
mssdk\bin\.;d:\mssdk\bin\winnt\.;e:\oracle\ora81\bin;e:\program
files\oracle\jre\1.1.7\bin;d:\bin;e:\devstudio\vc98\bin;e:\devstudio\common\
msdev98;e:\devstudio\common\tools\winnt;e:\devstudio\common\tools;d:\mks\bin
;d:\mks\bin\x11;d:\mks\mksnt;e:\winnt\system32;e:\winnt;e:\winnt\system32\wb
em;e:\program files\perforce;e:\program files\microsoft sql
server\80\tools\binn;e:\devstudio\common\msdev98\bin;d:\bugseeker2\bin;E:\Pr
ogram
Files\doxygen\bin;d:\polyhedra\4.1\win32\i386\bin;d:\src\db-4.0.14\build_win
32\Release;E:\Program Files\JavaSoft\JRE\1.3.0_02\bin\hotspot;
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories
java.protocol.handler.pkgs =
weblogic.net|weblogic.management|weblogic.net|weblogic.net|weblogic.utils|we
blogic.utils|weblogic.utils java.runtime.name = Java(TM) 2 Runtime
Environment, Standard Edition java.runtime.version = 1.3.1-b24
java.security.policy = =e:/bea\wlserver6.1sp1/lib/weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc. java.specification.version
= 1.3 java.vendor = Sun Microsystems Inc. java.vendor.url =
http://java.sun.com/ java.vendor.url.bug =
http://java.sun.com/cgi-bin/bugreport.cgi java.version = 1.3.1 java.vm.info
= mixed mode java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0 java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.3.1-b24 javax.rmi.CORBA.PortableRemoteObjectClass =
weblogic.iiop.PortableRemoteObjectDelegateImpl javax.rmi.CORBA.UtilClass =
weblogic.iiop.UtilDelegateImpl javax.xml.parsers.DocumentBuilderFactory =
weblogic.xml.jaxp.RegistryDocumentBuilderFactory
javax.xml.parsers.SAXParserFactory =
weblogic.xml.jaxp.RegistrySAXParserFactory
javax.xml.transform.TransformerFactory =
weblogic.xml.jaxp.RegistrySAXTransformerFactory jmx.implementation.name =
JMX RI jmx.implementation.vendor = Sun Microsystems
jmx.implementation.version = 1.0 jmx.specification.name = Java Management
Extensions jmx.specification.vendor = Sun Microsystems
jmx.specification.version = 1.0 Final Release line.separator =
org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser os.arch = x86
os.name = Windows 2000 os.version = 5.0 path.separator = ;
sun.boot.class.path =
e:\bea\jdk131\jre\lib\rt.jar;e:\bea\jdk131\jre\lib\i18n.jar;e:\bea\jdk131\jr
e\lib\sunrsasign.jar;e:\bea\jdk131\jre\classes sun.boot.library.path =
e:\bea\jdk131\jre\bin sun.cpu.endian = little sun.cpu.isalist = pentium i486
i386 sun.io.unicode.encoding = UnicodeLittle user.dir =
E:\bea\wlserver6.1sp1 user.home = E:\Documents and Settings\ewhite
user.language = en user.name = ewhite user.region = US user.timezone =
America/Chicago weblogic.Domain = cfgdomain weblogic.Name = cfgserver
weblogic.ProductionModeEnabled = true
Request Info
Protocol: HTTP/1.1
ServerName: seven
ServerPort: 7031
Secure: false
ContextPath: /console
ServletPath: /common/error.jsp
QueryString:
context=java%3Acomp&server=cfgdomain%3AName%3Dcfgserver%2CType%3DServer
PathInfo: null
PathTranslated: null
RequestURI: /console/common/error.jsp
AuthType: null
ContentType: null
CharacterEncoding: null
Locale: en_US
Method: GET
Session:
weblogic.servlet.internal.session.MemorySessionData@ca001
RequestedSessionId:
PJYQ1qF2jHmBElsIY3UWeyAv28eGyCuiyz4yM26b1118N4Tm3SXg!1873029388!169017744!70
31!7032!1016467710213
RequestedSessionIdFromCookie: true
RequestedSessionIdFromURL: false
UserPrincipal: system
RemoteUser: system
RemoteAddr: 10.19.1.144
RemoteHost: seven.vignette.com
Parameters
context = java:comp server = cfgdomain:Name=cfgserver,Type=Server
Attributes
wlinternalaction =
weblogic.management.console.actions.internal.InternalActionContext@36f7e6
java.util.Locale = en_US javax.servlet.error.exception_type = class
javax.naming.NameNotFoundException javax.servlet.error.message = Unable to
resolve comp. Resolved: '' Unresolved:'comp' javax.servlet.jsp.jspException
= javax.naming.NameNotFoundException: Unable to resolve comp. Resolved: ''
Unresolved:'comp' ; remaining name '' weblogic.auth.status = 0
weblogic.httpd.user = system weblogic.management.console.catalog.Catalog =
weblogic.management.console.catalog.XmlCatalog@192223
weblogic.management.console.helpers.BrowserHelper = User-Agent: Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.0; Q312461) IE: true Netscape: false
Supported: false JavscriptHrefs: false TableCellClick: true
DocumentReloadedOnResize: false DropdownStretchable: true CellSpacingBlank:
false EmptyCellBlank: false ImgOnclickSupported: true TableBorderFancy: true
PartialToWideTables: false DisabledControlSupported: true
weblogic.management.console.helpers.DebugHelper =
weblogic.management.console.helpers.DebugHelper@5caa65
weblogic.management.console.helpers.UnitsHelper =
weblogic.management.console.helpers.UnitsHelper@104bc9
weblogic.management.console.helpers.UrlHelper =
weblogic.management.console.helpers.UrlHelper@4d3bec
Headers
Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword,
*/* Accept-Encoding = gzip, deflate Accept-Language = en-us Connection =
Keep-Alive Cookie =
JSESSIONID=PJYQ1qF2jHmBElsIY3UWeyAv28eGyCuiyz4yM26b1118N4Tm3SXg!1873029388!1
69017744!7031!7032 Host = seven:7031 User-Agent = Mozilla/4.0 (compatible;
MSIE 6.0; Windows NT 5.0; Q312461)
BrowserInfo
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
Q312461)
IE: true
Netscape: false
Supported: false
JavscriptHrefs: false
TableCellClick: true
DocumentReloadedOnResize: false
DropdownStretchable: true
CellSpacingBlank: false
EmptyCellBlank: false
ImgOnclickSupported: true
TableBorderFancy: true
PartialToWideTables: false
DisabledControlSupported

There is a known problem in 6.1 SP1. The known problem was
corrected in SP2. Your symptoms are similar to the known
problem ...
DESCRIPTION: If you go to the examples server and view
the JNDI tree, there is a naming context called comp/env.
If you click on that naming context, you get message in
the JNDI tree in the left pane that says access denied.
You get the following exception in the right pane:
javax.naming.NameNotFoundException: Unable to
resolve comp.env Resolved: '' Unresolved:'comp' ;
remaining name 'env'
<>
--------------- nested within: ------------------
weblogic.management.console.actions.ActionException: Unable to resolve comp.env
Resolved: '' Unresolved:'comp' - with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve comp.env Resolved:
'' Unresolved:'comp' ; remaining name 'env']
at weblogic.management.console.actions.ErrorAction.(ErrorAction.java:38)
at weblogic.management.console.actions.jndi.ViewJndiContextAction.perform(ViewJndiContextAction.java:50)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Developer Relations Engineer
BEA Support

Similar Messages

  • OBIEE 11G 64-Bit Windows LDAP Admin Server Startup Issue

    All,
    I have OBIEE 11G installed on 64-bit Windows, and can see all my LDAP users inside Admin Console just fine. When I reorder my LDAP above the DefaultAuthenticator, and make them both 'SUFFICIENT', my Admin Server no longer starts. It hangs on a line in the AdminServer.log that roughly says '<Security initializing using security realm myrealm.>'. Has anyone ran into this? If so, how do you get the Admin Server to start with a non default LDAP authenticator? I've tried re-ordering numerous ways with the DefaultIdentityAsserter in the middle and at the bottom; I've also tried switching the Control Flags on both with REQUIRED and OPTIONAL, all to no avail. Finally, I tried deleting out the DefaultAuthenticator all together, and it still won't start. At this point, I'm assuming this is another 64-bit issue that was not tested properly. Any thoughts/help will be greatly appreciated.
    Thanks in Advance,
    Josh

    Paul,
    Unfortunately that made no difference. I have pasted in the startup log below. Perhaps someone has some insight into what's happening?
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <WebLogicServer> <HQ200-HYPPROD03> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1302613111266> <BEA-000000> <WebLogic Server "AdminServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Notice> <Log Management> <HQ200-HYPPROD03> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1302613111344> <BEA-170019> <The server log file D:\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Log Management> <HQ200-HYPPROD03> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1302613111360> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Diagnostics> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111438> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111594> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111594> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111594> <BEA-002622> <The protocol "http" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111594> <BEA-002622> <The protocol "https" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111594> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111610> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <RJVM> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111657> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address          :7002
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Server> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111688> <BEA-002609> <Channel Service initialized.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Socket> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111719> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Socket> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111751> <BEA-000436> <Allocating 3 reader threads.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <Socket> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111751> <BEA-000446> <Native IO Enabled.>
    ####<Apr 12, 2011 8:58:31 AM EDT> <Info> <IIOP> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613111907> <BEA-002014> <IIOP subsystem enabled.>
    ####<Apr 12, 2011 8:58:35 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613115079> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
    ####<Apr 12, 2011 8:58:35 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613115704> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Apr 12, 2011 8:58:35 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613115797> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_m7FMisDU3HeeJX/MUK4nqmEiSqI=>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116266> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116594> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116704> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.DomainRealmScope".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.RegistryScope".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.PKITypeScope".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.XACMLTypeScope".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.BEASAMLPartner".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116735> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Credential".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116751> <BEA-000000> <Parsing class "com.bea.common.security.store.data.CredentialMap".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116751> <BEA-000000> <Parsing class "com.bea.common.security.store.data.XACMLEntry".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116751> <BEA-000000> <Parsing class "com.bea.common.security.store.data.BEASAMLAssertingParty".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116766> <BEA-000000> <Parsing class "com.bea.common.security.store.data.BEASAMLRelyingParty".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116782> <BEA-000000> <Parsing class "com.bea.common.security.store.data.PasswordCredential".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116782> <BEA-000000> <Parsing class "com.bea.common.security.store.data.UserPasswordCredential".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116782> <BEA-000000> <Parsing class "com.bea.common.security.store.data.PasswordCredentialMap".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116797> <BEA-000000> <Parsing class "com.bea.common.security.store.data.ResourceMap".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116797> <BEA-000000> <Parsing class "com.bea.common.security.store.data.PKIResourceMap".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116797> <BEA-000000> <Parsing class "com.bea.common.security.store.data.WLSCertRegEntry".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116813> <BEA-000000> <Parsing class "com.bea.common.security.store.data.WLSCredMapCollectionInfo".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116813> <BEA-000000> <Parsing class "com.bea.common.security.store.data.WLSPolicyCollectionInfo".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116813> <BEA-000000> <Parsing class "com.bea.common.security.store.data.WLSRoleCollectionInfo".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116813> <BEA-000000> <Parsing class "com.bea.common.security.store.data.XACMLAuthorizationPolicy".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116829> <BEA-000000> <Parsing class "com.bea.common.security.store.data.XACMLRoleAssignmentPolicy".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116844> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Endpoint".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116844> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Partner".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116860> <BEA-000000> <Parsing class "com.bea.common.security.store.data.SPPartner".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116876> <BEA-000000> <Parsing class "com.bea.common.security.store.data.IdPPartner".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116907> <BEA-000000> <Parsing class "com.bea.common.security.store.data.SAML2CacheEntry".>
    ####<Apr 12, 2011 8:58:36 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613116922> <BEA-000000> <Parsing class "com.bea.common.security.store.data.SchemaVersion".>
    ####<Apr 12, 2011 8:58:37 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613117516> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    ####<Apr 12, 2011 8:58:37 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613117532> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
    ####<Apr 12, 2011 8:58:37 AM EDT> <Info> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613117766> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
    ####<Apr 12, 2011 8:58:37 AM EDT> <Notice> <Security> <HQ200-HYPPROD03> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302613117766> <BEA-090082> <Security initializing using security realm myrealm.>
    Thanks,
    Josh

  • Certificate error while admin server startup (solaris 8, wls 8.1.4)

    HI All,
    I am getting the following error while starting up my admin server using startWebLogic.sh.
    <Feb 5, 2010 7:51:19 AM GMT> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server "BOS1-ADMIN" for domain "BOS1">
    java.io.IOException: Inconsistent security configuration, Certificate expired: [
    Version: V3
    Subject: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: com.sun.net.ssl.internal.ssl.JSA_RSAPublicKey@672
    Validity: [From: Thu Feb 03 11:25:08 GMT 2005,
    To: Tue Feb 02 11:25:08 GMT 2010]
    Issuer: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00]
    [3]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: MD5withRSA
    Signature:
    0000: 74 15 DF 05 54 27 1D 1D D5 35 F4 99 24 1A 84 1C t...T'...5..$...
    0010: BF 93 25 FA 50 D7 1E 36 66 7F 30 1A EF 67 2A 79 ..%.P..6f.0..g*y
    0020: 4A 72 FD C1 3B 33 05 61 D0 52 92 2D 15 89 68 67 Jr..;3.a.R.-..hg
    0030: E8 13 A6 60 18 38 16 53 16 22 CC 4D 87 19 9F 30 ...`.8.S.".M...0
    0040: 28 F3 3C C0 4C C2 C4 34 69 D3 BA 5C B2 4D 8A FF (.<.L..4i..\.M..
    0050: AA DD BD 04 96 AF 69 05 73 77 8D 93 89 90 5D 23 ......i.sw....]#
    0060: E9 D0 CA 02 5A 20 39 40 85 12 A9 67 04 ED 7B 59 ....Z [email protected]
    0070: 34 FB 31 E7 AD F6 C0 AE E4 5E 66 BB 8E 7D 45 72 4.1......^f...Er
    at weblogic.t3.srvr.SSLListenThread.initSSLContext(SSLListenThread.java:205)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:139)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1637)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:890)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
    at weblogic.Server.main(Server.java:32)
    Any thoughts to share mates????
    I have already posted this topic in general discussion forum and as suggested by faisal posting here as well..Please let me know how to renew certificates????
    Cheers,
    Dinesh

    Hi Dinesh,
    Below are the steps to renew / get new certificates.
    Step A -- Create a Keystore file
    1. Using keytool, enter the following:
    keytool -genkey -alias server -keyalg RSA -keystore your_domain.jks
    'your_domain' in the command above should be the name of the domain you are securing. If you are ordering a Wildcard Certificate, do not include the * in the filename as it is not a valid filename character.
    2. You will be prompted to enter the information for your certificate.
    Please note: When prompted for the first and last name, DO NOT enter your first and last name. Instead, enter the name to which the certificate is being issued (e.g., www.yourdomain.com, mail.yourdomain.com, *.yourdomain.com).
    3. When prompted, enter 'y' or 'yes' to confirm. You will next be asked for a password. You will need to use this same password when generating a CSR and importing your certificates.
    Step B -- Generate a CSR from your new keystore
    1.     Use keytool to create a Certificate Signing Request from your keystore:
    keytool -certreq -alias server -keyalg RSA -file your_domain.csr -keystore your_domain.jks
    Again, 'your_domain' is the name of the domain you are securing. (without the * character if you are ordering a Wildcard Certificate).
    2.     Enter the keystore password.
    3.     Submit the CSR to the Certificate Authority for the certificates.
    Step C: Import and Install the Certificates.
    1.     First you will need to install the Root CA Certificate into your keystore. Copy-and-paste the root certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as trustroot.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the root certificate geotrustroot.pem into your keystore using the following command:
    keytool -import -alias geotrustca -keystore mykeystore -file geotrustroot.pem
    The command should be typed on one line. This command imports the GeoTrust Root CA Certificate into the keystore named mykeystore.
    Step D: Import and Install the SSL Server Certificate
    1.     Next install your SSL Server Certificate (public key) into your keystore. Copy-and-paste the server certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as public.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the SSL server certificate public.pem into your keystore using the following command:
    keytool -import -alias tomcat -keystore mykeystore -file public.pem
    The command should be typed on one line. This command imports the SSL server certificate into the keystore named
    mykeystore.
    Step E: Configuring Keystores
    1.     Both the GeoTrust root CA and SSL server certificates are now installed on your server. Next you will need to configure the keystores by following the instructions in the WebLogic documentation section Configuring Keystores.
    2.     Restart the WebLogic server.
    Hope the information helps.
    Regards,
    Raj

  • Admin Server startup for OAM

    1) OAM 11g installed, admin and managed server started fine.
    Port for OAM managed server is 14100 and port for Admin server is 7003
    Question: OAM console is accesible via hostname:7003/oamconsole
    What about port 14100? When is this port used, and why oamconsole not accesible via hostname:14100/oamconsole
    2) Following is message when Admin Server which hosts OAM is starting up
    <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
    Admin server is supposed to start first and then managed server (OAM here).
    Why is it looking to communicate with a managed server when admin server is starting up?

    968091 wrote:
    1) OAM 11g installed, admin and managed server started fine.
    Port for OAM managed server is 14100 and port for Admin server is 7003
    Question: OAM console is accesible via hostname:7003/oamconsole
    What about port 14100? When is this port used, and why oamconsole not accesible via hostname:14100/oamconsole
    /oamconsole is an administrative service and only available on the admin server.
    The managed service on 14100 is used for authentication and authorization services, ie for logging in and out.
    >
    2) Following is message when Admin Server which hosts OAM is starting up
    <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
    Admin server is supposed to start first and then managed server (OAM here).
    Why is it looking to communicate with a managed server when admin server is starting up?The managed service is used for authentication, even for /oamconsole service, so when the admin server starts up, it checks whether the login service is available which at this point it won't be, hence you get that error message. Once the managed server is started, that error should stop.

  • Weblogic Admin server startup failure in Fusion Apps environment.

    I am getting the following exception trace after applying SOA B5 patch:
    Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:101)
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:432)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
    Truncated. see log file for complete stacktrace
    >
    <Jul 3, 2012 10:40:15 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jul 3, 2012 10:40:15 AM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jul 3, 2012 10:40:15 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

    1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    2) Delete $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    3) copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/
    4) Restart the server.
    REgards
    Gourav

  • Error while starting the weblogic admin server for OSB

    Hi all,
    Please help.
    My admin server startup is breaking for weblogic 11g for the following cause :
    Caused By: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load elem
    ent "persistence-config"
    MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepo
    s" is invalid.
    ORA-06550: line 1, column 12:
    PLS-00201: identifier 'MDS_INTERNAL_SHREDDED.GETREPOSITORYVERSION' must be decla
    red
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    at oracle.mds.config.PConfig.loadFromBean(PConfig.java:684)
    at oracle.mds.config.PConfig.<init>(PConfig.java:499)
    at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:707)
    at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:764)
    at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:420)
    Truncated. see log file for complete stacktrace
    *>*
    *<Dec 15, 2011 12:51:22 PM GMT+05:30> <Error> <Deployer> <BEA-149231> <Unable to*
    set the activation state to true for the application 'wsm-pm'.
    *weblogic.application.ModuleException: [HTTP:101216]Servlet: "PolicyManagerValida*
    *tor" failed to preload on startup in Web application: "/wsm-pm".*
    oracle.adf.share.ADFShareException: MDSConfigurationException encountered in par
    seADFConfiguration
    at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConf
    ig.java:178)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfi
    gImpl.java:472)
    at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.j
    ava:543)
    at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.j
    ava:521)
    at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.ja
    va:586)
    at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.ja
    va:581)
    at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(
    ADFContextMDSConfigHelperImpl.java:274)
    at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:16
    *19)*
    at oracle.wsm.repository.mds.MDSInstanceFactory.getMDSInstance(MDSInstan
    ceFactory.java:95)
    at oracle.wsm.policymanager.bean.AbstractBean.getRepository(AbstractBean
    *.java:298)*
    at oracle.wsm.policymanager.bean.AbstractBean.createSession(AbstractBean
    *.java:198)*
    at oracle.wsm.policymanager.bean.UpgradeManagerBean.seedWSMPolicyReposit
    ory(UpgradeManagerBean.java:506)
    at oracle.wsm.policymanager.web.PolicyManagerValidator.init(PolicyManage
    rValidator.java:111)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
    ubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    *120)*
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
    tyHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
    ifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
    per.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
    mpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
    Thanks...

    I had a few packages and types in Invalid state.
    I compiled the same.
    But even then the same problem persists.
    Please help if any idea of any other change that may be needed..
    Thanks in advance

  • Unable to Start Weblogic Admin Server

    I am working on Windows environment with Weblogic 8.1 sp3
    when I start the admin from windows services the service shows as started but not able to get to console and also I tried starting the admin server from the command line it just stays here...
    <Sep 27, 2005 1:48:12 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file
    :\Projects\Domains\Broadlane\AdminServer\AdminServer.log is opened. All server side log events will be written to this file.>
    And also I enabled Verbose to see if it gives more info...but trying to load tons of files and hangs at some place
    [Opened C:\bea\JDK142~1\jre\lib\rt.jar]
    [Opened C:\bea\JDK142~1\jre\lib\sunrsasign.jar]
    [Opened C:\bea\JDK142~1\jre\lib\jsse.jar]
    [Opened C:\bea\JDK142~1\jre\lib\jce.jar]
    [Opened C:\bea\JDK142~1\jre\lib\charsets.jar]
    [Loaded java.lang.Object from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded java.io.Serializable from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded java.lang.Comparable from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded java.lang.CharSequence from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded java.lang.String from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded com.octetstring.vde.util.TimedActivityTask]
    [Loaded com.octetstring.vde.backend.standard.BackupTask]
    [Loaded com.octetstring.vde.util.TimedActivityThread]
    [Loaded com.octetstring.vde.backend.standard.TransactionLog]
    [Loaded java.io.RandomAccessFile from C:\bea\JDK142~1\jre\lib\rt.jar]
    [Loaded com.octetstring.vde.backend.standard.Cache]
    [Loaded com.octetstring.vde.backend.standard.DataFile]
    [Loaded com.octetstring.vde.util.ObjectPool]
    [Loaded com.octetstring.vde.backend.standard.RAFPool]
    [Loaded com.octetstring.vde.backend.standard.TransactionProcessor]
    and at this place just stays here with out going further, It is really frustrating me, because it doesnt throw any exceptions, I cleaned up everything in config.xml file just to start with basic with out any applications and database configurations in it, but it didnt helped me either
    Appreciate any help!
    Thanks in advance

    Hi hrushi,
    i'm not refering to the Weblogic console but your physical server console. You already did most of the tasks.
    Please do the steps below:
    1) Logon to your server Solaris console
    2) Get the PID of your Admin server Java process ex: ps -ef | grep java
    3) Execute the following command: kill -3 <pid>
    4) This will generate a Thread Dump within your Admin server startup log (normally nohup.out)
    5) Extract the Thread Dump and look at the Thread Stack Trace of the Weblogic start-up Thread
    6) The thread name you are looking or is: "Main Thread"
    7) Update this post with Stack Trace of the "Main Thread"
    Regards,
    P-H

  • Managed Servers vs. Admin Server - heap sizes

    I have a question. I opened a support ticket with BEA yesterday, the technician got back to me and completely confused the hell out of me.
    We're looking to upgrade to WLS10 with an admin server/managed server design. I was under the impression that each server instance, when fired up, starts up in its own JVM with its own memory allocations. If I set the admin server startup script to have a min and max of 1024, the managed server starts up with the same memory settings. The technician I spoke with yesterday from BEA support to clarify this then explains to me that each server instance, admin and managed, do not exist in their own JVMs but that they share the same JVM. I found verbage in the documentation that says the complete opposite...that one server instance can only exist in one JVM...SO if I have the admin server with 1024 and the managed server with 1024 and the machine only has 2 gigs, that's pretty much all I can have running on this machine, right?
    The thing I don't understand at all is why would I want the admin server and my application on the managed server to use the same amount of ram? My managed server should have way more ram available to it than the admin server which is rarely used throughout the day. Is there a way to set the admin server to 512 and then fire up the managed server with a gig and a half?
    I would think it makes more sense that you specify a different heap size for the admin versus the managed...but maybe not. What is the recommended heap size for the admin server? Is it strictly recommended to let them all use the same heap size settings? Can someone explain why I'd want the admin server to have access to the same amount my heavyweight, client-hit-all-day-long application?
    Any help would be greatly appreciated.
    Cheers,
    rlb

    Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
    At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
    Thanks again for your quick reply!
    Cheers,
    rlb

  • Javax.naming.NoInitialContextException ERROR

    I get the following error:
    Naming exception Error while connecting to the database : javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    I created a Java class which has a method which connects to the database using:
    InitialContext ctx = new InitialContext();
    javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup("jdbc/TMBLDB01CoreDS");
    m_connection = ds.getConnection();
    It errored out on the second line with the above error. I am using JDeveloper 10.1.3.
    I got it to work with a JDBC connection but prefer to use JNDI with JDBC.
    I started the Oracle AS Containers for J2EE (OC4J) by double clicking start_oc4j.bat.
    What is missing to make this work?

    Yes by adding the following solved that issue.
      env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);Another thing is I have added BC4J Client as library to my project. When I run I am getting
    javax.naming.NamingException: oracle.jbo.server.InitialContextImpl [Root exception is java.lang.ClassNotFoundException: oracle.jbo.server.InitialContextImpl]
         at oracle.jbo.common.JboInitialContextFactory.getInitialContext(JboInitialContextFactory.java:65)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)Do I need any other libraries?
    Thanks

  • Admin server start up failure

    All,
    Do you see the following error during admin server startup? What may be the cause?
    The password or id typo will not cause the follow errors.
    Thanks.
    ==========================================================
    java.lang.SecurityException: Invalid Subject: principals=[administrator, Adminis
    trators]
    at weblogic.security.service.SecurityServiceManager.seal(SecurityService
    Manager.java:880)
    at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.ja
    va:152)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:374)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    End server side stack trace
    ==========================================================

    check the filerealm.properties
    in the line
    Invalid Subject: principals=[administrator, Adminis trators] at
    it should be like this
    acl.boot.weblogic.server=Administrators,everyone
    group.Administrators=system,admin
    acl.lockServer.weblogic.admin=Administrators
    acl.unlockServer.weblogic.admin=Administrators
    acl.shutdown.weblogic.admin=Administrators
    thanks
    Mir

  • WLS 6.0:  javax.naming.NamingNotFoundException when selecting DataSource in server JNDI tree in Admin Console

    Summary of problem: Get a javax.naming.NamingNotFoundException when selecting the DataSource (see the configuration below) in server JNDI tree in Admin Console
    TheConnection Pool and a corresponding DataSource are configured as follows:
    <JDBCDataSource
    JNDIName="jdbc.PNStoreDB"
    Name="PNStoreDB"
    PoolName="PNStorePool"
    Targets="serverA"
    />
    <JDBCConnectionPool
    CapacityIncrement="2"
    DriverName="weblogic.jdbc.oci.Driver"
    InitialCapacity="2"
    LoginDelaySeconds="1"
    MaxCapacity="10"
    Name="PNStorePool"
    Properties="user=rms;password=rms;server=ora81"
    RefreshMinutes="10"
    Targets="serverA"
    TestTableName="dual"
    URL="jdbc:weblogic:oracle"
    />
    Can't figure out why this is happening. The following is output to the Admin Server command prompt:
    <May 18, 2001 10:20:02 AM EDT> <Error> <HTTP> <[WebAppServletContext(6233000,console)] exception raised on '/console/panel
    javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: '' Unresolved:'jdbc' ; remaining name ''
    <<no stack trace available>>
    I tried using a different JNDI name for the DataSource (e.g. just PNStoreDB) with no success.
    The weird thing is that it messes up other resources bound in the JNDI tree. For e.g. I have some EJB's bound under ejb/XXXX that I can click on and view in the Admin Console (JNDI tree) before I add the pool and DataSource. After I add them though, I see the same NameNotFoundException for these as well.
    Thanks in advance for your help.
    [att1.html]

    Are you sure that the connection pool and datasource deployed
    successfully? (Check the logs for an error.)
    Also, I suspect that you want a TxDataSource instead of a
    JDBCDataSource.
    -- Rob
    Weblogic NewsGroups wrote:
    Summary of problem: Get a javax.naming.NamingNotFoundException when
    selecting the DataSource (see the configuration below) in server JNDI
    tree in Admin Console
    TheConnection Pool and a corresponding DataSource are configured as
    follows:
    <JDBCDataSource
    JNDIName="jdbc.PNStoreDB"
    Name="PNStoreDB"
    PoolName="PNStorePool"
    Targets="serverA"
    />
    <JDBCConnectionPool
    CapacityIncrement="2"
    DriverName="weblogic.jdbc.oci.Driver"
    InitialCapacity="2"
    LoginDelaySeconds="1"
    MaxCapacity="10"
    Name="PNStorePool"
    Properties="user=rms;password=rms;server=ora81"
    RefreshMinutes="10"
    Targets="serverA"
    TestTableName="dual"
    URL="jdbc:weblogic:oracle"
    />
    Can't figure out why this is happening. The following is output to
    the Admin Server command prompt:
    <May 18, 2001 10:20:02 AM EDT> <Error> <HTTP>
    <[WebAppServletContext(6233000,console)] exception raised on
    '/console/panel
    javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved:
    '' Unresolved:'jdbc' ; remaining name ''
    <<no stack trace available>>
    I tried using a different JNDI name for the DataSource (e.g. just
    PNStoreDB) with no success.
    The weird thing is that it messes up other resources bound in the JNDI
    tree. For e.g. I have some EJB's bound under ejb/XXXX that I can
    click on and view in the Admin Console (JNDI tree) before I add the
    pool and DataSource. After I add them though, I see the same
    NameNotFoundException for these as well.
    Thanks in advance for your help.--
    Coming Soon: Building J2EE Applications & BEA WebLogic Server
    by Michael Girdley, Rob Woollen, and Sandra Emerson
    http://learnweblogic.com

  • WLS Admin and managed server startup issue

    Hi ,
    In one of WLS Domain both the Admin Server and Managed Server startup is just hanging at the below mentioned point :
    <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    After this there are no error messages or logs being generated and the server start up is not proceeding .
    Only message shown a while after this is :
    Warning : domain runtime mbean server has not been found after trying for 600 seconds
    Please provide some inputs on how to troubleshoot this issue .
    Checked the AdminServer.log and there are no errors reported there as well .
    Some more data from AdminServer.log :
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845368> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845632> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846193> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846208> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090082> <Security initializing using security realm myrealm.>
    Thanks
    Srinath
    Edited by: Srinath Menon on May 8, 2012 9:36 AM

    Hi Ashish ,
    Thanks for the inputs.
    Tried the same steps as mentioned but the issue still remains like that .
    Posting the thread dump collected for AdminServer:
    ===== FULL THREAD DUMP ===============
    Tue May 8 10:04:58 2012
    Oracle JRockit(R) R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32
    "Main Thread" id=1 idx=0x4 tid=9341 prio=5 alive, waiting, native_blocked
    -- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
    ^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
    at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
    at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
    at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:459)
    at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    ^-- Holding lock: java/lang/Class@0x9fa95598[biased lock]
    at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:879)
    at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:566)
    at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:467)
    at weblogic/Server.main(Server.java:71)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "(Signal Handler)" id=2 idx=0x8 tid=9342 prio=5 alive, native_blocked, daemon
    at <unknown>(???.c)@0xb7fe9410
    at sigiSignalHandlerThread+135(signalhandler.c:131)@0xb7ec2fd8
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(OC Main Thread)" id=3 idx=0xc tid=9343 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at ocMainThread+663(gcthreads.c:581)@0xb7d8a098
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(GC Worker Thread 1)" id=? idx=0x10 tid=9344 prio=5 alive, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
    at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
    at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(GC Worker Thread 2)" id=? idx=0x14 tid=9345 prio=5 alive, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
    at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
    at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(Code Generation Thread 1)" id=4 idx=0x18 tid=9348 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(Code Optimization Thread 1)" id=5 idx=0x1c tid=9349 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(VM Periodic Task)" id=6 idx=0x20 tid=9350 prio=10 alive, native_blocked, daemon
    at <unknown>(???.c)@0xb7fe9410
    at block_for_safepoint+106(safepoint.c:34)@0xb7ebad5b
    at eventTimedWait+239(event.c:83)@0xb7d6bd30
    at periodic_task_thread+627(periodictask.c:367)@0xb7e90dd4
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "Finalizer" id=7 idx=0x24 tid=9351 prio=8 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at RJNI_jrockit_memory_Finalizer_waitForFinalizees+211(finalhandles.c:1007)@0xb7d751f4
    at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native Method)
        at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
        at jrockit/memory/Finalizer$4.run(Finalizer.java:189)
        at java/lang/Thread.run(Thread.java:662)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "Reference Handler" id=8 idx=0x28 tid=9352 prio=10 alive, native_waiting, daemon
        at <unknown>(???.c)@0xb7fe9410
        at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
        at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
        at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
        at nativeUnlockAndWait+71(nativelock.c:686)@0xb7e790a8
        at RJNI_java_lang_ref_Reference_waitForActivatedQueue+38(semiref.c:342)@0xb7ebd9b7
        at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;(Native Method)
        at java/lang/ref/Reference.access$100(Reference.java:11)
        at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "(Sensor Event Thread)" id=9 idx=0x2c tid=9353 prio=5 alive, native_blocked, daemon
        at <unknown>(???.c)@0xb7fe9410
        at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
        at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
        at eventTimedWait+138(event.c:56)@0xb7d6bccb
        at eventWait+32(event.c:50)@0xb7d6bd81
        at sensor_event_loop+37(sensor.c:68)@0xb7ebfda6
        at thread_stub+146(lifecycle.c:808)@0xb7e2c333
        at start_thread+225(:0)@0x515832
        at __clone+93(:0)@0x46ae0e
    "VM JFR Buffer Thread" id=10 idx=0x30 tid=9354 prio=5 alive, in native, daemon
        at <unknown>(???.c)@0xb7fe9410
        at bufferthread+2135(vmjfr.c:1008)@0xb71744b8
        at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
        at thread_stub+146(lifecycle.c:808)@0xb7e2c333
        at start_thread+225(:0)@0x515832
        at __clone+93(:0)@0x46ae0e
    "Timer-0" id=13 idx=0x34 tid=9358 prio=5 alive, waiting, native_blocked, daemon
        -- Waiting for notification on: java/util/TaskQueue@0x9f9fc350[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at java/util/TimerThread.mainLoop(Timer.java:483)
    ^-- Lock released while waiting: java/util/TaskQueue@0x9f9fc350[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Timer-1" id=14 idx=0x38 tid=9363 prio=5 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: java/util/TaskQueue@0xa20ee240[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/util/TimerThread.mainLoop(Timer.java:509)
    ^-- Lock released while waiting: java/util/TaskQueue@0xa20ee240[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=15 idx=0x3c tid=9364 prio=5 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at netscape/ldap/LDAPMessageQueue.waitForMessage(LDAPMessageQueue.java:200)
    ^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[recursive]
    at netscape/ldap/LDAPMessageQueue.waitFirstMessage(LDAPMessageQueue.java:101)
    ^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
    at netscape/ldap/LDAPConnection.sendRequest(LDAPConnection.java:1796)
    ^-- Holding lock: netscape/ldap/LDAPConnection@0x9721f310[biased lock]
    at netscape/ldap/LDAPConnection.simpleBind(LDAPConnection.java:1763)
    at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1264)
    at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1273)
    at netscape/ldap/LDAPConnection.bind(LDAPConnection.java:1562)
    at weblogic/security/providers/authentication/LDAPAtnDelegate$LDAPFactory.newInstance(LDAPAtnDelegate.java:4134)
    at weblogic/security/utils/Pool.newInstance(Pool.java:37)
    at weblogic/security/utils/Pool.getInstance(Pool.java:33)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3478)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3470)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.authenticate(LDAPAtnDelegate.java:3522)
    at weblogic/security/providers/authentication/LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:227)
    at com/bea/common/security/internal/service/LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
    at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
    at com/bea/common/security/internal/service/LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(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)
        at javax/security/auth/login/LoginContext.invoke(LoginContext.java:769)
        at javax/security/auth/login/LoginContext.access$000(LoginContext.java:186)
        at javax/security/auth/login/LoginContext$4.run(LoginContext.java:683)
        at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
        at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
        at javax/security/auth/login/LoginContext.invokePriv(LoginContext.java:680)
        at javax/security/auth/login/LoginContext.login(LoginContext.java:579)
        at com/bea/common/security/internal/service/JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(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)
        at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at $Proxy28.login(Ljava/lang/String;Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
        at weblogic/security/service/internal/WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
        at com/bea/common/security/internal/service/JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(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)
        at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at $Proxy46.authenticate(Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
        at weblogic/security/service/WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
        at weblogic/security/service/PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
        at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
        at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
        at weblogic/security/service/SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic/security/SecurityService.start(SecurityService.java:141)
        at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic/work/ExecuteThread.execute(ExecuteThread.java:207)
        at weblogic/work/ExecuteThread.run(ExecuteThread.java:176)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "JFR request timer" id=16 idx=0x40 tid=9365 prio=5 alive, waiting, native_blocked, daemon
        -- Waiting for notification on: java/util/TaskQueue@0xa2049280[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at java/util/TimerThread.mainLoop(Timer.java:483)
    ^-- Lock released while waiting: java/util/TaskQueue@0xa2049280[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "weblogic.time.TimeEventGenerator" id=18 idx=0x44 tid=9366 prio=9 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
    ^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
    at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
    at java/lang/Thread.run(Thread.java:662)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "JMAPI event thread" id=19 idx=0x48 tid=9367 prio=5 alive, in native, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+526(nativelock.c:614)@0xb7e78b3f
    at nlMonitorWaitInner+79(nativelock.c:1112)@0xb7e78df0
    at nlMonitorWaitNoTransition+38(nativelock.c:1132)@0xb7e78e47
    at nativeRawMonitorWait+78(rawmonitor.c:161)@0xb7ea8caf
    at jvmti_RawMonitorWait+111(jvmtirawmonitors.c:95)@0xb7e1b420
    at threadProc+291(jmapi.c:305)@0x90452bd4
    at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "weblogic.timers.TimerThread" id=20 idx=0x4c tid=9368 prio=9 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:262)
    ^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace

  • Javax.naming.NamingException: when deploying to OC4J using admin.jar

    Additional details to posting (Problem Deploying to OC4J from Jbuilder8)
    Jul 8 2003 @3:27
    enter:-
    java -jar "\ora9ias\j2ee\home\admin.jar" ormi://myhost:23791 admin password
    and you get the error message:-
    javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
    java.net.ConnectionException: Connection refused: connect
    My server.xml contains entry &lt;rmi-config path="./rmi.xml" /&gt;
    and my rmi.xml reads:-
    &lt;?xml version="1.0" standalone="yes" ?&gt;
    &lt;!DOCTYPE rmi-server (View Source for full doctype...)&gt;
    - &lt;rmi-server port="23791" host="[ALL]"&gt;
    - &lt;log&gt;
    &lt;file path="../log/rmi.log" /&gt;
    &lt;/log&gt;
    &lt;/rmi-server&gt;
    I have repeatedly checked my hostname port user name and password
    along with the statements in the server.xml and rmi.xml as above, but with no
    success.
    Regards
    Gary.

    I am facing the same problem from this morning. I was able to start oc4j jvm without any problem today in the morning and i could deploy the war file and was able to test the web pages. But due to some unavoidable reasons i had to restart my machine and ever since then i am running into the following error.
    My server.xml has a reference to rmi.xml.
    Any help is highly appreciated.
    Regards
    Kiran
    D:\Java\JDev9i\j2ee\home>java -jar oc4j.jar
    Node started with id=647722646
    Error initializing web-site at ./http-web-site.xml: default-web-app not specifie
    d for Oracle9iAS Containers for J2EE HTTP Web Site
    Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized

  • I can not startup Managed server via admin server

    Admin server ip:172.16.219.25
    Admin server name:nstwssadm1.webex.com
    Managed server ip:172.16.219.189
    Managed server name:nstwss001.webex.com.
    I can start Managed server in comand line like 'startManagedWebLogic.sh nstwss001-s1 t3s://nstwssadm1.webex.com:9002'
    But, I can not startup Managed server in console, it appears following log:
    =========
    <Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server nst1::nstwss001-s1 ...>
    <Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'nstwss001-s1', pid: 11072>
    <Jun 29, 2006 8:56:19 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 Version ari-49095-20050826-1856-linux-ia32 from BEA Systems, Inc.>
    <Jun 29, 2006 8:56:19 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at https://172.16.219.25:9002 to check if there exists a running admin server at this URL.>
    <Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
    WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server https://172.16.219.25:9002 to retrieve the initial configuration.>
    <Jun 29, 2006 8:56:22 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/weblogic81/common/nodemanager/nstwss001-s1/nstwss001-s1.log is opened. All server side log events will be written to this file.>
    <Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
    Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:28 AM EDT> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : localhost>
    <Jun 29, 2006 8:56:28 AM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
    ===============================
    Who can help me on it?
    Thanks.

    your error says:
    'his server is unable to establish a connection to the <b>node manager</b>'
    check that your node manager is running when you try to start de manage server.

  • Javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'   - in Weblogic on starting the server

    Hi,
    I am not able to resolve the JNDI name - ATGProductionDS
    I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
    /atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
    /Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
    onfig\data\config
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource     Failed to resolve ATGProduct
    ionDS   javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
    ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
    Entries from Weblogic console -datasources
    ATGBatchDS
    Generic
    ATGBatchDS
    ATGProductionDS
    Generic
    ATGProductionDS
    atg_production_lockserver, atg_publishing_lockserver
    ATGPublishingDS
    Generic
    ATGPublishingDS
    atg_publishing_lockserver
    Please provide assistance.

    Hi,
    if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
    Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
    If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
    Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files?

Maybe you are looking for