Home » forums » Luminis Platform / System

TAs sent only after restart - Alternatives to a full restart?

Submitted by tbird on Wed, 2009-03-11 15:26

Our Targeted Announcements channel is not working consistently. Usually nothing happens when we send a TA. Then, after a restart, the TAs that were submitted before are actually sent.

We plan to upgrade to 4.1.1 or 4.2 to fix this. Until then, our workaround is to do a restart every time we want to send a TA.

Is there a better workaround, or even a fix? Is there a smaller piece we could restart, instead of a full restart?

Thanks
Terry

Luminis 4.1.0.22

‹ 64-bit JVM How to get SIS PIN? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Not seeing this behaviour

Submitted by ToddTrann on Wed, 2009-03-11 16:56.

Sorry, we do not see this behaviour. Haven't had such a problem with Luminis 4.0, 4.1 or 4.2.

Check your message broker destinations and configuration (using mbtool). Or log into port 7677 on your resource tier and use the GUI to check.

Todd

Re: Not seeing this behaviour

Submitted by tbird on Thu, 2009-03-12 14:33.

Hi Todd,

I didn't know what to look for, but I compared our TEST instance to PROD. (TEST TAs work ok, PROD has the problem. But, TEST is 4.1.1.27, PROD is 4.1.0.22.) These are the differences I see in the message broker:

Destinations:

TEST:
CPInternalDispatch # of Msgs: 14690 Total Size of Msgs: 15139120

PROD:
CPInternalDispatch # of Msgs: 31524 Total Size of Msgs: 19754283

Broker Configuration:

TEST:
Maximum # of messages in the system: 1000000
Maximum size of messages in the system: 1500m
Maximum message size: 300k

PROD:
Maximum # of messages in the system: 100000
Maximum size of messages in the system: 150m
Maximum message size: 300k

So, TEST has 10x the max # of messages and size of messages. Could the problem be that these values are too small in PROD?

Thanks
Terry

configman

Submitted by ToddTrann on Thu, 2009-03-12 16:42.

You'll want to investigate these commands fully:

mbtool list brokerstatus
mbtool list destinations
mbtool list destaccess
mbtool list deststatus

Also the value of
com.pipeline.abm.tmsjanitor.enabled
on the resource tier machine versus the web tiers, it should only be true from resource tier machine, the web tiers should give false.

As painful as this may be, you might also try dumping out ALL configman values from test, and ALL configman values from prod, and using a tool like WinMerge to compare the two, looking for differences.

Todd

Update on TAs not sending ?

Submitted by hwilly007 on Wed, 2010-03-10 13:30.

Curious if/how you solved this issue

- we are experincing similar issues with TAs working in Test but not Prod and not seeing anything that stands out in configman output diffs

 

thanks

 

Howard

Syndicate content