WebLogicServer server is in RUNNING but Weblogic Admin console is not accessible.

All,
My WebLogicServer server is in RUNNING state but I am not able to login to th Weblogic admin console. admin console port comes in CLOSE_WAIT state.
Admin console Page does not get loaded. when I tried to netstat -an | grep 7003 find port in CLOSE_WAIT state.
172.16.1.180.7003 172.16.1.180.62206 139264 0 130880 0 CLOSE_WAIT
172.16.1.180.7003 172.16.1.180.53183 139264 0 130880 0 CLOSE_WAIT
172.16.1.180.7003 172.16.1.180.39834 139264 0 130880 0 CLOSE_WAIT
<Oct 24, 2013 11:56:00 AM AST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "OAM_domain" running in Development Mode>
<Oct 24, 2013 11:56:00 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Oct 24, 2013 11:56:00 AM AST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Also, there are no errors getting log in log files.
Regards,
Ram

The Admin console is an app internal to Weblogic, the possible cause for the CLOSE_WAIT could be that, the port was closed by server but not by the internal web app.
so it is hung in CLOSE_WAIT state. You might want to restart the servers so that the ports are cleared.
Try restarting the admin server and check the state of the port 7003 and see if you can access Admin console fine.
Hope this helps

Similar Messages

Embedded weblogic admin console will not start

Hi Forum members,
I'm using JDeveloper Studio Edition Version 11.1.1.0.2 and trying to start the WebLogic admin console for
JDeveloper's embedded WebLogic Server.
The admin login screen appears, but after entering userid and password, the admin console crashes.
The log entries are below; thanks for your assistance.
<Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423103> <[consolehelp] Deployment descriptor /WEB-INF/netuix-config.xml malformed.>
<Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423443> <Exception while initializing SingleFileServlet: [javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument].
javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
     at com.bea.netuix.util.ThrowServletException.throwServletException(ThrowServletException.java:28)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1053)
     at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
     at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
     at com.bea.netuix.servlets.manager.SingleFileServlet.access$100(SingleFileServlet.java:48)
     Truncated. see log file for complete stacktrace
java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
     at com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument$Factory.parse(WeblogicPortalAppDocument.java:533)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadConfig(AppDescriptor.java:670)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1040)
     at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
     at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
     Truncated. see log file for complete stacktrace
>
<Nov 4, 2009 12:45:24 PM PST> <Error> <netuix> <BEA-423540> <No IPreferenceStore implementation has been registered in WEB-INF/netuix-config.xml. See the javadoc for com.bea.portlet.prefs.spi.IPreferenceStore for information on how to configure a preference store. Using a no-op store as a default.>
<Nov 4, 2009 12:45:57 PM PST> <Error> <netuix> <BEA-423203> <The included control tree for URI [PortalConfig/snmp/Snmp.book] is invalid.
com.bea.netuix.nf.UIControlException: Error creating tree from uri [PortalConfig/snmp/Snmp.book].
     at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:91)
     at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
     at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
     at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
     at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
     Truncated. see log file for complete stacktrace
com.bea.netuix.nf.UIControlException: One or more validation error(s) occurred during parsing [PortalConfig/snmp/Snmp.book]. The error(s) were: [Parser Error...
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'netuix:meta'. One of '{"http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":toggleButton, "http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":content}' is expected.
     at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:80)
     at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
     at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
     at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
     at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
     Truncated. see log file for complete stacktrace
>
<Nov 4, 2009 12:46:26 PM PST> <Warning> <netuix> <BEA-423319> <A default encoding was not found for webapp [console]. You can set a default encoding for portals in netuix-config.xml. Defaulting to [UTF-8].>
<Nov 4, 2009 12:46:27 PM PST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@3ee3a0 - appName: 'consoleapp', name: 'console', context-path: '/console', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@13442f1[
GET /console/console.portal HTTP/1.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 (CK-zz) Firefox/3.0.14
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://127.0.0.1:7101/console/login/LoginForm.jsp
Cookie: JSESSIONID=jWpJKxnS1N3pd3ryQRGShJF7qbkZt2KrP9DdTPCphJh9vwvyJndL!662735321; ADMINCONSOLESESSION=5012KxnLnRNpnk679vWrWSbX2SXrhv0nqN11JcwGzJvhbjNy7L4R!662735321
]] Root cause of ServletException.
java.lang.NoClassDefFoundError: Could not initialize class schemacom_bea_xml.system.sF6C6DB196AAE83D234595A687AE0370E.TypeSystemHolder
     at sun.misc.Unsafe.ensureClassInitialized(Native Method)
     at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
     at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
     at java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
     at java.lang.reflect.Field.getFieldAccessor(Field.java:899)
     Truncated. see log file for complete stacktrace

