Weblogic 8.1 SP4 Admin Console JDBC or Start-up changes not taking effect?!

Gents..I have an open case with BEA on this one but wanted to get some immediate help here. I am trying to make changes to my JDBC pools to check the connection pools (reserved, created, & released) however once I check the boxes and click "Apply" then restart WebLogic the changes I made just revert back to as if I never made them?! This is the same case for when I try to undeploy a start-up class in the Admin interface. Permissions on the config.xml look to be writtable by the user who is running the weblogic process. Also after making the changes I only see a 1 byte change to the config.xml and dont see the changes (undeploy etc) actually being made?!
Any help would be greatly appreciated!
Thx
Cody

I did a reinstallation and the problem didnt re-occur. So one neednt work on this problem.
Priya

Similar Messages

Weblogic 10, WLST and Admin Console Classpath Exceptions

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

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

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

Sun Oner Application Server 7 Admin Console doesn't start

When I start the Admin Console for Sun One Application Server 7, and after I login, the admin console doesn't display in the browser. I have tried starting the admin console with IE and Netscape browser, but the admin console has failed to start in either IE or netscape.

-Type this in your IE
http://localhost:4848
-IF it does not work type the following
http://kishan:4848 ("kishan" is your machine name)
-IF it does not work do the following
Forgot the Admin Server Port Number? If you do not remember the HTTP server port number of the administrative server, you can inspect the administrative server's configuration file to determine the HTTP server port number.
1. Navigate to the <domain_config_dir>/domain1/admin-server/config/ directory.
2. Open the server.xml file in your favorite editor. Look for the element:
<http-listener id="http-listener-1" address="0.0.0.0" port="4848"...
In this case, port 4848 is the HTTP port number in use.
Forgot the Username or Password? If you do not remember the administrative user name that was supplied during installation, try the user name "admin". This is the default user name specified in the server configuration dialog during installation. If you still cannot determine the user name, look in the following file:
<domain_config_dir>/domain1/admin-server/config/admpw
This file contains the administrator's user name followed by the encrypted form of the administrative user's password.
If you do not remember the administrator's password, then you can delete the administrative domain using the delete-domain subcommand of asadmin and create a new domain with a new administrative password.
Port Not Accessible? If the connection was refused when attempting to contact the administrative server's admin console application, it is likely that the administrative server is not running. Go back to the beginning of this section and double check the your startup procedures and the content of the administrative server's log file to determine the reason why the server is not running.

Admin Console for EE 8.1 2005Q4 Not Working

Hello everyone!
I've recently created a new zone with the following setup:
# zonecfg -z sunappserver
zonecfg:sunappserver> create -b
zonecfg:sunappserver> set zonepath=/zones/sunappserver
zonecfg:sunappserver> set autoboot=true
zonecfg:sunappserver> add net
zonecfg:sunappserver:net> set address=192.168.10.110
zonecfg:sunappserver:net> set physical=nge0
zonecfg:sunappserver:net> end
zonecfg:sunappserver> verify
zonecfg:sunappserver> commit
zonecfg:sunappserver> exitI then install the zone,
# zoneadm -z sunappserver install
Preparing to install zone <sunappserver>.
Creating list of files to copy from the global zone.
Copying <101729> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1080> packages on the zone.
Initialized <1080> packages on zone.
Zone <sunappserver> is initialized.
Installation of these packages generated errors: <SUNWjhrt SUNWjhdev SUNWaadm SUNWabe SUNWabhdw SUNWalab SUNWaman SUNWas8doc SUNWcdeu SUNWdev SUNWgndoc SUNWinab SUNWsjdscm SUNWsodoc>
Installation of <1> packages was skipped.
The file </zones/sunappserver/root/var/sadm/system/logs/install_log> contains a log of the zone installation.After I install EE 8.1_2005Q4 using all the defaults, I use the following to start the domain:
# cd /opt/SUNWappserver/appserver/bin
# ./asadmin
asadmin> start-domain --user admin domain1
Starting Domain domain1, please wait.
Log redirected to /var/appserver/domains/domain1/logs/server.log.
Please enter password>
Please enter the master password>
Domain domain1 started.
asadmin> quitI then attempt to go view the admin console at http://localhost:4848 but all I get is a blank page. No content or login. If I create a new zone, and use the bundled version this works properly. Needless to say, I have deleted the domain and recreated it with the following:
asadmin> create-domain --adminport 4848 --adminuser admin domain1
Please enter adminpassword>
Please enter adminpassword again>
Please enter the master password>
Please enter the master password again>
Using default port 8,080 for HTTP Instance.
Using default port 7,676 for JMS.
Using default port 3,700 for IIOP.
Using default port 8,181 for HTTP_SSL.
Using default port 3,820 for IIOP_SSL.
Using default port 3,920 for IIOP_MUTUALAUTH.
Using default port 8,686 for JMX_ADMIN.
Domain domain1 created.However, the end result is the same.
Am I missing something or does anyone have any ideas?
Thanks in advance!
Joshua Preston

