Authentication errors upon starting WLS 8.1 Admin server...

Please excuse my ignorance as I am far from a WL Admin. I have been working on a problem that has been preventing my admin server from starting for the past couple of days now and haven't a clue as to what could be causing it. The admin server fails to start and when I check the error logs this is all that I see:<br>
<b><i>The WebLogic Server did not start up properly.
Reason: weblogic.security.SecurityInitializationException: Authentication for user system denied</i></b><br>
Frustrating because it does not say what the problem is and when I spoke with the actual WL admin that set it up he did not seem to know either. He doesn't have a lot of time to spend looking into the problem right now because he is in the middle of another project and this is not a production issue because it is on a development server but it's where I have to do my testing so I have to get it back up. I did not configure it but do have complete access to whatever files I need to change I just don't know what I am supposed to do. He tells me that I need to do some research on the problem so here I am. If anyone has any suggestions on what I can do to even begin fixing the problem it would be much appreciated.<br>Thanks,<br>
Jon

It does tell you why the server won't start:
"Authentication for user system denied"
Thus, your boot identity (which is "system") can't be authenticated for some reason. It could be a bad password, improper configuration such that it can't find that user, or a missing user account.
The other post talks about these things.
An easy test for eliminating improper configuration is to copy config.xml to a safe place and then copy (or simply rename) config.xml.booted to config.xml. Then try to start the server.
If it still won't start you have one of the other two problems. Likewise, if it does start, you have a configuration problem.
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Similar Messages

Error in Starting WebServer (Ver 7) Admin Server

Hi,
I am getting the error shown below when starting the Webserver 7 admin
server. The Web server starts and I can administer the server but when deploying Access Manager getting agan the same java.lang.NoClassDefFoundError and can't AM complete configuration.
Please help me. After attending Access Manager 7.1 training
wanted to practice on this env.
My Env is:
uname -a:
SunOS sun1 5.10 Generic_120012-14 i86pc i386 i86pc
/etc/release:
Solaris 10 8/07 s10x_u4wos_12b X86
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
cat release_info :
Product=Java Enterprise System 5U1
Date=Mon Aug 20 18:05:55 PDT 2007
Build=08b
PatchLevel=000
[25/Dec/2007:19:06:54] info ( 8308): CORE1116: Sun Java System Web
Server 7.0U1 B07/18/2007 14:21
[25/Dec/2007:19:06:55] info ( 8309): CORE5076: Using [Java HotSpot(TM)
Server VM, Version 1.5.0_12] from [Sun Microsystems Inc.]
[25/Dec/2007:19:06:59] info ( 8309): WEB0100: Loading web module in
virtual server [admin-server] at [admingui]
[25/Dec/2007:19:07:00] info ( 8309): WEB0100: Loading web module in
virtual server [admin-server] at [jmxconnector]
[25/Dec/2007:19:07:06] info ( 8309): PWC1412: WebModule[jmxconnector]
ServletContext.log():PWC1409: Marking servlet remotejmx as unavailable
[25/Dec/2007:19:07:06] failure ( 8309): WebModule[jmxconnector]PWC1396:
Servlet /jmxconnector threw load() exception
java.lang.NoClassDefFoundError: javax/management/remote/message/Message
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at java.lang.Class.newInstance0(Class.java:321)
at java.lang.Class.newInstance(Class.java:303)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1119)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:994)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4731)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5123)
at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:182)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70)
at
com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:472)
at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304)
[25/Dec/2007:19:07:06] info ( 8309): HTTP3072: admin-ssl-port:
https://sun1.mysite.com:8989 ready to accept requests
[25/Dec/2007:19:07:06] info ( 8309): HTTP3072: admin-http-port:
http://sun1.mysite.com:8800 ready to accept requests
[25/Dec/2007:19:07:06] info ( 8309): CORE3274: successful server startup

jmxremote_optional.jar has
javax/management/remote/message/Message.class
<server-class-path> in admin-server/config/server.xml contains path to this jar file. You may want to check if this jar file exists and has correct permissions.

Can't start wls 8.1 admin server

