Hi I am new to jprofiler . My task is to profile a remote weblogic server for which i have followed the steps for remote profiling and came till sh file creation which the jprofiler creates itself. As i have read I need to start my weblogic server with this sh file .
But i am stuck up with the following error.
:Error occured during initialisation of VM could not find agent library in the absolute path ......./linuxX64/libjprofilerti.so
I can see the file in path mentioned in the error. Help needed quickly .
Thanks in advance,
Raghu dev
Likely, you're profiling a 32-bit JVM, not a 64-bit JVM. Repeat the integration wizard and deselect the "64-bit JVM" check box on the "Profiled JVM" step. Then it should work.
uncheck the 64-bit vm option in jprofiler while creating the profiling settings. this should solve the issue
Related
Runing the Build and Run Iot Edge Solution in Simulator stopped working suddenly, and the log builds the containers and stops at this message Network azure-iot-edge-dev is external, skipping Everything was working fine 5mins ago, tried rebooting, restarting docker, iotedgehubdev, but in vain. Do you know how can I get more logs and/or resolve this problem ?
This is a generic error that is thrown for a variety of reasons.
Possible causes can be:
Proxy blocking pulling images of edgeHub and edgeAgent
A problem in the deployment.template.json (or debug template), e.g. missing brackets
Ports of edgeHub that are in use
Docker configured for Windows containers when targeting Linux or visa-versa
The Build output or IoT hub output in Visual Studio usually gives a bit more information.
Do you know how can I get more logs and/or resolve this problem ?
Are you trying to debug/simulate it locally on windows 10 machine?
When you need to gather logs from an IoT Edge device, the most convenient way is to use the support-bundle command. By default, this command collects module, IoT Edge security manager and container engine logs, iotedge check JSON output, and other useful debug information. It compresses them into a single file for easy sharing. The support-bundle command is available in release 1.0.9 and later.
Run the support-bundle command with the --since flag to specify how long from the past you want to get logs. For example 6h will get logs since the last six hours, 6d since the last six days, 6m since the last six minutes and so on. Include the --help flag to see a complete list of options.
sudo iotedge support-bundle --since 6h
By default, the support-bundle command creates a zip file called support_bundle.zip in the directory where the command is called. Use the flag --output to specify a different path or file name for the output.
Incase if you are looking to debug the modules locally on VS2019, VS Code below documentations will be useful.
Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge and
Use Visual Studio Code to develop and debug modules for Azure IoT Edge
Please share the complete logs if the above doesn't help.
I have this issue when trying to start a project from within Visual Studio when it's not running in administrator mode. I always forget and end up with this error. Same goes for if I run "iotedgehubdev.exe setup" from a command prompt. It only works when the command prompt is running in administrator mode.
i have installed apache tomcat 8.5 one month ago with java 1.8 on Windows Server 2008 and it works ok.
now the service is stopped and i'm not able to restart it from apache configuration or Windows Services . It is always stopped.
i got the following error: "service terminated with service specific error incorrect function".
ther error in Windows Event viewer does not saying nothing more:
even its details tab:
What can i do?
I was trying to install Apache Tomcat/8.5.31 as Windows service and i was also facing the same error.
For me what finally worked was following these steps. Go to Tomcat installation directory's bin folder. You will see two EXEs (tomcat8.exe and tomcat8w.exe). tomcat8w.exe is a GUI application for monitoring and configuring Tomcat services. Double-click it and then go to Java tab
1) Enable the check box for Use default
2) In Java Classpath: section, specify the path to bootstrap.jar and tomcat-juli.jar. These should be present in your tomcat installation's bin directory itself:
<path_to_tomcat_installation>\bin\bootstrap.jar;<path_to_tomcat_installation>\bin\tomcat-juli.jar
To get more help, you may check the log at the following location provided you installed your Tomcat as Windows service using default LogPath option as described in the documentation: %SystemRoot%\System32\LogFiles\Apache
UPDATE: In another recent installation, i noticed that despite having configuration settings exactly similar to another working setup, i was still getting Incorrect function error under System log in Event Viewer. This time, i had to uncheck the Use default option and had to explicitly provide path to jvm.dll as shown below:
Java Classpath setting was still required as explained above.
Currently I have a Windows Server 2012 R2 Datacenter running Tomcat 9 & had the same problem. This happened after I ran Windows updates & restarted the Server.
Error messages below. (The blanked out text is my private data.)
Error showed when attempting to start the service.
Error in System Event Log
The following steps fixed the issue...
Navigate to your tomcat9w.exe Location: \Tomcat9\bin\
Right click your tomcat9w.exe and select Run as administrator.
Select the Java tab. Select Use default, Apply, & OK
Start your service.
Note: I unchecked the "Use default" box after I was able to get the service running correctly. Because I wanted to retain my existing configuration. Going forward the service has continued to work correctly.
Hope this helps!
I was also facing some issue with Tomcat 9 and Java 13 (tried all previously mentioned solutions but nothing worked). When I downgraded it to Java 11 and Pointed the jvm.dll from JDK 11 my issue got fixed (or Use Default if JAVA_HOME is set to Java 11).
In my case the only way I could get it to work, was to go to the "Startup" tab and change "Mode" from "JVM" to "Java". After that, it started fine and was able to confirm that by visiting the localhost.
(Definitely not an expert)
I fixed this issue by (re)installing Java. I was using the Java SDK downloaded by IntelliJ. Although I was able to direct Tomcat to that download during installation, it returned this "error service terminated" message at runtime. Instead I installed Java SDK directly from Oracle, Tomcat found the installation immediately during installation (I didn't need to point it), and this error disappeared.
It's possible the Java installation by IntelliJ was incomplete somehow and is the underlying cause of the problem, but I am definitely not an expert.
I fixed the issue by reinstalling Tomcat:
Search the Command Prompt icon
Right-click on it
Select Run as administrator
Change the folder to the bin folder of Tomcat
Execute appserver uninstall
Execute appserver install
It solved my problem.
I followed the below steps to fix the the above issue. it may help if someone still face the same.
Step 1. opened the installation directory : tomcat9w.exe Location: \Tomcat9\bin\
Step 2. Browsed the Jvm.dll path under "Java Tab" in Tomcat where it has installed
Step 3. Run the service but still faced same.
Step 4. then, Opened ""C:\Program Files (x86)\Apache Software Foundation\Tomcat 9.0\bin>startup.bat --> entered.
Finally it got fixed .
No information found for this. Is there any way to start weblogic in profiling mode? Or, maybe, it's activated by default?
Profiling action can be initiated 2 ways
1) Pass the profiling action while you execute the startWeblogic.sh. Following parameters can be appended
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8010
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
2) The same parameters can be appended from startup tab in weblogic server
Here's what i got. Mainly focused on remote profiling using NetBeans
generated remote profiling package for target OS and JVM architecture (32 or 64 bit) (Netbeans -> Profile -> Attach Profiler -> Change link, select OS and Java platform -> click "Create a remote profiling package" link)
copy this package to target machine
execute calibration script (calibrate.bat / calibrate.sh (chmod +x))
add specific argument to java_otps with path to this package
-agentpath:PathToProfilerPackage\lib\deployed\jdk16\windows-amd64\profilerinterface.dll=PathToProfilerPackage\lib,5140
restart weblogic. Startup will be interrupted until remote profiler connected
connect to a server using NetBeans profiler. Weblogic startup will continue.
However, i still can't download heap dump (which is available when attaching to local java.exe Weblogic process) but that's something.
Please help me how to connect JProfiler from windows machine to remote Virgo Jetty Server which is running in linux server.
Below are the steps I am following
From Choose Integration Wizard selecting Eclipse Virgo(Next)
Then I am selecting option of on remote computer with Linux platform(Next)
Then I am selecting JVM vendor Version etc (Next)
selecting option Wait or a connection from JProfiler GUI(Next)
Providing remote hostname:port(Next)
I was stuck at specifying remote installation directory
Here we didnt install JProfiler in our linux remote environment but we have server running there.I have seen option like If JProfiler is not installed,you can create archive and that contains profiling agent and extractit in above directory.Asking folder where to create Archive.
Can you please help what exactly this means what I need to do to create archive .Only thing I have done is installed JProfiler evaluation version in local machine and profiling local server.
Please help and let me know any additional information is required..Thanks in Advance..
If you select the option to create an archive in the integration wizard, JProfiler will create a .tar.gz file that contains the libraries for the profiling agent. You transfer that archive to the Linux server and extract it somewhere, e.g. to /home/myname/jprofiler by calling
mkdir /home/myname/jprofiler
cd /home/myname/jprofiler
tar xzvf /path/to/jprofiler_agent_linux-x64.tar.gz
In the integration wizard, specify /home/myname/jprofiler as the remote installation directory.
I can't figure out where I am going wrong. I have Eclipse Indigo, JBoss 7.1, JBoss Tools installed. I have this configuration working on my Windows7 64-bit system. I am attempting to set up a co-worker's Windows XP 32-bit machine with the same configuration but am not able to get the server to launch. I have configured the server but when I attempt to start the server, I get an error indicating that it was unable to start the server but there is no specific error listed.
I am able to start JBoss from the command prompt using the standalone.bat file.
I am able to configure the standalone.xml file from within Eclipse. I have confirmed this by checking the file in the standalone/configuration directory.
When I attempt to publish the project from within Eclipse, it does not publish.
Nothing gets written to server.log
The startup parameters match what I have on my computer.
I can't figure out what I am missing. Any suggestions would be appreciated!
Edit:
I have done some more checking. I am able to publish to the server and I am able to start the server (with the published application) fine from the command prompt. That part works. When I attempt to start the server from within Eclipse it gives me "Server JBoss 7.1 Runtime Server failed to start." It never writes anything to the console tab in Eclipse either so I can't tell why it is failing to start.
Also in the Servers tab, there is an entry called "Server Details". When I expand that entry, it says "Not Connected".
The answer to my problem is that Eclipse had be configured to use the java JDK, not the JRE. As soon as I switched over to use the JDK it started working fine. For some reason JBoss will start under 64-bit windows with the JRE but under 32-bit you need to use the JDK. I found the answer here: https://community.jboss.org/thread/169097