Stop weblogic server instance using nodemanager

Hi,
we're in the process of setting up our weblogic cluster. We've configured the nodemanager (script based).
Server starts and stops from the admin console work fine using the scripts:
ssh -o PasswordAuthentication=no -p %P %H wlscontrol.sh -d %D -s %S -c -r MYDOMAIN -n MYDOMAIN %C
The next step is that we want to configure a startup script ala start/stop/restart/status
And we can start servers from the command line:
ssh -o PasswordAuthentication=no -p 22 host wlscontrol.sh -d MYDOMAIN -s \'managed_server_name\' -c -r MYDOMAIN -n MYDOMAIN START
and using STAT to get the current status.
We noticed that STAT didn't work for servers that weren't started by the NM say using the startManagedWeblogic.sh script...
So what we want to do is control all starts and stops via the NM.
Thing is that there doesn't seem to be a STOP command. There is a KILL but that actually unix kills the process ... a little full on and the NM tried to restart the server ...
appreciate any ideas.
thanks,
Michael

Hi.
First, thanks for watching the video. To specify the server an application will run on, simply open the application's properties and go the the Run category. Then, select the appropriate WLS instance in the Bind to Integrated Application Server drop down list.
Best Regards,
Frédéric.

Similar Messages

NullPointerException while starting Weblogic server instance

          Hi,
          I am running Weblogic 7.0 SP1 on Windows 2000 SP3. I had configured a cluster
          with a single server in it. With that set up the admin server & Weblogic server
          instance started up fine. Both(admin & server instance) were run on the same machine.
          Then I added another server(on a different to the cluster & tried to start the
          local server instance after running the admin server. I get the following exception,
          C:\bea7>C:\bea7\jdk131_03\bin\java -Djava.compiler=NONE -ms64m -mx64m -classpath
          ""C:\SBM742\conf;C:\SBM742\ebmsapps;C:\SBM\jar\inetmssql.jar;.;C:\bea7\weblogic
          700\server\lib\weblogic_sp.jar;C:\bea7\weblogic700\server\lib\weblogic.jar;C:\SB
          M742\jar\tools.jar;C:\SBM742\jar\log4j.jar;C:\SBM742\BizPulse\JMSFileStore;C:\SB
          M742\BizPulse\jmsmaps;C:\SBM742\jar\castor-0.9.3-xml.jar;C:\SBM742\jar\jdbc-se2.
          0.jar;C:\SBM742\jar\jta1.0.1.jar;C:\SBM742\jar\jakarta-regexp-1.2.jar;C:\SBM742\
          jar\xerces-J_1.4.0.jar"" -Dweblogic.Name="MILPITAS" "-Dbea.home=C:\bea7" -Dweblo
          gic.management.server="milpitas.savvion.com:18793" "-Djava.security.policy==C:\b
          ea7\projects\sbm4.0\sbm.policy" -Dweblogic.ProductionModeEnabled=true -Dweblogic
          .management.username="system" -Dweblogic.management.password="wlsysadmin" weblog
          ic.Server
          Starting WebLogic Server...
          Connecting to http://milpitas.savvion.com:18793...
          <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090093> <No configuration
          da
          ta was found on server MILPITAS for realm CompatibilityRealm.>
          <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090082> <Security initializi
          ng using realm CompatibilityRealm.>
          <Apr 30, 2003 12:10:33 PM PDT> <Notice> <WebLogicServer> <000328> <Starting WebL
          ogic Managed Server "MILPITAS" for domain "sbm4.0">
          Starting Cluster Service...
          <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000138> <Listening for announ
          cements from cluster sbm_cluster on 237.0.0.1:7001>
          <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000133> <Waiting to synchroni
          ze with other running members of sbm_cluster>
          <Apr 30, 2003 12:11:38 PM PDT> <Notice> <Cluster> <000134> <Discovered and synch
          ronized with 1 other running members of sbm_cluster>
          <Apr 30, 2003 12:11:39 PM PDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception
          Throwable: java.lang.NullPointerException
          java.lang.NullPointerException
          at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          TransactionRecoveryService.java:345)
          at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          nsactionRecoveryServices(TransactionRecoveryService.java:390)
          at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          actionRecoveryService.java:160)
          at weblogic.transaction.internal.TransactionService.resume(TransactionSe
          rvice.java:138)
          at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          61)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          at weblogic.Server.main(Server.java:32)
          >
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.NullPointerException
          at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          TransactionRecoveryService.java:345)
          at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          nsactionRecoveryServices(TransactionRecoveryService.java:390)
          at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          actionRecoveryService.java:160)
          at weblogic.transaction.internal.TransactionService.resume(TransactionSe
          rvice.java:138)
          at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          61)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          at weblogic.Server.main(Server.java:32)
          Reason: Fatal initialization exception
          Throwable: java.lang.NullPointerException
          java.lang.NullPointerException
          at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          TransactionRecoveryService.java:345)
          at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          nsactionRecoveryServices(TransactionRecoveryService.java:390)
          at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          actionRecoveryService.java:160)
          at weblogic.transaction.internal.TransactionService.resume(TransactionSe
          rvice.java:138)
          at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          61)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          at weblogic.Server.main(Server.java:32)
          The local server instance doesn't start because of this. The other server added
          to the cluster was to run on a different machine & was not started yet. If I remove
          the other server the server instance starts up fine. I am attaching the config.xml(the
          working version, without the second server).
          This used to work in Weblogic 6.1.
          Thanks,
          Aejaz
          [config.xml]


