Troubles with managed servers start-up in RH EL AS 3.0

Hello
So, here is a problem: after release of Red Hat Enterprise Linux 3.0 with improved
thread management ppl normally expect instant performance boost and lots of other
nice things :)
The result is that JRocket does not work with this OS release (core dumps) - posted
to respectfull group.
When using Sun SDK (both bundled with WLS 8.1 sp1 and newer one from Sun (1.4.2_02)
it is not possible to properly start up managed server from the admin console:
somehow the NodeManager does not see the end of managed server output (the last
line it sees is about binding listener to port xxx). The managed server actually
starts up and works, also in the logs on the hard drive $BEA_HOME/weblogic81/common/
.. /NodeManagerLogs/server.log all the events are logged properly.
The fact that node manager can not read logs results in the CPU polling and extremelly
poor web interface (management) performance (node manager process consumes one
of CPUs completely), the managed server is shown as RUNNING, but the operation
is still in progress, so it is not possible to stop/restart it.
May be some nice patch available :) ? Or we have to go back to RH EL 2.1?
BR
VA

You can't declare the same variables/function more than once in a given timeline. That's what all the errors are telling you. The two options that Rob identified will work.
What you can do is extend the actions frame for the length of the occupied timeline so that variables/functions you declare in frame 1 are available in all frames along the timeline. To do this, you have the code in keyframe 1 and go to the end of the timeline and choose the command to Insert Frame. You should see the timeline between the first frame and the last becomes one large white frame area.
I will often have two layers dedicated to actionscript. One for the code that lives in frame 1 that gets shared along the timeline's length, and another for the commands that are specific to certain frames only.
If you need need text to appear/type-out in different frames then you just call the function that performs the typing while sending it the text that it needs to type. If you need to type it into a different textfield, then you could pass that to the typing function as well so that it targets the desired textfield.

Similar Messages

JMS with managed servers

I have created two independent server instances, each with their own applications directory, config.xml file, etc. Now I want them to be able to use JMS to communicate with each other. It is my impression that there are a couple of ways to do this, the easiest of these being to add the server instances as managed servers to the same administration server so they exist in the same domain, then set up a single JMS configuration for that domain. Is this right?
          If so, how do I set the administration server for an independent server instance? Must I also explicitly change its domain to match that of the administration server?
          Or is this not possible and I need to use a messaging bridge?
          Thanks in advance.
          David

Hi David,
          I'm not sure, but I don't think you can set up an admin server for an "independent server instance". I think all servers in the domain are either a "managed server", or an "admin server", where managed servers get their configuration from the admin server. Regardless, with the "domain" approach, I assume you are leaning towards going a bit further and configuring a cluster, which would automatically allow any app on any server within the cluster to transparently lookup any resource in the cluster in the global JNDI context. All of this information is in the general documentation (not the JMS documentation).
          I think there are pluses and minuses to either approach you mention. For simplicity, if you don't need clustering features, you might simply want to try the "interop" approach and see if its good enough for your purposes, rather than going through the trouble of setting up an admin server and a cluster:
          http://e-docs.bea.com/wls/docs81/faq/interop.html
          In this approach, cross-communication always involves references the remote server's URL at some point, but this URL might be specified via configuration (MDB, bridge, SAF, foreign dest all provide ability to specify a URL).
          Hope this helps,
          Tom

Best way to make managed servers start up on machine startup?

I had thought that if I used NodeManager to start servers from the admin console, if I rebooted the computer, and my RC scripts brought up the NodeManager (and AdminServer), that the NodeManager would note that the managed server had been in a running state before, and that it should be automatically restarted.
In my testing, it doesn't do that. I filed a support case to ask about this, and they concurred, saying that the NodeManager won't do that for me.
So, is the best strategy for starting up managed servers at system startup to write a wlst script that runs after NodeManager startup that tells the NodeManager to start the managed servers? Or is there a way to make the NodeManager automatically start the managed servers?

