Starting agent after VM startup

The new JDK 6 instrumentation API mentions the possiblity for "Starting Agents After VM Startup".
Unfortunately it isn't very specific: "The system class loader [..] must support a mechanism to add an agent JAR file to the system class path."
Can anybody provide me with a working example of how to bootstrap an agent from within the VM after it has started? Is it possible to load the agent directly and not from a jar file in the filesystem?
Thanks,
-dennis

Chris has an example in his blog:
http://blogs.sun.com/chegar/entry/diagnosing_deleteonexit_issues
Another example is http://blogs.sun.com/alanb/resource/MemViewer.java which bootstraps the management agent into a running VM.
Java agents must be deployed as a JAR file on the file system.

Similar Messages

MacBook will not start up after first startup session

I absolutely have no idea what is going on. I have the most updated version of Snow Leopard for my '09 MacBook. I've done every trick in the book that came with my MacBook and even done the Hardware Test. I make it past the white screen with the apple, but as soon as the second start begins it just continues to stay blue. One thing I've noticed is when I hold down the C key (I believe it's that one) and have the Mac Os X disc installed, a giant lock pops up, but I have no clue what it's for. If it's a master password I definitely don't remember. Any ideas?

That lock is for a Firmware Password or a Master Password if you have FileVault enabled. You will need to get past that in order to do anything such as repair the drive or reinstall Snow Leopard.
Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

Webdynpro application automatic start after j2ee startup

Hi ,
Is there a way to automatically start any specific webdynpro applications after j2ee startup
Oren

I guess you can write batch file for that.
Example
suppose you have a bat file which starts J2EE engine, startJ2EE.
You can write a new bat file with following commands.
startJ2EE.bat
explorer http://<server>:<port>/webdynpro/<URL as application>
Let me know if you need more help
Ashutosh

2007 Mac Book pro Shuts down at startup attempt. Tried reloading OSX and will not start up after that.

My Mac Book Pro started having issues. I tried to relaod the operating system and it worked for a moment. When I tried to do a time machine back up it failed.
Now itr Shuts down at startup attempt. Tried reloading OSX and will not start up after that.

Dr.Conga,
did you try to do a Time Machine backup from your MacBook Pro, or a Time Machine restoration to it?
Are you trying to reload your current version of OS X (10.7.4, to judge from your signature), or are you trying to reload the version of Mac OS X that came on the grey installation DVDs that originally came with your MacBook Pro?

Unable to start agent on RAC target after installation

Hi All,
I have just finised installing agent on solaris 10 RAC to be monitored by grid control 11g,but the agent will not start.
I installed the agent as the oracle user
I get this error when I try starting the agent.
-bash-3.00$ pwd
*/u01/app/oracle/agent11g*
-bash-3.00$ ./bin/emctl start agent
EM Configuration issue. /u01/app/oracle/agent11g/node1 not found.
-bash-3.00$
Please help

Hi,
Make sure that you have set all your environment variables properly before starting your agent service.
thanks,
X A H E E R

Cant start agent

Hi!
The agent went down this weekend and refuses to start. I only get this when I try to start it:
E:\oracle\product\10.2.0\agent10g\bin>emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
The Oracleagent10gAgent service is starting.......
The Oracleagent10gAgent service could not be started.
A service specific error occurred: 2.
More help is available by typing NET HELPMSG 3547.
Platform: Windows 2003
The NET HELP does not provide anything.
I have checked the different logs and nothing of use.
Any ideas?

Because Im such a nice guy, I will post the solution here :-)
I got good help from Oracle support.
We are using RAC, by the way.
First of all I had to delete all files located in:
E:\oracle\product\10.2.0\agent10g\sestows47.prg-dc.dhl.com\sysman\emd\state
E:\oracle\product\10.2.0\agent10g\sestows47.prg-dc.dhl.com\sysman\emd\upload
and
E:\oracle\product\10.2.0\agent10g\sestows47.prg-dc.dhl.com\sysman\log
After that, I was able to start the agent using:
emctl start agent
The agent are up and running this morning, but here are some solutions from Metalink if the problem occurs again:
Solution:
Article-ID: Note 434218.1
Title: Metric Collection error-Instance Health Check
initialization failed GIM-00104 LEM-00031 LEM-00033
1. Check if you have any hc_<sid>.dat file
ls -al $ORACLE_HOME/dbs/hc*
2. Stop the Database
3. Move all the hc_<sid>.dat file to hc_<sid>.dat file to hc_<sid>.dat_sic
4. Start the database
5. Change directory to the AGENT_HOME/bin directory.
Execute $emctl upload
Execute $emctl reload
The Metric collection error and errors in the emagent.trc will be gone.
Other solution
Article-ID: Note 379423.1
Circulation: PUBLISHED (EXTERNAL)
Folder: ST.EM.V10.Metrics
Topic: Metrics - Generic
Title: How to edit or disable the Health Check Metric Collection
in Grid Control 10.2
23-OCT-07 13:29:40 GMT
(Update for record id(s): 109700133)
UPDATE
======
Other solution is to disable the Healthcheck Metric For All Targets In One Shot
1. Stop the Agent with "emctl stop agent"
2. Edit the file $AGENT_HOME/sysman/admin/default_collection/instance.xmlp and change the section
<CollectionItem NAME="health_check" UPLOAD="NO" COLLECT_WHEN_DOWN="TRUE">
</CollectionItem>
to

