PHINMS Receiver Alarms
Badgett, Allen A.
Has anyone seen this problem? I’m getting the error message below. Can’t stop it. I even deleted the CDC staging route since I don’t use it.
Apparently it is in a cached memory somewhere.
Any thoughts will be appreciated.
Allen A. Badgett, Ph.D.
State Messaging Coordinator
Office of Management and Enterprise Systems
Information Services Division - OSDH
1000 N.E. 10th Street P.O. Box 24106
Oklahoma City, OK 73124
Office: (405) 271-9444 X 56026 Mobile: (405) 623 6905
carl.b...@ct.gov
Badgett, Allen A.
I’m not using the default database I’m using SQL server for transport out. I have searched it every way I can think of and don’t find a message being sent to CDCStaging receiver.
Where can I find it?
Allen
(M) 405 623 6905
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Travis Mayo
Hope all is well!!!
The problem is with RecordID #2.
Even if you have deleted this message, It might somehow be stuck in the memory cache or you may not have deleted the right database.
Recommended actions:
1. Delete all alarms
2. Delete RecordID #2 if it exists in your outgoing Default or MS SQL database. (be aware that the message may be in the default database, even if you are not meaning to use it. You can't delete the default database, you can only add additional databases)
3. Exit the console
4. Stop the PHINMS Tomcat Service
5. Stop the PHINMS database service
6. Re-Start the database, then tomcat, then the console... see what happens.
Trav
On Tuesday, May 31, 2016 at 2:39:21 PM UTC-4, Allen Badgett wrote:
Badgett, Allen A.
YES! Looks like I will retire September 1. OSDH has a nice buy out so I will take it. Where are you at now?
See below for response
From: phi...@googlegroups.com [mailto:phi...@googlegroups.com]
On Behalf Of Travis Mayo
Sent: Tuesday, May 31, 2016 2:40 PM
To: PHINMS User Community
Subject: [Caution: Message contains Redirect URL content] Re: PHINMS Receiver Alarms
Hey Allen,
Hope all is well!!!
The problem is with RecordID #2.
Even if you have deleted this message, It might somehow be stuck in the memory cache or you may not have deleted the right database.
I have looked everywhere to delete it. I looked at default DB and there are no records at all. I looked at my SQL database and could not find a record.
Recommended actions:
1. Delete all alarms
Have repeated this a number of times
2. Delete RecordID #2 if it exists in your outgoing Default or MS SQL database. (be aware that the message may be in the default database, even if you are not meaning to use it. You can't delete the default database, you can only add additional databases)
3. Exit the console
4. Stop the PHINMS Tomcat Service
Done
5. Stop the PHINMS database service
Done then I repeated it for good measure
6. Re-Start the database, then tomcat, then the console... see what happens.
Have restarted and so far so good but in the past it comes back a day or two later.
Trav
On Tuesday, May 31, 2016 at 2:39:21 PM UTC-4, Allen Badgett wrote:
Has anyone seen this problem? I’m getting the error message below. Can’t stop it. I even deleted the CDC staging route since I don’t use it.
Apparently it is in a cached memory somewhere.
Any thoughts will be appreciated.
Allen A. Badgett, Ph.D.
State Messaging Coordinator
Office of Management and Enterprise Systems
Information Services Division - OSDH
1000 N.E. 10th Street P.O. Box 24106
Oklahoma City, OK 73124
Office: (405) 271-9444 X 56026 Mobile: (405) 623 6905
--
Preacher Man
Travis, great to see you are still lurking!
I haven't took the time to figure how PHINMS decides which transport queue to use when you have more than one configured. Had a client who had configured a second (MSSQL) transport queue and developed what appeared to be a race condition in the folder poller. Both queues showed the file payload, but only one got to transmit it leaving the other forever stuck (file not found). Just got rid of the extra queue and never looked further into it.
In my own Phineas implementation each folder map can specify the transport queue to use. By the way, the java implementation (jPhineas) is up on GITHUB if anybody is interested. I peck away at it now and then when I get bored. Probably add some "MTS" extensions to it when/if CDC gets that project a bit more matured. But I'm not all that enamored with JSON/REST. I suspect by the time all of the needed security, duplicate detection, non-repudiation, etc. get wired in it won't that much "simpler" than good old SOAP.
Anyway, cheers to all!
Tom
From: All...@health.ok.gov
To: phi...@googlegroups.com
Subject: RE: [Caution: Message contains Redirect URL content] Re: PHINMS Receiver Alarms
Date: Tue, 31 May 2016 20:19:39 +0000
Badgett, Allen A.
Thanks for the comment. Looks like I will actually “retire”. Not sure how much access they will allow me.
I tried setting up two transport queues; the default DB and SQL Db. Never could get it to work. I just used SQL and deleted the default.
Loyall, David
I see no mention of the requeue cache in this thread.
...Maybe that’s because it’s not relevant here; if that’s the case, please pardon my noise!
Cheers,
--Dave Loyall
Any thoughts will be appreciated.
Allen A. Badgett, Ph.D.
State Messaging Coordinator
Office of Management and Enterprise Systems
Information Services Division - OSDH
1000 N.E. 10th Street P.O. Box 24106
Oklahoma City, OK 73124
Office: (405) 271-9444 X 56026 Mobile: (405) 623 6905
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
Preacher Man
It's always good to delete the requeue cache when troubles like this appear, although one should probably keep track of anything that was "attempted" and make sure things get resent afterwards.
As one of this groups "monitors", you can rest assured Allen that we won't remove your access just because your have retired (ok... you knew that - I'm just yankin' your chain).
cheers!
Tom
From: david....@nebraska.gov
To: phi...@googlegroups.com
Subject: RE: [Caution: Message contains Redirect URL content] RE: [Caution: Message contains Redirect URL content] Re: PHINMS Receiver Alarms