Hi there,
after a disk full exception i'm not able to restart admin server.
no warning and no exception on stdout or log file and admin server still frozen.
Any suggestion??
<b>-- stdout start -------------------------------</b>
<pre>bash-2.05$ ./startVgnAdminServer.sh
CLASSPATH=/app/vignette/runtime_services/8.1/install/server/lib/vgnclasspath.jar:/app/vignette/runtime_services/8.1/install/server/lib/vgnclasspath.jar:/app/vignette/java/lib/tools.jar:/app/vignette/runtime_services/8.1/install/server/lib/weblogic_sp.jar:/app/vignette/runtime_services/8.1/install/server/lib/weblogic.jar:/app/vignette/runtime_services/8.1/install/server/lib/ojdbc14.jar::/app/vignette/runtime_services/8.1/install/common/eval/pointbase/lib/pbserver44.jar:/app/vignette/runtime_services/8.1/install/common/eval/pointbase/lib/pbclient44.jar:/app/vignette/java/jre/lib/rt.jar:/app/vignette/runtime_services/8.1/install/server/lib/webservices.jar:
PATH=/app/vignette/runtime_services/8.1/install/server/bin:/app/vignette/java/jre/bin:/app/vignette/java/bin:/usr/bin:/bin:/usr/sbin:/sbin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<May 18, 2005 5:51:13 PM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1_05-b01 from Sun Microsystems Inc.>
<May 18, 2005 5:51:14 PM CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<May 18, 2005 5:51:14 PM CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR174792 03/23/2004 11:43:38
WebLogic Temporary Patch for CR173632 03/26/2004 13:38:16
WebLogic Temporary Patch for CR135189 02/04/2004 12:16:56
WebLogic Temporary Patch for CR134122 02/10/2004 02:58:30
WebLogic Temporary Patch for CR133071 01/14/2004 12:59:22
WebLogic Temporary Patch for CR132575 01/05/2004 13:00:03
WebLogic Temporary Patch for CR129505 12/03/2003 17:43:35
WebLogic Temporary Patch for CR129371 02/11/2004 14:19:37
WebLogic Temporary Patch for CR129122 11/25/2003 23:16:25
WebLogic Temporary Patch for CR128888 01/30/2004 13:04:13
WebLogic Temporary Patch for CR124746 01/09/2004 15:44:26
WebLogic Temporary Patch for CR124239 11/25/2003 23:48:06
WebLogic Temporary Patch for CR107373 04/15/2004 11:43:39
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<May 18, 2005 5:51:14 PM CEST> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at /app/vignette/runtime_services/8.1/domains/vgndomain/./config.xml.>
<May 18, 2005 5:51:19 PM CEST> <Notice> <Log Management> <BEA-170019> <The server log file /app/vignette/runtime_services/8.1/domains/vgndomain/VgnAdminServer/VgnAdminServer.log is opened. All server side log events will be written to this file.></pre>
<b>-- stdout end -------------------------
-- VgnAdminServer.log start -------------------------</b>
<pre>####<May 18, 2005 5:51:19 PM CEST> <Notice> <Log Management> <as501wfm> <VgnAdminServer> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /app/vignette/runtime_services/8.1/domains/vgndomain/VgnAdminServer/VgnAdminServer.log is opened. All server side log events will be written to this file.></pre>
<b>-- VgnAdminServer.log end -------------------------</b>
Thanks in advance, Stefano.

hi,
as I wrote in previous message, VgnAdminServer.log is empty:
<pre>-- VgnAdminServer.log start -------------------------
<pre>####<May 18, 2005 5:51:19 PM CEST> <Notice> <Log Management> <as501wfm> <VgnAdminServer> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /app/vignette/runtime_services/8.1/domains/vgndomain/VgnAdminServer/VgnAdminServer.log is opened. All server side log events will be written to this file.></pre>
-- VgnAdminServer.log end -------------------------</pre>

Error while starting WLS server

