BC4J send messaging adapter gets JMS exception

Running a 9i standalone application based on BC4J. The following code is trying to send a single VO to an 8i queue. Note: prior to entering this routine, I have already called the .writeXML() method on the same VO and looked at the text and the XML all looks great.
AdapterMessage[] msgs = new AdapterMessage[1];
try {
// set up queue connection
msgs[0] = AdapterMessage.newViewObjectMessage( vo );
sendMessage( msgs );
public void sendMessage( AdapterMessage[] messages)
try
ApplicationModule am = QWsetup.ApplicationModule();
BC4JSendingAdapter adapter = new BC4JSendingAdapter();
adapter.setShowTrace(true);
adapter.sendMessage( am, messages);
catch(AdapterFailureException e)
System.err.println("sendMessage error: "+e.getMessage()+"\n"+
e.getOriginalException());
e.printStackTrace();
I step into the adapter.sendMessage line and get the following in my message window...
[2] Creating JDBC Connection...
[3] oracle.jdbc.driver.OracleDriver
[4] jdbc:oracle:thin:@pgia05.pginw.com:1521:qmpgit
[5] Creating Topic Connection...
[6] Creating Topic Session...
[7] Creating Topic...
[8] Publishing message...
[9] Done.
sendMessage error: JMS exception while processing message
java.lang.NullPointerException

Hi Roger,
I've been looking into your error message: JMS Exception while processing message.
I was able to reproduce this error message. In my case I was trying to send a BESAdapter message without setting its mandatory properties. My code was:
BESAdapterMessage a = (BESAdapterMessage)BESAdapterMessage.newViewObjectMessage(empvo);
BESAdapterMessage[] messages = new BESAdapterMessage[] {a};
try
am.sendMessage(messages);
There are two mandatory properies of the adapter that must be set that I forgot. I found the answer in the help. If you do a search for BESAdapterMessage you will find page Using the Adapter Message class for message payloads. Scroll down this page to the section: Using the BESAdapterMessage Subclass.
Although you are using the adapter classes without the modeler you may find some of the other help topics in the UML Modeling Help useful. Look under Modeling Activities for e-business Integration -> Creating Messaging Adapters.
I have raised a bug to put more validation in so that the error message will specify that properties have not been sent. Here is the abstract from help:
The BESAdapterMessage class (oracle.bm.ebiadapters.BESAdapterMessage) is a subclass of AdapterMessage. It provides additional functionality which is needed by the e-business integration generators to achieve full integration. In addition to setting the payload, the BESAdapterMessage class allows you to set metadata properties which are mapped to JMS header fields. Some of these properties are mandatory and some are optional. For example, the setEventName(String eventName) and setEventKey(String eventKey) methods can be used to set the mandatory Event Name and Event Key properties. Once set, these properties are mapped to JMS header properties to allow the JMS messages to be correctly propagated between Oracle AQ queues.
I've also raised a doc. bug to look again at the doc in this area.
Thank you very much for taking the time to report on this problem. We are reliant on input from people like you to continue to improve our product.
Rgds
Susan

Similar Messages

  • Garbage added to log while sending message to Weblogic JMS topic

    Hi All,
    Was able to sucessfully send messages to Weblogic JMS topic and also able recieve them.
    But while sending the messages to topic loy of debug statements are printed to the standard output
    This is seen only in production and not in developement, and expecting it due config issue...
    Any ideas on this is greatly appriciatied.
    Thanks in advance !
    Cheers,
    Ambha

    Thanks for the replies,
    The problem is certainly not with logger settings...
    The statements which are getting printed are SSL debugging
    The following settings are used by the application which sends messages to the topic :
    Dssl.debug=true
    Dweblogic.StdoutDebugEnabled=true
    These settings are same in Dev, UAT, and Production. But why the debug statements are seen only
    in UAT and Production I am not sure...
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    any Ideas... ?
    Thanks
    Ambha

  • Resend message after catching JMS Exception

    Hi,
    If i resend message after catching JMS Exception is there any chance that the message will be send to the destination queue? (without reconnecting to the queue).
    thanks!

    The problem is you don't really know if its already been sent or not. Then if the broker's gone down you need to recreate your connection, sessions, producers, consumers etc.
    Its much easier to just use a JMS provider which supports auto-reconnection for you which totally hides and fixes all these problems
    http://activemq.apache.org/how-can-i-support-auto-reconnection.html
    James
    http://logicblaze.com/
    Open Source SOA

  • Sending messages concurrently to JMS queue

    Hi,
    I am using Weblogic 10.3 JMS. I have a .NET producer sending messages to a JMS queue using a threadpool. A Java consumer will be consuming the messages. Is it possible to pool the conections/sessions from the producer side to send messages concurrently from the threadpool. Please help.

    You can use standard .NET threading to produce messages in different threads.
    Keep in mind that producers and session instances themselves must not be multi-threaded, although they can all share the same connection.
    When you code, each thread could have a dedicated session and producer.
    Alternately, you could write a very simple pool that the threads share to cache producers. On the other hand, sessions and producers are light-weight once they've been created, so there's often little need to go through this trouble.
    Tom

  • Sender Mail adapter get no mails

    Hello,
    we are using the sender mail adapter to receive mails (IDOCS) from a Exchange server.
    A few days it works, but suddenly no mails are received.
    But in RWB the mail adapter status is green and shows, that there are no new mails. But when I check the mail box with OUTLOOK, there are some mails.
    When I deactivate and activate the mail adapter, all mails are read then.
    Pollinterval: 1 minute
    XI: SP10
    Who can help me are had s similar problem?
    Or is it possible to stop/start the mail adapter (or the adapter engine) automaitcally (more like a workarround)
    best regards
    Werner Magerl

    Hi All,
    I chekced your responses and tried accordingly. Our basis team has given me new link now and the error message has changed. I am getting following error message.
    exception caught during processing mail message; java.io.IOException: unexpected login response; read 001F BAD Command received in Invalid state.
    Does anyone have any idea what this error is?
    Thanks in advance,
    Devendra

  • Sending message to a JMS queue and making DB update through a single container managed transaction

    Can we use container managed transactions to send message to JMS queue and make DB updates in a sigle transaction. If yes then do we need 2pC license. I am using weblogic 6.0 SP2 and my database driver do not supports XA

    If your JMS provider is XA compliant, you can.
    If you are using WebLogic 6.0 JMS, it supports 2PC.
    The JDBC resource that does not support XA can participate in the global transaction
    creating a TXDataSource and setting "enable two-phase commit"=true in the Configuration
    panel.
    About the JMSConnectionFactory, on the console, in WebLogic 6.0, in the "Transaction"
    tab folder, set "User Transactions Enabled"=true.
    In your code, use non-transacted sessions.
    For 2pc protocol, you need a license or you'll get an exception.
    Sergi
    Manoj Bansal <[email protected]> wrote:
    Can we use container managed transactions to send message to JMS queue and
    make DB updates in a sigle transaction. If yes then do we need 2pC license.
    I am using weblogic 6.0 SP2 and my database driver do not supports XA

  • Sender SOAP adapter: get soap header data

    Hi,
    I've been going through various posts and blogs here on SDN + looked in the how to guide for SOAP adapter, but still find it quite difficult to actually find out how to do it. I've tried to follow recommendations seen, but it doesn't add up.
    So can someone please tell me how to get an element situated in the SOAP header of the request sent to XI via sender soap adapter?
    Let's for instance say the request looks like this:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Header>
              <SSN>1234567890</SSN>
         </SOAP-ENV:Header>
         <SOAP-ENV:Body>
              <event>
                   <elem1>data 1</elem1>
                   <elem2>data 2</elem2>
                   <elem3>data 3</elem3>
              </event>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    How can I get the data in the SSN-header element at mapping time?
    I'm sure this can be done by using adapter modules as the first step adapter, but I prefer doing it at mapping time if possible.
    Best Regards,
    Daniel

    I solved it on my own now. My missing link was the fact that I'm using XMLSPY to send request and thus need to replace all '&amp;' with & in Connection Endpoint.
    Message was edited by:
            Daniel Engsig-Karup

  • Garbage added to log file while sending messags to weblogic JMS topic

    Hi All,
    While I am sending messages to JMS Topic some debug statements are printed to stdout...
    which is only happening in production rather than in dev environment, hence I feel this is a configuration issue..
    sheding light on this issue is greatly appreciated,
    thanks in advance !
    regards,
    Ambha

    Thanks for the replies,
    The problem is certainly not with logger settings...
    The statements which are getting printed are SSL debugging
    The following settings are used by the application which sends messages to the topic :
    Dssl.debug=true
    Dweblogic.StdoutDebugEnabled=true
    These settings are same in Dev, UAT, and Production. But why the debug statements are seen only
    in UAT and Production I am not sure...
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    *<Some TIME IST> <Debug> <TLS> <000000> <......>*
    any Ideas... ?
    Thanks
    Ambha

  • Sender Mail adapter: Null Pointer Exception

    Hi ,
    Sender mail communication channel using mail package  & POP3 protocol is showing the Error: exception caught during processing mail message; java.lang.NullPointerException.  Initially it works fine but now it is showing this error. I could not get the root cause of this error.
    Can any one help me to resolve the issue?
    Thanks in Advance
    Krishna

    Hi Sherin Jose,
    There is no value mapping used here.
    I am not getting the root cause for this error. can any one suugest
    Thanks & regards,
    Krishna

  • Getting JMS Exception while starting the managed servers

    Hi ,
    I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
    Thanks in advance...
    <Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
    <Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    *<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
    MS destination: jms/BLAdminTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
    s "sbmejb1,sbmejb2">
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
    JMS destination: jms/BLCacheSyncTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
    MS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
    otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
    m76" running in Production Mode>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
    destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
    the JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
    MS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
    e JMS destination: jms/BPAdminTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    Hi Rohit,
    Thanks for your response..
    Below is the BLAdminTopic configuration.Please let me know if you need any further info.
    Topic:BLAdminTopic
    Type:Distributed Topic
    JNDI:jms/BLAdminTopic
    Sub Deployment :N/A
    Target:N/A
    BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
    BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
    Regards,
    Jyotiranjan

  • While deploying Campaign Optimizer test , Getting JMS Exception.

    Getting below error when test is deployed to satging but it fails to start.
    Below port is defined in DynamoMessagingDSSGlobal.xml and entries looks fine in XML and scenario Manager, Is anyone having any idea how to resolve this and why its coming.
    CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    Complete Log trace is:
    info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    ed May 23 18:40:07 CDT 2012' dynamo.log G-Data/servers/AdminServer/logs$ grep 'W
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407688 /atg/epub/DeploymentAgent state changing : new = DONE_APPLY : current = ACTIVE_APPLY : previous = DONE_PREPARE
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407689 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407706 /atg/epub/DeploymentAgent state changing : new = ACTIVE_ACTIVATE : current = DONE_APPLY : previous = ACTIVE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407798 /atg/epub/cache/SelectiveCacheInvalidator Found 0 repository item(s) in this deployment
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407799 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407801 /atg/epub/DeploymentAgent refreshing/updating VFS : /atg/epub/file/ConfigFileSystem
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Error adding process /CampaignOptimizer/tests/CO_05232012-abt90002.sdl; rolling back the transaction CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor --- CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407974 /atg/commerce/claimable/ClaimableRepository invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/commerce/catalog/ProductCatalog invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** info Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/search/repository/RefinementRepository Starting invalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407976 /atg/search/repository/RefinementRepository Starting premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407977 /atg/search/repository/RefinementRepository Completed premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407978 /atg/commerce/pricing/priceLists/PriceLists invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407979 /atg/epub/DeploymentAgent state changing : new = DONE_ACTIVATE : current = ACTIVE_ACTIVATE : previous = DONE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407981 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active

    Can you post the dynamoMessaging.xml if you still have this issue

  • Accessing remote jms provider to send message

    My application has web tier and app tier. I configured jms provider in web tier and created a message driven bean which listens to this provider. I want to ship all me exception stack trace to web tier logs. In app tier when any exception occurs I want to send message to topic (jms provider) in web tier so that mdb in web tier consumes this message and logs it to the log files. For this I should access jms provider in app tier. How can I achieve this?

    Hi,
    You can prevent administrators from changing the permissions for a connection by applying the
    Do not allow local administrators to customize permissions Group Policy setting. 
    This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
    Apart there is one command with which you can set the permission for that check the related
    article. Additionally checkthis
    thread for more detail.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Bridge NOT able to connect to one server and send message

    I have configure JMS bridge between MQ queue and a distributed queue ( which is targeting JMS servers in a cluster ).
    Bridge is able to connect to all servers and transfer messages, except one.
    Messages arriving on the MQ queue are delivered by the JMS bridge to all the JMS servers except one
    We turned on debug on MessagingBridge on affected server and got the error msg in the attached log.
    Following is the exception strace:
    <Jan 21, 2010 7:22:19 PM EST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "TsysTIPSBridge" encountered some problems in one of
    its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The excepti
    on caught was java.lang.Exception: javax.resource.ResourceException: Error sending message
    at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1470)
    at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:714)
    at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1325)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1251)
    at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:2070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:2066)
    at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2969)
    at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
    at java.lang.Thread.run(Thread.java:595)
    -------------- Linked Exception ------------
    javax.resource.ResourceException: Error creating producer or sending message
    at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1470)
    at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:815)
    at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:84)
    at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:707)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:704)
    at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1325)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1251)
    at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:2070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:2066)
    at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2969)
    at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
    at java.lang.Thread.run(Thread.java:595)
    -------------- Linked Exception 2 ------------
    javax.jms.MessageNotWriteableException: MQJMS0008: JMS Client attempts to write a read-only message
    at com.ibm.jms.JMSMessage.newMessageNotWriteableException(JMSMessage.java:4782)
    at com.ibm.jms.JMSMessage.setStringProperty(JMSMessage.java:5738)
    at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java)
    at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:773)
    at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:84)
    at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:707)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:704)
    at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1325)
    at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1251)
    at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:2070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:2066)
    at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2969)
    at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
    at java.lang.Thread.run(Thread.java:595)
    I am new to JMS
    Please help

    What version of WebLogic and MQ are you using?
    Have you ensured that the target Destination and Connection Factory are both WebLogic artifacts (neither should reference an MQ resource)?
    Tom

  • Sender RFC Adapter Issue

    Hi ,
    I am using the following scenarion  (SAP ECC)Sender RFC>PI 7.1->Receiver JDBC(ThirdParty).
    The issue is whenever the the ECC system is down and is up again , the RFC sender messages are getting struck in SM58(tRFC queue).What I manually do is , go the RFC Sender communication channel in PI and reactivate it again, by making a small change in the description of the communication channel.
    So, my question is , whether there is a automatical ways to handel this issue.
    Any other suggestions would be highly appreciated.
    Thanks,
    Venu

    There is no standard way to perform this automatically. I think restart of ECC is not a frequent practice in any business, therefore ideally you should add this as one of the post processing procedures after ECC restart.
    Technically, there is possibility of creating a scenario which can run through a job on ECC running once after each restart. This can call webservice in PI to fetch communication channel information and reactivate it. Not a solution I would recommend.
    Regards,
    Prateek

  • Creating a QueueReceiver after sending message to the QueueSender

              Hi,
              I'm implementing a blocking system, sending messages to a JMS Queue.
              In a servlet, in the init method, I'm creating the QueueSender object.
              When calling the servlet, in the service method, if I need to create a new
              message to let users know
              that one primary key is blocked, I create a message with a:
                   msg.setStringProperty("MyTablePrimaryKey", "PKValue");
              Then, I send it.
              If other clients want to update that record, he creates in the servlet's service
              a QueueBrowser like this:
              QueueBrowser receptor=qsession.createBrowser (myQueue, strFilter);
              where strFilter is "MyPrimaryKey IS NOT NULL".
              If the enumeration my QueueBrowser returns hasMoreElements(), the record is
              blocked.
              To unblock a record, I fetch the message from QueueBrowser with the with Enumeration.nextElement,
              and I set:
              message.setJMSExpiration(1);
              so the message is automatically deleted from the queue.
              I tried to use QueueReceiver to implement it, but as I don't know the filter's
              name in the init method of my servlet,
              it's not possible to read messages if the QueueReceiver is created after having
              sent those messages.
              Is my implementation correct? Is the behaviour of QueueReceiver logical?
              Of course, I'm thinking of doing all these things in EJBs to use transactions
              with JTA and JMS. Can be any problem
              with it?
              Sorry for the long question, but I've started discovering JMS a few hours
              ago, and it looks so interesting... :-)
              Best Regards,
              Ignacio
              

              Ignacio Sanchez wrote:
              > Tom Barnes <[email protected]> wrote:
              >
              >>
              >>Ignacio Sanchez wrote:
              >>
              >>>Hi,
              >>>
              >>> I'm implementing a blocking system, sending messages to a JMS Queue.
              >>>
              >>> In a servlet, in the init method, I'm creating the QueueSender
              >>
              >>object.
              >>
              >>> When calling the servlet, in the service method, if I need to create
              >>
              >>a new
              >>
              >>>message to let users know
              >>>that one primary key is blocked, I create a message with a:
              >>>     msg.setStringProperty("MyTablePrimaryKey", "PKValue");
              >>> Then, I send it.
              >>>
              >>> If other clients want to update that record, he creates in the
              >>
              >>servlet's service
              >>
              >>>a QueueBrowser like this:
              >>> QueueBrowser receptor=qsession.createBrowser (myQueue, strFilter);
              >>> where strFilter is "MyPrimaryKey IS NOT NULL".
              >>> If the enumeration my QueueBrowser returns hasMoreElements(), the
              >>
              >>record is
              >>
              >>>blocked.
              >>
              >>
              >>How? The QueueBrowser supplies a snap-shot of the queue, it doesn't
              >>prevent other receivers and queue-browsers from seeing the message.
              >>
              >
              >
              > That's exactly what I want. I want concurrent queue-browsers to see the same message.
              >
              >
              >>>
              >>> To unblock a record, I fetch the message from QueueBrowser with
              >>
              >>the with Enumeration.nextElement,
              >>
              >>>and I set:
              >>
              >>> message.setJMSExpiration(1);
              >>> so the message is automatically deleted from the queue.
              >>
              >>
              >>This will have no effect. Expiration can only be set when the message
              >>is sent, and only via the producer API not the message API. The message
              >>API setter is not intended for application use (see the
              >>javax.jms.Message javadoc). To delete the message you can
              >>create a QueueReceiver with a selector based on the message's
              >>message-id, then receive and acknowledge the message.
              >>
              >
              >
              > But it works!! I've tested once and again and it works fine for me. Shouldn't
              > it???
              >
              Gah!! This behavior is not supported. Do not depend on it to
              be there in future releases or SPs. Any changes to an already
              sent message by a client should propagate to the copy that
              is on the server.
              In fact, I think this may have already been fixed. Can you
              tell me which release and SP you are using?
              >>>
              >>> I tried to use QueueReceiver to implement it, but as I don't know
              >>
              >>the filter's
              >>
              >>>name in the init method of my servlet,
              >>> it's not possible to read messages if the QueueReceiver is created
              >>
              >>after having
              >>
              >>>sent those messages.
              >>
              >>I don't understand. If you can create the QueueBrowser when you
              >>need it, why can't you just create a QueueReceiver with a new selector?
              >
              > If I create a new QueueReceiver after having sent the message using a QueueSender,
              > the
              > receiver cannot read the messages already posted, even in selector is OK. But
              > it works with
              > a QueueBrowser ¿¿??¿¿
              If a QueueBrowser can see the message so should a QueueReceiver. They
              both use the same filter/selector mechanism. It is surprising
              that one worked and the other didn't. Or are you referring to
              the normal behavior that only one QueueReceiver can "see" the message
              at a time? And that once a QueueReceiver has a message the
              QueueBrowser will not "see" it?
              > That's why I'm using QueueBrowser and not QueueReceiver.
              >
              >
              >>>
              >>> Is my implementation correct? Is the behaviour of QueueReceiver
              >>
              >>logical?
              >>
              >>>
              >>> Of course, I'm thinking of doing all these things in EJBs to use
              >>
              >>transactions
              >>
              >>>with JTA and JMS. Can be any problem
              >>> with it?
              >>>
              >>> Sorry for the long question, but I've started discovering JMS a
              >>
              >>few hours
              >>
              >>>ago, and it looks so interesting... :-)
              >>>
              >>> Best Regards,
              >>> Ignacio
              >>
              >
              

