Menu
▾
▴
mailmanager-users
|
From: Dick C. <dca...@im...> - 2007-01-08 17:42:57
|
In our MailManager production version 2.0.10 and test version 2.1. We cannot select year 2007 in SEARCH Option? 2007 does not exist on the drop-down list for 'Year'. Both are running with PostgreSQL. I submitted this as a BUG fix request (#1630761). Anyone have any sggestions? Regards, Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 |
|
From: SJ.Stanaitis <sst...@dp...> - 2007-01-08 18:37:30
|
I had to add it to mine... Search.zpt I think is the filename. -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of Dick Calhoun Sent: Monday, January 08, 2007 12:41 PM To: Logicalware Mailmanager-users Subject: [Mailmanager-users] Search OPTIONS - No year 2007? In our MailManager production version 2.0.10 and test version 2.1. We cannot select year 2007 in SEARCH Option? 2007 does not exist on the drop-down list for 'Year'. Both are running with PostgreSQL. I submitted this as a BUG fix request (#1630761). Anyone have any sggestions? Regards, Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
|
From: Dick C. <dca...@im...> - 2007-01-08 20:33:35
|
Thanks Sam! It worked on both versions! Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 ----- Original Message ----- From: SJ.Stanaitis <sst...@dp...> To: Dick Calhoun <dca...@im...>, Logicalware Mailmanager-users <mai...@li...> Sent: Monday, January 8, 2007 1:37:13 PM GMT-0500 US/Eastern Subject: Re: [Mailmanager-users] Search OPTIONS - No year 2007? I had to add it to mine... Search.zpt I think is the filename. -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of Dick Calhoun Sent: Monday, January 08, 2007 12:41 PM To: Logicalware Mailmanager-users Subject: [Mailmanager-users] Search OPTIONS - No year 2007? In our MailManager production version 2.0.10 and test version 2.1. We cannot select year 2007 in SEARCH Option? 2007 does not exist on the drop-down list for 'Year'. Both are running with PostgreSQL. I submitted this as a BUG fix request (#1630761). Anyone have any sggestions? Regards, Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
|
From: Kevin C. <ke...@lo...> - 2007-01-09 15:17:27
|
On Mon, Jan 08, 2007 at 12:40:45PM -0500, Dick Calhoun wrote: > In our MailManager production version 2.0.10 and test version 2.1. We cannot select year 2007 in SEARCH Option? 2007 does not exist on the drop-down list for 'Year'. Both are running with PostgreSQL. I submitted this as a BUG fix request (#1630761). There's another bug for this on sourceforge, and a fix in subversion. Regards, Kevin |
|
From: Dick C. <dca...@im...> - 2007-01-09 17:22:48
|
Thanks Kevin, I found them, Will download the the changed files(referenced in Revision listing 3726 & 3727)and install them in my 2.1 test version. Regards the 2.0.10 production version. Should I install just the search.zpt file to fix that particular problem or leave well enough alone with my patched version of search.zpt? (NOTE: I changed the hardcoding to get at 2007 and it works.) You can close my bug report #1630761 Regards, Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 ----- Original Message ----- From: Kevin Campbell <ke...@lo...> To: Dick Calhoun <dca...@im...> Cc: Logicalware Mailmanager-users <mai...@li...> Sent: Tuesday, January 9, 2007 10:16:27 AM GMT-0500 US/Eastern Subject: Re: [Mailmanager-users] Search OPTIONS - No year 2007? On Mon, Jan 08, 2007 at 12:40:45PM -0500, Dick Calhoun wrote: > In our MailManager production version 2.0.10 and test version 2.1. We cannot select year 2007 in SEARCH Option? 2007 does not exist on the drop-down list for 'Year'. Both are running with PostgreSQL. I submitted this as a BUG fix request (#1630761). There's another bug for this on sourceforge, and a fix in subversion. Regards, Kevin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
|
From: Kevin C. <ke...@lo...> - 2007-01-10 11:17:49
|
On Tue, Jan 09, 2007 at 12:22:37PM -0500, Dick Calhoun wrote: > Thanks Kevin, > I found them, Will download the the changed files(referenced in Revision listing 3726 & 3727)and install them in my 2.1 test version. Regards the 2.0.10 production version. Should I install just the search.zpt file to fix that particular problem or leave well enough alone with my patched version of search.zpt? (NOTE: I changed the hardcoding to get at 2007 and it works.) Dick, I'd suggest just leaving your modification for the 2.0 release. The changes only exist for 2.1 at present, and there's enough differences that they won't backport directly. Regards, Kevin |
|
From: SJ.Stanaitis <sst...@dp...> - 2007-02-02 13:08:59
|
I had set up a script on my Slackware box to re-assign tickets older than 1 year to a specific Archive user, as I discovered that either due to performance issues on my system or MM when an active user gets a LARGE number of tickets (say over 20K) the entire system would slow down. Long story short, the script ran the other night, or tried to, and now MM is CRAWLING. The queries still go through without error, but the PSQL database is taking its sweet time to respond. I'm running PSQL 8.0.6 and MM 2.0.9. Awhile back I had inquired as to how I might delete tickets from the database manually, and did not receive a response so I used the following query: DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %"; Now I've discovered that while the mm_ticket table gets updated, and the tickets are no longer displayed, the messages are still stored in the mm_message table. Could that be part of the speed issue, all those un-linked messages? Is there any way to sync up the two tables, or export the active tickets, wipe the tables, and restore them? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network |
|
From: SJ.Stanaitis <sst...@dp...> - 2007-02-02 13:21:12
|
(Accidentally posted with wrong subject earlier) I had set up a script on my Slackware box to re-assign tickets older than 1 year to a specific Archive user, as I discovered that either due to performance issues on my system or MM when an active user gets a LARGE number of tickets (say over 20K) the entire system would slow down. Long story short, the script ran the other night, or tried to, and now MM is CRAWLING. The queries still go through without error, but the PSQL database is taking its sweet time to respond. I'm running PSQL 8.0.6 and MM 2.0.9. Awhile back I had inquired as to how I might delete tickets from the database manually, and did not receive a response so I used the following query: DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %"; Now I've discovered that while the mm_ticket table gets updated, and the tickets are no longer displayed, the messages are still stored in the mm_message table. Could that be part of the speed issue, all those un-linked messages? Is there any way to sync up the two tables, or export the active tickets, wipe the tables, and restore them? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network |
|
From: SJ.Stanaitis <sst...@dp...> - 2007-02-02 13:55:37
|
Also, it appears that the mm_ticket table is the one with problems, any update, insert, or delete queries are lagging big time. Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of SJ.Stanaitis Sent: Friday, February 02, 2007 8:21 AM To: sst...@dp...; 'Kevin Campbell' Cc: 'Logicalware Mailmanager-users' Subject: [Mailmanager-users] MM 2.0.9 PSQL 8.0.6 Woes... (Accidentally posted with wrong subject earlier) I had set up a script on my Slackware box to re-assign tickets older than 1 year to a specific Archive user, as I discovered that either due to performance issues on my system or MM when an active user gets a LARGE number of tickets (say over 20K) the entire system would slow down. Long story short, the script ran the other night, or tried to, and now MM is CRAWLING. The queries still go through without error, but the PSQL database is taking its sweet time to respond. I'm running PSQL 8.0.6 and MM 2.0.9. Awhile back I had inquired as to how I might delete tickets from the database manually, and did not receive a response so I used the following query: DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %"; Now I've discovered that while the mm_ticket table gets updated, and the tickets are no longer displayed, the messages are still stored in the mm_message table. Could that be part of the speed issue, all those un-linked messages? Is there any way to sync up the two tables, or export the active tickets, wipe the tables, and restore them? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
|
From: Kevin C. <ke...@lo...> - 2007-02-02 15:38:10
|
On Fri, Feb 02, 2007 at 08:20:54AM -0500, SJ.Stanaitis wrote: > (Accidentally posted with wrong subject earlier) > > I had set up a script on my Slackware box to re-assign tickets older than 1 > year to a specific Archive user, as I discovered that either due to > performance issues on my system or MM when an active user gets a LARGE > number of tickets (say over 20K) the entire system would slow down. > > Long story short, the script ran the other night, or tried to, and now MM is > CRAWLING. The queries still go through without error, but the PSQL database > is taking its sweet time to respond. I'm running PSQL 8.0.6 and MM 2.0.9. > > Awhile back I had inquired as to how I might delete tickets from the > database manually, and did not receive a response so I used the following > query: > > DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %"; > > Now I've discovered that while the mm_ticket table gets updated, and the > tickets are no longer displayed, the messages are still stored in the > mm_message table. Could that be part of the speed issue, all those > un-linked messages? > > Is there any way to sync up the two tables, or export the active tickets, > wipe the tables, and restore them? Sam, Please see the deleteTickets.sql method which should show what tables need to be altered in order to delete tickets. Deleting tickets from the database will improve performance, particularly in the 2.0 series where the full text index is stored on the mm_ticket table. As for performance issues, there are many performance issues which exist in the 2.0 series, which were resolved in 2.1 an 2.2 which is in development. I would certainly recommend looking at 2.1 if you are having problems. 20k ticket is not a relatively large number of tickets compared to our production installations so this should be something which can be resolved. Regards, Kevin -- Kevin Campbell Chief Technical Officer - Logicalware Ltd Office: +44 (0)131 225 5422 US & Canada: (347) 293 0699 Kev...@lo... ---------------------------------------------- Logical Progression LTD trading as Logicalware Ltd, Registered in the UK at 23 Manor Place, Edinburgh, EH3 7DX, Company Number SC234177 www.logicalware.com |
|
From: SJ.Stanaitis <sst...@dp...> - 2007-02-02 16:11:40
|
Kevin, Thanks for getting back to me so quick. I ended up running a "VACUUM FULL;" on the database, after which full performance was restored. I will check out that SQL file to see how to properly eliminate tickets moving forward. Have a good weekend! Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: Kevin Campbell [mailto:ke...@lo...] Sent: Friday, February 02, 2007 10:38 AM To: SJ.Stanaitis Cc: 'Logicalware Mailmanager-users' Subject: Re: [Mailmanager-users] MM 2.0.9 PSQL 8.0.6 Woes... On Fri, Feb 02, 2007 at 08:20:54AM -0500, SJ.Stanaitis wrote: > (Accidentally posted with wrong subject earlier) > > I had set up a script on my Slackware box to re-assign tickets older than 1 > year to a specific Archive user, as I discovered that either due to > performance issues on my system or MM when an active user gets a LARGE > number of tickets (say over 20K) the entire system would slow down. > > Long story short, the script ran the other night, or tried to, and now MM is > CRAWLING. The queries still go through without error, but the PSQL database > is taking its sweet time to respond. I'm running PSQL 8.0.6 and MM 2.0.9. > > Awhile back I had inquired as to how I might delete tickets from the > database manually, and did not receive a response so I used the following > query: > > DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %"; > > Now I've discovered that while the mm_ticket table gets updated, and the > tickets are no longer displayed, the messages are still stored in the > mm_message table. Could that be part of the speed issue, all those > un-linked messages? > > Is there any way to sync up the two tables, or export the active tickets, > wipe the tables, and restore them? Sam, Please see the deleteTickets.sql method which should show what tables need to be altered in order to delete tickets. Deleting tickets from the database will improve performance, particularly in the 2.0 series where the full text index is stored on the mm_ticket table. As for performance issues, there are many performance issues which exist in the 2.0 series, which were resolved in 2.1 an 2.2 which is in development. I would certainly recommend looking at 2.1 if you are having problems. 20k ticket is not a relatively large number of tickets compared to our production installations so this should be something which can be resolved. Regards, Kevin -- Kevin Campbell Chief Technical Officer - Logicalware Ltd Office: +44 (0)131 225 5422 US & Canada: (347) 293 0699 Kev...@lo... ---------------------------------------------- Logical Progression LTD trading as Logicalware Ltd, Registered in the UK at 23 Manor Place, Edinburgh, EH3 7DX, Company Number SC234177 www.logicalware.com |
Thanks for helping keep SourceForge clean.
X