Hi,
Am getting the below error
starting weblogic with Java version:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=myserver -Dja
<Jun 14, 2012 5:26:19 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Jun 14, 2012 5:26:19 PM IST> <Critical> <WebLogicServer> <BEA-000362>
<Server f ailed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already exists>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Jun 14, 2012 5:26:19 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>
This is very urgent and I need help to solve this.
Please reply back soon

this is the config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>mydomain</name>
<domain-version>10.3.6.0</domain-version>
<security-configuration>
<name>mydomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}DO7UStBZljQz8xV6biUOFJqdK5gsj1D1riTUGbO7Il4FWYqlhurBQqPIDqAINVjswiUuNnqW6Fgh0Q5w4DUkQRmdVVHObsY/RXP7geTmt3Ps3eW3s/ucrlxdMYGzv8Y/</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}+mvIGJfWsqWkZekqkwYV6gc9tsY7DPmRWa/avipt80U=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>myserver</name>
<listen-address></listen-address>
</server>
<embedded-ldap>
<name>mydomain</name>
<credential-encrypted>{AES}yVDi5dwjQzQyCxCHXqjB4h3brKgkcLEgHP/3nu0yf81UC/t27TfkQuFjKl8cxm7r</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.6.0</configuration-version>
<app-deployment>
<name>demantra_new2</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_new2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>demantra_JUNE14</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_JUNE14.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<library>
<name>api</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\server\lib\api.jar</source-path>
<deployment-principal-name>api</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>javax.servlet.jsp.jstl#[email protected]</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\Tomcat\lib\jstl-1.2.jar</source-path>
<deployment-principal-name>jstl</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>jstl#[email protected]</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\common\deployable-libraries\jstl-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</library>
<admin-server-name>myserver</admin-server-name>
<jdbc-system-resource>
<name>JDBC Data Source-0</name>
<target>myserver</target>
<descriptor-file-name>jdbc/JDBC_Data_Source-0-3407-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
Edited by: Manikanda Prabhu on Jun 14, 2012 5:03 AM

Authentication Error while starting managed server ...

          Hi everyone,
          is there anyone to help me in avoiding the SecurityException while starting managed
          server in a cluster. Weblogic version is 6.1.
          I have started the admin server in a cluster and is running fine. Also cluster
          is started successfully.
          When I start managed server appManaged (which is also included in the cluster),
          I get the following error:
          Starting WebLogic Server ....
          Connecting to http://appadmn:7001...
          <Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
          ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
          javax.naming.AuthenticationException. Root exception is java.lang.SecurityExcep
          tion: attempting to add an object which is not an instance of java.security.Prin
          cipal to a Subject's Principal Set
          at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
          at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(Boot
          ServicesStub.java:72)
          at weblogic.common.internal.BootServicesStub.authenticate(BootServicesSt
          ub.java:80)
          at weblogic.security.acl.internal.Security.authenticate(Security.java:10
          8)
          at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
          xtFactoryDelegate.java:461)
          at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
          textFactoryDelegate.java:316)
          at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
          tialContextFactoryDelegate.java:288)
          at weblogic.jndi.Environment.getContext(Environment.java:155)
          at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
          at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
          The start script for managed server appManaged is :
          %JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
          -Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
          -Dweblogic.management.username=system -Dweblogic.management.password=weblogic
          -Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
          BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
          -Dweblogic.management.discover=false weblogic.Server
          thanks.


I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else?

Help Please !!! Authentication error while starting managed server

Hi everyone,
is there anyone to help me in avoiding the SecurityException while starting managed
server in a cluster. Weblogic version is 6.1.
I have started the admin server in a cluster and is running fine. Also cluster
is started successfully.
When I start managed server appManaged (which is also included in the cluster),
I get the following error:
Starting WebLogic Server ....
Connecting to http://appadmn:7001...
<Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
javax.naming.AuthenticationException. Root exception is java.lang.SecurityExcep
tion: attempting to add an object which is not an instance of java.security.Prin
cipal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(Boot
ServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesSt
ub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:10
8)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:461)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:288)
at weblogic.jndi.Environment.getContext(Environment.java:155)
at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
The start script for managed server appManaged is :
%JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
-Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
-Dweblogic.management.username=system -Dweblogic.management.password=weblogic
-Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
-Dweblogic.management.discover=false weblogic.Server
thanks.

