Iam trying to start my demo server. But when i start it iam getting the error Native Agent not found, starting Pure Java Agent with heap walking and super stacks disabled. Please help@
Thanks for all your support
I have created a support ticket and the issue was resolved by creating a weex session.
The solution is
Adding c:\WINDOWS\system32 to the system PATH and re-installing the product allowed the demo server to start successfully.
As I understand it the native agent was for older releases of Java 1.4/1.5. For Anything's by after that the pure agent will be used. Is your demo server not starting? You would ideally see the line similar to ' server started in xyz time as the last line'. What do you see in the command window?
Thank you for your reply.
When I run the start-windows.bat multiple windows are opening without terminating.
Iam not even able to close the window until I restart my system.
You should have a shortcut for the Demo Server on your desktop. Just at double click on it and it should starT. Before doing this make sure that the port 8080 is not in use already...
Port 8080 is free but still when I open iam getting multiple windows open
What version of the product are you using? And is it possible for you to take a screenshot of your command window(s)?
To help even further, open a command window, navigate to where the DemoServer is installed on your system the use the start-windows.bat. This will catch anything thrown to STDOUT and if it errors, it will capture that error message as well as opposed to simply closing out the widow.. Screen capture what is happening there. As Rich stated, it should be in a wait state after you see something similar to this as a last line:
07:55:55,713 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 24s:802ms
[LISA AGENT:A][INFO][Stats Gathering Thread][04/07 07:55:59 (666)] Starting Dispatching...
In the STDOUT output, look for errors or exceptions or stack traces. If your content runs off the top and cannot be scrolled to, then your capture area is not large enough. Please expand the capture area by going into upper left icon, rightclicking, select Properties, set Buffer Size and Number of Buffers to 999, Select the Layout Tab, Screen Buffer Size "Height" should be 999 (II have my Width at 132), click okay, go back to the upper left icon in the command prompt window, right click, select Defaults, in the Options tab, set the Command History Buffer Size and Number of Buffers each to 999, in the Layout tab, set the Screen Buffer Size "Width" to 132 and "Height" to 9999. This setup allowed me to capturethe entire STDOUT from the DemoServer. Copy this entire section of output and attach to this discussion and it will help all of us get a clear picture of the issue you are running into.
I have tried executing the batch file in my command prompt but still iam not getting any errors just multiple windows opening.
PFA of the screenshot.
Hello Jenifer, please share the DevTest/LISA version and the Windows OS you are running. This may help us to recreate your issue and to narrow down the root cause.
Iam using DevTest8.0
OS version- wIndows 8 64 bit
Very odd indeed. Unfortunately, the screenshot doesn't give much info. So let's see if the problem can be better narrowed down. Inside your CA\DevTest\DemoServer\lisa-demo-server\start-windows.bat and CA\DevTest\DemoServer\lisa-demo-server\jboss\bin\run.bat files, change the first line from "echo off" to "echo on", save and start the demo server again. This should print out each line to stdout so we can better see where the problem might be occurring. Please take a new screenshot when done.
I have edited the 2 batch files and attached the screenshot.
Apparently - based on your screenshots - the PID env variable is not set, which means that the 'wmic' command fails to retrieve the PID of this running 'start-windows.bat' instance. This needs further investigation. As a workaround you can start the Demo Server manually: Please open a Windows command prompt with administrative privileges and navigate to LISA_HOME\DemoServer\lisa-demo-server\jboss\bin. Then call run.bat, which starts the demo server.
The 'wmic' command filters the Windows process list for a running instance of this batch file and retrieves the process ID. For some reason this command appears to fail.
I agree with Ulrich's assessment. The easiest work around for now is to just start the run.bat file directly. If you'd like to do a more in-depth session as to why the wmic command is failing to retrieve the PID, we would be glad to have a support engineer reach out to you and conduct a WebEx session. Just let us know.
I have executed the jboss server run.bat an got the following.
Please find the screenshot
Also it would be useful if we can have a webex session
This is very odd. Maybe there is something wrong with the scripting environment, i.e. command SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION fails. According to https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/setlocal.mspx?mfr=true and http://letmehelpyougeeks.blogspot.be/2010/01/setlocal-in-windows-batch-file.html this can be tested by following script. Can you please create and execute a windows batch file containing
VERIFY other 2>nul SETLOCAL ENABLEEXTENSIONS IF ERRORLEVEL 1 echo Unable to enable extensions
and post the output?
PFA screenshot whwn i executed the above batch file
To get to the bottom of the issue I recommend to open a ticket with CA support and have the support team to take a look.
Since there has not been a validated answer at this point, from a Support perspective I would want to try from scratch. I would uninstall this install of the demo server, download a fresh copy, install again, and then try to bring it up. Once this is done and it still does not work, I would put in a case to Support and have them troubleshoot it over a WebEx.
As eluded to here, they could be a problem with the installed JAVA version, perhaps a port is in use, perhaps the database is corrupted and causing problems, perhaps the path has incorrect paths in it that is causing problems, etc. Other things that might be examined on a cursory look at your system would be disk space, memory usage, other programs running, etc.
Some of the top people in the organization have responded to this and we all are flying a little blind, this the request for logs, STDOUT information, etc.
Retrieving data ...