Maybe you are looking for

  • My pictures won't show up on my Hard Drive when I try to view them from my MacBook Pro

    I just came back from a trip and have been trying to get my pictures off my iPhone and other camera to put on my external hard drive (it's about 17 GB, so I don't want to waste the space by keeping them on my MacBook). I transferred all the pictures

  • How do I hook up a PC monitor to my Mac?

    Five years ago, when I was young and foolish, I bought a PC. Last evening I dismantled it and the thought struck me that maybe I could use the perfectly good monitor as an adjunct to my FCE movie making. Perhaps I could display the browser on it and

  • CAD "Select reason for not ready" not appearing for some agents? Please help!

    Hi all, I have some users who when they click on 'Not Ready' in CAD (Cisco Agent Desktop) - they are not presented with the 'Select Reason for Not Ready' dialog box - it just goes straight to Not Ready. I have searched high and low but have not found

  • IPod Nano 4G won't work with my car stereo

    So I bought a new stereo for my car and it has a built in controls for an iPod and a dedicated wire for my iPod to directly connect to the stereo. I placed this wire in the glove box. Now the stereo was installed fine, everything works except for my

  • File Sender Adapter: Content Conversion :Mandatory parameter 'xml.keyfieldN

    i have a scenario where i had to pick a flat file and post it to RFC. on the basis of keyfields i had to pick the values <b>but i am getting mandatort field xml.keyfieldnamec: no value</b> my flat file is of type : E2EDL20                       02000