This is fixed in SP2.
          Sree Bodapati wrote:
          > This is probably fixed already please contact support@bea<DOT>com.
          >
          > /
          > sree
          >
          > "Aejaz" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > Hi,
          > >
          > > I am running Weblogic 7.0 SP1 on Windows 2000 SP3. I had configured a
          > cluster
          > > with a single server in it. With that set up the admin server & Weblogic
          > server
          > > instance started up fine. Both(admin & server instance) were run on the
          > same machine.
          > > Then I added another server(on a different to the cluster & tried to start
          > the
          > > local server instance after running the admin server. I get the following
          > exception,
          > >
          > >
          > C:\bea7>C:\bea7\jdk131_03\bin\java -Djava.compiler=NONE -ms64m -mx64m -class
          > path
          > >
          > ""C:\SBM742\conf;C:\SBM742\ebmsapps;C:\SBM\jar\inetmssql.jar;.;C:\bea7\weblo
          > gic
          > >
          > 700\server\lib\weblogic_sp.jar;C:\bea7\weblogic700\server\lib\weblogic.jar;C
          > :\SB
          > >
          > M742\jar\tools.jar;C:\SBM742\jar\log4j.jar;C:\SBM742\BizPulse\JMSFileStore;C
          > :\SB
          > >
          > M742\BizPulse\jmsmaps;C:\SBM742\jar\castor-0.9.3-xml.jar;C:\SBM742\jar\jdbc-
          > se2.
          > >
          > 0.jar;C:\SBM742\jar\jta1.0.1.jar;C:\SBM742\jar\jakarta-regexp-1.2.jar;C:\SBM
          > 742\
          > > jar\xerces-J_1.4.0.jar"" -Dweblogic.Name="MILPITAS"
          > "-Dbea.home=C:\bea7" -Dweblo
          > > gic.management.server="milpitas.savvion.com:18793"
          > "-Djava.security.policy==C:\b
          > >
          > ea7\projects\sbm4.0\sbm.policy" -Dweblogic.ProductionModeEnabled=true -Dwebl
          > ogic
          > > management.username="system" -Dweblogic.management.password="wlsysadmin"
          > weblog
          > > ic.Server
          > > Starting WebLogic Server...
          > > Connecting to http://milpitas.savvion.com:18793...
          > > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090093> <No
          > configuration
          > > da
          > > ta was found on server MILPITAS for realm CompatibilityRealm.>
          > > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090082> <Security
          > initializi
          > > ng using realm CompatibilityRealm.>
          > > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <WebLogicServer> <000328>
          > <Starting WebL
          > > ogic Managed Server "MILPITAS" for domain "sbm4.0">
          > > Starting Cluster Service...
          > > <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000138> <Listening for
          > announ
          > > cements from cluster sbm_cluster on 237.0.0.1:7001>
          > > <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000133> <Waiting to
          > synchroni
          > > ze with other running members of sbm_cluster>
          > > <Apr 30, 2003 12:11:38 PM PDT> <Notice> <Cluster> <000134> <Discovered and
          > synch
          > > ronized with 1 other running members of sbm_cluster>
          > > <Apr 30, 2003 12:11:39 PM PDT> <Emergency> <WebLogicServer> <000342>
          > <Unable to
          > > initialize the server: Fatal initialization exception
          > > Throwable: java.lang.NullPointerException
          > > java.lang.NullPointerException
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          > > TransactionRecoveryService.java:345)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          > > nsactionRecoveryServices(TransactionRecoveryService.java:390)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          > > actionRecoveryService.java:160)
          > > at
          > weblogic.transaction.internal.TransactionService.resume(TransactionSe
          > > rvice.java:138)
          > > at
          > weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          > > 61)
          > > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          > > at weblogic.Server.main(Server.java:32)
          > > >
          > >
          > ***************************************************************************
          > > The WebLogic Server did not start up properly.
          > > Exception raised:
          > > java.lang.NullPointerException
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          > > TransactionRecoveryService.java:345)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          > > nsactionRecoveryServices(TransactionRecoveryService.java:390)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          > > actionRecoveryService.java:160)
          > > at
          > weblogic.transaction.internal.TransactionService.resume(TransactionSe
          > > rvice.java:138)
          > > at
          > weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          > > 61)
          > > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          > > at weblogic.Server.main(Server.java:32)
          > > Reason: Fatal initialization exception
          > > Throwable: java.lang.NullPointerException
          > > java.lang.NullPointerException
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
          > > TransactionRecoveryService.java:345)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
          > > nsactionRecoveryServices(TransactionRecoveryService.java:390)
          > > at
          > weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
          > > actionRecoveryService.java:160)
          > > at
          > weblogic.transaction.internal.TransactionService.resume(TransactionSe
          > > rvice.java:138)
          > > at
          > weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
          > > 61)
          > > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
          > > at weblogic.Server.main(Server.java:32)
          > >
          > >
          > ***************************************************************************
          > >
          > > The local server instance doesn't start because of this. The other server
          > added
          > > to the cluster was to run on a different machine & was not started yet. If
          > I remove
          > > the other server the server instance starts up fine. I am attaching the
          > config.xml(the
          > > working version, without the second server).
          > >
          > > This used to work in Weblogic 6.1.
          > >
          > > Thanks,
          > > Aejaz
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support