3. Startup the agent with "emctl start agent"

Windows 7 boot camp screen goes black after windows startup screen!!!!!!

A few days ago when I tried to start my MacBook Pro in windows 7 (enterprise) I encountered a completly black screen after the startup screen.
1) Choose start in Windows 7 from boot camp menu (holding option after starting up computer)
2) Windows start up screen would appear and finish
3) For a very brief second my cursor pointer would appear and login screen would flash onto the screen, then the screen would go black
BUT
I CAN boot windows 7 in safe mode
The computer is still on when screen goes black (fan still running and i can use keyboard commands to shut down the computer)
I've been searching the Internet for DAYS to no avail
PLEASE someone help me....... ive already tried the sfc /scannow and dskchk commands in the command prompt window

Win 7 Enterprise is not supported by Boot Camp, you may or may not get it to work reliably, (I would not bother to try)
Read this document then pick a supported version of Windows for your Mac.

Could not start agent

Hi, I've managed to install SMC3.6 agent on a Solaris 8 platform but I was unable to start my agent. I get "Could not start agent" whenever i invoked the ./es-start -a command.
I've removed SMC3.6 agent and installed with 3.5 and it works. But I still prefer to use 3.6.
Do I require any patches for SMC3.6 agents?

I've tried "sh -x" like you asked me to and I get:
# sh -x
# ./es-start -aOops, I meant "sh -x es-start -a". "sh -x" should
show you every line of the startup shell script as
it's being run. But it looks like you found the
problem anyways...
couldn't load file "pkgsymon.so": ld.so.1: esd:
fatal: relocation error: file
/opt/SUNWsymon/base/lib/sparc-sun-solaris2.8/
liblaccess.so.1.0: symbol free_proflist:referenced
symbol not found
invalid command name "unordered_slice" while
executing "unordered_slice internal value"
invoked from within "source toe-basic.toe"
invoked from within "source base-$file.tcl"I'm no expert with Solaris libraries, but it looks
like the files "pkgsymon.so" or "liblaccess.so.1.0"
can't be found. You said that you had other Solaris 8
systems that run 3.6 fine: can you see where they
have those files:
find /opt/SUNWsymon -name pkgsymon.so
find /opt/SUNWsymon -name liblaccess.so.1.0
...then if they are in the right place (or exist at
all) on the problem box? And does it have a
/opt/SUNWsymon/base/lib/sparc-sun-solaris2.8
directory?
Maybe SunMC detected the wrong version of Solaris on
install or something, and either didn't install the
proper libraries, or put them in sparc-sun-solaris2.7
or sparc-sun-solaris2.9?
Does you root user have different environment
variables set (i.e. LD_LIBRARY_PATH) on the problem
box than on the ones that work?
At this point i'm just guessing: 3.6 is so new I
haven't had a lot of debugging time with it. Worst
case you can call Sun support and yell at them...
(just kidding, please don't do that :) )
Regards,
[email protected]
Hi Mike,
Found the 2 files in the /opt/SUNsymon. Checked and confirmed /opt/SUNWsymon/base/lib/sparc-sun-solaris2.8 is there. Will try touse sunchecktool to see if i need any patch fer that fella.
Anyway, about yelling at the Sun guys. That's a good one! :)
Thanks!

How can I get WebAS to not start-up after restarting Windows?

I would like to not have my WebAS auto start after I reboot windows.
I found of couple of options in Configuration tool but they did not stop it.
We have a firewall product that I cannot disable (per security policy), but I can terminate it once I get the desktop. However by that time WebAS has started and encounters blocks from firewall, and once this happens, half the time it causes my jcontrol.exe to result in NIETIMEOUT messages and once THAT happens I have to uninstall and reinstall EVERYTHING.
So, how can I configure WebAS to not automatically start-up after rebooting windows? I have searched help.sap.com and looked for options in Visual Admin and Configure tools.

Easier than it seems
Go to Administrative Tools/ Services in Windows.
Change Startup type of the services to Manual.
You can just sort by the 'Log On As' Column
".\SAPServiceJ2E"
or whatever you instance name is. You can always start the service from the MMC console after this.

Could not start Agent on a Solaris 5.10u2 x86 machine

Hi,
I installed SunMC 3.6.1 on a Solaris 5.10u2 x86 machine. Only Agent
and Concole are installed.
There's no error during installation and setup, but the agent could not be started.
# /opt/SUNWsymon/sbin/es-start -a
Could not start Agent.
After running svcs -x, I could see:
# svcs -x
svc:/application/management/sunmcagent:default has no "restarter" property group; ignoring.
svc:/application/management/sunmcplatform:default has no "restarter" property group; ignoring.
svc:/application/print/server:default (LP print server)
State: disabled since Mon Aug 21 10:41:38 2006
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)
# svcs -v
offline - Aug_21 - svc:/application/print/ipp-listener:default
offline - Aug_21 - svc:/application/print/rfc1179:default
- - - svc:/application/management/sunmcagent:default
How to solve this problem? Any help is appreciated.
Hal

