How to start default listener (like SYSTEM.DEFAULT.LISTENER.TCP) from MQ Explorer?
Should be possible, right? - Just like you can start a queue manager in Explorer.
If there is, can someone tell me how explicitly?
I know how to do it outside of Explorer using the MQSC command:
START LISTENER('SYSTEM.DEFAULT.LISTENER.TCP')
Make sure that your MQ Explorer list of listeners is showing system objects (one of the icons in the top right), then right click on the listener object that you want to start and choose Start from the context menu.
Related
Debugging service workers in FF seems ridiculously painful.
I know that from main page I can
go in the Application panel,
click onto "aboutdebugging",
search the new page for my worker among 200 others,
click start
click inspect then
I got to look for two consoles instead of one and passing
messages between the 2 is non trivial.
Tell me there's an easier way!
You need a nightly version to have a debug link near the worker.js in the application panel.
In the stable version, there's only a link that displays the source of the worker.js in a new tab. How useful is that?
Using ProEnv, I have configured my computer to start the standard debugger in case my Progress application shows a message (press the "Help" button and in the callstack, click on "Debug"), this is done using this ProEnv environment variable:
DLC=C:\PROGRE~1\OpenEdge
My application is started, using the -debugalert switch.
However, now I'm starting working with PDSOE (Progress Developer Studio for OpenEdge) and I would like to start up that debugger, in the mentioned case. I don't know how to do this, because PDSOE is based on Java technology (it's an Eclipse environment).
Does anybody know how to do this?
Thanks in advance
The way to launch the PDSOE variant of the debugger is from within PDSOE, using a "Debug Configuration". If you've run the application this way, the PDSOE debugger is used regardless of whether you use breakpoints or the <debug> button.
If you run the application from a "Launch Configuration", then the <debug> button will launch the standalone debugger.
They're basically functionally equivalent but TL;DR you'll need to run the application using PDSOE's "Debug Configuration".
Double click in the left margin of your source to set a break point (a small blue ball):
Then start your run configuration in debug mode:
You will be prompted to switch to debug perspective.
Add DEBUGGER:INITIATE(). DEBUGGER:SET-BREAK(). anywhere in the code and execute the application (provided you've already run prodebugenable -enable-all from the ProEnv in Admin mode).
Is there a way to detect when the user makes focus on the Project Explorer window in a RCP application? Is there an event I could use?
I researched and found that Project Explorer's id is org.eclipse.ui.navigator.ProjectExplorer but I still didn't find any solution to my problem.
You can use org.eclipse.ui.IPartListener to listen for changes to which part is active (and several other events).
You call the IPartService addPartListener method to set this up. You can get the part service in several ways depending on where you code is running. One of these is:
IPartService partService = PlatformUI.getWorkbench().getActiveWorkbenchWindow().getPartService();
partService.addPartListener(listener);
What property do I need to set in my Windows hosted WCF services so that a "Title" value will appear in the Debug "Attach to Process" dialog (as in the WcfSvcHost.exe entries below)?:
We are using the ServiceProcessInstaller & ServiceInstaller classes. I tried setting both the ServiceInstaller.DisplayName & ServiceInstaller.DisplayName properties but no change.
The WcfSvcHost.exe processes are the WCF service host processes started by Visual Studio when you start a debug session within a solution, see http://msdn.microsoft.com/en-us/library/bb552363.aspx. There is no way to specify a title for these processes.
Normally the title column would be filled for applications that host a user interface. For example, look at the Task Manager dialog, Applications tab. The applications shown there do have a title and these are displayed equally in the debug attach process window.
Starting the WCF service hosts by Visual Studio completely bypasses the ServiceProcessInstaller and ServiceInstaller classes, so no chance of getting it in that way. When you start (self) hosting your WCF service in a UI (winforms/WPF) application, you have the best chance of getting the title filled and being able to find your process.
Is there any plug-in for Visual Studio that can display the associated Application Pool name for those w3wp processes when debugging them with "Attach to Process..." ?
Usually I have to do following steps before debugging:
c:> \Windows\system32\inetsrv\appcmd list wps
then I get the process id for the Application Pool I want to debug, and then attach it in the Attach to Process window.
I feel it will be very pleasure if there's a plug in can do this automatically, but didn't find any such thing after Googled.
You can use a macro—see my answer to a related question. I am practically always attaching to one of a few specific Application Pools, so I’ve made buttons to attach to those specifically in one click. If you really want to choose from a dynamic list each time you’ll just have to build that dialog, but you can lift from my macro code to get the list.