WLST : Error connecting to a remote Weblogic server instance from OEPE 3.7

Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -
username = 'weblogic'
password = 'weblogic6'
url='t3://xxx.xxx.com:7001'
connect(username,password,url)
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace :
java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
Problem invoking WLST - Traceback (innermost last):
File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace
Connecting to the local weblogic server instance (t3://localhost:7001) works okay.
From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -
wls:/offline> connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.
I've compared the CLASSPATHs between OEPE and the command prompt.
Any assistance would be greatly appreciated.
Edited by: 950635 on Feb 1, 2013 7:47 PM

Hi,
1)To get mysql JDBC driver to work on my Linux system, i had to add the classpath for the driver to the .bashrc:
CLASSPATH=./:home/<user>/java/mm.mysql-2.0.6/:home/<user>/java
Note that I execute the java program as the user <user> (and .bashrc is the config. file of this <user>...). Perhaps you must do this as well for the Oracle driver on your client machine. I don't know if your client machine is UNIX/LINUX or WINDOWS. It should only be clear that the CLASSPATH is set in the config. file of the user under which the java program runs and that this user has the permission to access the files.
There are no differences between accessing the database locally than accessing it by a network connection. The only thing that matters are that the connection parameters are right and that the network works properly.
2) are you sure that the table tname (case sensitivity?) exits?
Marc

Start and stop Weblogic Server 5.1 on unix system

Hello,
How do I stop Weblogic Server 5.1 after I run startWebLogic.sh without
Weblogic Console? What's the best way to start weblogic Server in unix?
Create a user "weblogic" and start manually everytime I reboot the system or
build a script?
Thanks,
Hiu Sing

Hiu Sing Ngai wrote:
Hello,
How do I stop Weblogic Server 5.1 after I run startWebLogic.sh without
Weblogic Console?java weblogic.Admin <url> SHUTDOWN system password <seconds> <lockMessage>
What's the best way to start weblogic Server in unix?I would suggest you start the WLS from command line using our
build script or your own customized scripts.
--Kumar
>
Create a user "weblogic" and start manually everytime I reboot the system or
build a script?
Thanks,
Hiu Sing

I Can't stop weblogic server in bea workspace studio