If it matters to anyone, I tried writing a WLST script taken directly from examples that connects to the NodeManager and starts up a managed server, but it didn't work (I don't have the text of the error anymore). However, a similar version that connects to the AdminServer worked perfectly fine.
At this point, however, I'm not sure that I want to do this anyway. After a server restart, it's good to have the NodeManager and AdminServer automatically start, but I'm examining whether the ManagedServer startup should be automatic. I'll have to think about it.

Trouble with managing songs manually on 2 computers

I usually manually manage my songs on my iTouch so that i can add songs from different computers and i won't only have songs synced from one computer.
However after buying iPhone4, I've been having trouble with doing the same.
Even when i have already ticked the "manually manage music and videos" box on my computer, the box will be unticked when i plug it into another computer. And when i tick the box it says that i have already synced to one iTunes library and i need to erase and sync it to that computer.
So what is the point of MANUALLY managing my music and videos when i can't do so without erasing everything? I don't usually have problems with this on my iTouch.

Incorrect. Up until extremely recently, you'd do all your Syncing on one Mac, but could still plug your iPhone into another Mac to manually drop music/videos onto it (as long as the Manually Manage option was checked while on your main Mac.)
I'm not sure if it was an iTunes update or an iOS update that killed this fantastic feature, but something sure did. Now if I have some tunes on my home (secondary) Mac that I want to toss onto my iPhone before leaving for work in the morning, I can't! Argh!
Huge killer.

Configuratione exception with managed servers beta 2

Hello
I have downloaded the WLS 6.0 beta 2 version.
I did the following steps to start a managed server
1) I started the Default Admin server
2) I created new server called "testserver" throught default admin console
3)I saved the a)setEnv.cmd and b)startweblogic.cmd under as mydomain as a) setenvmanaged.cmd b)startweblogicmangaged.cmd
4) I edited the startweblogicmanaged.cmd and changed the -Dweblogic.name=testserver and i added -Dweblogic.management.server=http://127.0.0.1:7001
5) Opened another command window using "cmd" and I typed setenvmanaged.cmd first and then I typed startweblogicmanaged.cmd
But I get the following error messages
"Weblogic.management.configuration.ConfigurationException:admin URL: t3//127.0.0.1 with nested Exceiption" da da da da.....
I would appreciate if someone could tell me what is that wrong step I am doing. And also I have gonethrough the newsgroups and I also tried adding -Dweblogic.admin.host=127.0.0.1:7001 but still it gives the same error message
I appreciate ur response in advance
Thanks
Ranga

I am using beta-2 on Solaris
"Sanjeev Chopra" <[email protected]> wrote:
Are you using beta-1 ?
Joe Hoffman <[email protected]> wrote in message
news:[email protected]...
Sanjeev,
I get a similar problem when attempting to start PetStore as a managedserver
under the MyDomain admin server.
I have specified the following additional -D parameters in the petstorestart script:
weblogic.management.server=127.0.0.1:7001
weblogic.management.username=system
weblogic.managmenet.password=<I've tried the MyDomain pw and the petstorepw>
I get the following error on the petstore console:
The WebLogic Server did not start up properly.
Exception raised:weblogic.management.configuration.ConfigurationException: connecting to
http://127.0.0.1:7001/Bootstrap/ - with nested exception:
[java.io.FileNotFoundException: Response: '404' for url:
'http://127.0.0.1:7001/Bootstrap/'
java.io.FileNotFoundException: Response: '404' for url:
'http://127.0.0.1:7001/Bootstrap/'
atweblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:34
9)
atjava.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
atweblogic.management.Admin.getBootstrapLocalServer(Admin.java:812)
at weblogic.management.Admin.initialize(Admin.java:289)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:321)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:163)
at weblogic.Server.main(Server.java:35)
When I attempt to go to the http://127.0.0.1:7001/Bootstrap URL I get an
authentication
challenge. I've tried the Mydomain and Petstore credentials, but neitherwork.
Suggestions?
Thanks
Joe Hoffman
Denver, CO
"Sanjeev Chopra" <[email protected]> wrote:
I don't see anything wrong in your steps. Unless there is something which
we
are missing in your environment, this could be a bug in beta-2.
However, i have verified this with a recent internal release and do notget
any error. So this will be fixed as a part of the general release laterthis
month of WLS 6.0.
Can you post the complete error message with the stack trace which youget
at startup of the managed server ? It may throw some more light on whats
going on.
ranga <[email protected]> wrote in message
news:[email protected]...
Hello
I have downloaded the WLS 6.0 beta 2 version.
I did the following steps to start a managed server
1) I started the Default Admin server
2) I created new server called "testserver" throught default admin
console
3)I saved the a)setEnv.cmd and b)startweblogic.cmd under as mydomain asa) setenvmanaged.cmd b)startweblogicmangaged.cmd
4) I edited the startweblogicmanaged.cmd and changedthe -Dweblogic.name=testserver and i
added -Dweblogic.management.server=http://127.0.0.1:7001
5) Opened another command window using "cmd" and I typed
setenvmanaged.cmd
first and then I typed startweblogicmanaged.cmd
But I get the following error messages
"Weblogic.management.configuration.ConfigurationException:admin URL:t3//127.0.0.1 with nested Exceiption" da da da da.....
I would appreciate if someone could tell me what is that wrong step I
am
doing. And also I have gonethrough the newsgroups and I also tried
adding -Dweblogic.admin.host=127.0.0.1:7001 but still it gives the same
error message
I appreciate ur response in advance
Thanks
Ranga

