Generic JMS MDB Processing Questions

Using MessageDrivenBean
This bean can only receive a message from the JMS queue server using its onMessage(Message msg) method. If onMessage is called and cannot process the message due to some external resource being down, it seems the only two outcomes are to wait for the external resource to be available, or queue the message to another queue. I've read throwing an exception is not a "good programming" practice. My questions are:
- Is the above the proper way to code the onMessage() method?
- Is there a way to shutdown the MessageDrivenBean or JMS queue server when exiting the application?
Thanks for your help.
Joe

Is it also possible to have the consumer close itself
by queuing a close message to the queue with highest
priority and the consumer calling its close()
method?Not if you using onMessage. A consumer is driven by a session, a session is singlethreaded and calls onMessage, a close must wait until all onMessage calls have been finsihed. Hence, if you call close within onMessage, you have a deadlock.
But you can use the synchronous receive() method of a consumer and call close after you've received it.
-- Andreas

Similar Messages

  • How to interrupt MDB processing

    Hi
    We have a problem with web service call from MDB. Due to some network problems the call can hang for 30 minutes and any no way of setting timeout on JAX-WS port nor sun.net works. Whats more there is a silent transaction timeout on JTA (with no exception) and when web service call returnes after such a long time with success, the message is rolled back to JMS queue.
    I wonder if there is any wat to set timeout on MDB processing that would casue exception and let us control this behaviour. When there is more messages like described above it causes our queue processing to stall and gives us real headache !
    please help

    Thank you a lot for replies
    You both are right.
    As we went down to implementation details it appeared that there is no way (at lest not brutal way) to stop MDB processing. I believe that fiddling with threads in appserver environment is asking for troubles, so I decided to find the source of first problem: no timeout to WS processing.
    To our suprise it was caused by... migration from NetBeans 6.5 to 6.7. Somehow build scripts were affected and some jars were added to ejb jar, which were not there while using NB 6.5. Some of these jars were JAX-WS jars.
    It seams that timout does not work when using JAX-WS shipped with NB 6.7 but there is no problem using libraries shipped with Glassfish 2.1.
    When we removed JAX-WS from our deployment we got controls of timeouts back in our hands.
    thank you again

  • WAAS Application Requests - Process Question

    Non Technical Process Question
    We all have forms we have our users complete when a firewall rule or change is needed.  You may even have a similiar documents for when load balancers or DNS changes are required.  Does anyone have document they can share that outlines what pieces of information are needed for intergrating applications into WAAS?  What about ongoing changes?
    Source, destination and TCP port information is really a very small portion of the what needed to maintain a clean a defined methodolgy within the WAAS manager.  Does anyone have an example or can describe how you collect the initial information to set up WAAS but how do you keep track of changes that may be needed as the application charaterics change or the server farm expands horizontally?
    Thanks - Sam

    Sam,
    the general answer for detailed information on how to configure WAAS for certain applications is described here:
    http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v501/configuration/guide/policy.html
    In general, WAAS comes preconfigured for the most widly used applications in the industry.
    In order to understand, which configuration is necessary for a new application, one needs to understand the basic options WAAS offers.
    These are two options:
    1) Use an Application Optimizer (AO) if you need some dedicated protocol know how. ( e.g. (e)MAPI, CIFS, SSL, HTTP, ICA, to name some)
    2) Generic TCP traffic is optimized using TCP Flow Optimization (TFO), Data Redundancy Elemination (DRE) and Lempe Liv (LZ) compression.
    The in terms of processes, the question is:
    1) Is there a policy preconfigured for the new application?
         a) yes
              If an AO is used, does the AO need configuration? ( example: SSL AO requires certificates)
              Do we have specialities which require further fine tuning? ( Answer is mostly: no, Example: non-standard ports)
         b) no
              You define what you need for the application based on the protocol characteristics.
              If you have defined these characteristics you can choose one of the AOs, or define which of the "generic" options fit the traffic. For example, for traffic that is already compressed, it does not much benefit from LZ, so choosing only TFO and DRE. Another example is traffic that has not much of dublicate data, perhaps it does not benefit a lot from DRE, so you configure TFO only.
    Does that answer your question?
    Thanks,
    chris

  • Question related to my previous "background process" question.

    Hello Folks:
    Can I start a "Notification Service Subscriber" process through the
    normal startup procedure for other servers---i.e. by adding it to the
    config(ubb) file. If so, can I implement the background process as two
    different CORBA servers calling each other asynchronously to accomplish
    the work. Please let me know if there is any other way to accomplish
    what I have stated in the "background process" question.
    Thanks,
    Ram Ramesh
    678-358-3581

    Go to your forum preferences and set the email options.  You may also need to unsubscribe from forums / topics you are currently subscribed to.

  • How to write Generic JMS Adapter

    I want to write generic JMS Adapter. Any link , resources and ideas will be helpful for me.

    Thanks. I saw the ServiceMix. But I am unable to understand the XML file ie ServiceMix.xml. Any kind of help in understanding it will be very helpful. I want to know what changes are required to be made in ServiceMix.xml to communicate from one message Server to other. Being more specific we are not using any application server. We have embedded OpenJMS. That is OpenJms is used for the messaging purpose.

  • Generic JMS Adapter for SeeBeyond

    Hi Guys,
    I am trying to post a mesage on a SeeBeyond JMS queue and so, I have to access it using a JMS Adapter of Generic Type. (as SeeBeyond JMS service does not support a JNDI lookup)
    To do the same, we have already imported all the JAR files needed to access a SeeBeyond JMS service into out XI Server.
    Any help on how to configure a JMS adapter Generically to accees the SeeBeyond JMS in specific or how to configure a Generic JMS adapter would be very helpful.
    Thanks and Regards,
    Bhavesh

    Bump - Were having the same issue.
    Has anyone found a way to connect to Tibco with a user/pwd?
    Version 14.0.297.

  • JMS - MDB

    Hi everybody,
    I'm new to JMS/MDB and have following problem while deploying MDB under JBOSS:
    22:58:47,735 INFO [EjbModule] Deploying MyPublisher
    22:58:47,745 INFO [EjbModule] Deploying topicMessageBean
    22:58:47,795 WARN [StatelessSessionContainer] message-destination 'PhysicalTopic' has no jndi-name in jboss.xml
    22:58:47,845 INFO [ProxyFactory] Bound EJB Home 'MyPublisher' to jndi 'ejb/MyEj
    bReference'
    22:58:47,865 INFO [EJBDeployer] Deployed: file:/D:/DownLoads/ejb/JBoss/jboss-4.
    0.3/jboss-4.0.3/server/default/deploy/simplemessage.jar
    jboss.xml
    <jboss>
    <enterprise-beans>
    <message-driven>
    <ejb-name>topicMessageBean</ejb-name>
    <destination-jndi-name>topic/MyMDBTopic</destination-jndi-name>
    <mdb-connection-factory>
    <jndi-name>jms/MyTopicConnectionFactory</jndi-name>
    </mdb-connection-factory>
    </message-driven>
    <message-destination>
    <message-destination-name>PhysicalTopic</message-destination-name>
    <jndi-name>topic/MyMDBTopic</jndi-name>
    </message-destination>
    <session>
    <ejb-name>MyPublisher</ejb-name>
    <jndi-name>ejb/MyEjbReference</jndi-name>
    <resource-ref>
    <res-ref-name>jms/MyTopicConnectionFactory</res-ref-name>
    <jndi-name>jms/TopicConnectionFactory</jndi-name>
    <default-resource-principal>
    <name>guest</name>
    <password>guest</password>
    </default-resource-principal>
    </resource-ref>
    </session>
    </enterprise-beans>
    </jboss>
    ejb-jar.xml
    <ejb-jar>
    <display-name>MessageJAR</display-name>
    <enterprise-beans>
    <message-driven>
    <display-name>Topic Message Bean</display-name>
    <ejb-name>topicMessageBean</ejb-name>
    <ejb-class>MessageBean</ejb-class>
    <messaging-type>javax.jms.MessageListener</messaging-type>
    <message-selector></message-selector>
    <transaction-type>Container</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    <message-destination-link>PhysicalTopic</message-destination-link>
    </message-driven-destination>
    <activation-config>
                        <activation-config-property>
                        <activation-config-property-name>messageSelector</activation-config-property-name>
                        <activation-config-property-value>NewsType = 'Sports' OR NewsType = 'Opinion'</activation-config-property-value>
                        </activation-config-property>
                        <activation-config-property>
                        <activation-config-property-name>subscriptionDurability</activation-config-property-name>
                        <activation-config-property-value>NonDurable</activation-config-property-value>
                        </activation-config-property>
                   </activation-config>
    </message-driven>
    <session>
    <display-name>MyPublisher</display-name>
    <ejb-name>MyPublisher</ejb-name>
    <home>PublisherHome</home>
    <remote>Publisher</remote>
    <ejb-class>PublisherBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
         <res-ref-name>jms/MyTopicConnectionFactory</res-ref-name>
              <res-type>javax.jms.TopicConnectionFactory</res-type>
              <res-auth>Container</res-auth>
              <res-sharing-scope>Shareable</res-sharing-scope>
         </resource-ref>
         <message-destination-ref>
         <!--message-destination-ref-name>topic/TopicName</message-destination-ref-name-->
              <message-destination-ref-name>topic/MyMDBTopic</message-destination-ref-name>
              <message-destination-type>javax.jms.Topic</message-destination-type>
              <message-destination-usage>Produces</message-destination-usage>
              <message-destination-link>PhysicalTopic</message-destination-link>
         </message-destination-ref>
         <security-identity>
    <use-caller-identity/>
    </security-identity>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
         <container-transaction>
         <method>
              <ejb-name>topicMessageBean</ejb-name>
              <method-name>onMessage</method-name>
              <method-params>
              <method-param>javax.jms.Message</method-param>
              </method-params>
         </method>
         <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
         <method>
              <ejb-name>MyPublisher</ejb-name>
              <method-intf>Remote</method-intf>
              <method-name>publishNews</method-name>
         </method>
         <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <message-destination>
         <message-destination-name>PhysicalTopic</message-destination-name>
         </message-destination>
    </assembly-descriptor>
    </ejb-jar>
    can somebody help???
    Zahid

    Thanks for the reply.
    I'm not getting any errors. The MDB doesn't get invoked when a message is sent on the Topic its listening on.
    The deployment descriptors are given below:
    ejb-jar.xml
    <message-driven>
    <ejb-name>PkgMDB</ejb-name>
    <ejb-class>com.pkg.jms.PkgMDB</ejb-class>
    <transaction-type>Container</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    </message-driven-destination>
    </message-driven>
    orion-ejb-jar.xml
    <message-driven-deployment name="PkgMDB"
    destination-location="jms/PkgTopic"
    connection-factory-location="jms/PkgConFactory">
    <resource-ref-mapping name="jms/PkgTopic" />
    <resource-ref-mapping name="jms/PkgConFactory" />
    </message-driven-deployment>
    jms.xml
    <topic name="jms/PkgTopic" location="jms/PkgTopic">
    </topic>
    <topic-connection-factory name="jms/PkgConFactory" location="jms/PkgConFactory">
    </topic-connection-factory>
    web.xml
    <resource-ref>
    <res-ref-name>jms/PkgTopic</res-ref-name>
    <res-type>javax.jms.Topic</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    <resource-ref>
    <res-ref-name>jms/PkgConFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    Regards
    Ranga

  • JMS - MDB, jboss deployment problem

    Hi everybody,
    I'm new to JMS/MDB and have following problem while deploying MDB under JBOSS:
    22:58:47,735 INFO [EjbModule] Deploying MyPublisher
    22:58:47,745 INFO [EjbModule] Deploying topicMessageBean
    22:58:47,795 WARN [StatelessSessionContainer] message-destination 'PhysicalTopic' has no jndi-name in jboss.xml
    22:58:47,845 INFO [ProxyFactory] Bound EJB Home 'MyPublisher' to jndi 'ejb/MyEj
    bReference'
    22:58:47,865 INFO [EJBDeployer] Deployed: file:/D:/DownLoads/ejb/JBoss/jboss-4.
    0.3/jboss-4.0.3/server/default/deploy/simplemessage.jar
    jboss.xml
    <jboss>
    <enterprise-beans>
    <message-driven>
    <ejb-name>topicMessageBean</ejb-name>
    <destination-jndi-name>topic/MyMDBTopic</destination-jndi-name>
    <mdb-connection-factory>
    <jndi-name>jms/MyTopicConnectionFactory</jndi-name>
    </mdb-connection-factory>
    </message-driven>
    <message-destination>
    <message-destination-name>PhysicalTopic</message-destination-name>
    <jndi-name>topic/MyMDBTopic</jndi-name>
    </message-destination>
    <session>
    <ejb-name>MyPublisher</ejb-name>
    <jndi-name>ejb/MyEjbReference</jndi-name>
    <resource-ref>
    <res-ref-name>jms/MyTopicConnectionFactory</res-ref-name>
    <jndi-name>jms/TopicConnectionFactory</jndi-name>
    <default-resource-principal>
    <name>guest</name>
    <password>guest</password>
    </default-resource-principal>
    </resource-ref>
    </session>
    </enterprise-beans>
    </jboss>
    ejb-jar.xml
    <ejb-jar>
    <display-name>MessageJAR</display-name>
    <enterprise-beans>
    <message-driven>
    <display-name>Topic Message Bean</display-name>
    <ejb-name>topicMessageBean</ejb-name>
    <ejb-class>MessageBean</ejb-class>
    <messaging-type>javax.jms.MessageListener</messaging-type>
    <message-selector></message-selector>
    <transaction-type>Container</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    <message-destination-link>PhysicalTopic</message-destination-link>
    </message-driven-destination>
    <activation-config>
    <activation-config-property>
    <activation-config-property-name>messageSelector</activation-config-property-name>
    <activation-config-property-value>NewsType = 'Sports' OR NewsType = 'Opinion'</activation-config-property-value>
    </activation-config-property>
    <activation-config-property>
    <activation-config-property-name>subscriptionDurability</activation-config-property-name>
    <activation-config-property-value>NonDurable</activation-config-property-value>
    </activation-config-property>
    </activation-config>
    </message-driven>
    <session>
    <display-name>MyPublisher</display-name>
    <ejb-name>MyPublisher</ejb-name>
    <home>PublisherHome</home>
    <remote>Publisher</remote>
    <ejb-class>PublisherBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
    <res-ref-name>jms/MyTopicConnectionFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <message-destination-ref>
    <!--message-destination-ref-name>topic/TopicName</message-destination-ref-name-->
    <message-destination-ref-name>topic/MyMDBTopic</message-destination-ref-name>
    <message-destination-type>javax.jms.Topic</message-destination-type>
    <message-destination-usage>Produces</message-destination-usage>
    <message-destination-link>PhysicalTopic</message-destination-link>
    </message-destination-ref>
    <security-identity>
    <use-caller-identity/>
    </security-identity>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>topicMessageBean</ejb-name>
    <method-name>onMessage</method-name>
    <method-params>
    <method-param>javax.jms.Message</method-param>
    </method-params>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>MyPublisher</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>publishNews</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <message-destination>
    <message-destination-name>PhysicalTopic</message-destination-name>
    </message-destination>
    </assembly-descriptor>
    </ejb-jar>
    can somebody help???
    Zahid

    Hi,
    if possible, try with "max-bean-in-free-pool=1".
    note: it would be performance impact, as there would be single bean instance.
    Thanks,
    Qumar Hussain

  • JMS with MDB design question

    Hi All,
    Here is my situation. I have a JMS Queue and a MDB that consumes the messages delivered to this queue. In the OnMessage method of the MDB,I do some business processing including talking to a database. My requirement is that if the database is not available for some reason,I have to keep retrying the whole thing for half an hour at some predefined intervals. How can this be achieved?
    Thanks

    hi.
    i agree with arnaud that the use of timer is better. thanks for that, arnaud.
    additionally, i'd like to add that i don't think you should use a transaction for this sort of messaging, since from what i understand, you are talking single messaging here, and creating transactions for a single message flow is an overkill for most needs. also, it takes a lot of resources from the application server.
    the other point to consider is that you are not talking about a case where a message did not reach it's destination. as far as the messaging provider is concerned, the message was consumed by the MDB, and the problem occured in latter processing. you also, as crackers noted, have the issue of configuring the provider to handle the redeliveries, which is again a pain in a body-part.
    i think this is a design-related case, and i might go over the messaging-provider's acks here, and send acks on a different queue.
    nimo.

  • How to manage parallel processing for queue JMS/MDB?

    Hello, we are developing a system in WebLogic Server 10g (10.3.0) that contains multiple JMS queues associated with each in an MDB. We need know how manage the parallelism of the message for each queue? for example:
    Queue 1: up to 4 messages in parallel
    Queue 2: up to 2 messages in parallel
    Queue 3: up to 5 messages in parallel
    Can also perform this configuration from the WebLogic Server Admin Console?
    Thank you very much,
    Lucas.

    Thanks a lot Tom for the reply, I have read about the descriptor setting 'max-beans-in-free-pool' and I searched this concept at the Administration Console without success.
    I suppose other way is create a “Session Pools” under the JMSServer, and then create a “Consumer” and define the setting “Messages Maximum”. One of the disadvantages is that “Session Pools” don’t support JTA, from the documentation:
    +Session pools enable an application to process messages concurrently. Session pools are now used rarely, as they are not a required part of the J2EE specification, do not support JTA user transactions, and are largely superseded by message-driven beans (MDBs), which are a required part of the J2EE specification.+
    I continue reading the MDB chapter of the performance and tuning guide in the documentation, thanks for any contribution to the topic.
    Lucas.

  • MDB tx processing question

    Tom,
    My understanding was that WebLogic by default configuration would pull n messages at a time from the a foreign jms server (via JMS connection poller) ; and process the n messages using the same MDB in n different transactions. Is this correct?
    If it is , what would be the conditions when the message would just stay in WebLogic layer - and weblogic MDB will continuously try to process the message - assuming the code in MDB called setRollbackOnly upon processing failure within the MDB. MDB is transactional.
    We see a thread that seems to sit in the state below in our application - no matter how many threaddumps I take the thread stays at this point. I see no other thread waiting on a lock for anything. But this seemingly stuck thread is causing 5 messages on Tibco EMS to stay in pending state until I shutdown the WLS node - which then breaks the tibco session and tibco then makes the messages available for redelivery and another WLS instance picks it up. Do note that WLS does not report any stuck threads either (stuck thread timeout set to 600 seconds) and my threaddumps span across 5 seconds to 45 minutes.
    "ContinuousJMSMessagePoller :MessageProcessor-Tes-Mts" id=4973 idx=0xde tid=1717 prio=5 alive, daemon
    at java/util/HashMap.get(HashMap.java:344)[optimized]
    at org/jboss/cache/UnversionedNode.getDirect(UnversionedNode.java:203)[inlined]
    at org/jboss/cache/invocation/NodeInvocationDelegate.getDirect(NodeInvocationDelegate.java:212)[optimized]
    at org/jboss/cache/CacheImpl._get(CacheImpl.java:702)[optimized]
    at sun/reflect/GeneratedMethodAccessor176.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)[optimized]
    at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
    at java/lang/reflect/Method.invoke(Method.java:585)[optimized]
    at org/jgroups/blocks/MethodCall.invoke(MethodCall.java:330)
    at org/jboss/cache/interceptors/CallInterceptor.invoke(CallInterceptor.java:53)
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/EvictionInterceptor.handleGetKeyValueMethod(EvictionInterceptor.java:200)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/PessimisticLockInterceptor.handleGetKeyValueMethod(PessimisticLockInterceptor.java:347)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:81)
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)[inlined]
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:58)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/TxInterceptor.handleNonTxMethod(TxInterceptor.java:456)
    at org/jboss/cache/interceptors/TxInterceptor.handleGetKeyValueMethod(TxInterceptor.java:250)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/CacheMgmtInterceptor.handleGetKeyValueMethod(CacheMgmtInterceptor.java:81)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73)
    at org/jboss/cache/invocation/AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123)
    at org/jboss/cache/invocation/AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64)
    at org/jboss/cache/invocation/CacheInvocationDelegate.get(CacheInvocationDelegate.java:382)
    at com/myapp/core/CacheService.get(CacheService.java:188)
    at com/myapp/core/CacheService.getFinancialInstrument(CacheService.java:273)
    at com/myapp/util/TradeDalUtils.lookupFinancialInstrument(TradeDalUtils.java:768)
    at com/myapp/xom/ReferenceData.getFinancialInstrumentByIdentifier(ReferenceData.java:330)
    at com/myapp/xom/CMMExecutionModel.getFiForPrimaryExecutionItem(CMMExecutionModel.java:1170)
    at sun/reflect/GeneratedMethodAccessor57908.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
        at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
    at java/lang/reflect/Method.invoke(Method.java:585)[optimized]
    at ilog/rules/inset/IlrExecMethodValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
    at ilog/rules/inset/IlrExecNaryValue.a(Lilog/rules/inset/IlrMatchContext;)[Ljava/lang/Object;(Unknown Source)[optimized]
    at ilog/rules/inset/IlrExecNaryValue.a(ILjava/lang/Class;Lilog/rules/inset/IlrMatchContext;)[Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecStaticMethodValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecStoreValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecBinaryTest.evaluate(Lilog/rules/inset/IlrMatchContext;)Z(Unknown Source)
        at ilog/rules/inset/IlrExecAndTest.evaluate(Lilog/rules/inset/IlrMatchContext;)Z(Unknown Source)
        at ilog/rules/engine/IlrTestRuleMem.i(Lilog/rules/engine/IlrPartial;)Z(Unknown Source)
        at ilog/rules/engine/IlrTestRuleMem.if(Lilog/rules/engine/IlrPartial;IIJ)Lilog/rules/engine/IlrRuleInstance;(Unknown Source)
        at ilog/rules/engine/IlrDefaultRuleMem.aa()V(Unknown Source)
        at ilog/rules/engine/IlrRuleMem.T()V(Unknown Source)
        at ilog/rules/engine/IlrAgenda.a([Lilog/rules/engine/IlrRule;Lilog/rules/engine/IlrAgendaFilter;IZ)I(Unknown Source)[optimized]
    at ilog/rules/engine/IlrEngine.fireAgendaRules([Lilog/rules/engine/IlrRule;Lilog/rules/engine/IlrAgendaFilter;IZ)I(Unknown Source)[inlined]
    at ilog/rules/inset/IlrExecRuleTask.a(Lilog/rules/engine/IlrTaskEngine;)V(Unknown Source)[inlined]
    at ilog/rules/inset/IlrExecRuleTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeSubFlow(Lilog/rules/inset/IlrExecFlowNode;Z)I(Unknown Source)
    at ilog/rules/inset/IlrExecFlowTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeSubFlow(Lilog/rules/inset/IlrExecFlowNode;Z)I(Unknown Source)
    at ilog/rules/inset/IlrExecFlowTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.if(Z)V(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.a(Z)V(Unknown Source)
    at ilog/rules/engine/IlrContext.a(Z)Lilog/rules/engine/IlrParameterMap;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[recursive]
    at ilog/rules/engine/IlrContext.execute()Lilog/rules/engine/IlrParameterMap;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[recursive]
    at ilog/rules/bres/xu/spi/IlrEngineManager.execute()Ljava/util/Map;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[thin lock]
    at ilog/rules/bres/xu/spi/IlrTransactionalEngineManager.execute()Ljava/util/Map;(Unknown Source)
    ^-- Holding lock: ilog/rules/bres/xu/spi/IlrTransactionalEngineManager@0x13897c90[thin lock]
    at ilog/rules/bres/xu/spi/IlrManagedXUConnection.contextExecute(Lilog/rules/bres/xu/cci/IlrXUConnection;)Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/xu/cci/IlrXUConnection.contextExecute()Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/xu/cci/IlrXUInteraction.contextExecute(Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.dispatchExecution(Ljava/lang/String;Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.execute(Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.execute(Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;)Ljavax/resource/cci/Record;(Unknown Source)[optimized]
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.executeInteraction(Ljavax/resource/cci/Interaction;Ljavax/resource/cci/Record;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;)Ljavax/resource/cci/Record;(Unknown Source)
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.execute(Ljavax/resource/cci/ConnectionFactory;Ljava/lang/String;Ljava/util/Map;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;ZZLjavax/resource/cci/Interaction;)Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.executeStateless(Ljavax/resource/cci/ConnectionFactory;Ljavax/resource/cci/Connection;Ljavax/resource/cci/Interaction;Lilog/rules/bres/session/IlrSessionRequest;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at ilog/rules/bres/session/ejb/IlrStatelessRuleSessionEJB.executeRules(Lilog/rules/bres/session/IlrSessionRequest;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at ilog/rules/bres/session/ejb/IlrStatelessRuleSessionEJB_ugt9ms_ELOImpl.executeRules(IlrStatelessRuleSessionEJB_ugt9ms_ELOImpl.java:145)
    at ilog/rules/bres/session/ejb/IlrGateLocal.executeRules(Lilog/rules/bres/session/IlrSessionRequest;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at com/myapp/rules/jrules/JRuleSession.executeRules(JRuleSession.java:79)
    at com/myapp/core/RuleInvoker.invokeRule(RuleInvoker.java:52)
    at com/myapp/core/statemachine/StateMachine.executeRule(StateMachine.java:143)
    at com/myapp/core/statemachine/StateMachine.doTransition(StateMachine.java:109)
    at com/myapp/core/statemachine/StateMachine.doStateMachineTransitions(StateMachine.java:87)
    at com/myapp/core/statemachine/StateMachine.doTransition(StateMachine.java:64)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.doTESMessageProcessing(TesMessageHandler.java:263)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.tesProcessing(TesMessageHandler.java:134)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.process(TesMessageHandler.java:112)
    at com/myapp/core/FullReSequenceMessageProcessor.doStateMachine(FullReSequenceMessageProcessor.java:173)
    at com/myapp/core/FullReSequenceMessageProcessor.processMessage(FullReSequenceMessageProcessor.java:333)
    at com/myapp/core/MessageProcessorMDB.onMessage(MessageProcessorMDB.java:81)
    at weblogic/ejb/container/internal/MDListener.execute(MDListener.java:429)[inlined]
    at weblogic/ejb/container/internal/MDListener.transactionalOnMessage(MDListener.java:335)[inlined]
    at weblogic/ejb/container/internal/ContinuousJMSMessagePoller.processOneMessage(ContinuousJMSMessagePoller.java:129)[optimized]
    at weblogic/ejb/container/internal/JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
    at weblogic/ejb/container/internal/ContinuousJMSMessagePoller.pollForChild(ContinuousJMSMessagePoller.java:185)
    at weblogic/ejb/container/internal/JMSMessagePoller.run(JMSMessagePoller.java:530)
    at java/lang/Thread.run(Thread.java:595)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace
    Edited by: user1631781 on Jun 9, 2010 10:05 AM

    My understanding was that WebLogic by default configuration would pull n messages at a time from the a foreign >jms server (via JMS connection poller) ; and process the n messages using the same MDB in n different >transactions. Is this correct? Its possible for MDB to process more than one message in a transaction using a weblogic specific feature called MDB Transaction batching.This depends on the max-messages-in-transactions descriptor in weblogic-ejb-jar.xml. This controls mdb transaction batch size.
    http://download.oracle.com/docs/cd/E15051_01/wls/docs103/ejb/message_beans.html#wp1161543
    In your case the thread seems to be stuck at the application code level. I doubt if it is related to transactions.
    at java/util/HashMap.get(HashMap.java:344)[optimized]
    at org/jboss/cache/UnversionedNode.getDirect(UnversionedNode.java:203)[inlined]

  • Container managed transactions in 9.0.3 (plus AQ JMS/MDB)

    Something for "real programmers", similar to MDB Transaction Exception on OC4J 9.0.4 (MDB Transaction Exception on OC4J 9.0.4) but little bit different. Maybe author of the mentioned thread can find some answers here also.
    We have an MDB accessing AQ in database (this works either with 9i and 8i). MDB receives the message (actually TextMessage), retrieves the content/properties and calls some EJBs making database operations. When we used just the same DataSource for JMS resource provider and SQL operations, everything worked OK. But we need to move one step further - making calls to several databases, some 8i, some might 9i. We were able to start CMT for one DataSource, i. e. configuring OrionCMTDataSource over JDBC ORACLE driver (if you use different DataSource class, message remains stucked in queue and eventually expires. If you don't specify container managed transactions for MDB in ejb-jar.xml, it works with any DataSource class - but message is lost every time exception occurs - not very pleasant situation).
    We are trying to configure DataSources so they provide transactional support while using commit coordinator. There are some documents describing this - in 9iAS Data Sources and JTA, Orion Data Sources and possibly JTA description in 9i database documentation. Both ORACLE documents are very similar. Generally, these are main steps:
    1) configure each data source so they provides CMT support (wrap native driver/data source by OrionCMTDataSource class)
    2) create datasource commit-coordinator database, also using CMT(?)
    3) create user in commit-coordinator database and same in each other database with connect, resource, create session + force any transaction priviledge (since it would commit other users transactions)
    4) create database links from commit-coordinator database to each databases (but... see questions below)
    5) configure commit coordinator so it uses proper data source
    6) add each DB link as a property to data sources
    7) configure data source for JMS
    8) connect JMS resource provider with JMS data source
    9) Start container, send message, etc.
    So far the only result we've got is a trace file in database user dumps and generic "javax.transaction.SystemExeption: Could not commit: error code 29540". User dump occurs in a "remote" database, not the one where commit coordinator resides. If I drop database links, result is the same, so it seems like problem with data source itself. In a dump there is piece of text like this: "FATAL ERROR IN TWO-TASK SERVER: error = 12571" and "ksedmp: internal or fatal error
    Current SQL statement for this session:
    begin dbms_aqin.aq$_dequeue_in( :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15, :16, :17, :18, :19, :20, :21, :22, :23, :24, :25, :26, :27, :28, :29); end; ". I think AQ call is just a coincidence since it is the first one involved in transactions. Down there in HEX part of a dump there is a message about protocol or network error ("probably ORA-28546")
    Here is an example of data source configuration we are using:
    <!-- Passport CMT DataSource -->
    <data-source
    name="PassportDS"
    class="com.evermind.sql.OrionCMTDataSource"
    location="jdbc/PassportDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="int"
    password="int"
    url="jdbc:oracle:thin:@ws18885:1521:ICON"
    inactivity-timeout="30">
    <property name="dblink" value="ICON.WS18885.APPG.COM"/>
    There are some questions pending. Obvious one is if CMT is working or not at all and we should find some different solution (Bean managed transactions or use XA, hmmm). Other one might be that database link has to be "fully-qualified". I'm not sure what it means: using username and password? Using database name along with domain (if any)? So far it seems links are not used anyway.
    We've tried several databases, like 9.2.0.1 and 9.0.3 versions. Result is the same.
    We've tried to use XA data source of ORACLE (oracle.jdbc.xa.client.OracleXADataSource) and OrionCMT data source bound by xa-source-location to it but container gets stucked upon restart with "Investingating resource 'XADataSource PassportXADS' for recovery..." and similar messages for an hour.
    There is an OracleJTADataSource mentioned in several documents, but I cannot find any in jdbc classes - was it deprecated?
    Lies the problem in JMS itself? So far we've been able to use AQ in 8i and 9i and succesfully commit every transaction - provided transaction was local.
    Since XA itself is working I guess problem might be with configuration.
    I will appreciate any opinion on CMT... also, if you have any questions, please ask.
    Myrra

    Hi Per,
    I don't have an answer for you -- sorry {:-( -- only a suggestion (which
    you may have already tried, anyway :-). Have you tried running OC4J
    in "debug" mode? The following web-page gives details on how to do that:
    http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
    Also, if you aren't already aware of them, the following web-sites
    may also be helpful (not in any particular order):
    http://www.orionserver.com
    http://www.orionsupport.com
    http://www.elephantwalker.com
    Good Luck,
    Avi.

  • Error connecting WLS 10.3.1 JMS & MDBs with Oracle Advanced Queuing

    I followed the guide at http://blogs.oracle.com/imc/2010/12/how_to_use_oracle_aq_with_message-driven_beans_in_weblogic.html. Since the AQ queues were already set up by SAs and had been working with stateless session beans, I assume they're OK for use with MDBs. Names had to be changed in the WLS foreign server definition, destinations & connection factories to match.
    My MDB is:
    package xxxx;
    import javax.ejb.MessageDriven;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    @MessageDriven(name = "TestQueueListenerEJB")
    public class TestQueueListener implements MessageListener
    public void onMessage(Message message)
    if ( message instanceof TextMessage )
    try
    System.out.println("AQMDBTest: text message " + ((TextMessage)message).getText() + " processed");
    catch (JMSException e)
    e.printStackTrace();
    else
    System.out.println("AQMDBTest: generic message " + message.toString() +
    " of type " + message.getClass().getName() + " processed");
    And the relevant portion of the weblogic-ejb-jar.xml is:
    <weblogic-enterprise-bean>
    <ejb-name>TestQueueListenerEJB</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>1</max-beans-in-free-pool>
    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>TestQueue</destination-jndi-name>
    <connection-factory-jndi-name>TestQueueConnectionFactory</connection-factory-jndi-name>
    </message-driven-descriptor>
    </weblogic-enterprise-bean>
    So when I deploy this to my test domain I get an error:
    <Feb 23, 2011 3:11:28 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TestQueueListenerEJB is unable to connect to the
    JMS destination: TestQueue. The Error was:
    Can not get destination information. The destination JNDI name is TestQueue, the provider URL is null>
    The test connection of the datasource is successful.
    What else could I have wrong? This is my first post to this topic. Please let me know what additional information I need to provide about this. Or if I've provided too much.
    Thanks very much,
    Jim Greetham

    OK. So I got my DBAs to create a new user with the necessary privs. Created a new queue, table, etc. I have been able to receive messages from it. So I have some looking to do in my production database queue definitions.
    Jim

  • Asynchronous - JMS, MDB design

    Hi,
    I am writing a portion of a J2EE application and would like to perform asynchronous processing. Im new to JMS. Following are some questions i have:
    - How does JMS process message, queue and MDB? I mean when a message is send to a queue, how does it know which MDB should be receiving the message?
    - Im using JBoss which has JMS support. Under normal circumtances, is it all right to use the default queue that comes with the JMSProvider (i.e. the application server in this case)? Or should we write some other codes for create queue?
    - In terms of design, should one MDB only performs a single function? The reason for this is that a MDB seems to only have a single 'onMessage' method?
    Thanks much.
    Veny

    - How does JMS process message, queue and MDB? I mean when a message is send to a queue, how does it know which MDB should be receiving the message?
    Beans are randomly selected from pool, very much similar to 'stateless session bean'.
    - I'm using JBoss which has JMS support. Under normal circumstances, is it all right to use the default queue that comes with the JMSProvider (i.e. the application server in this case)? Or should we write some other codes for create queue?
    You may want to create your own app specific queue(s) unless you are writing 'Hello MDB' application.
    - In terms of design, should one MDB only perform a single function? The reason for this is that a MDB seems to only have a single 'onMessage' method?
    MDBs are never invoked by client directly and can not maintain conversational state for any specific client. When container receives any message it simply calls 'onMessage' on a randomly picked MDB and pass the message. There is no need and use of any other methods - isn't it?
    Cheers,
    Sudhaker Raj
    http://thej2ee.com

  • Weblogic 6.1 JMS/EJB Design Question

    Any thoughts from gurus or those who have skinned their knees on similar
    issues would be GREATLY appreciated!
    Environment:
    Weblogic 6.1 sp3/Oracle 8.1.7 on Solaris
    I've got a webservice that invokes the webservice ejb and then delegates
    down to business layer ejb that delegates down to data layer dao classes
    that store off on average 150 records which include a clob field containing
    about 4k of data. (All in one JTA transaction) (I'll refer to this as
    operation 1)
    There is a logically independent process (parsing the clob data elements)
    that I'd like to kick off after all 150 records have been stored. (Needs
    access to the committed data) (I'll refer to this as operation 2)
    Questions:
    1. Can a stateless session ejb running under a single phase JTS transaction
    safely post a message to a JMS topic or queue running on the same weblogic
    instance?
    2. If so, are there any guidelines as to whether the transaction for
    operation 1 will complete before the sender receives notification? (the
    concern being that operation 2 will be notified but the data it is
    interested in will not be visible yet) If no guarantees, would configuring
    a JMS message delivery delay help?
    3. This operation will get invoked perhaps a thousand times a day, and I'm
    fearful of falling into the message redelivery trap from transaction
    rollbacks which possibly could occur from operation 2. Above all else, I
    care about NOT having the queue get clogged up with resends. Given that
    bias, should I use NOTSUPPORTED then have the session bean that the MDB
    delegates to start a transaction or would using BMT from the MDB be more
    correct?
    4. Any other thoughts?
    Thanks!

    Alan May wrote:
    Any thoughts from gurus or those who have skinned their knees on similar
    issues would be GREATLY appreciated!
    Environment:
    Weblogic 6.1 sp3/Oracle 8.1.7 on Solaris
    I've got a webservice that invokes the webservice ejb and then delegates
    down to business layer ejb that delegates down to data layer dao classes
    that store off on average 150 records which include a clob field containing
    about 4k of data. (All in one JTA transaction) (I'll refer to this as
    operation 1)
    There is a logically independent process (parsing the clob data elements)
    that I'd like to kick off after all 150 records have been stored. (Needs
    access to the committed data) (I'll refer to this as operation 2)
    Questions:
    1. Can a stateless session ejb running under a single phase JTS transaction
    safely post a message to a JMS topic or queue running on the same weblogic
    instance?So is the first transaction going to be writing 150 records to the
    database and the publishing a JMS message? Yes, this can all be one in
    one transaction in WLS, but it will be a XA/2PC transaction. I'm
    curious why you specified single-phase?
    >
    2. If so, are there any guidelines as to whether the transaction for
    operation 1 will complete before the sender receives notification? (the
    concern being that operation 2 will be notified but the data it is
    interested in will not be visible yet) I'm not sure I follow you here. If the message publish is part of the
    transaction then no consumer will receive the message before the publish
    transaction commits.
    If no guarantees, would configuring a JMS message delivery delay help?
    3. This operation will get invoked perhaps a thousand times a day, and I'm
    fearful of falling into the message redelivery trap from transaction
    rollbacks which possibly could occur from operation 2. There's 2 important WLS JMS features I would suggest you look into:
    1) Message redelivery delay & limits
    2) Error destinations
    Take a look at
    http://e-docs.bea.com/wls/docs81/jms/implement.html#1255066
    Above all else, I
    care about NOT having the queue get clogged up with resends. Given that
    bias, should I use NOTSUPPORTED then have the session bean that the MDB
    delegates to start a transaction or would using BMT from the MDB be more
    correct?I think you'd be better off using redelivery limits and delay than
    trying to do the JMS acknowledgement and transaction management yourself.
    -- Rob
    >
    4. Any other thoughts?
    Thanks!

