Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
flbpmdev

Member
Registered:
Posts: 42
Reply with quote  #1 

I'm using the Jscript.NET sendmail to send email messages.  We are using FileSite DMS, so documents are opened from special files called NRLS, that have data in their body that Outlook clients with the FileSite plug in can interpret to open them.  Without getting bogged down in how all that works, here is my problem:

 

When an action needs to send an email, it calls a server side vbscript that creates the NRLs for the FileSite documents that have been "attached" to the Metastorm folder.  It stores these files on the IIS server and the path to the files are stored in a memo variable as %memAttachmentList.  For example, memAttachmentList might reference 2 attachments as "C:\metastormAttachmments\0000000000001234\x.nrl;C:\metastormAttachments\0000000000001234\y.nrl". 

This variable is then used when sendmail is called as the attachments parameter.

 

It works great, except for one big problem I just realized I have with it today:  I need to delete those files off the server after the mail is sent.  I thought this would be no problem, because I could just follow up the call to sendmail with another vbscript that will delete the files.  However, it seems that sendmail somehow hangs on to the files after it runs, because any attempt to delete them fails.  When I try to manually delete them with Windows Explorer, it tells me they are in use by COM surrogate.  The only way I can delete them is to restart the Metastorm Service, which is obviously not a viable solution. 

 

Any ideas what's going on?   If I create the files and don't use the sendmail Jscript.NET, I have no problem deleting them via another script or manually.  But after sendmail references them as an attachment, they get locked up until I restart the Metastorm service. 

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
I used to have that problem. I would wait a few minutes and delete the files. It always worked after a while IIRC. If the engine is keeping a lock on them, Metastorm need to fix that (although with only a month to go until it is no longer supported....).

We had a separate process sending out emails, so it was easier to manage. I am pretty certain we do something similar in the  Email Query Report library:
http://processmapping.com.au/freestuff/metastormbpm7giveaway/Libraries.html


__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #3 
Update: no, sorry, that uses the normal email function, not a script.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #4 

Quote:
Originally Posted by Jerome
(although with only a month to go until it is no longer supported....)

Presuming you are referring to V7.6, support was extended until May 2013 not quite a year ago.

If you are referring to something else ... I apologize in advance for presuming the wrong thing.
0
flbpmdev

Member
Registered:
Posts: 42
Reply with quote  #5 

Thanks for the reply Jerome.  You are right, if I wait a while (not sure what the exact time is yet), it will release and I can delete the file.   I'll set up a scheduled task to run in the middle of the night to clean up the files each night.  I even tested a modified sendmail in which I cleared the Attachments collection of the message object after the smtp.send, but that made no difference.  At least I now know they are not held forever and I'll be able to clean them up at a later time without having to restart the engine.

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #6 
Quote:
Originally Posted by BMellert

Quote:
Originally Posted by Jerome
(although with only a month to go until it is no longer supported....)

Presuming you are referring to V7.6, support was extended until May 2013 not quite a year ago.

If you are referring to something else ... I apologize in advance for presuming the wrong thing.


Interesting.

I wish they would tell us!


__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #7 

As usual, they weren't obvious about it, and I had to dig around to find the links below (again).  When we found out we backed off on converting our items to V9 since we weren't so much "under the gun" since we had other projects to get out first (V7 since part of existing maps/solutions).  (I fear performance will be slower in some respects from what has been moved thus far, but that is something else when I have a full application to compare against.)


Since 7.6.4 just/finally came out, I don't know how they could have extended support.  (Condisering they originally told me it was due out last November.)

http://community.metastorm.com/t5/Everything-BPM-Version-9/Metastorm-BPM-Product-End-of-Life-Dates/m-p/275379#M306

http://www.metastorm.com/customers/csecure/bpm_prod.asp or perhaps http://www.metastorm.com/customers/csecure/docs/gen/Metastorm_Product_End_of_Life_Dates_jun2011.pdf

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #8 
I believe many are doing similar things. It is hard to grasp, but Metastorm BPM version 9 has been out for two and a half years now, and very few customers have upgraded from version 7 (we still have some on version 6).

There's a lesson somewhere in that. I think it is that the upgrade process is too daunting for many. I also think that given what we have learned after many upgrades ourselves, that Metatsorm both underplayed the complexity, and completely misunderstood it. Because of this, the path will be littered with tales of woe. Having said that, the latest migration tools are much better than the original. Those were almost useless for anything but simple systems. At least Metastorm has addressed those issues.

I am thinking of writing a guide, but do not have the required time right now. If the market were there (and I believe it is) it could be very useful. Perhaps a CD training course / guide would be more lucrative since people would be prepared to pay more?

If I could justify the cost ....

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
KarlD

Avatar / Picture

Guru
Registered:
Posts: 113
Reply with quote  #9 
I have to admit 7.6 is probably the best version of Metastorm BPM I have worked with. Mostly it was predictable and the 'issues' could be compensated for in the design of the process. It is, if the term can be applied to Metastorm BPM, quick and easy.

Then we have version 9. A very different tool. Moving my skill set to version 9 was painful in the begining. Not just learning the new interface and designer but also the elements of the migrations and how the 'undocumented' features affect the design. So a much steeper learning curve than with previous version upgrades.

Is it worth the move to version 9? Yes, I think it is. We are all in the business of change, it seems contradictory that we should be the ones to oppose it.

Would a guide have been useful? Probably, but how many of us actualy read all the instructions before putting together flat pack furniture! Looking back I'm not sure I would have understood a migration guide without actualy doing a migration and that takes time. Some sort of reference on the common issues would be good, but then its all in the forum.

Both version 7 and version 9 do the same thing but in very different ways. There are good and bad with both. Accept that change is inevitable and look on it as the begining of a new chapter...
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #10 
I agree that 7.6 has become pretty good (although the fact that 7.6.4.0 was withdrawn is a worry). I am doing some 7.6 development this last month, and it is quicker, but the whole database design restrictions are really frustrating me! Datasets were so badly flawed it was amazing we did not complain more.

Ho, hum. Roll on 9.1. At least we are developing with a good view to migration, so we'll have fewer problems.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!