Anyone else having trouble with .Mac servers?

I can get nothing at the moment from the iDisk with a browser; not even from the Sites folder with the old homepage url. One error message I receive is actually a 403:
Even images used in previous posts here, hosted on the iDisk, are not rendering:
http://discussions.apple.com/message.jspa?messageID=7506050#7506050
Anyone else having difficulties?
P.S. ...and now this error:

.Mac to shut down Wednesday in advance of MobileMe launch
According to a .Mac support page, and Macworld the .Mac service will be taken offline at 6 p.m. PT on Wednesday, July 9.
There is a lot of new info here about any help we may need, and what all has been going on:
http://www.apple.com/support/dotmac/
http://www.macworld.com/article/134325/2008/07/mobileme.html?t=232
Look at the +System Status+ to the right of the page.
MobileMe Launch 7/9/2008, started at 8pm PT
With the exception of the new web apps, all of the following services are available: Mail, iChat, iDisk, Sync, Back to My Mac, and all published pages, including Galleries and iWeb sites.
The MobileMe web apps will be available as soon as possible.
+System Status:+
Recent History
07.08.2008:: 2:45PM - 03:15PM PT
".Mac members experienced difficulties viewing published pages. Normal service has been restored. We apologize for any inconvenience."

Hi Guys and girls, I am having trouble with photoshop just starting up randomly

Every hour or so Photoshop just launches for no reason at all - I can be watching a movie so it's not something I'm doing whilst at the computer - any help on this matter would be most appreciated - I think I've changed a setting accidentally or uninstalled something I may have needed?
Any help on this matter would be so appreciated.
Sincerely
Matty

Contact the app developer for their advice.

Starting cluster fails, managed servers can't seem to connect to admin serv

I have been trying to run the WebLogic JPA example from,
http://wiki.eclipse.org/EclipseLink/Examples/JPA/CacheCoordination
but not having much luck on three different Linux machines,
The first issue I found was if you did not set the memory options just right, the JVM would just hang,
I am now using,
               <jvmarg value="-XX:PermSize=512m"/>
               <jvmarg value="-XX:MaxPermSize=960m"/>
with JDK 1.7_17, not sure if there are better options...
The 3 servers are started using (each with different port, all server run on the same machine, as with the admin server),
<java classname="weblogic.Server"
fork="true"
failonerror="true">
<jvmarg value="-server"/>

               <jvmarg value="-XX:PermSize=512m"/>
               <jvmarg value="-XX:MaxPermSize=960m"/>
<env key="PATH" value="${env.JAVA_HOME}/bin:${env.PATH}"/>
               <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