Hi,
I can't stop weblogic server with eclipse stop button (just throw me a timeout), only can I do is killing the java.exe process or run stopWeblogic.exe.
How can i solve this bug??
Thanks a lot.
Edited by: user3023949 on 27-mar-2009 5:59

Hi,
I can't stop weblogic server with eclipse stop button (just throw me a timeout), only can I do is killing the java.exe process or run stopWeblogic.exe.
How can i solve this bug??
Thanks a lot.
Edited by: user3023949 on 27-mar-2009 5:59

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

How do I get the WebLogic server to use the XMLRegistry?

I'm using WebLogic 7.0.2, and I want to use the Apache TransformerFactory and DocumentBuilderFactory
instead of the default weblogic.* classes. I've found the documentation, where
I define an XML Registry as follows (snippet from my config.xml)...
<Server ListenAddress="####" ListenPort="####" Name="myserver"
NativeIOEnabled="true" ServerVersion="7.0.2.0"
StdoutEnabled="true" StdoutSeverityLevel="8"
StuckThreadMaxTime="14400"
XMLEntityCache="XMLCacheMBean_myserver" XMLRegistry="CT XML Registry">
<COM Name="myserver"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="myserver"/>
<JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="myserver"/>
<JTARecoveryService Name="myserver"/>
<KernelDebug Name="myserver"/>
<Log FileName="myserver/myserver.log" Name="myserver"/>
<SSL Enabled="true" HostnameVerificationIgnored="true"
ListenPort="###" Name="myserver"
ServerCertificateFileName="democert.pem"
ServerPrivateKeyAlias="demokey" ServerPrivateKeyPassPhrase="{3DES}gAuVwsR68oAlLdIfO1PAtw=="/>
<ServerDebug Name="myserver"/>
<ServerStart Name="myserver"/>
<WebServer DefaultWebApp="DefaultWebApp"
LogFileName="myserver/access.log" LoggingEnabled="true" Name="myserver"/>
</Server>
<XMLEntityCache Name="XMLCacheMBean_myserver"/>
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="CT XML Registry"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
TransformerFactory="org.apache.xalan.processor.TransformerFactoryImpl"
WhenToCache="cache-on-reference"/>
I've played aorund with xercesImpl being in and out of classpaths, etc. But no
matter what I do, calls to TransformerFactory.newInstance creates an instance
of weblogic.xml.jaxp.RegistrySAXTransformerFactory and DocumentBuilderFactory.newInstance()
creates an instance of weblogic.xml.jaxp.RegistryDocumentBuilderFactory.
I don't want to use these classes, and supposedly I can control which classes
I will use, but it's not working for me. Has anyone been able to get this working?
Is there anything else that I'm missing?
Thanks,
Ed

