EAR startup fails when weblogic managed server restart happens

My EAR startup is failing whenever we have server restart,we have 2 managed server in a weblogic cluster 10.2. if we remove migratable option from JMS server it works. can anybody tell what can be the root cause of this failure and how this links with non-migratable JMS server? Also if we go ahead with non-migratable JMS server whats the impact of not having migratable JMS server?
Thanks in advance,
Manoj,

Similar Messages

Notify when managed server restarts automatically after a crash.

I am trying to see if there is some way I can be notified (by email) when a managed server a cluster restarts automatically. I am running Weblogic 9.2 on Solaris Sparc 5.10.
I can certainly compare the PIDs of the last and the new JVM but am looking for a slick way to do it especially at the Node Manager level.
Thanks.

Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks!

How to disable autostart (application) when managed server restart ?

Hi Ppl,
How to disable autostart (application) when managed server restart ?
I want some of the applications to remain not started. In WebSPhere, we have an option disable auto start for applications.
I don't find in weblogic.
Thanks

Hi,
I agree with Faisal. When you shutdown your WL server while the application is running, the thing is when you start your server again, it would automatically start the application with it. Now if the application was down when you shutdown the server, it _the application_ won't start with the server.
So it depends on the application last state, when you start your server.
Regards,
Mohab

Weblogic managed server crash and automatic restart on Solaris SPARC platform

hi Everyone,
We are facing a problem a problem with Weblogic managed server where the managed server crashes and automatically restarts (via nodemanager) on Solaris SPARC platform.
The system info is as below:
OS:                            Oracle Solaris 11.1 SPARC
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
                           Assembled 19 September 2012