<sysproperty key="weblogic.Name" value="server1"/>
<sysproperty key="bea.home" value="${JEE_HOME}"/>
<sysproperty key="weblogic.management.server" value="${JEE_HOST}:7001"/>
<sysproperty key="weblogic.management.username" value="${JEE_USER}"/>
<sysproperty key="weblogic.management.password" value="${JEE_PASSWORD}"/>
<sysproperty key="java.security.police" value='"${JEE_SERVER}/lib/weblogic.policy"'/>
<sysproperty key="weblogic.RootDirectory" value="${JEE_DOMAIN}"/>
<sysproperty key="weblogic.Stdout" value="server1.log"/>
<sysproperty key="weblogic.Stderr" value="server1.err"/>
<classpath>
<fileset dir="${JEE_SERVER}/lib" includes="weblogic.jar,weblogic_sp.jar"/>
<pathelement location="${env.JAVA_HOME}/lib/tools.jar"/>
</classpath>
</java>
I found that the start-up would sometimes fail on some of the machines unless I used,
               <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
But on once machine this does not help either,
I also tried using unicast, but still does not start,
the admin server starts, then the managed servers start and seem to try to connect to the admin server and just never do, never get past STARTING (to STARTED in the log).
Another have any other ideas?

How are you starting the managed servers. try running the command
from /MW_HOME/user_projects/domains/bifoundation_domain/bin
nohup sh ./startManagedWebLogic.sh bi_server1 http://localhost:7001> start_bi_server1.log &
and see how it goes. make sure you have set the boot.properties files under security folder so that it wont get failed looking for username and password.
hope it helps

Starting managed servers