I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else?

Error upon starting Weblogic server : Exception thrown while loading uddi

Hi,
I am getting $Proxy41.getDefaultWebApp(Unknown Source) error while starting the weblogic. Any one has clue? Below is the stack from myserv.log file.
Environment:
OS : Windows 2000 server
WLS: Weblogic 7.0SP2
Oracle client : Oracle 9i RC2
IIS : IIS 5.0
<Exception thrown while loading uddi: java.lang.ClassCastException: weblogic.management.configuration.ApplicationManagerMBean_CachingStub>
java.lang.ClassCastException: weblogic.management.configuration.ApplicationManagerMBean_CachingStub
     at $Proxy41.getDefaultWebApp(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.getDefaultWebApp(WebServerMBean_CachingStub.java:226)
     at weblogic.servlet.internal.WebAppServletContext.initFromMBean(WebAppServletContext.java:1312)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:1054)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:1009)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:502)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:371)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:1598)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:735)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
####<Dec 14, 2005 11:19:54 AM PST> <Error> <Deployer> <rsecav-webenam> <myserver> <main> <kernel identity> <> <149205> <The Slave Deployer failed to initialize the application uddi due to error weblogic.management.ApplicationException: Prepare failed. Task Id = null
Module Name: uddi, Error: Could not load uddi: java.lang.ClassCastException: weblogic.management.configuration.ApplicationManagerMBean_CachingStub
}.>
weblogic.management.ApplicationException: Prepare failed. Task Id = null
Module Name: uddi, Error: Could not load uddi: java.lang.ClassCastException: weblogic.management.configuration.ApplicationManagerMBean_CachingStub
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
Thanks in advance,
Manu

Hi Manu,
can I know how you over come this problem? I am using Weblogic 7 with Service Pack 4. I will be thankful to u if you can mail ur response to me on my mail [email protected]
Thanks and Regards,
Suresh Vemulapalli

Error: distiller error upon start-up

I am running the CC suite on a PC-Windows 7, 64bit and get error upon error which are slowing down and crashing my system: Here is the error I get upon start up of my computer:
Any guidance would be much appreciated.

Try removing the SC Info folder as per the instructions in the Remove the SC Info folder section of the following troubleshooting document:
iTunes repeatedly prompts to authorize computer to play iTunes Store purchases

Itunes X error upon start up, "ituneshelper had crash unexectedly"

Hi guys, need some advice here. After installing itunes X, i keep getting this error upon startup of my macbook, "ituneshelper had crash unexpectly"
I went to completely remove my itunes x and reinstall it again. The problems come back.
Here is the report i got
Process: iTunesHelper [206]
Path: /Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/MacOS/iTu nesHelper
Identifier: iTunesHelper
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Interval Since Last Report: 7318 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 9
Date/Time: 2010-09-10 16:24:29.092 +0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A6BF8E3C-498F-4D5A-A128-8A9E9755D75B
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022

I've been searching for day s with no resolve on this so I did the only thing left to do... Clean everything out.It's the first time in 3 years, but I backed everything up and did a clean install of OSX. All is good.

Error in starting the domain in application server 8.2

