No announcement yet.

[MC 3.0.x] Ability to stop a search in the client ?

  • Filter
  • Time
  • Show
Clear All
new posts

  • [MC 3.0.x] Ability to stop a search in the client ?


    is there a way to stop a search from the GUI ?
    If you launch a search using very few criteria (like raw message contains 'abc'), and if you have a lot of files, your GUI is completly stuck for hours

    If there isn't such an "action" button, maybe it should be a good feature to add.



  • #2
    Note that text searching was much improved in 3.0.2, so if you aren't already, make sure to update to the latest version (3.0.3).

    There's an open issue for this: MIRTH-3229
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

    - How do I foo?
    - You just bar.


    • #3
      My MC is already 3.0.3
      I'll have a look at the open issue.


      • #4
        So is there a way to stop a search?


        Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

        Appliance Version 3.11.4
        Mirth Connect Version 3.8.0
        Java Version 1.6.0_45-b06
        Java (64 bit) Version 1.6.0_45-b06
        Java 7 (64 bit) Version 1.7.0_151-b15
        Java 8 (64 bit) Version 1.8.0_181-b13
        PostgreSQL Version 9.6.8


        • #5
          Currently no. If you can find the search query being run and stop it via Postgres or whatever database you're running, that should end up stopping the search currently.

          Other than that like Nick said we are aware of it and have an open issue to add such a feature.


          • #6
            I run into this problem all the time myself... here's what I do.

            If you are running MS SQL, this will be helpful. It's an enhancement on the sp_who2 stored procedure...

            --Setup a Temp Table to hold the sp_who2 Results	
            	declare @tempTable table 
            	SPID INT,Status VARCHAR(255),
            	Login VARCHAR(255),HostName VARCHAR(255),
            	BlkBy VARCHAR(255),DBName VARCHAR(255),
            	Command VARCHAR(255),CPUTime INT,
            	DiskIO INT,LastBatch VARCHAR(255),
            	ProgramName VARCHAR(255),SPID2 INT,
            	REQUESTID INT
            --Now populate the temp table from sp_who2
            	INSERT IGNORE INTO @tempTable 
            	EXEC sp_who2
            --Now you may select, sort, filter, etc the results easily
            	select *
            	from @tempTable
            --Replace 'mirthdb' with your own mirth database name
            	where DBName = 'mirthdb'  
            --I like to only look at RUNNABLE status' 
            	and Status = 'RUNNABLE'
            --You can also just look for SELECT commands
            	and Command = 'SELECT'
            Comment out any of my additional where clauses to get more information...

            The above will return a list of those SELECT commands that are RUNNABLE on your Mirth Database.

            Look for one that has a large CPUTime, that's most likely your long running channel search.

            Once you've located it, note the SPID in the first column....

            Now, open another query window and type the following (replace [SPID] with your SPID):

            kill [SPID]
            This will hard stop the Mirth Channel search. When you go back to Mirth you'll see an error message that states An Unexpected error has occurred.

            Click close, then exit the channel and go back to the Dashboard, and you're done.

            I then suggest you familiarize yourself with the Advanced search options and how to streamline your searches.

            Hope this helps some!