Hi,
Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
1. How to start the managed servers using NodeManager from the command line? Already
NodeManager configured and able to start managed servers from the Admin Console.
So from the console start/stop/kill managed servers is fine. From the command
line, if I use `weblogic.Server` to start managed server it's not using the node
manager.
2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
defaults to `nodemanager.sh`. Any details on this please ?
3. Each time we start managed server with Node Manager, it writes the output to
the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
From the documentation it looks like we can set logs directory
`-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
the log file name also?
4. Where is the location of the java applications `System.out`, if the managed
server is started with NodeManager. If the managed server is started with `weblogic.Server`
the `System.out` are printed to the console. So this enables us to redirect to
a file.
thanks
Sarva Meduri

I think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

Starting managed servers after rebooting

Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

I think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

Node Manager Not Starting Managed Servers

I have nodemanager configured to restart managed servers automatically upon reboot but when I physically restart the 2nd node none of the managed servers start and there are no errors. Steps completed and verified....
1) Nodemanager.properties has domain path and 'crashrecoveryenabled' set to 'true'
2) managed servers have autorestart set to 'true' and -Xnohup parameter added to startup arguments.
3) Boot.properties files ave the username and password (encrypted) to start up the server.
Here is the nodemanager.log file and you can clearly see it is grabbing the startup files. It almost looks like the server files are trying to get loaded before the nodemanager port is available but I see no errors. Any ideas?
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Working directory is "C:\bea\user_projects\domains\QA10311">
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Server output log file is "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\logs\WebProxyServer2.out">
<Dec 28, 2009 9:47:09 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<Dec 28, 2009 9:47:16 AM> <INFO> <Loading identity key store: FileName=C:/bea/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Dec 28, 2009 9:47:18 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <ACR2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ACR2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <CommandNet2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\CommandNet2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <FPCE2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\FPCE2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <MQServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\MQServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <PortalServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\PortalServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <ShoppingCart2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ShoppingCart2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <webapp2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\webapp2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WebProxyServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WUA2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WUA2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:27 AM> <INFO> <Secure socket listener started on port 5556, host qaportal2.FCQA.COM>

Hi,
Entries in nodemanager.properties looks fine, but how are you testing this functionality?
If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
This has worked for me...!
Thanks,
Ranjan
http://www.middlewaresupport.wordpress.com

Mail is not connecting with pop servers

Question 1.- I have two email addresses that I manage with Mail. Both are POP. Suddenly Mail stopped connecting with both of them. I erased an account and can't set up the new one because it gives me an error message to check my user name and password. On the other hand, my iphone is working fine with both servers. Support people at one of the providers couldn't help me.
Can somebody help me?
Question 2.- When I set up my Prodigy account, it automatically shows as "Yahoo POP". Prodigy has nothing to do with Yahoo so, anybody knows why this happens?
Thank you!!!

Okay, now we're a bit further... I hope...
First,
Just tried and now I can't send anything from the server Tagra from my iphone either!! What a mess!! It's telling me the server does not allow relaying.
that's easy: You must be trying to send email with or from a different address (e.g. [email protected]) by using the Tagra SMTP server (mail.tagra.com.mx). Most SMTP servers don't like that and protest.
So, on your iPhone, go to Settings and the Prodigy and any other non-Tagra account, and make sure that not mail.tagra.com.mx but the correct outgoing mail server is chosen! Only your Tagra account must use Tagra servers, no other one!
For iPhone setup see e.g. this Prodigy iPhone setup.
That should work again.
Now back to your Mac.
Your trouble could be the result of some hiccup in a DNS server. So, you'll make one addition and one change to be safe. No worries, it's nothing critical, I'll try to explain here:
1) I guess the current DNS entry in your Mac (192.168.1.254) is your router's IP address, and in the router are DNS addresses stored. To be safe, please add in Network -> Advanced -> DNS under DNS server also these two numbers: 200.33.146.193 and 200.33.146.201, above the old number, and each one in its own line. These two are some of Prodigy's DNS servers. So, it should read now:
200.33.146.193
200.33.146.201
192.168.1.254
Okay! This will make sure that your Mac uses Prodigy DNS servers, no matter what's in your router, but the router stays in as well.
2) In Apple Mail -> Preferences -> Prodigy account, replace the mail server names in text format with their IP addresses in number format. It's the same, but avoids certain trouble with DNS servers.
For the Incoming Mail Server, make it: 148.235.52.179
For the Outgoing Mail Server, make it: 148.235.52.32
Again, it's the same servers, only in number format. And you can always change it back, only we have reason to hope that with the numbers it'll work.
All other settings incl ports etc must remain the same, e.g. the same as in the iPhone instructions.
Now close all apps, and restart the Mac.
And now try if Apple Mail works for your Prodigy account... I'm crossing my fingers...

Managed Servers not starting with options configured in config.xml

Hi,
I Installed an Weblogic 10.3 on a Red Hat system and i configured an domain and 2 managed servers.
I configured the servers with some java arguments like this:
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m
I do see in the ${DOMAIN_HOME}/config/config.xml the managed servers with the settings that I have configured it via the Web Gui Admin Console.
Now I want to start the Managed Servers with the following command:
+cd ${DOMAIN_HOME}/bin+
+./startManagedWebLogic.sh managed-server1 http://admin:port+
When i check the console, I don't see the correct JVM settings! Also other options that I configured in the Web Gui Admin Console, don't appear in the logfile.
The JVM settings I see, are those from the AdminServer.
How can I change/fix this?
Please help.
Kind regards,
Werner

Hi,
Please add the changes to the startup script startManagedWeblogic.sh.
You can add the memory args settings as "-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m"
Please let me know if it dosent fix.

Problem Starting Managed Servers

Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring up my Managed
Server its not reading the command line arguments which I supplied through the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
are not read and so I am having errors like Unable to load libraries, etc.
Also when I saw the log file for managed server the class path and the arguments
are printed in a different way than I have set. I dont know if thats a problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the console is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I havent typed that
in the console. Has any one have experince with setting the command line arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatly appreciated.
Thanks,
Kiran

Seems a method signature does not match with the implementation in the
library either due to namemangling or incompatible versions of libraries.
You are loading your own custom native libraries for security.
Best would be use the default startManagedServer -- once the server has
started, copy and paste the entire value of java.library.path into the
startup arguments for Remote start.
For instance in my server log file:
####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
<main> <system> <> <141034> <Java system property: java.library.path =
/home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
I would set that as the arguments :
-Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
usr/lib
If this does not work, then java for some reason is not taking library paths
set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
of arguments to java. Another thing is before starting the NodeManager, set
the LD_LIBRARY_PATH to point the library directories and see if this helps.
regards,
Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
>
Sabha,
I am trying to start the managed server via remote start. After readingyour reply
I have cleaned up the argument list for remote start. Now I am gettingaltogether
a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
I dont know why I am having trouble to do the same through the remotestart).
>
I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
to the argument liist which I did. Below you can find the exact error Ihave got:
>
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
referenced symbol not found
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
va:52)
>
atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
9)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
l.java:208)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
rImpl.java:81)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.security.acl.Realm.getRealm(Realm.java:84)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
>
Please let me know if you need more description.
Thanks,
Kiran
"Sabha" <[email protected]> wrote:
Either you are attempting to start a managed server through its
NodeManager
for which the remote startup arguments are not correct or something else
is
wrong. How are you starting the server? The remote start is only when you
want to start the server through NodeManager and not for normalinvocation
of the startManagedServer script.
Does the server really start? can you paste the startup arguments for the
remote start of the managed server as saved in the config.xml.
What is the log generated when the managed server is startedup.
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Sabha,
The main problem is:
What ever I am trying to give in the command line arguments through theConsole:
Servers -> serverName -> Remote Start->Arguments.
is not being read during managed server start up.
I have all the libraries defined defined in java.lib.path. I dont knowwhy
its not
being read by managed server during start up. Am I missing something.
-Kiran
"Sabha" <[email protected]> wrote:
If its unable to load the performance packs, try setting
java.library.path
to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
can just copy what is in the admin weblogic.log file for the
java.library.path (make sure the paths are correct and applicable forthe
maanged server box also) and pass that as an argument as
in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server
and
managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring
up
my
Managed
Server its not reading the command line arguments which I supplied
through
the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason
these
command arguments
are not read and so I am having errors like Unable to load
libraries,
etc.
Also when I saw the log file for managed server the class path and
the
arguments
are printed in a different way than I have set. I dont know if thats
a
problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
i
c
6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
i
t
y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the
console
is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I
havent
typed that
in the console. Has any one have experince with setting the command
line
arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatlyappreciated.
Thanks,
Kiran

Start managed servers via admin console

Hello,
I have installed weblogic server, created a domain, added a managed server. All working fine. Now I want to be able to start managed server through admin console.
According to this documentation (http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/confignodemgr.html), it should all be pre-configured for development environment. But when i try start the managed server in admin console, it says "server does not have a machine associated with it." I added a machine and assigned that machine to the managed server, now it says "the Node Manager associated with machine m1 is not reachable.".
Can someone point to instructions on how to setup this on dev environment. In one of the instructions, it is suggested to change nodemanager.properties in common\nodemanager folder. But this file doesn't exist in my environment.
All i want is to start all admin and managed server with one script or with start the admin server and able to start the managed servers via console.
Thanks,

Hi,
Check from the console whether your node manager is reachable or not.
Console Path:
Machines -> <YOUR_MACHINE_NAME> -> Monitoring (tab) -> Node Manager Status (sub-tab) -> Status: Reachable
You Can follow the below link for "Node manager not reachable"
http://middlewaremagic.com/weblogic/?p=5205
Once done,check the status of the node manager.
Still even after this if the node manager is not reachable
Check the node manager logs,whether you get any exceptions
location $weblogic_home\wlserver_10.3\common\nodemanager\nodemanger.log
You can take help of the below link for trouble shooting the basic node manager exceptions.
http://middlewaremagic.com/weblogic/?p=2887
Or You can even paste the error's on this post itself,we will guide you .
Regards
FAbian

Troubles with managed servers start-up in RH EL AS 3.0

Similar Messages

Maybe you are looking for