The Fusion Middleware is installed on my Windows XP laptop. To start my admin server, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Start Admin Server for WebLogic Server Domain" menu item.
After the admin server is running, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Admin Server Console" menu item.
A web browser pops up and after a few minutes, the login screen appears. After logging in, the admin console return a error screen. The log file contains the previous posted entries.

Admin console is not accessible even when the Admin server is running

Running Weblogic 10.3.2 on RHEL 5.x and EM -11.0.1.0
Found the following errors in the server logs
<May 26, 2010 1:59:35 PM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'FMW Welcome Page Application [Version=11.1.0.0.0]'.
java.lang.IllegalArgumentException: URI is not hierarchical
at java.io.File.<init>(File.java:363)
at oracle.as.jmx.framework.util.MBeansXmlServletContextListenerSupport.getRelativePathsToMBeansXmlFiles(MBeansXmlServletContextListenerSupport.jav
There is a deployment problem with the welcome page.
Could not access the admin console.
Reinstalled everything but getting the same error
Thanks in Advance
Anurag

yes solved.......there was firewall enabled which was not allowing the https traffic to flow.
Firewall disabled and the admin console was accessible.
Thanks!!

SOA Suite 11g on WLS: Admin console EM not accessible

Hello everybody,
I am trying to install and run a sample SOA composite using SOASuite11g. Here are steps i followed-
1> Created schemas using RCU
2> Installed using JDeveloper11.1.1. 1.0.exe, which has installed Weblogic server and Jdeveloper.
3> Created a WLS domain (only admin server, no managed server and machines) and targeted al avalilable soa_suite components to the admin server.
4> Installed SOA Composite Editor (using Find Patches and Upgrade option in JDeveloper)
5> createed a basic soa composite project in jdeveloper and deployed that to the soa server.
6> if i go to http://localhost:port/soa_infra, the project is shown depolyed.
However, I am not getting any app under http://localhost:port/em or http://localhost:port/BPELConsole
If I login to the weblogic console http://localhost:port/console, under deployed applications there seems to be no such app.
Is it a problem with the version i have installed that even though it installs weblogic domain with soa_infra components, it does not supply the enterprise manager component.
Is there a way i can test the deployed compoiste?
Thank a lot in advance. Regards.
sibendu

Hi,
There is no BPELConsole in 11g. You can test your composites from EM, if you have selected EM during domain creation. If you haven't, then extend your domain with EM.
To extend the domain with EM, stop your servers in domain. Invoke the config. Select extend option. Select the EM template.
EM will be available in http://host:port/em
You can alternatively test your composites if you know the composite WSDL. You can use SOAP UI or any SOAP testing tools.
Usually it will be something like
http://host:port/soa-infra/services/default/TaskFormVerifyComposite!51.0/client?WSDL
In the above wsdl, till default it will be same for all the composite, followed by composite name, a ! symbol, followed by revision and then your exposed service. If you omit the revision, then the default revision will be invoked.
Hope this helps..!!!

Em showing everything is down including the admin server eventhough they are up in Weblogic Admin Console

Hi there,
We are running with Oracle Fusion Middleware 11.1.1.3.0 on top of Oracle Weblogic 10.3.3.0 which is installed on Windows Server 2008 64 bit. We have configured two SOA domains under this middleware home.For example, we will consider the SOA domain name as SOA1 and SOA2. When we logon to SOA1 Em console, Everything is showing the exact status as like SOA1 admin console. Whereas SOA2 is not the same case. SOA2 EM console showing all in red down arrow including Admin server but SOA2 admin console says everything running fine.
We checked the Oracle Doc ID 1484381.1 for more troubleshooting, But they have provided the patch only the version from 11.1.1.5.0 or later. Also we could see below error in the emos.log
[2015-03-03T10:49:58.166+01:00] [AdminServer] [NOTIFICATION:24] [] [oracle.sysman.emas.sdk.model.jmx.JMXUtil] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Found no object names where one was expected for query: oracle.dms:name=AggreSpy,type=Spy,*
[2015-03-03T10:49:58.175+01:00] [AdminServer] [NOTIFICATION:24] [] [oracle.sysman.emas.model.region.FMWRegionModel] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Error getting Response metrics
[2015-03-03T10:49:58.176+01:00] [AdminServer] [NOTIFICATION:32] [] [oracle.sysman.emas.model.region.FMWRegionModel] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Error getting Response metrics[[
Please help us to make sync the SOA2 EM console with SOA2 Admin console.
Thanks
Lakshman,

Hi Lakshman,
what about about the WLS admin console? What is reported there for both
domains?
When starting the managed servers for SOA2 domain, have you provided
the URL of the Admin Server of SOA2 domain?
Cheers,
A.

Weblogic Admin Console Running on different port

H,
We are using Weblogic 6.1 SP2. Is it possible to run Weblogic Admin Console and
our web application on the same Weblogic server, but with the console running
on a different port?
Thanks,
Jenny Chen

Thanks!
"Mark Griffith" <[email protected]> wrote:
There is an administration port, but this was not introduced until 7.1,
and
we simplified its setup and configuration in 8.1.
http://edocs.bea.com/wls/docs81/ConsoleHelp/domain.html#enabling
cheers
mbg
"Jenny Chen" <[email protected]> wrote in message
news:[email protected]..
H,
We are using Weblogic 6.1 SP2. Is it possible to run Weblogic AdminConsole and
our web application on the same Weblogic server, but with the consolerunning
on a different port?
Thanks,
Jenny Chen

Why cannot login to weblogic admin console . no error.

Why I cannot login to weblogic admin console. I keep getting login screen. I reset the userid and password but still cannot login
Here is what's in the log file:
Sep 26, 2010 8:55:14 PM EDT> <Warning> <HTTP> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914272> <BEA-101296> <Unable to load the default compiler class "com.sun.tools.javac.Main". Using the default javac compiler to compile JSPs.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914319> <BEA-000365> <Server state changed to STANDBY>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914335> <BEA-000365> <Server state changed to STARTING>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281003> <SAF Service has been initialized.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281002> <SAF Service has been started.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <WseeCore> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-220502> <The Wsee Service is starting>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Deployer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914366> <BEA-149209> <Resuming.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-320000> <The Diagnostics subsystem is initializing on Server myserver.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=C:\mydomain\servers\myserver\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (430fff8d-1448-4efe-ae57-8e17de6fd97a) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=0.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Log Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\mydomain\servers\myserver\logs/mydomain.log.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Log Management> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914507> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914538> <BEA-000365> <Server state changed to ADMIN>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914569> <BEA-000365> <Server state changed to RESUMING>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914663> <BEA-141052> <The auto deployment poller has started.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002610> <Dynamic Listener Service initialized.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default" is now listening on 172.16.37.59:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-000331> <Started WebLogic Admin Server "myserver" for domain "mydomain" running in Development Mode>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000365> <Server state changed to RUNNING>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000360> <Server started in RUNNING mode>
####<Sep 26, 2010 8:55:15 PM EDT> <Info> <J2EE> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915429> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
####<Sep 26, 2010 8:55:15 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915569> <BEA-010008> <EJB Deploying file: mejb.jar>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548916288> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
####<Sep 26, 2010 8:55:27 PM EDT> <Info> <WorkManager> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548927226> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928226> <BEA-423101> <[console] Initializing the NetUIx container>
####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928523> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929164> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929195> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<Sep 26, 2010 8:56:14 PM EDT> <Info> <Health> <TAXWARE_TEST> <myserver> <weblogic.GCMonitor> <<anonymous>> <> <> <1285548974540> <BEA-310002> <86% of the total memory in the server is free>

There is no error. Is there another domain on your OS? can you please put here your config.xml file and your login screen image here.
May be you use wrong console to login.

Problem while Deploying application in weblogic admin console

Hi all,
Recently i got an issue while deploying application through weblogic admin console,
I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
My weblogic 10.3 was running in windows 2008 r2
Kindly need a help to resolve this problem ASAP.
Regards,
Rakhi

Hi sir,
thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
Kindly give me a perfect resolution on this issue. because i was so confused on this part.
Regards,
Rakhi..

Weblogic admin console fails to start when commons logging is used.

I have an application that requires commons logging.
I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
Any ideas on why this is occuring?
See the error below:
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
Are you thinking that maybe we are we missing a step somewhere else within the site?
Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
We prefer to use the method with commons logging for our application.
One more specific here what we did on our last attempt.
1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
We are still not able to get the Weblogic admin console to start
Any other ideas?
Edited by: user13094648 on May 21, 2010 10:29 AM
Edited by: user13094648 on May 21, 2010 10:37 AM

Weblog Admin Console

Hi.
It used to be possible to turn on the weblog admin console in blojsom by deleting the # sign in the "flavor.properties" file for a weblog and then going online to the page weblog/yourweblogname/?flavor=admin.
I'm running OS X server 10.4.5 and although there are some great upgrades in this from the previous version (full podcast support with itunes store integration, etc.), I miss the old blojsom admin console. Maybe I'm missing something obvious, but how do I get it enabled and then access it? The old instructions here no longer apply:
http://www.theappleblog.com/2005/07/03/apples-blog-server/
New instructions, please? Thanks.

I was able to turn on the admin consolse on a OS X 10.4.5 server in the manner you suggest - uncomment the admin flavor in the users's flavor.properties file.
Mac OS X (10.4.5)

Weblogic Admin Console wl:tag Extensions & Navigation

Does anyone have a cunning tip to help fix my Navigation problem when using the Weblogic Admin Console extension tag wl:tab to create tabbed pages ?
          I have a JSP page (console.jsp) used to create a dialog containing a tabbed interface:
          <wl:dialog>
          <wl:tab name='AdminTab' label='Admin' >
          <jsp:include page="adminPage.jsp" />
          </wl:tab>
          <wl:tab name='ConfigTab' label='Configuration'>
          <jsp:include page="configPage.jsp" />
          </wl:tab>
          <wl:tab name='QueryTab' label='Query'>
          <jsp:include page="queryPage.jsp" />
          </wl:tab>
          </wl:dialog>
          When I select one of the tabbed pages and submit from it I currently use struts to navigate back to the console.jsp page which redraws the tabbed dialog. Is there any way to navigate back to display the contents of a specific tab ?

user489948 wrote:
<Sep 6, 2012 10:50:21 AM EDT> <Info> <Management> <BEA-141223> <The server name bi_server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.>The above message suggests that there is no managed server called bi_server1 configured on that WLS, but only an AdminServer.
If I try to start a non existing managed server (bi_server2) the same way I get:
+<Oct 10, 2012 2:07:52 PM EEST> <Info> <Management> <BEA-141223> <The server name bi_server2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer,bi_server1}.>+
You can check what is configured in your domain by reviewing <DOMAIN_HOME>\config\config.xml file (look for the <server> tags) but I think you have only
+<server>+
+<name>AdminServer</name>+

WebLogic Admin Console won't work with java security manager enabled.

By just enabling the security manager on the command line with -Djava.security.manager and using the default weblogic.policy in the server/lib directory, the admin console will not work. I just see a blank page when I try to access the admin console with permission errors all over on the server console.
In looking at the admin console's weblogic.xml it should have access to everything since it contains:
grant {
permission java.security.AllPermission;
Are there known issues with this? If I add this permission to the weblogic.policy file everything works fine but then I might as well not turn on the security manager.
Thanks,
Dave

David,
I was glad to see your post regarding WLS 9.2 and the troubles with enabling Java Security Manager.
Were you able to learn any more on things like - why doesn't the admin console work when the security manager is enabled with the default policy file. Also, why is it so difficult to add permissions for your own applications and get them to actually work.
I'd be curious to see if you were able to get it to work or if you have any insights or resources that can help with this as we are really struggling to get a restrictive policy file that works.
Thanks,
D

Weblogic admin console default password ?

Hi All
I am trying to log in to Peoplesoft Weblogic admin console
http://<server>:<port>/console/login/LoginForm.jsp is the url i am using and i am getting the log in page
entered the default user id and password as " system and password as password "
Below is the error message:
Authentication Denied
The username or password has been refused by WebLogic Server. Please try again.
What could be the reason?
WebLogic Server "PIA" version: WebLogic Server 10.3.1.0
PeopleTools 8.50
HR 9.1
Tuxedo10gR3_32_win_2k3_x86_VS2005
Have installed successfully, and Peoplesoft application is working fine.
Please let me know.
Thanks for your help.
Edited by: AfjalK on Dec 26, 2009 12:21 PM

The logon credentials have changed from Tools 8.50. Instead of system/password it's now system/Passw0rd. It is in the install guide but I didn't spot it first time through either.
Duncan

Is there a way to disable concurrent Weblogic Admin Console sessions for the same user?

A coworker on another workstation and I are able to log into same user account on the Weblogic Admin Console at the same time. I would like to restrict access so only one session per user account can be logged in to the Admin Console. Is this possible?
Alternatively, is there a way to log identifiable information (IP/workstation) when multiple sessions for one account occur at the same time?
I am using 10.3.6.0

Hi,
You could also check the http access logs for such info. There you could see records for the received requests, with each record starting with the source IP that initiated the request.
The default location for access logs is ${DOMAIN_HOME}/servers/${SERVER_NAME}/logs. Of course in your case, the ${SERVER_NAME} would be your admin server name (AdminServer if left as default).
Regards,
Mohab

Authentication denied on Weblogic admin console

I was playing with security policy for web applications and now I can't login from
console any more. It gives following error : Authentication Denied
The username or password has been refused by WebLogic Server. Please try again.
I can start the server from command line. How can I find out what is the problem
and how can I fix it ?
Thanks,
MK

Hi AB.
You can write your own pages and add them to WebLogic admin console by writing a console extension, here is a link to bea doc http://e-docs.bea.com/wls/docs100/console_ext/understandext.html
Regards,
Felix

WebLogicServer server is in RUNNING but Weblogic Admin console is not accessible.

Similar Messages

Maybe you are looking for