Maybe you are looking for

  • How to post URL link in sap script

    How to give link in sap script.. For example if someone select [sap|www.sdn.sap.com]. it will direct to www.sdn.sap.com Regards Sas PS: Insert Test --> Hypertext option tried but not working properly... Hey no replies....any one any idea?

  • Wiered problem with FTP

    Hi All, I have configured a simple sender file communication channel (with sender agreement). The error I get in CC Monitoring is <b>Could not process file 'test.xml': com.sap.aii.adapter.file.ftp.FTPEx: 550 jai/: No such file or directory.</b> The p

  • I cant see profile pictures in my facebook account when i log on through firefox

    i cant see profile pictures of my friends in homepage and in their profiles in facebook when i log on through firefox. == This happened == Every time Firefox opened == a month ago

  • What is the correct step of posting to FICO?

    Hi, now my step is : step1: PC00_M99_PA03_RELEA - Release Payroll step2: PC00_M28_CALC - Start Payroll step3:PC00_M99_CIPE - Create Posting Run ,  run "S-Creation of simulation documents" step4:PC00_M99_PA03_END - Exit Payroll step5:PC00_M99_CIPE - C

  • Splitting a Number String without using split()

    What is the better way of converting a number string where the numbers are seperated by a white space into an array without using the split() method or tocharArray e.g numberString = "12 13 14" numberArray[0] = 12, numberArray[1] = 13, etc