Well guys,
Just as an FYI, I have failed to notice that the default installation makes the admin console gui running on port 4849 secure!
So, after following the directions and connecting to:
http://localhost:4849without any success, it is actually a secure port! Therefore,
https://localhost:4849works properly!
I open my mouth only to change feet.
Thanks!
Joshua Preston.

Jrun4 admin console won't start

windows 2000 sp4, IIS5
jrun4 update 6
port is correctly set to 8000
permissions are wide open
admin server is running
after restarting the default and admin services, i noticed
the default-out.log indicated it was listening on port 8100.
there's no such entry for the admin-out.log, though it says "No
JDBC data sources have been configured for htis server...
Any ideas?

My FMS is running on a Centos-Based VPS.
You can install FMS using the default velues expect installing Apache (as its already serving as your Web Server).
After that, you'll have to open both ports 1935 for FMS (if you choose it by default) and 1111 for the Admin Server.
You can use this SSH command as root user to open a port on your Centos Based firewall:
"iptables -I INPUT -p tcp --dport 1935 --syn -j ACCEPT"
"iptables -I INPUT -p tcp --dport 1111 --syn -j ACCEPT"
If you would like to open a udb port for FMS, you can use this SSH command:
"iptables -I INPUT -p udp --dport 1935 -j ACCEPT"
*Without the quotes....
You can use yougetsignal.com to see if the ports are open on your mydomain.com or IP and accessible from the public.
If both ports are open on you Server's firewall, you'll have to be sure that FMS and the Admin Server are running, otherwise yougetsignal will told you that the ports are closed while they're open, because there's no services using them.
To start FMS and the Admin Server, do the following command:
"cd /opt/adobe/fms"
and :
"./fmsmgr server fms start"
and:
"./fmsmgr adminserver start"
Now, you have to go to /opt/adobe/fms/webroot/ and copy both fms_adminConsole.htm and the folder "swfs" and paste them somewhere in your webroot (/home/your-username/public_html)
and run it from your domain name by pointing the browser to where you paste the copied file and folder.
Any further questions, don't hesitate to ask,
Ilimaan

OAS 10.1.2 / chgiphost / EM-Console doesn't start after change of hostname

Hello!
I changed on my OAS 10.1.2 ip-address and hostname with script /$ORACLE_HOME/chgip/chgiphost.sh -mid.
But I can't start em-console and get the following error in em-application.log:
Portal Configuration Interface failed to initialise:
oracle.sysman.emSDK.emd.comm.CommException: IOException in sending Request :: newHostname.domain:cn=oldHostname.domain...
It seem's that chgiphost.sh script doesn't change em-console configuration.
Any ideas?
regards
Harald.

Solution:
I secured Enterprise Mangager (HTTPS, emctl secure...).
First, I must unsecure EM-Console, run "chgiphost.sh -mid" and then re-secure EM-Console.
Look at: Metalink - Note 280034.1 How to Secure and Unsecure the AS Control 10g Console
regards
Harald.

Weblogic 9.x admin console slowest and worst application ever

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

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

Start and Stop Weblogic From Admin Console

Hi All,
I am using weblogic7.0.I wanted to start and stop the weblogic server from the
Admin Console(ie., from the GUI).I can stop the server but I cannot start.In order
to start from admin console what should I do.
Please post your suggestions.
Thanks blazix

