I have setup a JMeter client and server , following the instructions in the documentation .
I could successfully invoke transactions locally as well remotely .
Now I want to increase the number of JMeter servers
added the server Ip and port in jmeter.properties
made an entry in server rmi config file
started the client
When I start the server , it starts but does not refer to the rmi server config , in logs it says
jmeter.Launcher$Companion.prepareJMeterArguments$jmeter - No rmi server mapping found, using default server.rmi.localport - assuming no ssh tunnelling in effect
The command used to run server:
java -jar jmeter-corda-4.0-capsule.jar -XjmeterProperties jmeter.properties -XrverRmiMappings sample-server-rmi.config -- -s
Any config has to be modified? other then the remote_hosts and server rmi config file?
I'd say to take a look at the jmeter page on the docs to double check whether any of the config options to see if any of them have changed. (https://docs.corda.net/docs/corda-enterprise/4.4/performance-testing/running-jmeter-corda.html#running-jmeter-corda)
So this is a feature that only works on corda enterprise and NOT on corda open source, if you're paying R3 for it you should have a contact for enterprise support that should be able to help you with the small stuff like this.
Worth mentioning as well that there's new releases of corda (now 4.5) so you might want to take a look at that as well to see if your issue has been fixed already.
Related
I get:
JMX is not enabled to receive remote connections. \
Please see cassandra-env.sh for more info.
and I am not familiar with cassandra-env.sh
I tried nano /etc/cassandra/cassandra-env.sh in the terminal but from there I'm lost
By default, JMX is only enabled from local, so you can't log in remotely. To change that you need to modify the cassandra-env.sh:
https://docs.datastax.com/en/archived/ddacsecurity/doc/ddacsecurity/secureJmxAuthentication.html
Where you see:
if [ "$LOCAL_JMX" = "yes" ]; then
JVM_OPTS="$JVM_OPTS -Dcassandra.jmx.local.port=$JMX_PORT"
You'll need to change to no so that it hits the remote loop. Then you'll need to configure the following params:
-Dcassandra.jmx.remote.port=7199
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=10.101.35.37
If you want SSL then you'll need to configure that as well. JMX is just java, so it's not specific to Cassandra. The configuration is actually found in java documentation:
Remote JMX connection
You didn't provide a lot of detail in your post but I'm guessing that you saw the warning in the Cassandra system.log.
During startup, Cassandra performs certain checks to make sure that the node is configured correctly. One of the checks it performs is to verify that the JMX port is configured.
In your case, you didn't configure JMX for remote access so the WARN was logged by the StartupChecks.java class. There is no reason to be alarmed by the message. It is completely fine to not allow remote JMX access, particularly since you are most likely just trying Cassandra out for the first time.
Remote access isn't necessary for Cassandra to function. Unless you plan to run management commands like nodetool remotely, it's perfectly fine to leave it as-is. You will still be able to run admin commands locally on your Mac. Cheers!
I'm using both JIRA and Confluence on the same server, running on Windows, using Apache Tomcat.
I have two domains pointing at the server, jira.company.com and confluence.company.com.
JIRA is running fine on port 80 in the Apache Tomcat instance, and I can get to that on the JIRA.company.com domain just fine.
Confluence is currently running on port 8090 on the same machine. What I'm trying to do is get Confluence working on the confluence.company.com domain.
Most of the documentation I can see is about configuring virtual hosts and reverse proxies in httpd.conf, however in Apache Tomcat all I have to work with is the server.xml file.
I understand I can add another host to the JIRA server.xml file to point to a different docBase for Confluence, but I have a feeling this breaks Atlassian's own recommendations found here.
When I add an additional host entry into Confluence's server.xml it's ignored, and the confluence.company.com domain sends me through to JIRA.
I've done some searching and found similar questions but they don't seem to apply to my configuration - they all mention httpd.conf which isn't present on my server.
My questions:
Can I run Confluence on the subdomain by adding an extra entry in JIRA's server.xml? If possible, is this bad?
Is there another way to get my Confluence Apache instance listening on port 80 but on it's own domain name?
I can do all this on IIS with my eyes shut, but in Apache/Tomcat I'm a little lost. Thanks in advance!
Tomcat is not really meant to directly handle incoming requests as usually an Apache or other proxy is put in front of it to hide the ports and provide other useful features you would need for Single Sign On etc. Note that there is a difference between the Apache Webserver, which is commonly only called "Apache" and "Apache Tomcat", which is only an application server made by the Apache Foundation community and named "Tomcat". Tomcat only supports basic webserver functionality.
In any case, you can use the IIS as a webserver and proxy to forward the requests and at the same time hide the ports of the applications. I personally haven't used IIS but Atlassian offers a thorough explanation for the Confluence and/or JIRA integration with IIS as a proxy: https://confluence.atlassian.com/adminjiraserver071/integrating-jira-applications-with-iis-802593039.html
The page covers JIRA for the most part but section 4 also has additional information if you want to hook up both JIRA and Confluence on the same server, which is exactly your use case.
the request from ihs is passed to plugin then to the application server and server received it.there is no cluster environment here.the server is up and running fine.But the response is not going back to plugin.how to troubleshoot?
(I would have made this a comment, but I don't have enough rep points).
You may need to engage IBM WebSphere Support to assist with this, but typically, for that type of issue, you would need to trace both sides of the connection (IHS plugin and WebSphere). Specifically,
Set LogLevel="Trace" in the plugin-cfg.xml
Set the following trace spec on the AppServer:
=info:com.ibm.ws.webcontainer=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all
Reproducing the failure and reviewing the http_plugin.log and trace.log may provide some clues.
Do you receive some type of error in the browser? timeout? Is there anything (firewall, proxy) sitting between the IHS server and WebSphere AppServer?
It could be DNS problem with your WebSphere server. Can you please let us know about your IHS and plugin. Is it installed on same server where WebSphere is or on different server? If IHS and plugin is on different server just check that WebSphere server is able to resolve the IP address of IHS server using hostname. If not try to update host file with IP and hostname of your IHS server. It should work.
Does the client or the plugin not getting the response? Will that the request result in secure connection (i.e HTTPS/SSL...)?
The WAS server should extract most of the ports correctly if IHS/plugin is used in between. If using different webServer/load balancer(LB), the WAS server may not extract the listerning ports on the webServer/LB correctly.
You can take a look at the sample setting in PK55330 where a different web server is used in place of the IHS.
http://www-01.ibm.com/support/docview.wss?uid=swg1PK55330
Regards,
I am using 'jp#gc - PerfMon Metrics Collector' Lister for this and as you know it requires 'ServerAgent' running on the connecting server.
Step by step instruction would be very helpful.
And also, if anyone knows of any better alternatives to monitor the servers using jmeter then please share with me, it would be a great help.
You can follow the below Steps:
Download ServerAgent2.2.1.zip file(URL: http://jmeter-plugins.org/downloads/all/)
Unzip and Paste the folder in the Machine where Server is hosted.
Run startAgent.sh(Linux) and startAgent.bat(Windows) in the Server Machine.
Get the Server IP and add the same in the Jmeter Properties File.
remote_hosts=
Add the (Perfmon metrics collector)Listener in the Test Plan.
Host/IP: Add the Server Host/IP
Port: By default 4444
Metrics to be collected: What metric you want to collect.
Can anyone help me setup web polygraph for testing an HTTPS servers via proxy servers in middle
linux machine:192.168.21.7
proxy server :192.168.21.9
https server : 192.168.21.11
This link contains the needed information:
http://www.web-polygraph.org/docs/userman/simple.html
Basically polygraph has couple files which are bundled with it and use for testing.
The manual I gave you give example that uses polysrv but on different distributions you will probably have different names for the tool(on ubuntu it's polygraph-server and polygraph-client)
You need to set the listening service ip+port outgoing "robot" ip and then start it using command line.
For https setup we will configure our pg file on server and client with SslWrap module.
Details of same can be found in http://www.web-polygraph.org/docs/reference/models/ssl.html