I want to deploy a application EAR on newly created domain. For this :
1. Got the 8.2 Java application server installed on solaris box.
2. Created domain using the asadmin command -> create-domain --adminport 4848 --adminuser admin <DOMAIN_NAME>
On starting the domain with this command - sh asadmin start-domain --user admin <DOMAIN_NAME. I am facing the below issue. Please note this is a fresh installation of the app server and a new domain
To troubleshoot this, I have already followed below steps , without any resolution:
1. Checked port with - netstat -an|grep 45184 and also checked the processes using ps -fu <unix_user>. Even after killing the process, same error.
2. Gave full permissions on /AppServer8.2/imq/var/instances
3. Logged in as root user and then tried to start domain
4. Updated domain.xml with some other port , checked this port if it is free , then replaced in domain.xml
5. No logs generated in /AppServer8.2/imq/var/instances
Please help me in resolving this issue. I have downloaded the 9.1 application server and will install and check in the meantime
[#|2013-07-29T14:14:34.067+0530|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
/usr/j2se/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/PostCUG_Track1/AppServer8.2/domains/MPCBebk/logs/server.log
-Djava.endorsed.dirs=/PostCUG_Track1/AppServer8.2/lib/endorsed
-Djava.security.policy=/PostCUG_Track1/AppServer8.2/domains/MPCBebk/config/server.policy
-Djava.security.auth.login.config=/PostCUG_Track1/AppServer8.2/domains/MPCBebk/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/PostCUG_Track1/AppServer8.2/domains/MPCBebk/config/keystore.jks
-Djavax.net.ssl.trustStore=/PostCUG_Track1/AppServer8.2/domains/MPCBebk/config/cacerts.jks
-Djava.ext.dirs=/usr/j2se/jre/lib/ext:/PostCUG_Track1/AppServer8.2/domains/MPCBebk/lib/ext:/PostCUG_Track1/AppServer8.2/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=MPCBebk
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/PostCUG_Track1/AppServer8.2/domains/MPCBebk
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=MPCBebk
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/PostCUG_Track1/AppServer8.2/config
-Djava.library.path=/usr/j2se/jre/lib/sparc/client:/usr/j2se/jre/lib/sparc/client:/usr/j2se/jre/lib/sparc:/usr/j2se/jre/../lib/sparc:/PostCUG_Track1/AppServer8.2/lib:/usr/lib/lwp:/PostCUG_Track1/AppServer8.2/lib:/usr/lib/lwp:/usr/j2se/jre/lib/sparc/client:/usr/j2se/jre/lib/sparc:/usr/j2se/jre/../lib/sparc:/PostCUG_Track1/AppServer8.2/lib:/PostCUG_Track1/AppServer8.2/lib:/PostCUG_Track1/AppServer8.2/lib:/opt/CA/SharedComponents/lib:/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/PostCUG_Track1/AppServer8.2/lib/appserv-rt.jar:/usr/j2se/lib/tools.jar:/PostCUG_Track1/AppServer8.2/lib/j2ee.jar:/PostCUG_Track1/AppServer8.2/lib/activation.jar:/PostCUG_Track1/AppServer8.2/lib/mail.jar:/PostCUG_Track1/AppServer8.2/lib/appserv-cmp.jar:/PostCUG_Track1/AppServer8.2/lib/admin-cli.jar:/PostCUG_Track1/AppServer8.2/lib/appserv-admin.jar:/PostCUG_Track1/AppServer8.2/lib/appserv-jstl.jar:/PostCUG_Track1/AppServer8.2/lib/commons-launcher.jar:/PostCUG_Track1/AppServer8.2/lib/commons-logging.jar:/PostCUG_Track1/AppServer8.2/lib/j2ee-svc.jar:/PostCUG_Track1/AppServer8.2/lib/jaxr-api.jar:/PostCUG_Track1/AppServer8.2/lib/jaxr-impl.jar:/PostCUG_Track1/AppServer8.2/lib/jaxrpc-api.jar:/PostCUG_Track1/AppServer8.2/lib/jaxrpc-impl.jar:/PostCUG_Track1/AppServer8.2/lib/dom.jar:/PostCUG_Track1/AppServer8.2/lib/relaxngDatatype.jar:/PostCUG_Track1/AppServer8.2/lib/jax-qname.jar:/PostCUG_Track1/AppServer8.2/lib/saaj-api.jar:/PostCUG_Track1/AppServer8.2/lib/saaj-impl.jar:/PostCUG_Track1/AppServer8.2/lib/xsdlib.jar:/PostCUG_Track1/AppServer8.2/lib/jmxremote.jar:/PostCUG_Track1/AppServer8.2/lib/jmxremote_optional.jar:/PostCUG_Track1/AppServer8.2/lib/jsf-api.jar:/PostCUG_Track1/AppServer8.2/lib/jsf-impl.jar:/PostCUG_Track1/AppServer8.2/lib/rmissl.jar:/PostCUG_Track1/AppServer8.2/lib/xalan.jar:/PostCUG_Track1/AppServer8.2/lib/xercesImpl.jar:/PostCUG_Track1/AppServer8.2/lib/appserv-upgrade.jar:/PostCUG_Track1/AppServer8.2/lib/appserv-ext.jar:/PostCUG_Track1/AppServer8.2/lib/install/applications/jmsra/imqjmsra.jar:/PostCUG_Track1/AppServer8.2/imq/lib/jaxm-api.jar:/PostCUG_Track1/AppServer8.2/imq/lib/fscontext.jar:/PostCUG_Track1/AppServer8.2/lib/ant/lib/ant.jar
com.sun.enterprise.server.PEMain
start
display|#]
[#|2013-07-29T14:15:35.774+0530|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2013-07-29T14:15:35.776+0530|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory /PostCUG_Track1/AppServer8.2/imq/var/instances|#]
[#|2013-07-29T14:15:35.776+0530|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2013-07-29T14:15:35.777+0530|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:45184]. - cause: java.io.IOException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:45184]. - cause: java.io.IOException
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:191)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:116)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:291)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:113)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:98)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1949)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:745)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:315)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
... 3 more
Caused by: java.io.IOException
at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:118)
at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:81)
at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:73)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sun.messaging.jmq.io.PortMapperTable.readLine(PortMapperTable.java:277)
at com.sun.messaging.jmq.io.PortMapperTable.read(PortMapperTable.java:233)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:185)
... 21 more
Caused by: java.io.IOException: Invalid argument
at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method)
at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:136)
at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:70)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:59)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:70)
at com.sun.enterprise.server.ss.ASSelector.select(ASSelector.java:92)
at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:101)
... 28 more
|#]
[#|2013-07-29T14:15:35.798+0530|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:45184]. - cause: java.io.IOException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:376)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:178)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:172)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]

Hi,
Try to manually download the file from application server using standard transactions, and than check how many records are you able to download from app. server.
I guess there might be something wrong with the format of 583rd record, which makes sap assume that the file has come to an end.
Hope this will help you.
Regards,
Vinit...

Starting Managed Servers without admin Server

dear All
i have a Weblogic Server contains the following
Admin Server
LoadBalancer Server
Cluster Contains Server1 & Server2
and every thing is fine, but i have the following problem : while starting any Node from Cluster or LoadBalancer Server using startManagedWebLogic.cmd without starting up admin server, i am getting the following error in my log
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: weblogic.security.service.SecurityServiceRuntimeException: Invalid host or port for admin server..     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getIdStoreConfig(LdapIdentityStoreProvider.java:195)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.access$300(LdapIdentityStoreProvider.java:70)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:242)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:114)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:70)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:798)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:792)
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:283)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1020)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:879)
     at weblogic.security.SecurityService.start(SecurityService.java:142)
     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)