I was unable to use the XMLRegistry touse the Xerces2 libraries with WebLogic 7.
I did find in WebLogic 7 doco that the latest release of Xerces that it would
internally support was 1.4.4 (http://e-docs.bea.com/wls/docs70/xml/xml_admin.html#1066271).
If I wanted to use this version of Xerces, I would need to use WebLogic 8. This
is not an option for me at this stage.
So, I used this approach. When starting the WebLogic server, you can assign ClassPath
entries to an environment variable called PRE_CLASSPATH. This will prepend the
class path used by the App Container's JVM with the values in the variable. I
added the xercesImpl and xalan jars to this entry.
Because the WebLogic class loaders will always defer to the parent class loader,
it will check this class path first. So now I can directly instantiate the apach
implementation classes (typecasting them back to their API interface definitions)
and use them within the container.
"Ed Hillmann" <[email protected]> wrote:
>
I'm using WebLogic 7.0.2, and I want to use the Apache TransformerFactory
and DocumentBuilderFactory
instead of the default weblogic.* classes. I've found the documentation,
where
I define an XML Registry as follows (snippet from my config.xml)...
<Server ListenAddress="####" ListenPort="####" Name="myserver"
NativeIOEnabled="true" ServerVersion="7.0.2.0"
StdoutEnabled="true" StdoutSeverityLevel="8"
StuckThreadMaxTime="14400"
XMLEntityCache="XMLCacheMBean_myserver" XMLRegistry="CT XML Registry">
<COM Name="myserver"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="myserver"/>
<JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="myserver"/>
<JTARecoveryService Name="myserver"/>
<KernelDebug Name="myserver"/>
<Log FileName="myserver/myserver.log" Name="myserver"/>
<SSL Enabled="true" HostnameVerificationIgnored="true"
ListenPort="###" Name="myserver"
ServerCertificateFileName="democert.pem"
ServerPrivateKeyAlias="demokey" ServerPrivateKeyPassPhrase="{3DES}gAuVwsR68oAlLdIfO1PAtw=="/>
<ServerDebug Name="myserver"/>
<ServerStart Name="myserver"/>
<WebServer DefaultWebApp="DefaultWebApp"
LogFileName="myserver/access.log" LoggingEnabled="true" Name="myserver"/>
</Server>
<XMLEntityCache Name="XMLCacheMBean_myserver"/>
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="CT XML Registry"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
TransformerFactory="org.apache.xalan.processor.TransformerFactoryImpl"
WhenToCache="cache-on-reference"/>
I've played aorund with xercesImpl being in and out of classpaths, etc.
But no
matter what I do, calls to TransformerFactory.newInstance creates an
instance
of weblogic.xml.jaxp.RegistrySAXTransformerFactory and DocumentBuilderFactory.newInstance()
creates an instance of weblogic.xml.jaxp.RegistryDocumentBuilderFactory.
I don't want to use these classes, and supposedly I can control which
classes
I will use, but it's not working for me. Has anyone been able to get
this working?
Is there anything else that I'm missing?
Thanks,
Ed

Error , while stopping Weblogic server 5.1

Hello,
Encountered the following error while stopping the bea Weblogic server 5.1 on
AIX 4.3. Seeking for Valuable solution / Suggestion.
Submitting shutdown command to Weblogic Server on Port 80.
Failed to connect to t3://10.72.111.15:80 due to :
[Weblogic.rmi. Unexpected Exception: Marshalling
-with nested exception:
[Weblogic.rjvm.PeerGoneException:
-with nested exception:
[Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception creating
response stream] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser;Local Class not compatible: Stream
Classdesc serialVersionUID=6699361079932480379
local class serialVersionUID=2825328378974757378]]]]

Narayan,
Can you provide more information on the configuration, JDK, Service Pack
level and also manner in which you shutdown the server.
Can you try using the following command to shutdown the server
java weblogic.Admin URL SHUTDOWN system password
http://www.weblogic.com/docs51/admindocs/weblogicserver.html#shutdown
Also make sure you set the classpath before running this command
If you are testing with any service pack prior to sp8, I would suggest you
test with the latest service pack for WebLogic Server 5.1 which is sp10.
If you need just the service pack for WLS 5.1 , you will need to have a
websupport login and password. Please refer to this url for more
information on this.
http://contact.bea.com/bea/www/BEACustRegLogin.jsp
http://websupport.bea.com/custsupp/
Hope this helps
Raj Alagumalai
"Narayan" <[email protected]> wrote in
news:3ba61ba3$[email protected]:
>
Hello,
Encountered the following error while stopping the bea Weblogic server
5.1 on AIX 4.3. Seeking for Valuable solution / Suggestion.
Submitting shutdown command to Weblogic Server on Port 80.
Failed to connect to t3://10.72.111.15:80 due to :
[Weblogic.rmi. Unexpected Exception: Marshalling
-with nested exception:
[Weblogic.rjvm.PeerGoneException:
-with nested exception:
[Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception
creating response stream] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser;Local Class not
compatible: Stream Classdesc serialVersionUID=6699361079932480379
local class serialVersionUID=2825328378974757378]]]]

Error while stopping Weblogic server

I have created a new domain and installed my application here, after deplotyment when i stop teh server it throws the following exception:
Cannot shutdown a server when using a BootIdentify file AND running in Production mode
I have created boot.properties file also.still it is throwing this error,.I am not getting any clue on this error, there is no clear details availablei n the archives also , so please advise.
Thanks
Vishy