You need to run the Node Manager on the manged servers you wish to remotely
start.
Chris
"blazix" <[email protected]> wrote in message
news:3fc37eea$[email protected]..
>
Hi All,
I am using weblogic7.0.I wanted to start and stop the weblogic server fromthe
Admin Console(ie., from the GUI).I can stop the server but I cannotstart.In order
to start from admin console what should I do.
Please post your suggestions.
Thanks blazix

Unable to start Managed server from admin console using nodemanager

I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman

GUI Admin console not launching and fixed

Hello,
I spent some time on this might help someone...
I installed the Sun Java System application 8, everything worked (app server, pointbase, deploytool) except the gui admin console (localhost:4848). It would not launch. It <blinked>blinked</blinked>. Really - the tab text blinked on firefox. So I ...
1. checked PATH and JAVA_HOME to be correct.
2. rebooted
2. reinstalled appserver
3. rebooted
4. tried firefox & microsoft ie
To no avail.
I then turned off my firewall. It worked. It might for you too.
ciao,
-rob

Hi Andy,
I am not sure why you are unable to see the users and groups through the
console., you should be able to. Can you post the config.xml?
thanks,
-satya
Andy Levy <[email protected]> wrote in message
news:3b700c36$[email protected]..
>
We're running WLS 6.0 Sp2 on Windows 2000 Professional.
"Satya Ghattu" <[email protected]> wrote:
Andy,
Could you please tell us what Version of Weblogic you are running?
thanks,
-satya
Andy Levy <[email protected]> wrote in message
news:[email protected]..
We created a new Realm in WebLogic, which specifies the location ofthe
Netscape
LDAP server. Our Weblogic application, called TGSLC, is able to findthe
ldap
server to use for authentication. My problem is this- the Admin
Console
is not
displaying the new users and groups from the LDAP server. Shouldn'tthe
WebLogic
Admin Console display any users and groups specified in the ldap
server,
which
is referenced in the customized Realm?

Admin Console Integration for Users in a Custom Realm

We are implementing a custom realm and are having troubles getting our Users to
show up in the User list.
Our user class extends weblogic.security.acl.User, and is forced to use the default
CTOR because our data access layer requires it.
Unfortunately, getName() returns null if the User(String) constructor is not used.
Furthermore, Identity::setName() is final, so it seems as though there is no
way to set the user's name after construction.
I am correct in this?
If so, any thoughts on whether it is worth going down the path of making my user
class implement Principal instead of extending weblogic.security.acl.User? I
would be forced to try to guess at what methods in User are required to integrate
with the admin console, I believe. I have not been able to find any documentation
that specifies what api/contract the console uses when it attempts to display
user, role, acl information for a custom realm.
Any advice would be greatly appreciated.
-chris

My comments mixed with your text
"Chris Goodacre" <[email protected]> wrote:
>
We are implementing a custom realm and are having troubles getting our
Users to
show up in the User list.
Our user class extends weblogic.security.acl.User, and is forced to use
the default
CTOR because our data access layer requires it.
Unfortunately, getName() returns null if the User(String) constructor
is not used.Yes.
Furthermore, Identity::setName() is final, so it seems as though there
is no
way to set the user's name after construction.
I am correct in this?Yes. Changing a user's name on a constructed user object is like mutating that
user to another user - a security hole. It isn't allowed.
>
If so, any thoughts on whether it is worth going down the path of making
my user
class implement Principal instead of extending weblogic.security.acl.User?I'd try to stay with extending weblogic.security.acl.User, but also implement
weblogic.security.acl.CredentialChanger, so you can change passwords through the
console (otherwise you get NullPointerExceptions).
You really want to get around not being able to supply a user name as part of
the ctor.
I
would be forced to try to guess at what methods in User are required
to integrate
with the admin console, I believe. I have not been able to find any
documentation
that specifies what api/contract the console uses when it attempts to
display
user, role, acl information for a custom realm.
Any advice would be greatly appreciated.
-chris1. Your realm should extend AbstractManageableRealm and implement DebuggableRealm
if you want to integrate with the console.
2. The only contract is to implement all the methods!
3. Check the type of the user and group objects being passed to your realm - if
they're not your user and group type, reject the call.
4. The documentation is indeed terrible, and often wrong. The examples shipped
are incomplete (the RBDMS realm shipped has approx 1/3 of the functionality).
You'll get good with jad.
Should all be better in 7.0 with JAAS. The realm interfaces is a dog.
Good luck,
simon.