Isn't this exactly what the admin service is used for?
I think you need to start the admin server before starting the other servers.
Timo

Starting weblogic cluster and admin server on Win 2000 platform

Hi! Here's my problem scenario:
I'm running my WLS 8.1 application as WLS cluster on Win 2000 platform. I have
3 replicated WLS servers in my cluster and of course one WLS server as admin server
(4 WLS servers all together). I'm starting my WLS application using Win services
which behind a scene call win 2000 comand interpreter batch-file to start the
servers. Currently I have 4 different win 2000 services each calling different
batch-files to start a WLS server (4 all together). Here's my question:
Is there any way to start my cluster (3 managed WLS servers) and WLS admin server
from single win 2000 command file (using single win 2000 service). Using win 2000
AT-command interpreter command I can start executables and command(s) and command-files
at background at specific date and time, but I want to start my WLS application
on every win 2000 platform boot, is there any way to achieve this ???
Best Regards!
Jami

hi,
Thanks for stepping up!
But I wasn't using any clustering or loadbalancing.
Just a simple Admin server, Managed server set up.
256 Meg, Pentium box running Win 2000 premium edition.
I tried tweeking around the heap size too.... coz' the operations were slogging
like anything...
Bal
"Raja Mukherjee" <[email protected]> wrote:
It seems like network issue....do you have Windows Clustering/Load Balancing
service turned on by any chance? I would also use netmon to see the traffic
between the ips....
..raja
"Bala" <[email protected]> wrote in message
news:3b3a6c00$[email protected]..
hi,
I am looking at a strange behaviour with WLS6.0SP1 installed on WINDOWS2000 Premium.
I brought up the Admin server and a Managed server. After a while theAdmin Server
is compeletely
losing the control of the managed server (for no reason).
when I tried monitoring the managed server from the console, I couldnot
access
the manager server
and the status down (red ball). I tried restarting the Admin Server
in the discover mode - NO LUCK.
But when I restart the Managed server and go to the Web Based Admin
Console and refresh, it worked. But I dont think we should be doingthat
in a
production environment.
Did anybody come across such a problem before ???
Is this a problem with Win 2000 ???
coz' it never happened with NT workstation
thanks in advance

