Priority on Destinations in a Broker?

Hey,
I've a bit of a problem with the JMS queue, it goes like ..
I've 1 broker with 4queues/destinations
in queue 1, 2 and 3 .. the consumer will possibly create a message to be put onto queue 4
If 1 + 2 + 3 are getting alot of traffic, I'm seeing that queue 4 isn't getting processed as quick as I'd like at all .. and its a good deal more important than the other 3 queues.
Is there a way to setup the broker so that anything from queue 4 takes prioriy over everything else?
so if there are alot of messages in 1,2,3 .. but one comes in for queue 4, it will jump to the top everytime?
Hopefully someone can help :)
Thanks
/Bal

so if there are alot of messages in 1,2,3 .. but one comes in for queue 4, it will jump to the top everytime?sounds like you are using 1 connection for the consumers on these queues (?), if yes, use a different connection for queue #4's consumer from other consumers.

Similar Messages

  • Cluster and temporary destinations visibility

    Hi all,
    does anyone of you know if temporary destinations as TemporaryTopic and TemporaryQueue are visible in a Sun One Message Queue cluster ? If I create a temp destination on a broker in a cluster, this temp destination is visible also to other machines partecipating in the same cluster as is for "Normal" non temporary Topics and Queues ?
    Thanks all for you help !
    Stefano.

    What I had in mind is just this, as we have planned to use a cluster but this is not yet ready for testings, I was just looking around for a confirmation. In your opinion Miss Linda is this a feature of a particular release of Sun One or is already present in our 3.0.1, Service Pack 2 version ?
    Thanks for your courtesy !
    Stefano.

  • Can I set a destination object with command line

    I have installed sun java system message queue 3.5 with sp1. Course of I can not run admin console, I want to know if I can set destination object with command.
    Thanks

    all admin console functions are supported through the
    command line administration tools
    To change attributes on a destination administered
    object, use imqobjmgr
    http://docs.sun.com/source/817-3727/adminobj.html#wp14381
    To create and administer physical destinations on the broker
    use imqcmd
    http://docs.sun.com/source/817-3727/brkrmgmt.html#wp19759

  • Broker clustering question

    In our current setup, we have a few brokers clustered together without a master broker. These brokers serve the same client applications and therefore should have the same set of topics/destinations. My question is should I create these topics on each of the broker or should I just create them on one of the brokers and let JMS provider service to replicate these topics on all other brokers when they are clustered? I have created these topics on the broker before I put it to the cluster and I have seen some strange behaviours with the cluster and I'm not sure if it's related. Does anybody know?
    Thanks in advance for your feedbacks.

    Currently we created all the destinations on the broker before we added it to the cluster. These destinations are the same as the ones that are already created on all of the brokers on the cluster. Will that confuse JMS service provider because it will try to forward the information to all the brokers in the cluster? We saw messages stuck on ACTIVE subscribers. We saw messages got lost. We saw messages went through for a few hours and a subscriber became INACTIVE for no reasons. I'm not sure if these are related, but I have no ideas where to look.
    Is there any reason why you cannot use a master broker?We didn't want to use a master broker because our requirements didn't allow us to have a single point failure. With a designated master node, and if that node dies, will the cluster still function? Another reason is because we have a pre-defined set of destinations and connection factories on all of the brokers, we don't think a master node will be neccessary. Is it correct?
    Thanks.

  • Broker wait for all receiver to acknowledge before returning from publish()

    Does the broker wait for all receiver to acknowledge before returning from publish()?
    If suppose i had 10 subscribers. I observerd 10th subscriber getting message late. I thought publisher will wait for acknolodge for each subscriber ? else why it getting message late ?

    I assume you are questioning why the subscriber's onMessage() is getting
    called way after the publisher's publish() had returned.
    The JMS publishers only know that it is sending msgs to a destination.
    Whether there are 0 or 100 subscribers to the destination is something it
    doesn't know or care about.
    The message is sent to a destination on the broker first and then it is
    delivered to the subscribers of the destination.
    The publisher's publish() method will not return until the message has
    been successfully delivered (and persisted if necessary) to the broker.
    Note that this does not mean that the message has been successfully
    received by any subscribers.

  • Sun Java System Application Server 8.2 PE With Sun MQ 4.1

    Hi,
    I sucessfully deployed my bvrowser application on sjsas8.2-PE on solaris Sparc machine. As we all know sjsas8.2 comes with Sun MQ 3.7 but i want to use Sun MQ 4.1 instead. I sucessfully installed the Sun MQ 4.1 on sparc machine as a separate instance. Am I right here????....
    If I am right than what do i have to do to use MQ 4.1 instead of using default application server MQ 3.7. Do i have to upgrade the MQ instance??? My server support the JMS using following Xml....format...If I provide the information correctly....
    <LISTENER active="true" type="jmslistener" id="JMS">
    <ADAPTERID>Anything</ADAPTERID>
    <CONSUMER>
    <OUTPUT_QUEUE>OUTQ</OUTPUT_QUEUE>
    <DEAD_LETTER_QUEUE>DeadLetter</DEAD_LETTER_QUEUE>
    </CONSUMER>
    <NBTHREADS>5</NBTHREADS>
    <INPUT_QUEUE>INQ</INPUT_QUEUE>
    <TRANSACTIONAL_QUEUE>true</TRANSACTIONAL_QUEUE>
    <JNDI>
    <FACTORY_NAME>QueueConnectionFactory</FACTORY_NAME> *<--- What will the FACTORY_NAME in MQ 4.1*
    <INITIAL_FACTORY>com.sun.jndi.fscontext.RefFSContextFactory</INITIAL_FACTORY> *<--- What is INITIAL_FACTORY in MQ 4.1*
    <PROVIDER_URL>file:///tmp</PROVIDER_URL> *<-- What will the provider URL*
    <SECURITY_PRINCIPAL></SECURITY_PRINCIPAL> *<--- We can ignore this*
    <SECURITY_CREDENTIALS></SECURITY_CREDENTIALS> *<---- We can ignore this*
    </JNDI>
    </LISTENER>
    I do not have any idea how to work around this...please help....
    Thanks in advance:)

    I found out the solution.... First of all we do not need to integrate Sun MQ 4.1 with Application server.Please find out the procedure below to work around with Sun Application Server 8.2 PE and Sun MQ 4.1 using your application.
    Installation Required_
    Sun Application Server 8.2
    Sun MQ 4.1
    Process_ (steps are same for all platform, I used Sun Solaris Sparc machine with Linux - Command line)
    *1)* First of all start you MQ 4.1 Broker on some port using command:
    $ imqbrokerd -port <port_num> (7676 is already used by Application Server MQ v 3.7 so try some other say 7677)
    Now from another session add your physical destinations to this broker we have started on <ip_address>:<port_num> using commands
    $ imqcmd -b <ip_address>:<port_num> create dst -t q -n QIN
    $ imqcmd -b <ip_address>:<port_num> create dst -t q -n QOUT .... and so on
    You can check your destination using following commands:
    $ imqcmd -b <ip_address>:<port_num> list dst - will show you following screen shot
    Username: admin
    Password:
    Listing all the destinations on the broker specified by:
    Host Primary Port
    10.44.5.14 7677
    Name Type State Producers Consumers Msgs
    Total Count UnAck Avg Size
    QIN Queue RUNNING 0 0 0 0 0.0
    QOUT Queue RUNNING 0 0 0 0 0.0
    mq.sys.dmq Queue RUNNING 0 0 0 0 0.0
    Successfully listed destinations.
    Now our queues are ready to ROCK!!!!
    *2)* Secondly create a JMS connection factory using Application Server GUI with address list 'mq://<ip_address>:<port_num>'
    *3)* That's it. You are ready to use this connection factory and queues. I am copying a test application which sends data to queue and retrieves it back as follows: (*Note: I added appserv-admin.jar, appser-rt.jar, j2ee.jar/javaee.jar (both worked for me) and imqjmsra.jar in my test application lib directory as an external jar files)*
    import java.util.Properties;
    import javax.jms.Connection;
    import javax.jms.ConnectionFactory;
    import javax.jms.Destination;
    import javax.jms.MessageConsumer;
    import javax.jms.MessageProducer;
    import javax.jms.Session;
    import javax.jms.TextMessage;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    public class Connect {
    * @param args
    public static void main(String[] args) {
    if (args.length < 1)
    throw new RuntimeException("java -cp . Connect {serverName}");
    Connect c = new Connect();
    c.testConnect(args[0]);
    public void testConnect(String serverAddress) {
    try {
    Properties props = new Properties();
    props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
    props.setProperty(Context.PROVIDER_URL,"iiop://"+serverAddress+":3700");
    InitialContext jmsContext=new InitialContext(props);
    // We need to find out what name the JMS connection factory is bound to in SunMQ
    String jmsConnectionFactoryName = "TCSQCF";
    Object obj = jmsContext.lookup(jmsConnectionFactoryName);
    if (obj instanceof javax.jms.ConnectionFactory) {
    // the JMS connection factory
    ConnectionFactory connectionFactory=(ConnectionFactory) obj;
    Connection connection=connectionFactory.createConnection();
    // do something useful with a JMS connection
    Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
    connection.start();
    Destination outQueue = session.createQueue("QOUT");
    MessageProducer mp = session.createProducer(outQueue);
    TextMessage msg = session.createTextMessage("Meaage From QOUT");
    mp.send(msg);
    //                Destination inQueue = session.createQueue("QIN");
    Destination inQueue = session.createQueue("QOUT");
    MessageConsumer mc = session.createConsumer(inQueue);
    TextMessage receivedMsg = null;
    while ((receivedMsg = (TextMessage) mc.receive(1000)) != null) {
    System.out.println("Received: " + receivedMsg.toString());
    Destination outQueue2 = session.createQueue("QIN");
    MessageProducer mp2 = session.createProducer(outQueue2);
    TextMessage msg2 = session.createTextMessage("Message From QIN");
    mp2.send(msg2);
    Destination inQueue2 = session.createQueue("QIN");
    MessageConsumer mc2 = session.createConsumer(inQueue2);
    TextMessage receivedMsg2 = null;
    while ((receivedMsg2 = (TextMessage) mc2.receive(1000)) != null) {
    System.out.println("Received: " + receivedMsg2.toString());
    connection.close();
    } catch (Exception e) {
    // an error occurred, just print it out
    e.printStackTrace();
    NOW WHEN I INTEGRATE THE SAME SETTINGS INTO MY ENTERPRISE APPLICATION. I AM HAVING PROBLEM WHICH IS ADDRESSED IN THIS THREAD. IF ANYONE KNOW THE CAUSE AND SOLUTION PLEASE LET ME KNOW WHAT SHOULD I DO TO MAKE IT RIGHT.
    http://forums.sun.com/thread.jspa?threadID=5352394&tstart=0
    I HOPE I GAVE THE ANSWER OF MY OWN QUESTION HERE...HEHEHEHEH :)...BEST OF LUCK
    Edited by: Sheeraz on Dec 4, 2008 3:51 AM

  • SCCM 2012 R2 Distribution Point Installs but does not send packet.

    I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
    send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got. 
    The computer account is in the Administrators group and Admin Domains; 
    Already checked the WMI with Wbemtest; 
    I uninstalled and installed the DP again; 
    Below is the log, changed the name to contoso by issues of customer privacy.
    Sleep 928 seconds...      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:00:07       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:12:13       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5264 (0x1490)
    Thread Handle = 0000000000002330       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5264 (0x1490)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41              
    5264 (0x1490)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    DP thread with thread handle 0000000000002330 and thread ID 5264 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5364 (0x14F4)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41                5364 (0x14F4)
    Failed to process package LAA00003 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41      
    5364 (0x14F4)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:46       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    2528 (0x09E0)
    Sleep 1824 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5736 (0x1668)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5736 (0x1668)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    5736 (0x1668)
    Thread Handle = 0000000000002A50      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with thread handle 0000000000002A50 and thread ID 5736 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5328 (0x14D0)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47       5328 (0x14D0)
    Failed to process package LAA00004 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47      
    5328 (0x14D0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:42:18       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:23       5112 (0x13F8)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5112 (0x13F8)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    5112 (0x13F8)
    Thread Handle = 0000000000001CF0      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:23      
    5012 (0x1394)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:24       5012 (0x1394)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24                5012 (0x1394)
    Failed to process package LAA00003 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:24      
    5012 (0x1394)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:24      
    5012 (0x1394)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:29       4576 (0x11E0)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       4576 (0x11E0)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    4576 (0x11E0)
    Thread Handle = 00000000000025F8       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with thread handle 00000000000025F8 and thread ID 4576 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:29      
    5996 (0x176C)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:30       5996 (0x176C)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30       5996 (0x176C)
    Failed to process package LAA00004 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30      
    5996 (0x176C)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:30      
    5996 (0x176C)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA.   SMS_DISTRIBUTION_MANAGER             14/08/2014
    00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       5292 (0x14AC)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32       4008 (0x0FA8)
    Processing status update for package LAA00003              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32               
    4008 (0x0FA8)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Sleep 1048 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA     SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Sleep 1043 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA.  SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39              
    4008 (0x0FA8)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39       4008 (0x0FA8)
    Processing status update for package LAA00004              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39               
    4008 (0x0FA8)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA    SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 1038 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleep 1033 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:28       5292 (0x14AC)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       5292 (0x14AC)
    Found notification for package 'LAA00003'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Found notification for package 'LAA00004'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x388 (904)      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33              
    2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34              
    2528 (0x09E0)
    Sleep 3600 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
    Lucas Simoes MCTS

    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              13/08/2014 23:57:10               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    13/08/2014 23:57:10       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xBE8)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x3B4)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       3048 (0x0BE8)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       948 (0x03B4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45       3048 (0x0BE8)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45      
    3048 (0x0BE8)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52       948 (0x03B4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52      
    948 (0x03B4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:52       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x1680)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:52               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x18A4)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:16       5760 (0x1680)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:17       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43       6308 (0x18A4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43      
    6308 (0x18A4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50       5760 (0x1680)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50      
    5760 (0x1680)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xF28)      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x11D0)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       3880 (0x0F28)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       4560 (0x11D0)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:16       3880 (0x0F28)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       3880 (0x0F28)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27      
    3880 (0x0F28)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34      
    4560 (0x11D0)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 01:19:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 01:19:34       4004 (0x0FA4)
    No (more) send requests found to process.     
    SMS_PACKAGE_TRANSFER_MANAG
    Lucas Simoes Rezende MCP, MCTS , ITIL V3

  • Nokia Internet Radio Error: Connection Timed Out. ...

    Hi,
    I'm having an issue with the Nokia Internet Radio application on the Nokia N95. The app launches ok but if I try and browse the station directory or perform a search I get the error 'Connection Timed Out. Try Again' This happens almost instantly i.e. it doesn't look like it's even trying to connect. If I go to the shoutcast site and click on the 'Tune In' button next to a station the Internet radio app launches and I get an error saying 'General: System Error' and the application closes then goes back to the browser and a message saying 'Web: No Gateway Reply' The application worked fine up until recently. I upgraded to FW V 21.0.016 and hasn't worked since so it may be that this has caused the problem. I've removed and re-downloaded \ re-installed the software but still get the same issue. Web browsing works fine, so I know my internet settings are fine, and the old open-source version of the radio player even works so it's just an issue with this app. Any advice on how to fix it would be much appreciated. Thanks.

    I had the same problem and I fixed it.  For me, it was because I am on the Rogers network in Canada.  Regardless of where you are many cellular neworks use firewalls and something called NAT (Network Address Translation).  Nokia should really make people aware of this because probably 50% of people around the world have this problem.  The solution for me was to use Rogers VPN or Public IP to access the internet.  Rogers blocks access to this internet connection so you have to add the service to your account for $10 per month but I have heard that other carriers like FIDO have not blocked access to it.
    On the Nokia n79 this requires creating a new access point under TOOLS>SETTINGS>CONNECTIONS>DESTINATIONS.  Add a new access point with the following settings:
    Connection Name: Rogers VPN (or whatever you want to call it)
    Data Bearer: Packet Data
    Access Point Name: vpn.com
    User Name: wapuser1
    Prompt Password: No
    Password: wapuser
    Authenticaiton: Normal
    Homepage: None
    Use Access Point: After Confirmation (or change if you want something else)
    That's it. When you load the internet radio Application and it lists your options select "Rogers VPN".  If you don't see it in the list, press the soft button for Options then "Select Access Point" and you will see the full list.  If you want the VPN to be the first thing you see you can change the priority under destination settings.  Just select the VPN and press "Organize" then "Change priority". 

  • From where the VBRK-STCEG field value in the invoice header gets filled.

    Hi Friends,
    I have a scenario in my client system. I have one sales organisation in Spain which sends a order to France based sales organisation. In the France based sales organisation the sales order will be created with sold to partner as the Spain sales organisation, and the delivery can happen either to same partner or sometimes to another ship to partner who is based in Spain.
    Now, my issue is whenever the France organisation creates invoice against Spain organisation for the sales order delivered, the VAT number of the customer in the VBRK-STCEG field is populated from Ship to partner's master data. The same value will be fetched into the table VEIAV-KUNDEUINR.
    In my case, I want the bill to partners VAT number to be populated in VBRK-STCEG field. How can it be done and where I need to maintain the config for this?
    Thanks
    Chandramouli

    Hello Chandramouli,
    Please find below some SAP Documentation for VAT set up in the IMG Config:
    Maintain Sales Tax Identification Number Determination
    In this IMG activity, you maintain how VAT registration numbers are determined in the sales order and billing document.
    Tax classification is included in this activity.
    Options available to assign to the Sales organization are:
    blank - according to priority rule
    A - generally from sold-to party
    B - generally from payer
    C - according to priority rule, destination country from ship-to party
    If you leave the field blank, the standard priority rule works as follows:
    1. If the payer has a VAT ID number and RG <> AG, then the tax number and tax classification are copied from the payer (in this case, the ship-to party is not relevant).
    The tax number is taken according to the 'tax country of destination'.
    2. If 1. does not apply:
    If the ship-to party has a VAT registration number and the sold-to party does not, tax number and tax classification are copied from the ship-to party.
    3. If 2. does not apply:
    Tax number and tax classification are copied from the sold-to party.
    If you enter A, tax number and tax classification are generally copied from the sold-to party.
    The tax number is copied according to the 'country of destination relevant for taxes'.
    If you enter B, tax number and tax classification are generally copied from the payer.
    The tax number is copied according to the 'country of destination relevant for taxes'.
    I hope this information is useful to you in your work.
    Best Regards
    Sitaraman

  • TTL of message in queue

    Hi all!
    How can I define message time-to-live in queue? I've got some messages in queue with expiraton date by the year 2038.

    1. I've applied patch 116568-53 on my test system.
    2. I've executed patch-config and install-newconfig. Then imsimta chbuild and imsimta cnbuild have been executed.
    3. start-msg
    4. My directory has been updated from cfgdir_diff.ldif and ugdir_diff.ldif.
    5. imta.cnf contain:
    defaults logging notices 1 2 4 7 copywarnpost ......
    ! tcp_local
    tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver sa
    slswitchchannel tcp_auth missingrecipientpolicy 0
    tcp-daemon
    etc.
    6. After that I've sent message on [email protected]
    7. root@sun/opt/SUNWmsgsr/sbin> ./imsimta cache -dump
    channel : tcp_local
    file name : /opt/SUNWmsgsr/data/queue/tcp_local/011/ZXe0j750N0so7.00
    subdirectory : 11
    enqueue time : 22-Sep-2004 16:43:38.00
    last delivery attempt : 22-Sep-2004 17:12:07.00
    processing priority : 3
    destination system : ddddddd.com
    recipient count : 1
    message size : 1 (kbyte)
    owner : mailsrv
    expiration date : 19-Jan-2038 06:14:07.00
    8. qm.maint> his 1
    Message id: 1
    Filename: /opt/SUNWmsgsr/data/queue/tcp_local/011/ZXe0j750N0so7.00
    Transport layer information:
    Envelope From: address: [email protected]
    Envelope To: addresses: [email protected]
    Message delivery history:
    Wed, 22 Sep 2004 16:43:39 +0400 (MSD)
    TCP active open: Failed connect() Error: Connection refused
    Wed, 22 Sep 2004 16:55:23 +0400 (MSD)
    TCP active open: Failed connect() Error: Connection refused
    What does "expiration date" mean ? Why 2038 year ?

  • Remove Extra Columns in Approver Inbox

    There are several columns in the Shopping Cart Approval Manageru2019s inbox that I want to remove, (they are blank) however these fields do not appear in the POWL layout list in SPRO.  Any suggestions on how to hide these fields?
    The feeder type is SAPSRM_IBO_FEEDER_WI and has the following field catalog
    PRIORITYTEXT - Priority
    STATUSTEXT - Status
    TS_SEL (Technical Column)
    WI_AAGENT (Hidden Column)
    WI_CD (Technical Column)
    WI_CD_TS - Sent On
    WI_CONFIRM - (Technical Column)
    WI_END_TS - Due Date
    WI_FORW_BY - Forwarded By
    WI_ID - (Technical Column)
    WI_LANG (Hidden Column)
    WI_PRIO (Technical Column)
    WI_REJECT (Technical Column)
    WI_RHTEXT (Hidden Column)
    WI_RH_TASK (Hidden Column)
    WI_STAT (Technical Column)
    WI_SUBST_FOR - Substitute For
    WI_TEXT - Subject
    However The fields that appear in the Managers Inbox are:
    Subject
    Destination (Blank)
    Descr. (Blank)
    Sent On
    Priority
    RFC Destination (Blank)
    Due Date
    Status
    Forwarded By
    Substitute For
    WI Creator (Blank)
    Thanks
    Jon

    Hi,
    After the refresh button there will be one icon click that
    you can see personalize view
    you can set there whatever column youwant.
    in our case we have
    1.Subject
    2.From
    3.Sent Date
    4.due Date
    5. Status
    Each user can set according to the use.
    If you want the same set of column for all the users you have to help of ABAP and Portal team to set that
    Regards
    G.Ganesh Kumar

  • Absolute message TTL is 14 days ?

    it seems any message has a maximum time where it can stay in any queue :
    snoopy # > ./imsimta cache -view
    channel : ims-ms
    file name : /mail/messaging/msg-snoopy/imta/queue/ims ms/019/ZY0H570020BLZVD0.00
    subdirectory : 19
    enqueue time : 7-Nov-2002 15:09:32.00
    last delivery attempt : 7-Nov-2002 15:09:32.00
    processing priority : 1
    destination system : ims-ms
    recipient count : 1
    message size : 3529 (kbytes)
    owner : mailserv
    expiration date : 21-Nov-2002 15:09:32.00
    this would mean the message will be rejected when it's expiration time has come, ignoring the fact that it maybe should stay any longer due to some overquota retention policy.
    I have put a retention time of 30 days for any message if it can't be delivered to an overquota user. When the message is spooled to an overquota user, i effectively receive some notification mail saying that it will try for another 28 days, then one week later, another mail saying it will try for another 21 days.
    However, after 14 days, the mail gets rejected, with a message "manually aborted by postmaster"
    i suspect this comes from this "expiration date". (it's too much a coincidence)
    The question is : where can i change this expiration date (which seems to be set when the mail is enqueued for the first time) to reflect my retention policy of 30 days ?
    Thanks

    The 28 days seem to be written in your "ims-ms" channel definition in the imta.cnf. The TTL depends on the "notices" keyword. Whatever value you set there should be the TTL in days. Don't know why the message bounces after 14 day. Maybe you should set a policy of 30 days in your "defaults" channel definition and remove the one from "ims-ms"?
    Just a thought.
    Joerg

  • Sun's MQ Clustering issue.

    Cluster issue with Sun Message Queue 3.5
    We are developing a basic ESB (Enterprise Service Bus) system with MQ3 as the JMS
    provider. Naturally we want to cluster multiple brokers on different boxes incase one
    fails. For development and testing we�ve setup two MQ3 brokers on two different
    Windows 2000 machines and both are configured the same and have created the same
    destinations on both. We have one producer client running on a RS6000 AIX machine
    sending messages to a message queue, and one consumer client running on a iSeries
    reading the messages. (Note: There are no problems when we�re not clustering and using
    just one broker). The problem is after the consumer processes about 1k-3k messages it
    like drops its active connection to the message queue. Looking at the Administration
    Console it appears the active consumer rolls down to backup consumer. Here is what the
    console shows.
    When working ok:
    Current Number of Messages: 65231
    Current Total Message Bytes: 501033112 bytes
         Current Number of Producers: 1
    Current Number of Active Consumers: 1
    Current Number of Backup Consumers: 0
    When it stops receiving messages:
    Current Number of Messages: 72652
    Current Total Message Bytes: 515987678 bytes
         Current Number of Producers: 1
    Current Number of Active Consumers: 0
    Current Number of Backup Consumers: 1
    At this point the consumer does not pick up anymore messages, it waits on onMessage().
    However, the producer keeps on running just fine. Also we�re using persistent queues,
    not topics.
    Following are the configuration settings.
    Here is the startup screen shot, both brokers are the same except for the name, this one is
    CFERRIS the other is CFERRIS2K so I just show one here.
    C:\Program Files\Sun\MessageQueue3\bin>imqbrokerd -license try
    [12/Apr/2005:11:35:40 CDT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version:  3.5 SP2  (Build 48-G)
    Compile:  Fri 08/27/2004
    Copyright &#8976; 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_05 Sun Microsystems Inc. c:\j2sdk1.4.2_05\jre
    *****  Trial license enabled.  This license will expire on     *****
    *****  Jun 28, 2005.  This license is for evaluation purposes  *****
    *****  only. You are in violation of the license agreement if  *****
    *****  you use this product with this license enabled in a     *****
    *****  production environment.                                 *****
    [12/Apr/2005:11:35:40 CDT]    IMQ_HOME=C:\Program Files\Sun\MessageQueue3
    [12/Apr/2005:11:35:40 CDT] IMQ_VARHOME=C:\Program Files\Sun\MessageQueue3\var
    [12/Apr/2005:11:35:41 CDT] Windows 2000 5.0 x86 CFERRIS (1 cpu) cferris
    [12/Apr/2005:11:35:41 CDT] Java Heap Size: max=194432k, current=16256k
    [12/Apr/2005:11:35:41 CDT] Arguments: -license try
    [12/Apr/2005:11:35:41 CDT] [B1060]: Loading persistent data...
    [12/Apr/2005:11:35:41 CDT] Using built-in file-based persistent store: C:\Progra
    m Files\Sun\MessageQueue3\var\instances\imqbroker\
    [12/Apr/2005:11:35:45 CDT] [B1039]: Broker "imqbroker@CFERRIS:7676" ready.From the config.properties for both brokers, they are the same:
    #Last Update:
    #Fri Apr 08 15:19:45 CDT 2005
    imq.jms.min_threads=10
    imq.instanceconfig.version=300
    imq.autocreate.queue=false
    imq.jms.tcp.port=0
    imq.cluster.url=file\:\\H\:\\MIS\\928DataBrokerInterfaces\\MOM\\cluster.properties
    imq.autocreate.topic=false
    imq.jms.max_threads=1000
    From the cluster.properties file:
    #Last Update:
    #Fri Mar 25 15:47:49 CST 2005
    imq.cluster.brokerlist=cferris2k:7676,cferris:7676
    imq.cluster.masterbroker=cferris2k
    From imqcmd query bkr which are the same on both boxes.
    Querying the broker specified by:
    Host         Primary Port
    localhost    7676
    Version                                              3.5 SP2
    Instance Name                                        imqbroker
    Primary Port                                         7676
    Current Number of Messages in System                 0
    Current Total Message Bytes in System                0
    Max Number of Messages in System                     unlimited (-1)
    Max Total Message Bytes in System                    unlimited (-1)
    Max Message Size                                     70m
    Auto Create Queues                                   false
    Auto Create Topics                                   false
    Auto Created Queue Max Number of Active Consumers    1
    Auto Created Queue Max Number of Backup Consumers    0
    Cluster Broker List (active)                         CFERRIS/10.3.xxx.xx:7676 (imqbroker), CFERRIS2K/10.3.xxx.xx:7676(imqbroker)
    Cluster Broker List (configured)                     cferris2k:7676,cferris:7676
    Cluster Master Broker                                cferris2k
    Cluster URL                                          file:\H:\MIS\Project Office
    \928DataBrokerInterfaces\A-Request-Requirements\MOM\cluster.properties
    Log Level                                            INFO
    Log Rollover Interval (seconds)                      604800
    Log Rollover Size (bytes)                            unlimited (-1)
    Successfully queried the broker.From imqcmd query dst
    C:\>imqcmd query dst -t q -n resultsFromBOS
    Querying the destination where:
    Destination Name    Destination Type
    resultsFromBOS      Queue
    On the broker specified by:
    Host         Primary Port
    localhost    7676
    Destination Name                      resultsFromBOS
    Destination Type                      Queue
    Destination State                     RUNNING
    Created Administratively              true
    Current Number of Messages            0
    Current Total Message Bytes           0
    Current Number of Producers           0
    Current Number of Active Consumers    0
    Current Number of Backup Consumers    0
    Max Number of Messages                unlimited (-1)
    Max Total Message Bytes               unlimited (-1)
    Max Bytes per Message                 unlimited (-1)
    Max Number of Producers               unlimited (-1)
    Max Number of Active Consumers        unlimited (-1)
    Max Number of Backup Consumers        3
    Limit Behavior                        REJECT_NEWEST
    Consumer Flow Limit                   1000
    Is Local Destination                  false
    Local Delivery is Preferred           false
    Successfully queried the destination.For development and testing I am not using JDNI. The following shows
    how I configured the connection factory.
        public ConsumerClient(int acknowledgementMode) {
          // Initiate the factory and connection.
          // Also directly instantiate and configure the object.
          connectFactory = new com.sun.messaging.ConnectionFactory();
          try {
              connectFactory.setProperty("imqAddressList",
                                                          �mq\://cferris2k\:7676/jms,mq\://cferris\:7676/jms�);
              connectFactory.setProperty("imqReconnectEnabled", �true�);
              // Set client ID/user ID
              connectFactory.setProperty("imqDefaultUsername", "admin");
              connectFactory.setProperty("imqDefaultPassword", "admin");
              connectFactory.setProperty("imqAddressListIterations", "-1");
              connectFactory.setProperty("imqReconnectAttempts", "5");
              connectFactory.setProperty("imqAddressListBehavior", "RANDOM");
              // Next create the connection and session
              connection = connectFactory.createConnection();
              session = connection.createSession(false, acknowledgementMode);
              logger.info("A connection and session have been established by ConsumerClient");
          catch(JMSException jmsError){
              reportError("Error creating the connection factory. Following is the message: ",
                           jmsError.getMessage());
        }  // of constructor I added the three properties imqAddressListIterations, imqReconnectAttempts
    and imqAddressListBehavior as an attempt to fix it, but this did not work, so
    previously they were the defaults. I am wondering if I needed to create destination
    queues on all the brokers or just the master?
    Any help with figuring this will greatly be appreciated!!
    Thanks, Chris

    Chris,
    This is fishy.
    Since the queue is configured to have unlimited active consumers, it should never attach a consumer as a backup. It seems like when the client reconnects, it somehow is establishing the consumers as a backup.
    The first thing I'd try is to change maxNumBackupConsumers on the queue to 0. Hopefully this will either keep the consumer a primary (active) consumer, or trigger another error that would shed more light.
    The other curious thing is why is the client loosing it's connection in the first place? To narrow this down I would turn off reconnect (i.e. set imqReconnectEnabled to false), and register a connection exception listener (Connection.setExceptionListener) and see what exception is being generated. Also check the broker's log file and see if there are any interesting messages.
    When you have brokers clustered, you can create a destination on any broker in the cluster, and the destination will be propogated across the cluster. The following SunSolve document contains more details:
    79051 Sun Java[TM] System Message Queue: Understanding the Role of a Master Broker in an MQ Cluster
    And one other thing about clusters. Messages are persisted on the broker the sender is connected to. Messages are then forwarded to consumers anywhere on the cluster. Acknowledgements flow back to the "producing" broker and are processed by it. If a broker goes down, the messages it holds in its persistent store are not available until that broker comes back up. We're looking at improving data availability in a future MQ release and you can get it today in conjuction with the SunCluster product.
    Joe

  • JMS on Sun Application Server 9.0

    Using Netbeans 5.5 Beta and App Server 9.0 (Java EE 5).
    I'm interested in finding a very comprehensive tutorial on how to create a client application that posts and recieves messages from a message service.
    The Sun tutorial online takes me through a bit of confusion without explaining a lot of the basics beforehand. I have an "App Client Module", and I'm not entirely certain as to what that is.
    Is there some way I can just make a Swing application and enable some class in there to send & receive JMS messages on an application server? If so, how? If not, why not?
    When are messages purged from the JMS? Can you set an expiration? Can you write your clients in such a way that the messages are deleted upon receipt? I'm overall very confused and would like to see some better explanations that don't assume any knowledge on my behalf ;)

    So, I guess really what I'm asking then is - where does the integrity come from? Do the clients communicate directly with each other?
    What if I wanted to use MDBs? I'm trying to centralize the messaging process so that it doesn't have to be a direct connection between two programs. They simply have to know the server and any interested applications or beans can just reach in for the information...
    If I may quote:
    "All Message Queue messages travel from a message producer to a message consumer by way of a destination on a message broker. Message delivery is thus a two-stage process: the message is first delivered from the producer to the destination and later from the destination to the consumer. Physical destinations on the broker are created administratively by a Message Queue administrator, using the administration tools described in the Message Queue Administration Guide; the broker provides routing and delivery services for messages sent to such a destination."
    This tutorial still seems to operate on the basis that there is something in between two or more clients exchanging messages - unless I'm misreading.
    Sorry if this is frustrating at all :)

  • Connecting to WiFi stops 3G?

    1. Is there such a thing as autoconnect to familier networks?Meaning If i connect once to wifi network, will it always connect to it, even if encrypted?
    2.IF answer to (1) is yes:
    If I'm about to enter an area with a Wifi network that my Nokia 701 automatically connects to,     will it connect to it and stop using 3G? Meaning, does it use only Wifi, and not 3G, when connected to Wifi?
    3. Is there an option to make wifi automatically connect to an UNLOCKED wifi network? Meaning I'm entering my office with my phone for a first time, wifi on - will it automatically connect to the open network in the office? 
    THANKS.
    Solved!
    Go to Solution.

     To answer question one, once you have connected to a Wi-Fi network the phone will remember that network and connect to it again automatically. However, you will need to set it's priority above your mobile 3G connection.
     So, for question two. Your phone will automatically connect to a known Wi-Fi access point once it's in range providing that it is given a higher priority in your destinations list. The best thing to do is to set 3G as the lowest priority in destinations and all known Wi-Fi access points above 3G.
     Lastly, your phone will not automatically connect to open Wi-Fi networks unless you have manually connected in the past and the phone has remembered that access point in your destinations list.
    Ray. 

Maybe you are looking for