Issue in Weblogic Server - Server Stops abruptly
Hi All,
I am facing an issue with Weblogic server(8.1). One of the managed servers stops abruptly. Server run for some days. After 5 or 6 days it stops without giving any log message. Admin(mgt server) and this managed server are running in the same box(AIX Environment). Below is the only log I got. Any idea why it is happening?
According to the BEA Message it may be due to network problem. Since both the servers are running in same box, i don't think it is network issue.
Can anyone please help me on this? - thanks in advance
Log Trace Message:
==================
<AF[196]: Allocation Failure. need 528 bytes, 67173345 ms since last AF>
<AF[196]: managing allocation failure, action=1 (0/1040390840) (32611304/33283912)>
<GC(197): freeing class jsp_servlet._ofr._invoice._shipper._jsp.__exceptioninvoicelist(302453c8)>
<GC(197): freeing class jsp_servlet._lcom._common._jsp.__page_navigation(3024ecc8)>
<Dec 21, 2005 10:47:18 PM KST> <Warning> <Management> <BEA-141138> <Managed Server ofrserver is disconnected from the ad
min server. This may be either due to a managed server getting temporarily partitioned or the managed server process exi
ting.>
<GC(197): freeing class jsp_servlet._ofr._filter._jsp.__filterdetails(30252718)>
<GC(197): freeing class jsp_servlet._lcom._admin._jsp.__devtools(3040f898)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__devtoolslogin(3040f260)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__processdevtoolslogin(30411870)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__xmlcommmanagerimport(30413e58)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__processxmlcommmanagerimport(30414a88)>
<GC(197): unloaded and freed 8 classes>
<GC(197): GC cycle started Wed Dec 21 22:47:23 2005
<GC(197): freed 721499624 bytes, 70% free (754110928/1073674752), in 263157 ms>
<GC(197): mark: 248258 ms, sweep: 1857 ms, compact: 13042 ms>
<GC(197): refs: soft 0 (age >= 32), weak 0, final 27363, phantom 0>
<GC(197): moved 0 objects, 0 bytes, IC reason=14>
<GC(197): stop threads time: 1356, start threads time: 19>
<AF[196]: completed in 282883 ms>
Thanks,
Shanmuga perumal
[email protected]
I think you should be able to follow the same steps but whenever you come across Domain B in the instructions, just substitute the values for Domain A. Because it is the same domain you may not even have to go through some of the certificate steps. If you have questions I suggest you post them in the WLS Security forum.
WebLogic Server - Security
Similar Messages
-
Email alert if SQL Server Services stop abruptly
Hi,
I am a SQL Server DBA and I am currently working on setting up email alerts in case if SQL Server services stop abruptly.I have currently written a VB script which runs every 1 hr and checks if a SQL Server Service is running or not. This VB Script runs
with the help of Windows Task Scheduler.In case if a SQL Server service has stopped, this VB script immediately sends an email via. SMTP Server.
Please let me know if this is a good solution or is there any other better solution or is there any feature available in SQL/windows using which the same can be achieved.
Environment:
SQL 2008 R2
OS: Windows Server 2008
Thanks a lot in advance :)
Regards,
Tauhid S ShaikhHi Tauhid,
I do have same requirement, please could you share the code.
Regards
Siraj Ahmed -
Administrator Login & Issue with Weblogic Admin Server Console
I recently applied a PeopleTools patch to a test environment. I will be doing this to production soon, and as I was going through my screenshots of what I did in test, I ran across an area that may cause me an issue when I apply it to production.
There is a screen which prompts you for the administrator login and password for the weblogic domain. I wasn't sure of this when I did it in test, but in the PeopleTools install doc, it said the default is system/Passw0rd
This worked fine in test. However, the person who set this up in production may have used a different password. I don't want to get halfway through the patch and have to abort because I don't know the password.
I did some research and read there was a file with this info. I think it was boot.properties, but it was encrypted.
I then started the Weblogic Admin Server Console in test and was able to login with system/Passsw0rd so that verified a way of confirming the password in test.
I tried to do the same in production, but the Weblogic Admin Server Console page does not come up. The webserver is running, and if it wasn't, my phone would be ringing. Why does the console not come up?
However, the screen that comes up during the patch that prompts you for this asks you to enter your password, and re-enter it on the next line, so maybe its setting the password, not verifying that you know it. Is this true, I could make it whatever I want?
The WebLogicAdmin_weblogic.log file has not been updated in months. This may have been when we did the last upgrade.
Can you tell me how to determine/verify this password?
Thanks,
RogerI'm not sure if there's an easy way to verify this. If I'm not mistaken you'll have batch file called startweblogicadmin.bat in the bin directory. You have to start this to get the administrator console running. It will be running on port :9999 by default if you haven't changed this.
-
JNDI lookup issue in weblogic 10 server
Hi all,
I have a serious problem in getting the datasource lookup. My application uses EJB3 and JPA and it is deployed in weblogic10. I configured datasource in the domain (ex:mydomain) using weblogic 10 admin console. Now when i try to call from a client program, it is giving me javax.naming.NameNotFoundException. I use eclipse IDE to deploy the application. From the IDE, i can start the oracle 10.3 server and it automatically deploys the application into the server in mydomain. The admin console shows that the application deployed fine. And i can see the webcontent WAR file and EJB jar deployed. Coming back to the issue.... I verified user_projects\domains\mydomain\config\jdbc\datasource-jdbc.xml and user_projects\domains\mydomain\config\config.xml file enteries. My entries are present in those files.
When i start the server i am getting below error...
<< Stacktrace >>
javax.naming.NameNotFoundException: While trying to look up jdbc in /app.; remaining name 'jdbc'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at weblogic.deployment.PersistenceUnitInfoImpl.lookUpAppScopedDataSource(PersistenceUnitInfoImpl.java:529)
at weblogic.deployment.PersistenceUnitInfoImpl.reconfig(PersistenceUnitInfoImpl.java:549)
at weblogic.ejb.container.deployer.EJBModule.reconfigPersistenceUnits(EJBModule.java:529)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:515)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
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)
<< Client program snippet >>
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://10.237.76.132:7001");
InitialContext ctx = null;
ctx = new InitialContext(ht);
Object obj = (Object)ctx.lookup(EmployeeBean.RemoteJNDIName);
EmployeeRemote empRemote = (EmployeeRemote)PortableRemoteObject.narrow(obj,com.acs.test.emp.EmployeeRemote.class);
List empList = empRemote.getEmployeeDetails(1);
System.out.println("SUCCESS"+empList.size());
<< Persistence.xml >>
<?xml version="1.0" encoding="UTF-8"?>
<!-- Persistence deployment descriptor for dev profile -->
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0">
<persistence-unit name="cmsepool">
<jta-data-source>java:/mydatasource</jta-data-source>
<class>com.acs.test.emp.EmployeeVO</class>
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>Make sure that this Datasource you created is Targetted to Admin Server and full Cluster (incase of cluster domain). From Admin Console, select your datasource and check for the Targets tab. Since its JNDI lookup error, most probably it may not be deployed properly.
HTH
Ravi Jegga -
Performance Issues in weblogic managed server
Hi,
We are facing performance issues in our managed servers in weblogic domain and in logs it is showing this error continuously.
<Oct 2, 2013 10:39:27 AM MST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '47' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "700" seconds working on the request "Workmanager: OIMMDBWorkManager, Version: 0, Scheduled=false, Started=true, Started time: 700360 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-294 "[STUCK] ExecuteThread: '47' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {
-- Blocked trying to get lock: java.io.PrintStream@41a53700[not locked]
java.io.PrintStream.println(PrintStream.java:755)
com.wyndham.operations.user.eventHandlers.PostCreateOperationsEventHandler.execute(PostCreateOperationsEventHandler.java:60)
oracle.iam.platform.kernel.impl.OrchProcessData.runPostProcessEvents(OrchProcessData.java:1225)
oracle.iam.platform.kernel.impl.OrchProcessData.runEvents(OrchProcessData.java:665)
oracle.iam.platform.kernel.impl.OrchProcessData.executeEvents(OrchProcessData.java:268)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeProcess(OrchestrationEngineImpl.java:810)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.notifyParentProcess(OrchestrationEngineImpl.java:971)
oracle.iam.platform.kernel.impl.OrchProcessData.runEvents(OrchProcessData.java:665)
oracle.iam.platform.kernel.impl.OrchProcessData.executeEvents(OrchProcessData.java:268)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeProcess(OrchestrationEngineImpl.java:810)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeChildProcess(OrchestrationEngineImpl.java:880)
oracle.iam.platform.kernel.impl.OrchProcessData.handleAdditionalChanges(OrchProcessData.java:552)
oracle.iam.platform.kernel.impl.OrchProcessData.runEvents(OrchProcessData.java:665)
oracle.iam.platform.kernel.impl.OrchProcessData.executeEvents(OrchProcessData.java:268)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeProcess(OrchestrationEngineImpl.java:815)
oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeProcess(OrchestrationEngineImpl.java:843)
oracle.iam.platform.kernel.impl.OrhestrationAsyncTask.execute(OrhestrationAsyncTask.java:97)
oracle.iam.platform.async.impl.TaskExecutor.executeUnmanagedTask(TaskExecutor.java:99)
oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:52)
oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:60)
sun.reflect.GeneratedMethodAccessor1493.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:575)
com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:86)
com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:102)
com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:151)
$Proxy460.onMessage(Unknown Source)
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:518)
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:467)
weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4638)
weblogic.jms.client.JMSSession.execute(JMSSession.java:4134)
weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3820)
weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
We have performed workload manager tuning in weblogic console as below.
The property ‘Maximum Threads Constraint’ of work managers OIMMDBWorkManager = 80 and OIMUIWorkManager = 20
Please suggest the solution.Hi,
If you look more closely at the STUCK Thread stack trace, you will notice that the thread is attempting to acquire a LOCK on the following Object monitor: java.io.PrintStream@41a53700. The native thread state is also in a BLOCKED state.
My primary recommendation is to generate a full JVM Thread Dump (next re-occurence) so we can identify the potential culprit Thread holding such lock. One more thing, please see if you have multiple snapshots of this thread 294?
I also recommend to review the following source code:
com.wyndham.operations.user.eventHandlers.PostCreateOperationsEventHandler.execute(PostCreateOperationsEventHandler.java:60)
Sharing the same Stream object in this case would trigger thread lock contention given java.io.PrintStream has built-in synchronization ex:
public void println(String x) {
synchronized (this) {
print(x);
newLine();
Regards,
P-H
http://javaeesupportpatterns.blogspot.com -
Weblogic Portal Server interrupted abruptly error
hi,
i have an issue with weblogic portal server 9.2,
At times my workshops get hang and i have to kill the weblogic portal server instance,
the next time i start the workshop and try to start the weblogic portal server it gives error either that there is exclusive lock on the ear project or it says like the server was interrupted abruptly, and the server does not start,
How do i solve such kind of issue, my server is not starting and i need to resolve such kind of error urgently,
thanks in advanceHi,
If the error is about the exclusive lock on the ear project it means you have made a lock on the resources in weblogic server admin console.You need to realase the lock from the console.
Also if some unexpected error comes?
Just apply the weblogic 9.2 patch before starting the workshop.You can find the patch at C:\bea92\workshop92\workshop4WP location.Run the WLWPatchInitialize.cmd script.
This might be helpful for you.
Thanks
Bishnu -
Java.rmi.server.ExportException: while stopping weblogic Managed server
Hello,
I am getting the below error while I try to stop the weblogic managed server from the stop script in the server. I am able to do it thru the console.
the weblogic version is 9.23.
-server -Xms1536m -Xmx1536m
Stopping Weblogic Server...
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9990; nested exception is:
java.net.BindException: Address already in use
I am a newbie , so anyone could help me figure out the things I need to check so that I can troubleshoot the issue?
thanks in advance.Are you using a custom script or <domain>/bin/stopManagedWebLogic.sh ?
The msg you've informed seems to be an error that happens when you try to start a managed server that is trying to use a port that is already in use. -
Whole server migarion issue in weblogic
I have configured the Script Based node manager. Through admin console i am able to start the remote managed servers psMS1 , psMS2.
192.168.9.11 –> Adminserver , psMS1
192.168.9.22 –> psMS2
We have create Two unix machine Unix1 , Unix1.
Unix1 –> assign servers Adminserver , psMS1.
Unix2 –> assing server psMS2.
The Two manager servers (psMS1,psMS2) is configured with Cluster (CLUST).
But If i configure the Whole server migration option in the weblogic Admin console. I am unable to start Two managed servers. I mentioned the Two managed severs errors logs.
psMS1 Error log :- ( 192.168.9.11 ) –> Unix1 machine
<Fri Dec 3 15:14:09 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* 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 *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS1 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS1/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS1 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:14:11 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:14:13 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:14:15 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:15 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:14:16 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS1/logs/psMS1.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:14:22 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:15:01 PM IST> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.11:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:250:56ff:feaf:649a:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS1" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:07:19 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:250:56ff:feaf:649a:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.11:5003 was shutdown.>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
psMS2 Error log :- ( 192.168.9.22 ) –> Unix2 machine
<Fri Dec 3 15:32:35 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* 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 *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS2 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS2/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS2 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:32:38 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:32:40 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:32:43 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:32:43 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:32:44 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS2/logs/psMS2.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:32:50 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:225:11ff:feca:8710:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.22:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS2" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:00:32 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:225:11ff:feca:8710:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.22:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5005 was shutdown.>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
How to resolve the problem during the Script based node manager during the Whole Server Migration in Clustered Environment(CLUST).
In my knowledge the main reason is " <Cluster> <BEA-000163> <Stopping "async" replication service> "
Regards,
S.Vinoth Babu
Edited by: Vinoth Babu on Dec 9, 2010 2:05 AMMaybe this helps, there are some system requirements before you can use whole server migration
- WSM uses a floating IP address, for each migratable server. This means that the migratable server candidate machines have to be in the same subnet
(because the virtual IP address must be valid on all candidate machines).
- WSM requires the use of the node manager. You must make sure the node manager on each candidate machine is properly initialized with the security-related
files it need to authenticate and accept commands from the admin server.
- WSM uses the node manager to migrate the floating IP address and assign it to the target machine. As such, the default configuration assumes that the
machines are similar; specifically, it assumes the following:
1 The netmask associated with the virtual IP is the same on all machines.
2 The network device name is the same on all machines.
3 The functional behavior of the platform-specific OS command used to add and remove the virtual IP is the same.
- WSM only supports migration of a single virtual IP address for each migratable server. Therefore, a migratable server cannot define any network channels
that use a Listen Address different from the virtual IP address associated with the server. If you need your servers to use multiple network channels associated
with multiple IP addresses, you cannot use the WSM framework.
- WSM assumes that any server-specific state is already shared through some highly available sharing mechanism. For example, the server’s default persistent store
where it keeps its XA transaction logs must be accessible on all candidate machines using the exact same path.
The configuration steps are as follows:
- Create your domain. Make sure that you set up each managed server's to Listen Address to its virtual IP address and assign it to a machine.
- Set up the node manager for each candidate machine. For each machine, edit the nodemanager.properties file to set the NetMask property to the netmask
associated with the virtual IP addresses being used and Interface to the network device name with which to associate the virtual IP address.
- Verify the domain and node manager configuration. Start up the domain and each clustered managed server via its node manager. This not only ensures that the
node managers and servers are properly configured but also initializes the node managers with the password files they need to accept commands from the admin server.
Do not forget to start managed servers on all candidate machines to ensure that the node manager and domain directory are properly initialized.
- Choose and configure your leasing mechanism. Like automatic service migration, automatic whole server migration relies on leasing. Use the cluster's Migration Configuration
tab to select the appropriate Migration Basis.
- If you choose database leasing, be sure to create and configure your nontransactional data source, create the leasing table, and use the cluster's Migration Configuration tab
to set the Data Source for Automatic Migration and Auto Migration Table Name appropriately.
- Grant superuser privileges to the wlsifconfig script. Node managers use the ${WL_HOME}/common/bin/wlsifconfig.sh script to add and remove virtual IP addresses from the
machines. By default, the file is set up to use sudo; sudo typically prompts you for your password the first time you run it and periodically after that. To do this without needing
to input your password, you need to add the NOPASSWD option to the relevant entry in your /etc/sudoers file. Do not forget to add the wlsifconfig script to your PATH so that
the node managers can locate it. (weblogic machine1 = NOPASSWD: /wlserver_10.3/common/bin/wlsifconfig.sh)
- Enable automatic server migration. The last step is to use each managed server's Migration Configuration tab to select the Automatic Server Migration Enabled checkbox
and restart the servers.
Debugging problems with whole server migration can be tricky so you will probably want to add -Dweblogic.debug.DebugServerMigration=true to the Java command line
used to start your servers. -
Weblogic Admin server restart issue
While restarting Oracle Weblogic Admin server, it is not running after below log.
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
Mar 12, 2015 7:33:07 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
INFO: Pushed ldap name and types info to libOvd. Ldaps : DefaultAuthenticator:idstore.ldap.provideridstore.ldap.Hi,
These messages are Info Message Can you please post the complete Error stack for the same
Check the below threads which have similar issue reported
Integrated JDeveloper Weblogic 12C issues
Weblogic server not starting due to OutOfMemory
SOA Suite 12c Integrated Weblogic / Coherence Issue
Unable to run my application
Hope it helps -
Issue listeneing queue from Weblogic Cluster server with multiple managed server
Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
--ManagedServer01(http://server01.myhost.com:7001)
--ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
JMSserver01 targeting: ManagedServer01
JMSserver02 targeting: ManagedServer02
JMSmodule
ConnectionFactory01 targeting:JMSserver01,JMSserver02
UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
mysystemmodule!JMSserver01@UDQueue01
mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
mysystemmodule!JMSserver01@UDQueue01 10
mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
mysystemmodule!JMSserver01@UDQueue01 0
mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz -
Start/Stop Weblogic Admin Server
Hello,
I have installed Forms 11g in my home Pc, so is it possible to Start/Stop Weblogic Admin Server and the Dos window that appears, not to ask me about username and password?
I mean like a bat file (script), to enter the username and password in a text file
if yes, also the same in WLS_FORMS?
Thank you.Starting an Administration Server with a Startup Script
An Administration Server is a WebLogic Server instance that maintains configuration data for a domain. In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. In a production environment, you create Managed Servers to run applications. For more information about Administration Servers and Managed Servers, see "Understanding WebLogic Server Domains" in Understanding Domain Configuration for Oracle WebLogic Server.
You can start an Administration Server with a default startup script or create your own. To start an Administration Server with the WebLogic Server-included startup script:
If you have not already done so, use the Configuration Wizard or WebLogic Scripting Tool (WLST) to create a domain.
See Creating Domains Using the Configuration Wizard or "Creating Domains Using WLST Offline" in Oracle WebLogic Scripting Tool.
Open a shell (command prompt) on the computer on which you created the domain.
Change to the directory in which you located the domain.
By default, this directory is MW_HOME\user_projects\domains\DOMAIN_NAME, where DOMAIN_NAME is the root directory of the domain. (The name of this directory is the name of the domain.)
Run one of the following scripts:
bin/startWebLogic.cmd (Windows)
bin\startWebLogic.sh (UNIX and Windows. On Windows, this script supports the MKS and Cygnus BASH UNIX shell emulators.)
Note:
If you use a Configuration Wizard template that is provided by WebLogic Server, your domain directory includes a start script named startWebLogic. If you use a domain template from another source, the wizard might not create a start script, or it might create a script with a different name. The template designer determines whether the wizard creates a start script and the name of the script.
The startWebLogic script does the following:
Sets environment variables by invoking DOMAIN_NAME\bin\setDomainEnv.cmd (setDomainEnv.sh on UNIX), where DOMAIN_NAME is the directory in which you located the domain; for example, WL_HOME\user_projects\domains\DOMAIN_NAME, and where WL_HOME is the location in which you installed WebLogic Server.
Invokes the java weblogic.Server command, which starts a JVM that is configured to run a WebLogic Server instance.
When the server successfully completes its startup process, it writes the following message to standard out (which, by default, is the command window):
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Starting an Administration Server from the Windows Start Menu
When you create an Administration Server on a Windows computer, the Configuration Wizard creates a shortcut on the Start Menu for starting the server (User Projects > DOMAIN_NAME > Start Admin Server for WebLogic Server Domain).
The command that the Configuration Wizard adds to the Start menu opens a command window and calls the startup script that is described in Starting an Administration Server with a Startup Script. When the server has successfully completed its startup process, it writes the following message to standard out (which, by default, is the command window):
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Mark this helpful/correct to help others too -
Issues with import server : MDIS stops automatically
Hello Experts,
We are facing a critical issue, our MDIS server gets stopped automatically. Evan after restarting along with DB, the issue is not solved. We thought it might be some memory issues, but it is not, we cleared the old files from archive folder and from logs also, still when we start the MDIS it gets stopped in few minutes, we are not able to solve the issue,.. Have any one faced similar issue or clue or any guess how this can be sorted out?
Thanks
Vinothhi Vinothkumar
the MDIS is stopped with the MDS stopping or only the MDIS is stopped.
1.when the MDIS is stopped,what operations do you perform,and please check the MDIS log as well as the MDS log.
2.also,check the MDIS ini and MDS ini parameters,make sure they are configured properly.
3.clear up your port files,including the ready,exception and archive folders.then try to restart your MDS,MDIS,MDSS.
please get the results for further analysis.
best regards
Stephen -
Not able to start the weblogic admin server
Hi,
I am getting the error while starting the weblogic admin server of OAM console.
Below is the stack trace of the error
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7003
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
Kindly help me to solve this issue.
Is anyone had faced this issue.....Hi,
I had tried by putting the username and password in boot.properties but we are getting the same issue.
we tried by editing the config.xml file of the domain.
i.e. by
Before: <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
and restarted the admin server but shows the same error.
kindly suggest us... -
WebLogic Admin server fails to start after reboot
Hi Gurus,
Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
Looking at the AdminServer.log:
*####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
java.lang.AssertionError: weblogic.management.provider.EditFailedException:
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
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)
Caused By: weblogic.management.provider.EditFailedException:
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
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)
Caused By: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
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)
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
Kindly guide me with this. Thanks!
Edited by: Kent Pawar. on Oct 11, 2012 8:51 AMIssue is :
Caused By: weblogic.management.provider.EditFailedException:
One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
some workaround you can try to restore the Admin Server :
Under domain dir ,
\pending directory -- take backup and delete the dir .
Under Admin Server Dir :
data\store --- take backup and delete the dir .
thanks,
Sandeep -
Problem in weblogic sip server 3.1 ( Giving ssl exception )
Hi All ,
I am facing some issue while trying to run weblogic server it is saying "WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from" , I also tried the options -Dweblogic.security.TrustKeyStore=DemoTrust but nothing is helping , Below are the logs please help.
wls:/offline> wls:/offline> Launching NodeManager ...
Properties: {NodeManagerHome=/opt/bea/sipserver311/common/nodemanager,}
Command: /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/bin/java -classpath /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/rt.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/i18n.jar:/opt/bea/patch_weblogic311/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/lib/tools.jar:/opt/bea/sipserver311/server/lib/weblogic_sp.jar:/opt/bea/sipserver311/server/lib/weblogic.jar:/opt/bea/sipserver311/server/lib/wlss/sipservlet.jar:/opt/bea/sipserver311/server/lib/wlss/wlss.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/profile-service-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-mbeaninfo.jar:/opt/bea/sipserver311/server/lib/wlss/wlss_i18n.jar:/opt/bea/sipserver311/server/lib/wlss/wlssechosvr.jar:/opt/bea/sipserver311/server/lib/wlss/wlssdiameter.jar:/opt/bea/sipserver311/server/lib/wlss/sctp.jar:/opt/bea/sipserver311/server/lib/webservices.jar weblogic.NodeManager
NMProcess: <Apr 8, 2009 3:19:40 AM> <INFO> <Loading domains file: /opt/bea/sipserver311/common/nodemanager/nodemanager.domains>
NMProcess: <Apr 8, 2009 3:19:43 AM> <INFO> <Loading identity key store: FileName=/opt/saurabh.jks, Type=jks, PassPhraseUsed=true>
NMProcess: <Apr 8, 2009 3:19:44 AM> <INFO> <Loaded node manager configuration properties from '/opt/bea/sipserver311/common/nodemanager/nodemanager.properties'>
NMProcess: <Apr 8, 2009 3:19:46 AM> <INFO> <Secure socket listener started on port 5556, host ari23bems>
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under /opt/bea/sipserver311/common/nodemanager
wls:/offline> Connecting to Node Manager ...
<Apr 8, 2009 3:19:53 AM CDT> <Warning> <Security> <BEA-090542> <Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1379, in nmConnect
WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client. Use dumpStack() to view the full stacktrace'
wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM CDT> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
Not connected to Node Manager
wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
NMProcess: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
NMProcess: at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
NMProcess: at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
NMProcess: at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
NMProcess: at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.read(Unknown Source)
NMProcess: at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
NMProcess: at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
NMProcess: at java.io.InputStreamReader.read(InputStreamReader.java:167)
NMProcess: at java.io.BufferedReader.fill(BufferedReader.java:136)
NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:299)
NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:362)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
Connecting to t3s://ari23bems:7002 with userid saurabhAdmin ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3s://ari23bems:7002 Use dumpStack() to view the full stacktrace'
wls:/offline> Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
wls:/offline> Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
wls:/offline>
Exiting WebLogic Scripting Tool.Hi All ,
I am facing some issue while trying to run weblogic server it is saying "WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from" , I also tried the options -Dweblogic.security.TrustKeyStore=DemoTrust but nothing is helping , Below are the logs please help.
wls:/offline> wls:/offline> Launching NodeManager ...
Properties: {NodeManagerHome=/opt/bea/sipserver311/common/nodemanager,}
Command: /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/bin/java -classpath /opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/rt.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/jre/lib/i18n.jar:/opt/bea/patch_weblogic311/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit-R27.5.0-jdk1.5.0_14/lib/tools.jar:/opt/bea/sipserver311/server/lib/weblogic_sp.jar:/opt/bea/sipserver311/server/lib/weblogic.jar:/opt/bea/sipserver311/server/lib/wlss/sipservlet.jar:/opt/bea/sipserver311/server/lib/wlss/wlss.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/profile-service-descriptor-binding.jar:/opt/bea/sipserver311/server/lib/wlss/wlss-mbeaninfo.jar:/opt/bea/sipserver311/server/lib/wlss/wlss_i18n.jar:/opt/bea/sipserver311/server/lib/wlss/wlssechosvr.jar:/opt/bea/sipserver311/server/lib/wlss/wlssdiameter.jar:/opt/bea/sipserver311/server/lib/wlss/sctp.jar:/opt/bea/sipserver311/server/lib/webservices.jar weblogic.NodeManager
NMProcess: <Apr 8, 2009 3:19:40 AM> <INFO> <Loading domains file: /opt/bea/sipserver311/common/nodemanager/nodemanager.domains>
NMProcess: <Apr 8, 2009 3:19:43 AM> <INFO> <Loading identity key store: FileName=/opt/saurabh.jks, Type=jks, PassPhraseUsed=true>
NMProcess: <Apr 8, 2009 3:19:44 AM> <INFO> <Loaded node manager configuration properties from '/opt/bea/sipserver311/common/nodemanager/nodemanager.properties'>
NMProcess: <Apr 8, 2009 3:19:46 AM> <INFO> <Secure socket listener started on port 5556, host ari23bems>
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under /opt/bea/sipserver311/common/nodemanager
wls:/offline> Connecting to Node Manager ...
<Apr 8, 2009 3:19:53 AM CDT> <Warning> <Security> <BEA-090542> <Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1379, in nmConnect
WLSTException: 'Error occured while performing nmConnect : Cannot connect to Node Manager.[Security:090542]Certificate chain received from ari23bems - 10.82.23.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client. Use dumpStack() to view the full stacktrace'
wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM CDT> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
Not connected to Node Manager
wls:/offline> NMProcess: <Apr 8, 2009 3:19:54 AM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
NMProcess: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from ari23bems - 10.82.23.11. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
NMProcess: at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
NMProcess: at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
NMProcess: at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
NMProcess: at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
NMProcess: at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
NMProcess: at com.certicom.tls.record.ReadHandler.read(Unknown Source)
NMProcess: at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
NMProcess: at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
NMProcess: at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
NMProcess: at java.io.InputStreamReader.read(InputStreamReader.java:167)
NMProcess: at java.io.BufferedReader.fill(BufferedReader.java:136)
NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:299)
NMProcess: at java.io.BufferedReader.readLine(BufferedReader.java:362)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
Connecting to t3s://ari23bems:7002 with userid saurabhAdmin ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3s://ari23bems:7002 Use dumpStack() to view the full stacktrace'
wls:/offline> Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
wls:/offline> Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the serverError occured while performing start : You should be connected to an admin server or a NM to start a server Use dumpStack() to view the full stacktrace'
wls:/offline>
Exiting WebLogic Scripting Tool.
Maybe you are looking for
-
Dear All, Our Client want a report in which what are all the payments made against the Purchase orders. Is there any std report available? Please advice what to do if std report not available. Regards
-
Vertical Scroll bar In List Item
Dear All: I have to fill up list box with 100 values and i want to see only 4 values at a time,next 4 values should be shown by scrolling down vartical scroll bar.(The same functionality as we usually see in web pages' list box) I shall be very thank
-
Hi Guys, Appreciate your help on what I assume is an easy solution and probably is a stupid question. There are items on the home page that I would like to delete or move from the 2nd page to the 1st (or vice versa). Can't figure out how to do that.
-
Hi all, thanks in advance this website is such a great resource to have questions answered! Running PSE9, Win7, Canon 1100D with CR2 raw format, facebook. I shoot in raw and work with my photos in the organizer in raw, only changing format when necce
-
Oracle10g OEM Intranet URL Error
I am working in an Intranet at our university. I have installed Oracle10g everything is installed accurately. When I tried to access the URL http://hgpc39.uovs.ac.za:5500/em. The URL never works. I have installed Oracle10g at my home computer it is n