uname:SunOS 5.11 11.1 sun4v
(T2 libthread)
rlimit: STACK 8192k, CORE infinity, NOFILE 65536, AS infinity
load average:1.04 0.52 0.32
CPU:total 4 v9, popc, vis1, vis2, vis3, blk_init, cbcond, sun4v, niagara_plus
Memory: 8k page, physical 16777216k(5930008k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (23.25-b01) for solaris-sparc JRE (1.7.0_25-b11), built on May 15 2013 04:30:17 by "" with Sun Studio 12u1
The pstack output of analyzing the core file is as below (for the particular thread, I can attach the entire output of pstack if required):
--- called from signal handler with signal 11 (SIGSEGV) ---
ffffffff7ec1a7c4 memcpy%sun4v-hwcap3 (103d34720, 10a7e7710, 108ae1060, 6300, 0, ffffffff5f66394b) + 990
ffffffff36102fa4 ZIP_GetEntry (103d34720, ffffffff636f66a4, bd, 103d347f0, a26f1c, 2f) + e4
ffffffff36103440 Java_java_util_zip_ZipFile_getEntry (2b, ffffffff636f66a4, 103d34720, ffffffff636f6b70, 2b, 1) + a8
ffffffff7586ac1c * *java/util/zip/ZipFile.getEntry(J[BZ)J [compiled]
ffffffff75b61b58 * *java/util/zip/ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; [compiled] +39 (line 606)
ffffffff75b61b58 * *java/util/jar/JarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;+3 (line 452)
ffffffff75b61b58 * *weblogic/utils/classloaders/ZipClassFinder.getSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+36 (line 75)
ffffffff75b6eb84 * *weblogic/utils/classloaders/JarClassFinder.getSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +6 (line 100)
ffffffff75a40938 * *weblogic/utils/classloaders/AbstractClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +74 (line 58)
ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
ffffffff75806d10 * weblogic/application/utils/CompositeWebAppFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+5 (line 176)
ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
ffffffff75806d10 * weblogic/utils/classloaders/CodeGenClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+43 (line 48)
ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.findLocalClass(Ljava/lang/String;)Ljava/lang/Class;+87 (line 571)
ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;+117 (line 515)
ffffffff75806d10 * weblogic/utils/classloaders/ChangeAwareClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;+60 (line 121)
ffffffff75a465c8 * *java/lang/ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; [compiled] +71 (line 836)
ffffffff75db42c0 * *java/lang/ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class; [compiled] +4 (line 714)
ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;+2 (line 358)
ffffffff75806d10 * weblogic/utils/classloaders/ChangeAwareClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;+27 (line 83)
ffffffff7580024c * StubRoutines (1)
ffffffff3691f44c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (ffffffff636f7f98, 10234f000, 2, c, 2, 10) + 2f4
ffffffff36e546c0 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_pnGSymbol_63pnGThread__v_ (ffffffff636f7f98, 1013e7748, 10234f000, 10011bf30, 100119ec0, 772d4ec08) + 1b8
ffffffff3725bf0c __1cQSystemDictionaryTload_instance_class6FpnGSymbol_nGHandle_pnGThread__nTinstanceKlassHandle__ (105cb6100, 1013e7978, 10234f000, 102b6e500, 0, 1013e7748) + 494
ffffffff3725a028 __1cQSystemDictionarybEresolve_instance_class_or_null6FpnGSymbol_nGHandle_3pnGThread__pnMklassOopDesc__ (105cb6100, 19dc00, 70, 10234f000, 70, 1013e7700) + ae0
ffffffff37257800 __1cQSystemDictionaryPresolve_or_fail6FpnGSymbol_nGHandle_3bpnGThread__pnMklassOopDesc__ (105cb6100, 1013e76f0, 1013e76f8, 1, 10234f000, 1) + 290
ffffffff368ba9dc __1cTconstantPoolOopDescNklass_at_impl6FnSconstantPoolHandle_ipnGThread__pnMklassOopDesc__ (10201b6e0, 1013e7978, 10234f000, 10201b6e0, 783cfb098, ffffffff37588000) + 264
ffffffff36937380 __1cSInterpreterRuntimeE_new6FpnKJavaThread_pnTconstantPoolOopDesc_i_v_ (10234f000, 77548b730, 49, 10201b6e0, 1013e76e8, 10234f000) + b8
ffffffff7581ab58 * com/jdedwards/base/logging/log4j/JdeLogger.warn(ILjava/lang/String;Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Throwable;)V+14
ffffffff75807bcc * com/jdedwards/system/security/proxy/SecurityServerProxyImpl.install(Ljava/util/Hashtable;)Lcom/jdedwards/system/security/proxy/SecurityServerProxyImpl;+30
ffffffff75806d10 * com/jdedwards/system/security/proxy/SecurityServerProxyFactory.create(Ljava/util/Hashtable;)Lcom/jdedwards/system/security/SecurityServer;+1
ffffffff75807898 * com/jdedwards/system/security/SecurityServerInstance.getInstance()Lcom/jdedwards/system/security/SecurityServer;+27
ffffffff75806d10 * com/jdedwards/mgmt/security/UserManager.checkPassword(Ljava/lang/String;Ljava/lang/String;)Z+59
ffffffff75806b24 * com/jdedwards/mgmt/security/UserManagerImpl.checkPassword(Ljava/lang/String;Ljava/lang/String;)Z+5
ffffffff75806b24 * com/jdedwards/mgmt/security/SCFLoginModule.login()Z+481
The output of the hs_err_pid1127.log file is as below:
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0xffffffff7ec1a544, pid=1127, tid=20
# JRE version: 7.0_25-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# C [libc.so.1+0x11a544] memcpy%sun4v-hwcap3+0x710
# Core dump written. Default location: /slot/ems9437/appmgr/Oracle/Middleware/user_projects/domains/smc_domain/core or core.1127
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x000000010294d000): JavaThread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon [_thread_in_native, id=20, stack(0xffffffff62f00000,0xffffffff63000000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0xffffffff5f6ce000
I ran the suspect code which i believed was causing the issue as a standalone Java program using the same Java executable and it worked fine without any crash.
Appreciate any inputs / discussion / feedback / thoughts on this topic.
Good day.

I just wanted to throw in one more thought. I have also seen that there is a restart=true parameter. Maybe if we set this to true, and just issue the command to shut down the server in the script, the managed server will restart on its own.
Would greatly appreciate any advice!

The Oracle MapViewer brings the WebLogic Managed Server to crash

Problem Description: The Oracle MapViewer brings the WebLogic Managed Server to crash, when we call a GetMap-Request with wrong Coordinates.
This was found out for the SRS=EPSG:25833. Example:
http://igdb-qm-svra1.blva.bayern.de:8080/mapviewer/wms?
REQUEST=getMap&
Version=1.1.1&
LAYERS=&
FORMAT=image/png&
TRANSPARENT=false&
STYLES=&
Datasource=igvert_alkis_wms&
basemap=AT_WMS_TN-KOMPLETT&
SRS=EPSG:25833&
BBOX=3.32358690717E7,5529425.0143,3.32369088846E7,5530464.8272&
WIDTH=500&
HEIGHT=500&
With the Enterprise Manager was also evaluated during and after a crash of Server the SQL-Statements.
If the SQL statements executed on the database itself, it takes a few seconds after a correct answer returns.
I know that have the look for the EPSG coordinate as follows:
BBOX=235869.071700,5529425.014300,236908.884600,5530464.827200&
My question therefore: Why are these coordinates by the Oracle MapViewer approved and not caught? An Request with incorrect
coordinates goes into a StuckThreads and then the ManagedServer crashed.
In the appendix you will find the evaluation of the Enterprise Manager.
I have tested the request with two different versions of Oracle MapViewer (Ver11_1_1_5_B110527 and Ver11_B100426). In both the same problem occurs on.
I have also filed an SR.
Best Regards
Kerstin

Hi,
Can you confirm that you're trying to setup a managed server on another machine using the pack/unpack commands ?
You might to want to take a look at that post.
Clustering of 2 Physical server
Hope that helps !
Regards

Weblogic.management.server bound more than once?

Sorry if I already posted this in cluster, but I realized that it should belong here instead....
I have an admin server that does not belong in any cluster. I set up 2 managed server (app01,
app02) targetted to "app cluster". I can start up app01 or app02 by itself, when when I start both
up, I get the following message on both managed servers; the admin server, on the other hand, does
not display any errors. Why are the managed servers trying to bind weblogic.management.server to
jndi????
<Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster> <Adding
server -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to cluster view>
<Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster>
<Adding -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to the cluster>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.server in the jndi tree. The object you have bound
weblogic.management.internal.RemoteMBeanServerImpl from fortran is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed from one
server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.server in the jndi tree. The object you have bound
weblogic.management.internal.RemoteMBeanServerImpl_WLStub from fortran-1 is non clusterable and you
have tried to bind more than once from two or more servers. Such objects can only deployed from one
server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.adminhome in the jndi tree. The object you have bound
weblogic.management.internal.AdminMBeanHomeImpl from fortran is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed from one server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.adminhome in the jndi tree. The object you have bound
weblogic.management.internal.AdminMBeanHomeImpl_WLStub from fortran-1 is non clusterable and you
have tried to bind more than once from two or more servers. Such objects can only deployed from one
server.>
Gene

Prasad diagnosed the problem. Look in clustering under the same title if you're interested!
Gene
"Gene Chuang" <[email protected]> wrote in message news:[email protected]...
Sorry if I already posted this in cluster, but I realized that it should belong here instead....
I have an admin server that does not belong in any cluster. I set up 2 managed server (app01,
app02) targetted to "app cluster". I can start up app01 or app02 by itself, when when I startboth
up, I get the following message on both managed servers; the admin server, on the other hand,does
not display any errors. Why are the managed servers trying to bind weblogic.management.server to
jndi????
<Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster> <Adding
server -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to cluster view>
<Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster>
<Adding -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to the cluster>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.server in the jndi tree. The object you have bound
weblogic.management.internal.RemoteMBeanServerImpl from fortran is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed from one
server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.server in the jndi tree. The object you have bound
weblogic.management.internal.RemoteMBeanServerImpl_WLStub from fortran-1 is non clusterable andyou
have tried to bind more than once from two or more servers. Such objects can only deployed fromone
server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.adminhome in the jndi tree. The object you have bound
weblogic.management.internal.AdminMBeanHomeImpl from fortran is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed from one server.>
<Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
the name weblogic.management.adminhome in the jndi tree. The object you have bound
weblogic.management.internal.AdminMBeanHomeImpl_WLStub from fortran-1 is non clusterable and you
have tried to bind more than once from two or more servers. Such objects can only deployed fromone
server.>
Gene

EJB 3.0, BC4J and weblogic managed server

Hi, I've got a problem using EJB 3.0 with a BC4J Application module in a weblogic managed server.
My bean is a stateless session bean that use BC4J for database transaction.
When I call the bean the first time, It returns de values I need, without problem. If I do the same call again, I always get "null". I deployed the same bean on the AdminServer, linking to the same DataSource, It works fine and I never got a null result.
My application module is created insid my EJB abstract class by :
_am = (BaseServiceImpl)Configuration.createRootApplicationModule(adfModel, adfConfiguration);*
Where adfModel and adfConfiguration are configured through annotations in my EJB Implementation.
In my abstract EJB, I have a methode with a +@PreDestroy+ method like that :
+@PreDestroy+
*protected void releaseModele() {*
*if (_am != null) {*
Configuration.releaseRootApplicationModule(_am, false);
_am = null;*
My Data Source on the server is defined as Supporting Global Transaction, one-phase commit. I activated the BC4J Logs on the server to see what was going on and I see that the JDBC seems to close after the first call :
*** closing jdbc connection now **** (weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection@0)
And that is when I've got the error on the server :
oracle.jbo.InvalidObjAccessException: JBO-25036: An invalid object operation was invoked on type View Object with name AppModAD
So, my JDBC connection seems to close somewhere beetween the first and the second call, but only on a managed server... Someone has ever encountered a problem like that?
Maybe there is something with the configuration of a datasource on a managed server? Or with the lifecycle of an

The solution was to NOT have glabal transaction checked in the configuration of the data-source and "Failover Transaction State Upon Managed Release" uncked in the configuration of the Business component configuration.

Error when starting managed server Message Too Long

          Hi,
          I'm trying to setup clustering with WLS6.1sp2.
          I use the jdk include with wls
          2 servers in the cluster OS=AIX
          1 Adminserver running on Solaris 8
          When I start a managed server on one of the clustered machines
          I see the following error.
          Starting Cluster Service ....
          <Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
          on port 7001, ip address 10.160.3.74>
          <Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
          java.io.IOException: Message too long
          java.io.IOException: Message too long
          at java.net.PlainDatagramSocketImpl.send(Native Method)
          at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
          at java.net.DatagramSocket.send(DatagramSocket.java:341)
          at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
          at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
          at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
          Code))
          at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
          at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
          at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
          at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
          at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)
          >
          <Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
          (cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
          <Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
          Server "s01ap007" for domain "axa" running in Production Mode>
          Also deploying doesn't seem to succeed could this be coused by this error
          I hope someone can help me.
          Best regards,
          Peter Van der Goten


          Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
          I will post this also here.
          The problem was that the upd_sendspace variable was set on
          a mutch to low value (9126) or something in this range
          It had to be set on 32769.
          this was done with no -o udp_sendspace=32769
          Best regards,
          Peter
          "Peter Van der Goten" <[email protected]> wrote:
          >
          >Hi,
          >I'm trying to setup clustering with WLS6.1sp2.
          >I use the jdk include with wls
          >2 servers in the cluster OS=AIX
          >1 Adminserver running on Solaris 8
          >
          >When I start a managed server on one of the clustered machines
          >I see the following error.
          >Starting Cluster Service ....
          ><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
          >listening
          >on port 7001, ip address 10.160.3.74>
          ><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
          >message:
          >java.io.IOException: Message too long
          >java.io.IOException: Message too long
          > at java.net.PlainDatagramSocketImpl.send(Native Method)
          > at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
          > at java.net.DatagramSocket.send(DatagramSocket.java:341)
          > at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
          > at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
          > at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
          >Code))
          > at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
          > at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
          > at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
          > at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
          > at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          > at weblogic.Server.main(Server.java:35)
          >>
          ><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
          >messages
          >(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
          ><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
          >Managed
          >Server "s01ap007" for domain "axa" running in Production Mode>
          >
          >Also deploying doesn't seem to succeed could this be coused by this error
          >
          >I hope someone can help me.
          >Best regards,
          >Peter Van der Goten
          >

Management console fails connecting to Management server.

I have installed Oracle 9.2 on Red Hat Advanced Server V2.1.
Also installed Management server and client software on the system.
Started everything up: oemctl start oms, agentctl start agent, apachectl start...
Run Manager Console on Linux machine (i.e. locally)
Runs successfully - connecting stand-alone
Runs successfully - connecting to management sever
Installed client software on a Windows NT PC.
Runs successfully - connecting stand-alone
FAILS - connecting to Management server
On another NT PC, try running web interface to Management server
FAILS - Same error as when using thick client.
Failure is the same in both cases: The exception (java.lang.NullPointerException) occured.
Failure of both of these suggested a server issue...
Don't know where to find management server logs?
Looking at $ORACLE_HOME/Apache/Apache/logs/error_log seems unable to find files, e.g.:
[Mon Nov 25 10:01:46 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/readme/emreadme.htm
[Mon Nov 25 10:01:57 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/java/awt/KeyboardFocusManager.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.properties
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/vt/console/app/ConsoleBean
Info.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/sun/beans/infos/ConsoleBeanInfo.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/emSDK/client/appContainer/
WebApplicationBeanInfo.class
I have tried reinstalling Oracle website, however this made no difference.

Can you ping the server which is running OEM from the client NT machine?
Are you trying to connect using DNS or IP?
Verify that this works first.

Deployment of Web Application when the managed Server is down .....

Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

This is currently being fixed in 7.0 line, contact [email protected] and reference
CR110687
Cheers
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

InvalidClassException when starting managed server

Hi,
I just created a new managed server from the admin console, but it won't start. Regardless whether I try to start it via the admin console (using NodeManager) or a start script (startManagedWebLogic.sh), it fails with a complaint about an InvalidClassException. For example:
<24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <Starting Server mydomain::VemaQuickServer ...>
<24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'VemaQuickServer', pid: 21452>
<24.05.2006 15.08 Uhr CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_06-b05 from Sun Microsystems Inc.>
<24.05.2006 15.08 Uhr CEST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://192.168.1.202:9001 to check if there exists a running admin server at this URL.>
<24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<24.05.2006 15.08 Uhr CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
<24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://192.168.1.202:9001 to retrieve the initial configuration.>
<24.05.2006 15.08 Uhr CEST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through URL: http://192.168.1.202:9001/wl_management_internal2/Bootstrap, user: system
java.io.InvalidClassException: javax.management.ObjectName; local class incompatible: stream classdesc serialVersionUID = -5467795090068647408, local class serialVersionUID = 1081892073854801359
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)>
Any ideas what is going on ?
Regards
Heiko

WLS 8.1 does not support JDK 5.
You will need to upgrade to WLS 9.x to use JDK 5.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

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.

OBIEE 11.1.1.5 Weblogic Managed Server bi_server1 crashed

Hello OTN,
We are facing weblogic managed server crash issues. Our environment is RedHat Enterprise Linux version 5 X86_64 bit. Below is the exact error message captured from the output of the command (sh startManagedWebLogic.sh)
/u01/app/oracle/fmw1/user_projects/domains/bifoundation_domain/bin/startWebLogic.sh: line 180: 2337 Segmentation fault ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
Request your directions...
--Joe

Hi Joe,
Segmentation refers to internal memory management by the OS. May be you want to narrow on the cause here. Here are few things you may want to check
1. Did you make any modifications on the weblogic server? May be threads/stacks params etc
2. How about the JVM heap size? Is it default or have you tuned it?
3. Any modifications of the startup/config/common scripts?
Hope this helps.
Thank you,
Dhar

Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

Hi,
I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
Is there a way to change this?

SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

How to deploy a weblogic 8 ear file to a weblogic 7 server

Hi,
DOes anyone know how I can deploy a ear file built from weblogic 8 server into a weblogic 7 server? Any help is appreciated. Thanks!

You would
a. Create a new tablespace to hold rollback segments
b. Create rollback segments in the new tablespace
c. Bring the new rollback segments online and the old rollback segments offline
d. Wait for all the old rollback segments to go offline (they'd be in PENDING OFFLINE if there are active transactions)
d. Drop the old rollback segments
e. Drop the old rollback tablespace -- after confirming that it has NO active rollback segments and NO OTHER segments at all
f. Modify your init.ora to specify the new rollback segments in the "rollback_segments=" parameter
If you want to switch back to the old tablespace name and segment names, you'd do steps a to e and then run them again to recreate the old tablespace name (with 1 datafile, excluding the one you want to drop) and segment names.

EAR startup fails when weblogic managed server restart happens

Similar Messages

Maybe you are looking for