I really want to start working with "The Grinder" but unfortunately my agent doesn't find the console what ever I try.
The message issued by the agent is "(agent): Failed to connect to 'localhost/127.0.0.1:6372', proceeding without the console; set grinder.useConsole=false to disable this warning."
Both console and agent are located on local-host.
It happens both when I start the agent without a grinder.properties file at all and when I do use grinder.properties file with a default grinder.consoleHost property.
It happens even when I set grinder.consoleHost to be my IP.
Any ideas?
Well, stupid as it may sound, don't set the Console Host property in the console itself. To set this property open the console -> File -> Options -> Communication tab. Leave the Console Host empty otherwise the agent won't connect to the console (have no idea why, I thought setting it to be my IP was a good idea).
If you set the console host in the console, you'll also need to set the same value in the grinder.consoleHost key in the grinder.properties file used by the Agents.
Related
After a CLI application exits, on prod profile, i'd like it to go back to the shell instead of re-prompting the dev mode ("Press [space] to restart, [e] to edit command line args...")
Also would not need the "Press [h] for more options>" on startup.
Would it be possible to get quarkus "dev mode" totally out of the way in prod?
Description:
Add a configuration value/switch to disable the GRPC server in dev mode
At the moment there is no way to disable starting of the GRPC server in dev mode. For instance if only the client is used it is weird to have to assign a random port to the GRPC server to solve port collision for instance from a real GRPC server. So I don't really know if this is an actual feature request or a small bug.
Implementation ideas:
Have a configuration value which disables the starting of the server, e.g.:
quarkus.grpc.server.enable
If you go into Options > Cross Platform, where's an option to set up an SSH connection. However, I cannot force this thing to connect.
I have a Linux machine, I can connect to it with PuTTY just fine using password authentication. However, when I try to configure a connection in Visual Studio, it highlights the username and password boxes in red, as if there's a problem with them. I have no idea why it's not letting me log in. No matter which account I try, it just refuses. There's no diagnostic message or anything, it just highlights the fields in red.
Is there some prerequisit I'm missing? I don't understand why it won't let me connect. Is there somewhere I can look for extra diagnostic output?
OK, so it took me quite some time to figure this out. I'm writing this in case it helps anyone else...
Options > Cross Platform > Connection Manager is the page I was looking at, where you can set up an SSH connection. However, if you go to Options > Cross Platform > Logging and Diagnostics, you can click a button to turn on diagnostic logging. (!)
Once logging was turned on, VS reports:
Renci.SshNet.Common.SshAuthenticationException: No suitable authentication method found to complete authentication (publickey,keyboard-interactive).
In other words, VS isn't even trying to authenticate, because none of the available methods on the SSH server match the methods VS is trying to use.
Long story short, it turns out password authentication is disabled on the SSH server. "What?! But I use password authentication every day to log in!" No, you do not. Apparently there is "password" authentication and "keyboard interactive" authentication, and these are somehow not the same thing. You log in using "keyboard interactive" auth, which is enabled, but VS is trying to use "password" auth, which is disabled. Once you realise this, it's perfectly obvious why you can't log in.
So, go edit /etc/ssh/sshd_config, and turn on password authentication. (In my case, there was a line that literally says PasswordAuthentication no. Change that to yes, restart the SSH daemon, VS can now connect just fine.)
I have installed Android studio and i want to build first app. Unfortunately "Gradle project sync failed" Error: Connection refused: connect.
I know it's because i use proxy server (my company does). I already made changes in Setings->HTTP Proxy-> Auto-detect proxy settings, but I guess, Gradle doesn't look on it. I read I should make write in gradle.properties my proxy server, user and password, but I don't know this parameters, and i don't know how to get them (even if it is available or not).
Can you help me? there are two ways: 1. If you know tell me how to avoid this problem without that parameters. For example like Auto-detect 2. How to get those parameters?
Apparently this code works
systemProp.http.proxyHost=<hostname>
systemProp.http.proxyPort=8080
systemProp.http.proxyUser=
systemProp.http.proxyPassword=
systemProp.http.nonProxyHosts=localhost
or for https
systemProp.https.proxyHost=<hostname>
systemProp.https.proxyPort=8080
systemProp.https.proxyUser=
systemProp.https.proxyPassword=
systemProp.https.nonProxyHosts=localhost
when password isn't set up.
It should be in gradle.properties file.
Enable No Proxy from Appearance and Behavior -> System Settings-> HTTP Proxy -> NO Proxy
This is worked for me
When I try to launch the weblogic console page in my browser after starting weblogic using command prompt, the login page isn't coming up for a long time.
I see the "Deploying application for /console" message followed by a long sequence of "." (dot/period). This is going on for a long time.
I observed this message printed on the command prompt from where I launched the startWebLogic.cmd file
<Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 5 secs>"
Is this the reason for the console not coming up? If yes, how to resolve it?
If the console app is deploying extremely slow, you can change to following setting:
Login to the WebLogic admin console
Click your domain name link on the left hand side
Open Configuration tab and General sub-tab
Uncheck the box labeled Enable on-demand deployment of internal applications
Save
Activate changes
I have just set up the plugin remote debugger on my CRM server as a service and I can now connect to it and debug plugins with no problem.
My question is does the user always need to be logged onto the server in order for the service to be running and working? I set it up so that it runs as LocalSystem but when the user isn't logged in and I try to debug anything it says I cannot connect to it.
So does this mean I have to keep the user on always or is there some configuration that I've missed?
You will need to be logged in to run the remote debugger- it is designed to be set up for short term debugging and turned off after you are finished debugging.
Using the PluginTool for local debugging on your workstation is another option:
Is it possible to place an org in it's own process