HammerNonResponsiveMode

HammerNonResponsiveMode SearchSearch
Author Message
Mike
New member
Username: Messageguy1

Post Number: 12
Registered: 01-2009
Posted on Wednesday, February 04, 2009 - 05:19 pm:   

Hello,

Having (and thank you for all your help) correctly setup my scenario, I tried some testing. All is well with casual testing, and so I wrote a batch script to blast 100 messages, one after the other, to the gateway. I even tried running two at the same time (so 200 messages total, 2 coming in from different sources, very intensely).

I typically can get about 50-150 in or so in this fashion before the following occurs:


11:32:21:950 [7] Debug: 1 recipient entries
11:32:21:950 [7] ThreadProcessConnection: Before message loop
11:32:21:950 [7] ThreadProcessConnection: Before message loop
11:32:21:950 [7] ThreadProcessConnection: Begin message loop
11:32:21:950 [7] ThreadProcessConnection: End message loop
11:32:21:980 [7] ThreadProcessConnection: Request processing complete
11:32:50:031 [5] ThreadProcessModem: Before ModemAllocate - Sierra Wireless AirCard GPRS Modem
11:32:50:031 [5] ThreadProcessModem: After ModemAllocate - Sierra Wireless AirCard GPRS Modem - OK
11:32:50:031 [5] ThreadProcessModem: Re-initializing modem: Sierra Wireless AirCard GPRS Modem ...
11:32:51:683 [5] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID
11:32:51:683 [5] HammerNonResponsiveModem: Begin
11:34:21:242 [5] HammerNonResponsiveModem: FAILED
11:34:21:242 [5] ThreadProcessModem: Before ModemRelease - Sierra Wireless AirCard GPRS Modem
11:34:21:242 [5] ThreadProcessModem: After ModemRelease - Sierra Wireless AirCard GPRS Modem


The modem is dead until I reboot the entire machine. I increased the programmatic delay in these requests and am having mixed success so far. While i am doing this, i was curious.. Is there a way to gracefully handle this so the modem will never die in this fashion?

What does HammerNonResponsiveMode mean? What are the general recommended procedures and practices for the occasional large quantity of msgs passing through?
Mike
New member
Username: Messageguy1

Post Number: 13
Registered: 01-2009
Posted on Wednesday, February 04, 2009 - 06:26 pm:   

update:

it seems increasing the delay much higher between messages has allowed things to run safely.

But..i'm still curious, is this a generally accepted practice, or are there better ways?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 427
Registered: 08-2008
Posted on Wednesday, February 04, 2009 - 08:42 pm:   

Hi Mike,

That is unusual.

What model modem is that? (Is it an Express Card, PC Card, or USB?)

What all this means is that the modem has gone into an unstable state.

Indicators of a problem would occur earlier in the log. Typically what you'd see is some sort of timeout error waiting for a response when sending a message. What it means is that there is no data coming in from the modem at all. NowSMS tries sending a few commands to wake up the modem. If the modem doesn't wake up, it takes more drastic action (I guess our programmers call it the "hammer"). Part of that action is to get Windows to reinit the modem.

Unfortunately, if the software in the modem has "hung" ... sometimes the only thing that can be done is a hard reset of the modem itself.

(If the modem is on a card, then that would mean actually removing and reinserting it, or rebooting.)

We started to see increased frequency of this type of problem last year with newer modems. And we were about to add a configuration option to reboot automatically on modem errors. But then we did some study with one particular modem that frequently exhibited this problem, and we were able to resolve it with some additional "hammer" action. It would be good if you could try the update at http://www.nowsms.com/download/nowsms2009.zip to see if this makes the modem more reliable.

It's always possible that the modem itself is having problems (for example, a card modem might start failing if it gets too hot). But we were encouraged enough by the improvements in this particular update that we held off adding the option to reboot on modem failure as that seemed too drastic.

--
Des
NowSMS Support