Narayan,
Can you provide more information on the configuration, JDK, Service Pack
level and also manner in which you shutdown the server.
Can you try using the following command to shutdown the server
java weblogic.Admin URL SHUTDOWN system password
http://www.weblogic.com/docs51/admindocs/weblogicserver.html#shutdown
Also make sure you set the classpath before running this command
If you are testing with any service pack prior to sp8, I would suggest you
test with the latest service pack for WebLogic Server 5.1 which is sp10.
If you need just the service pack for WLS 5.1 , you will need to have a
websupport login and password. Please refer to this url for more
information on this.
http://contact.bea.com/bea/www/BEACustRegLogin.jsp
http://websupport.bea.com/custsupp/
Hope this helps
Raj Alagumalai
"Narayan" <[email protected]> wrote in
news:3ba61ba3$[email protected]:
>
Hello,
Encountered the following error while stopping the bea Weblogic server
5.1 on AIX 4.3. Seeking for Valuable solution / Suggestion.
Submitting shutdown command to Weblogic Server on Port 80.
Failed to connect to t3://10.72.111.15:80 due to :
[Weblogic.rmi. Unexpected Exception: Marshalling
-with nested exception:
[Weblogic.rjvm.PeerGoneException:
-with nested exception:
[Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception
creating response stream] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser;Local Class not
compatible: Stream Classdesc serialVersionUID=6699361079932480379
local class serialVersionUID=2825328378974757378]]]]

Could not execute command "getState" for server server01 using nodemanager

Hi,
I have built a weblogic 9.1 env with 2 managed servers running on different boxes from the admin server.
I am having problems in starting the managed servers using the nodemanager. I get the following error message in the Admin server log:
<Error> <NodeManager> <BEA-300034> <Could not execute command "getState" for server "******" using the node manager. Reason: I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found).>
I get the following message on the admin console:
For server ******, the Node Manager associated with machine ******-machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
I can start the managed server using the "startMangedWeblogic.sh" without any issues.
Any help on this would be greatly appreciated.
Thanks

one more thing to add:
I get the following error in the Managed server log:
<I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:74)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:46)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:239)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:170)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:104)
at weblogic.nodemanager.server.Handler.run(Handler.java:64)
at java.lang.Thread.run(Thread.java:595)

Creating a new web server instance using script

Hi
We have to create 10 instances of sun one 6.1 web server again and again. Creating them from GUI and deleting them after testing is going to be a time consuming process. Is there a way to copy an existing instance with the help of some command line tool or shell script (If we know what enteries should be there in each configuration file). Any help will be appreciated.
Thanks
Anoop

6.1 unfortunately does not provide a way to create instances through command line tool. With 7.0 (soon to be released as Beta in the coming weeks) will have a full fledged command line tool for all server administration tasks
meanwhile, as a temporary work around one could do the following within a shell or perl script.
[ this approach is totally not supported by Sun. You are on your own ]
1. cd INSTALL_ROOT
2. copy https-HOSTNAME to https-test (/bin/cp -Rf https-HOSTNAME https-TEST) - assuming TEST is the new instance name that you want to create.
3. use a script to edit the following files and replace 'https-HOSTNAME' to https-TEST in all occurrences.
list of files to change:
start , stop , reconfig , restart , rotate
config/magnus.conf
config/server.xml
4. finally, you can use 'HttpServerAdmin' to change the listener port, security settings etc
./bin/https/bin/HttpServerAdmin -h
http://docs.sun.com/source/819-0130/agcmdln.html
for eg ( i would do something like this )
(to create instance https-TEST from default server instance, assuming you do not have special ACL file configured in the default instance, I would do something like )
use a perl script to copy https-HOSTNAME to https-TEST
(/bin/cp -Rf https-HOSTNAME https-TEST)
/bin/cp httpacl/generated.http-HOSTNAME.acl httpacl/generated.http-TEST.acl
cd https-TEST
replace https-HOSTNAME to https-TEST in following files (start, stop, restart, reconfig, rotate, config/magnus.conf, config/server.xml)
cd ..
now delete the listener socket id
./bin/https-TEST/bin/HttpServerAdmin delete -l -id ls1 -sinst https-TEST -d INSTALL_ROOT (where you server is installed)
followed by create a new listener socket id
./bin/https-TEST/bin/HttpServerAdmin create -l -id ls1 -ip ANY -port NEW_PORT -sname HOSTNAME -defaultvs https-TEST -sinst https-TEST -d INSTALL_ROOT
[ similarly, you can perform other server admin tasks using this command' ]

WLS http access logs not written to when starting WLS instance using nodemanager

When starting managed WLS instances using node manager the HTTP access logs are
not written to (the WLS log in the same directory is written to). All other functionality
of the WLS instances seem to operate just fine when started using node manager.
When we start the same managed WLS instances using a start-up script the HTTP
access logs are written to.
===
How can we get HTTP access logs to be written to when starting a WLS instance
using node manager?

I think I know the answer to this one!
I got bitten by the same bug (at least I think it is a bug). Check the location
specified for the HTTP-access log for your server instance. It is probably a relative
location, right?
According to the docs, relative paths should start from the Root Directory (see
your Remote Start config), but it seems like the BEA-programmers forgot to retrieve
the Root Directory and instead blindly writes to the process' current working
directory (CWD).
And when started by the Node Managet, the CWD = WL_HOME/common/nodemanager.
If you are as paronoid as I am (and you should be too), that directory should
not be writeable by anyone. Because my BEA installation was owned by 'bin', and
the processes run by 'beawls', I got an error message in my NM-logs pointing to
the problem. In your case, you are probably running NM as a user that has write-access
to your NM-home, and all your missing HTTP-access logs are deep, down there.
Jan Bruun Andersen

How to avoid time wastage in starting & Stopping weblogic server during development ?

It is very frustrating to stop the server and start the server for any small changes made in the application.
Is developer supposed to restart the server for for any small changes made along with the testing?
One restart(Stop and Start) activity takes more than 10-15 mins. in debug mode.
1) I make some changes then I start server in debug mode
2) I see some mistakes in my bean code
3) I change my bean.java or Impl.java
4) I make a futile effort to reload Jars and reload the page
5) It never takes my changes
6) Only changes in properties of jspx components will accept the changes at the page refresh
6) I add new component or new binding to jspx page, This will not even pay heed to re-deployment, I need restart the server
7) I work only 7 hrs a day (1 hr-lunch)! 7*60=420 mins.... lets say I make code changes 10 times a day 10*20(200) half day
is gone in just restarting server/redeploying changes.
8) So frustrating..... !!!
Que:
1) Is the developer is supposed to imagine all the errors beforehand and code so that he wont waste time in restarting?
2) How nice it would be that you just recompile the changes and you get to see your changes just by refresh...
that is why pl/sql development is so fast.
3) Is there any way to do it like that? or Are there are any quick tricks or precautions to avoid restarting the server.
4) Am I not following the correct development/deployment methods?
It will be really great help for me if you experts guide me on the practise you follow for restarting/redeploying.
Thanks
Rahul