Index page not showing in the Admin Console

Hello I have downloaded the J2EE package. It was working fine for a couple of months. Recently though, I had a problem in the admin console. After I login successfully, not all the framesets of the admin page is displaying. The top frameset and the left frameset display perfectly. However the index frameset displayed exception messages. I tried reinstalling my J2SE and J2EE and still, the exception shows up. The following is the stacktrace of the errors displayed:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: java.lang.RuntimeException: java.lang.IllegalArgumentException: http
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:286)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
root cause
com.sun.enterprise.tools.guiframework.exception.FrameworkError: java.lang.RuntimeException: java.lang.IllegalArgumentException: http
     com.sun.enterprise.tools.guiframework.view.descriptors.ViewDescriptor.registerChildren(ViewDescriptor.java:198)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.registerViewDescriptorChildren(DescriptorViewHelper.java:66)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.registerViewDescriptorChildren(DescriptorViewBeanBase.java:112)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.(DescriptorViewBeanBase.java:59)
     com.sun.enterprise.tools.guiframework.view.CCNodeEventHandlerViewBeanBase.(CCNodeEventHandlerViewBeanBase.java:26)
     com.sun.enterprise.tools.guiframework.view.descriptors.CCNodeEventHandlerViewBeanBaseDescriptor.getInstance(CCNodeEventHandlerViewBeanBaseDescriptor.java:37)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewManager.getView(DescriptorViewManager.java:190)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewManager.getView(DescriptorViewManager.java:150)
     com.sun.enterprise.tools.guiframework.view.DescriptorViewManager.getViewBean(DescriptorViewManager.java:58)
     com.sun.enterprise.tools.guiframework.view.BaseServlet.handleException(BaseServlet.java:268)
     com.sun.enterprise.tools.guiframework.view.BaseServlet.processRequest(BaseServlet.java:191)
     com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:465)
     com.sun.enterprise.tools.admingui.AdminGUIServlet.doGet(AdminGUIServlet.java:58)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:748)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
note The full stack trace of the root cause is available in the Sun-Java-System/Application-Server-PE-8.0 logs.
Sun-Java-System/Application-Server-PE-8.0

Sure thing Lance, here it is:

Historical Reports Link Missing in Admin Console Menu

Hi,
We have a weird situation in a new installation. In Admin Console Menu Historical Reports Link does not appear. I have checked WIN table, it seems ok, there is a row for Historical Report, also all records about historical reports inside xlWebAdmin.properties and xlDefaultAdmin.properties files are there.
Any ideas why this link happens to be missing?

Hi,
I'd bid that the audit module is not installed then. At least in UPA_USR you'd see the row that belongs to the XELSYSADM user. I don't know if you can manually enable it someway.
If you have any free dev machine (or in a VM), I'd advice you to make a fresh install of OIM without the audit module, and see if the resulting system seems to your actual one. Installing in a XP environment under JBOSS won't take you more than 30 minutes.
Regards,

Admin console for connector doesn't work

          I deployed the sample connector "BlackBoxNoTx.rar" under
          wlserver6.1_beta\samples\examples\jconnector\simple.
          There's no error. but in admin console for deployments/connector,
          I can not see any configuration info(such as JNDI name)under monitoring. It always
          display blank.
          Is it a known bug?
          thanks


Hi
The language problem is a mystery. Maybe that's why your password doesn't work anymore - just a thought.
However Reset Password is found in the menu bar on the Installer application.
Then you may have a chance to select the hard drive, and then your user name.
regards roam

Weblogic 8.1 SP4 Admin Console JDBC or Start-up changes not taking effect?!

Similar Messages

Maybe you are looking for