Programmatically start/stop applications without admin server connection

I know I can programmatically start/stop an application through WebLogic's deployment API, but the call needs to go through admin server. I was wondering if there's a way for an application to start/stop another application on the same managed server when the admin server is down. I remember a managed server could be started without an admin server (unless it's started for the first time). So I suppose there must be some way to programmatically start/stop local applications without an admin server as well.
Thank you for your help in advance.

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Taking long time to start when weblogic 11g admin server

Hi
When I ran following command in linux 64-bit environmnt to start weblogic 11g admin server, it is taking such a long time (some time it is taking one and half hour, some time it is taking 24 hours and still showing work under process)
$HOME/Middleware/user_projects/domains/soa_domain/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic$123 > server.log &
Please help me out.
Linux OS 64-bit installaed
Weblogic 11g server (64-bit) installed
SOA SUIT 11g (64-bit) Installed
SYStem COnfiguration:
RAM 4 GB
HDD 160 GB (Single Partition)
Core 2 duo Processor
Thanks
Phani

How much memory have you configured for the servers?
When the memory (Xmx and Xms - JVM parameters) is too small start-up times can get long.
I saw that you have SOA environment. To tune your environment this link might help: http://middlewaremagic.com/weblogic/?p=6040

Problem while starting Managed Servers from Admin Server console

I am facing a problem while trying to start the managed servers in wlp8.1 portal from the admin server console.
<Dec 7, 2004 4:52:14 PM IST> <Info> <NodeManager@*.*:5555> <Starting Server orbitPortalDomain::orbit_ManagedServer1 ...>
<Dec 7, 2004 4:52:16 PM IST> <Info> <NodeManager@*.*:5555> <Server orbitPortalDomain::orbit_ManagedServer1 started, process id = 1,832>
<Dec 7, 2004 4:52:17 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.6.0.212:7001 to check if there exists a running admin server at this URL.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.6.0.212:7001 to retrieve the initial configuration.>
<Dec 7, 2004 4:52:21 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea_turner\weblogic81\common\nodemanager\orbit_ManagedServer1\orbit_ManagedServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>(WSRPIdentityAsserterProviderImpl.java:45)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:232)
at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:939)
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:257)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:698)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:731)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:874)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:717)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Reason: com/bea/wsrp/util/debug/Debug
pls advice
Thanks
Sasanka

Hello,
There is a lot of stuff on this thread:
http://forum.java.sun.com/thread.jspa?threadID=567363&messageID=2801617
these guys are trying to run weblogic with JBuilder.
Looks like your classpath is incorrect, can you go to your admin console-->server-->remote start
copy the classpath and post it here.
Check for spaces in your classpath, missing jars or directories and miss spelt paths.
Has this problem been occuring as soon as you installed WLP or not?
Cheers,
Hoos

Authentication errors upon starting WLS 8.1 Admin server...

Similar Messages

Maybe you are looking for