Rahul, please tell us your jdev version!
1) this always helps! In the old days you only compiled once a day and if the compiler found an error you had to wait a whole day until you got the next chance. Do feel privileged that you can compile multiple times. A restart is not nessecary in every case, but depending on the version you hit to restart more often. You should try to find out why it takes so long and minimize this time! Using 11.1.1.7.0 i start my server in less then a minute.
2) answer depends on the jdev version, but you don't get the speed of pl/sql for wenn application development.
3) one thing to do is to define the jdbc connections used in the server or then use jndi to access the resource. This way you don't lose a minute or connection stopping the server. Next it's best to keep the server as clean as possible. Read the log when the server starts and stops you get plenty of info what takes how long. Then start optimizing.
4) no, your method is ok.
Timo

How to run two WebLogic server instances on the same machine

The setup is to run server instance A with all EJBs and server instance
B with all servlets.
I edited the weblogic.properties under myserver to include all EJBs and
create server2 under \weblogic parallel to myserver and put a new
weblogic.properties under server2 that has all the servlets aliases.
Is this the right way?
two server ran but I cannot hit the servlet.

The setup is to run server instance A with all EJBs and server instance
B with all servlets.
I edited the weblogic.properties under myserver to include all EJBs and
create server2 under \weblogic parallel to myserver and put a new
weblogic.properties under server2 that has all the servlets aliases.
Is this the right way?
two server ran but I cannot hit the servlet.

Oracle Weblogic Server Installation using the user "oracle"

Hi,
I installed two instances of weblogic server for FMW 11g on linux x86-64. One was with the user oracle and other was with the user orawls, both belonging to the group oinstall. I had installed Admin Server and created managed servers soa_server1 and bam_server1. I have issues in starting up the instance with oracle user and the instance with the orawls user starts fine. I have a separate thread going on for that issue.
I just wanted to know if there were any existing known issues when installing the WLS as oracle user ?
Cheers,
- AR

I have no issues with the oracle user. I do it all the time.
Which thread are you referring to?
--olaf

Stop weblogic server instance using nodemanager

Similar Messages

Maybe you are looking for