Is there any way to start Web Sphere 8.x in debug mode through Ant script?
I see nothing is related to it in the documentation here. Just wondering if someone has way arround to do this.
As soon as I start it in debug mode, it display "Listining for transport dt_socket at address: 7777" and then nothing happens afterwards.
Server operations available as options: create, start, stop, status, and package.
"debug" works as an operation too, just like bin/server debug server-name
Related
I am executing performance tests using jmeter+docker setup. When I try to run the tests after docker set up, It starts execution but freezes at
INFO o.a.j.p.h.s.h.LazyLayeredConnectionSocketFactory: Setting up HTTP TrustAll Socket Factory
This is before starting the first test.
If I kill the process and restart the execution, It will move from above step, execute first thread group and freeze again on second thread group.
FYI - I have added trust certificates and invoking them using command line
-Djavax.net.ssl.keyStore=path of certificates
-Djavax.net.ssl.keyStorePassword=password
Can anyone please help me figuring out what am I missing here ? TIA.
Unfortunately your question doesn't provide sufficient level of details.
Try the following:
First of all try reproducing the issue without Docker virtualization, if it cannot be reproduced on the host machine - double check your docker setup, inspect docker logs, container logs and so on.
If it can be reproduced without Docker:
Increase JMeter's logging level to DEBUG
Add the next line to system.properties file
javax.net.debug=all
it will enable debug output for SSL/TLS connections
When JMeter "freezes" next time take a thread dump
This way you will know at which line of code JMeter gets stuck so you will know the exact reason.
I'm a Quarkus newbie and using Eclipse with the Quarkus plugin.
Whether I start manually with mvnw clean quarkus:dev or using an Eclipse Quarkus launch configuration, the application always seems to run tests.
I see something like
Listening for transport dt_socket at address: 62021
Press [h] for more options>
Tests paused
Press [r] to resume testing, [h] for more options>
Press [r] to resume testing, [o] Toggle test output, [h] for more options>
and nothing happens for a while until then I see the Quarkus logo, my log messages etc.
Perhaps I haven't read the documentation thoroughly enough, but I found no configuration to switch this off and start the application straight in dev mode.
Can someone help me?
What you see in the output is continuous testing. Works in conjunction with hot reload where tests run immediately after code changes have been saved.
More information you can find here: Quarkus - Continuous Testing
Continuous testing can be disabled via configuration property quarkus.test.continuous-testing=disabled. The default mode of continuous testing is paused. See: Quarkus - Continuous Testing - Configuration
I have been working on Jmeter from quite sometime now and I have been trying to use Jmeter Plugin SSHMon , but I am stuck as even after configuring it completely it simply says "Waiting for samples" and does not render anything on the graph.
I am trying to execute the command on the Linux box and have passed all the relevant parameter for collecting the stats. But still I am not able to capture anything. Any help or pointer will be appreciated.
I also tried connecting the Linux box using Putty and executing the command and the command does work, but when I execute the test the Plugin does not capture anything
Please find the ScreenShot attached
In the majority of cases the answer lives in jmeter.log file, check it for any suspicious entries, if something is not working most probably there will be a cause identifier there. Also make sure to actually run your test as SSHMon is a Listener and relies on Sampler Results so if your test is not running - it will not show anything.
As an alternative you can use JMeter PerfMon Plugin which has EXEC metric so you can collect the same numbers, however PerfMon will require Server Agent to be up and running on the remote Linux system.
After a lot of trail and error I was able to get SSHMon working. Please find the solution below
Ok Guys, so its a lot tricky as you would expect. So I thought that installing the Perfmon Agent on the server made Jmeter collect the stats for SSHMon listner but there is a catch to it. To start off I will let you know that installing the Perfmon Agent on the servers and then using the plugin to collect the stats works smooth. You can definately use this option. But it requires for the Agent to be started everytime you want to run a test and if there are multiple servers you will have to restart on those server. Not sure if there is a way to automate the restart of the agent or to keep it running for a longer time. If you are lazy like me or you have installation restriction on the servers or hell bent on using SSHMon then what you need to do is stated below.
You should always start Jmeter with the command line argument --->
jmeter -H "Proxy" -P "Port" -u "UserName" -a "Password"
The arguments are self explanatory. Once you do that Jmeter will be launched, but wait its not done yet!!
When you start executing your test the command prompt in which you have started the Jmeter will prompt for Kerberos UserName [YourUsername]: you have to again Enter you username here, which you use to start Jmeter or login to you system. Followed by this it will prompt you to enter kerberos Password for your UserName: Enter Your Password and Voila!!
The thing is, it happens in the background so you never see what is happening on the Command Prompt you used to start Jmeter.
Please see below for more clarity.
Kerberos Username[UserName]: UserName Kerberos
Password for UserName: Password
I have attached the screen shot as well in the question as well as here showing the issue being resolved. Please refer "Solution ScreenShot". Cheers!!
Hope this helps Guys!! :)
Also please hit up for the answer if it helps you!! :)
Can anyone explain how to enable debug logging in Eucalyptus 4.0.0 properly?
I set LOGLEVEL="DEBUG" in /etc/eucalyptus/eucalyptus.conf
Then I restarted everything but logs still only show INFO, WARN and ERROR.
You're on the right track. Setting LOGLEVEL="DEBUG" in eucalyptus.conf is valid for C-based components, and Java-based components which have not yet fully bootstrapped. When you set DEBUG in eucalyptus.conf, you'll need to restart the affected components on just that machine. So for example, on the NC, you would need to issue a restart, eg, "service eucalyptus-nc restart" in order to pick up the new value.
For the Java components, in particular after they've bootstrapped, you set the cloud-wide PROPERTY thusly:
euca-modify-property -p cloud.euca_log_level=DEBUG
and the output will tell you what the property was, and what is has become, if done correctly.
For example:
# euca-modify-property -p cloud.euca_log_level=DEBUG
PROPERTY cloud.euca_log_level DEBUG was INFO
Once you've set that, you're good to go. No need to restart any of the Java components, anywhere in the cloud.
I am debugging a lotus script agent using debug a lotus script. Agent is debugging fine but I have another lotus script agent inside that and my debugger is not going to that code line by line.Please help me how to do this.
Thanks in advance.
An agent, that is called in script from another agent runs in the background. These agents can not be debugged easily. If the called agent runs on the server, you can use the remote debugger, to debug that agent: you have to enable it in the server document, start the remote debug task, and enable remote debugging in the properties of the called agent. Then you have to be fast. You define a delay that each agent waits for the debugger to attach, before it really starts with its code. During this time, you have to start the remote debugger, open the database and select the agent to debug... Quite painful. And the normal Debugger has to be off and the agent you startet has to run in client background mode, otherwise you will not be able to switch to remote debugger...
If both agents are LotusScript and it is not needed, that they:
Run with different rights or
Run on different servers,
then there normally is no need for an agent calling another agent.
Use script- libraries and subs / functions instead, then you do not need two agents...
I recommend to you use a simple log in the second agent. You can use NotesLog (look at Domino Developer's Help), or you can write your own class as you need it.
In my apps, I use a LotusScript framework, written by me. In that framework, I have a CS_Log class, who connects to a LogAgents.nsf database and writes all in simple documents. Also, I have a CS_Document class, with a Dump method, who writes the full content of a document, for example.
The most times, debugging it's the best option. But in cases like this, I prefer to write all in a log.