Hi Hal, :)
# /opt/SUNWsymon/sbin/es-start -a
Could not start Agent.I've seen this before too. "svcadm enable/disable sunmcagent" didn't fix things. But for some reason if I started the agent interactively (es-start -ai) it worked... and I let the Agent load a few modules and verified it worked in the Console. Then once I quit out of interactive mode (thereby stopping the Agent) svcadm enable/disable and es-start/stop worked correctly again.
I had that happen to me 2-3 times now, and every time mucking about in interactive mode a bit fixed it. It must reset something in svcs.
Regards,
[email protected]
http://www.HalcyonInc.com

Pending message redelivery wait period after server startup

Hi, I have seen an strange behaviour in the way pending JMS messages are
          redelivered to MDBs at server startup.
          In my unit test I have seen that, killing Weblogic during an MDB code
          execution as expected makes the container to redelivery unconfirmed message
          at server startup. I have also seen that it's redelivered about 4 minutes
          after server is started (more info of this in thread: "Problem with
          persistent messages and MDBs" 25 October 2002)
          After a recent crash we have had on the system in wich there were a lot of
          messages pending to deliver to an MDB we saw that they were being
          redelivered just after the MDBs were deployed while system was starting. Of
          course due to the fact that some components needed by the MDB were not
          deployed by that time, a lot of exceptions were raised making messages to be
          queued again and promptly delivered wich caused more exceptions. Just a big
          mess!
          I'm tring to figure a good work-around about this, what I wanted to know is
          how is implemented the "delay" to send messages after server startup. Is it
          done by comparing timestamp of message (when did it enter the queue and
          thereby persisted on the store) with current system time?. That approach of
          course will fail if any of the messages were sent before that "delay" time.
          If this is the case and there isn't a fix for it this is what I have in
          mind:
          Each MDB will have a private attribute wich will be used to detect when
          system has completely started. By default it will be false and after a
          message is sent to the MDB the first line of the onMessage method will test
          wether system has started or not (by checking weblogic connection port i.e.
          7001. Btw. is there any better way of checking server has finished start-up)
          if not, a runtime exception will be launched that will force message to be
          redelivered (without trying to execute any MDB code), I think setting a
          proper redelivery delay i.e. 30-60 secs. will allow server to startup with
          less problems (in the situation I described above JVM crashed with an 11
          system signal)
          Any other ideas to deal with this?
          Thanks in advance.
          Regards.
          Ignacio.


Hi Ignacio,
          I think you can usually control the order in which ejb's are booted,
          through a combination of console settings and
          meta file entries. I suggest posting to the ejb newsgroup
          to find out how.
          The four minute delay you see is normal for resolving
          interrupted transactions, but I believe that an enhancement
          was put into a 7.0 SP to reduce or eliminate this interval,
          and that 8.1 has no interval. Post to the transaction
          newsgroup for more info, or contact customer support.
          Given that you referenced earlier posts on this issue, you
          probably already know how to tune the interval down to one
          minute even without the enhancements.
          There is no other delay for sending messages at system startup,
          as soon as the MDB is booted it attaches to JMS, and JMS
          starts delivering messages whose transactional state is known.
          Tom
          P.S. I suppose one way to detect end-of-boot is to
          place a startup class last in the boot order.
          P.P.S. For MDBs one alternative is to code a "sleep" in the onMessage if
          an unavailable resource is detected - this
          is hokey, but works as long as you have made sure that
          max-beans-in-free-pool totals do not come near or exceed
          available thread pool size.
          Ignacio G. Dupont wrote:
          > Hi, I have seen an strange behaviour in the way pending JMS messages are
          > redelivered to MDBs at server startup.
          >
          > In my unit test I have seen that, killing Weblogic during an MDB code
          > execution as expected makes the container to redelivery unconfirmed message
          > at server startup. I have also seen that it's redelivered about 4 minutes
          > after server is started (more info of this in thread: "Problem with
          > persistent messages and MDBs" 25 October 2002)
          >
          > After a recent crash we have had on the system in wich there were a lot of
          > messages pending to deliver to an MDB we saw that they were being
          > redelivered just after the MDBs were deployed while system was starting. Of
          > course due to the fact that some components needed by the MDB were not
          > deployed by that time, a lot of exceptions were raised making messages to be
          > queued again and promptly delivered wich caused more exceptions. Just a big
          > mess!
          >
          > I'm tring to figure a good work-around about this, what I wanted to know is
          > how is implemented the "delay" to send messages after server startup. Is it
          > done by comparing timestamp of message (when did it enter the queue and
          > thereby persisted on the store) with current system time?. That approach of
          > course will fail if any of the messages were sent before that "delay" time.
          >
          > If this is the case and there isn't a fix for it this is what I have in
          > mind:
          >
          > Each MDB will have a private attribute wich will be used to detect when
          > system has completely started. By default it will be false and after a
          > message is sent to the MDB the first line of the onMessage method will test
          > wether system has started or not (by checking weblogic connection port i.e.
          > 7001. Btw. is there any better way of checking server has finished start-up)
          > if not, a runtime exception will be launched that will force message to be
          > redelivered (without trying to execute any MDB code), I think setting a
          > proper redelivery delay i.e. 30-60 secs. will allow server to startup with
          > less problems (in the situation I described above JVM crashed with an 11
          > system signal)
          >
          > Any other ideas to deal with this?
          >
          > Thanks in advance.
          >
          > Regards.
          >
          > Ignacio.
          >
          >

How to shutdown and start agent in ODI 11g in Linux Environment

Hi Experts,
Pls any one can help me on "How to shutdown and start agent in ODI 11g in Linux Environment" and where can I find Agent.sh and Agentshutdown.sh files location in ODI 11g and parallely how can I find Odiparameter.sh file location
Thanks in Advance
Regards
Phani

Phani ,
Go to your <ODI_11g_HOME>/oracledi/agent/bin
and you will find agent.sh , agent_<standalone_agent>.sh and odiparams.sh and other agent files.
Step 1. Update your odiparams.sh
Step 2. Create the Physical and Logical Agent int your Topology using the same port_number and name provide while creating the Stand alone agent during installation ( or) create accordingly the agent in Topology with name and port number as required and make the modification in agent_<stand_alone>.sh file
Step 3. After doing so start your agent_<stand_alone>.sh
Step 4. Repeat the process 2-3 for any number of stand alone agent created on different ports and steps 1 to 3 for different Work repository
Thanks
Dev

Can't start apache after linking mod_wl_20.so in the https.conf

I get a segementation fault when trying to start apache after i have linked the apache plug-in.
Anyone ever run into this?
I fails whether the <IfModule> statement is there or not.

Appreciate your response. This is all I have done.
Installed IHS 2.0.47, copied mod_wl_20.so file to modules directory and made one entry in httpd.conf:
LoadModule weblogic_module modules/mod_wl_20.so
IHS core dumps on when tried to startup. This is all that is documented in the "Using Web Server Plug-Ins with WebLogic Server" document. Please let me know if I am missing any additional information. Thanks! i would appreciate if you can email me your httpd.conf file for my reference. Thanks!
[email protected] or [email protected]
Suresh,

Can't Start Portal After Install

After downloading and installing the of evaluation Portal 4.0 SP1, I get the following message upon startup when I enter the system password that I entered during installation:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I even tried "weblogic" for the system password and I get the same message.
What password should I use to start the server?

I've followed the directions and am experiencing the exact same problem. Brand
new installation of Weblogic server 6.1 SP2 with examples. That install is working.
Then added Portal 4.0 SP1, updated the license file and I have the same issue
with the Illegal access exception resulting in the "Fatal initialization exception"....
Hmm!
[email protected] (Bowrat) wrote:
Below listed are the common errors you run into during installation
process:
- You need to have the correct version numbers of both the weblogic
server and the portal server. For instance the portal server 4.0 (eval
copy) will only run on WebLogic 6.1 SP1. So check the edocs for
supported platforms
- Make sure you have the installed the full version of the weblogic
server (including examples)
- Finally, you need to run the UpdateLicense.cmd file to update the
license.bea under ur Bea Root
Give it a shot after u have checked all of the above three - goodluck
- Bowrat
www.Bowstreet.com
Steve Anderson <[email protected]> wrote in message news:<[email protected]>...
From: Steve Anderson <[email protected]>
Newsgroups: weblogic.support.install
Subject: Can't Start Portal After Install
References:
NNTP-Posting-Host: 209.11.114.150
X-Original-NNTP-Posting-Host: 209.11.114.150
Message-ID: <[email protected]>
Date: 13 Feb 2002 20:25:53 -0800
X-Trace: 13 Feb 2002 20:25:53 -0800, 209.11.114.150
Organization: BEA SYSTEMS Inc
Lines: 18
XPident: firewall-user
Path: newsgroups.bea.com!209.11.114.150
Xref: newsgroups.bea.com weblogic.support.install:9600
After downloading and installing the of evaluation Portal 4.0 SP1,I get the following message upon startup when I enter the system password
that I entered during installation:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I even tried "weblogic" for the system password and I get the samemessage.
What password should I use to start the server?

Scheduler exception while starting agent in odi11g

Hi,
While starting the agent,it has been started with the below exception.
After scheduling a scenario at a specified time,when i try to test the agent and update the schedule, its successful
But when i try to view the schedule,its giving error like 'Unable to connect to the agent'
Also the scheduled execution is not getting called at the defined time.
There is some Scheduler Execption i could see while starting the agent as below
OracleDI: Starting Agent ...
2013-07-04 14:29:19.604 NOTIFICATION ODI-1128 Agent PHYSICAL_AGENT is starting.
Application Server: STANDALONE. Agent Version: 11.1.1.6.3 - 08/05/2012. Port: 20910. JMX Port: 21910.
2013-07-04 14:29:23.707 NOTIFICATION ODI-1136 Starting Schedulers on Agent PHYSICAL_AGENT.
2013-07-04 14:29:24.160 NOTIFICATION ODI-1111 Agent PHYSICAL_AGENT started. Agent version: 11.1.1.6.3 - 08/05/2012.
Port: 20910. JMX Port: 21910.
Exception in thread "DwgCmdScheduler-PCS_WORKREP_PRD_NEW" java.lang.NullPointerException
        at com.sunopsis.timer.filterbased.SnpsBetweenHoursFilter.equals(SnpsBetweenHoursFilter.java:112)
        at java.util.AbstractList.equals(AbstractList.java:507)
        at com.sunopsis.timer.filterbased.FilterBasedTaskScheduleDefinition.equals(FilterBasedTaskScheduleDefinition.java:50)
        at com.sunopsis.timer.SnpsTaskManager.updateDefinitionList(SnpsTaskManager.java:94)
        at com.sunopsis.timer.SnpsAbstractScheduler.run(SnpsAbstractScheduler.java:161)
        at oracle.odi.runtime.agent.scheduler.OdiAgentScheduler.run(OdiAgentScheduler.java:138)
        at java.lang.Thread.run(Thread.java:662)
2013-07-04 14:29:24.425 NOTIFICATION ODI-1137 Scheduler started for work repository PCS_WORKREP_PRD_NEW
on Agent PHYSICAL_AGENT.
Could anyone pls advice on this
Many thanks in advance....!
Kasthuri

Hi Prasad,
Thanks for your reply.
Everything is fine there in odiparams.bat file (In windows am handling)
Physical agent test and update schedule are even successful in topology.
Facing "Unable to connect to agent" only when i try to "View schedule"
Also the scheduled job is not getting executed at the specified time.
Thanks,
Kasthuri

Starting agent after VM startup

Similar Messages

Maybe you are looking for