Problem in Automated Failover in JMS Clustering

Hi,
          I am facing a problem in JMS clustering, now let me explain the scenario.
          I have 2 managed servers participating in the weblogic cluster, now since JMS is a singleton service what i did is i have created 2 JMS servers and targeted them to Managedservers 1 and 2 respectively.I have also created a DistributedTopic
          Now in my case an applet is the JMS client i have registered the exception listener on both the topic connection and WLSession, now when i bring down one managed server forcefully(Ctrl-C) the call back method onException is supposed to have been called,which has reconnect method which tries to get the connection but it does not happen in this clustered environment.
          I have checked the same thing without a cluster i.e with a single server (Admin server) and it seems to be calling the Onexception call back method.
          What is wrong with this approach.
          Another query just to add on to this is, is this the right approach to achieve automated failover in a clustered environment or do i have to go with Migratable servers concept(not clear on this though).
          Thanks in advance.
          Suresh

I think is correct.U must stop all the server of the cluster, or to know how of the two your client is using. U can used the amministration console to monitoring the status of the destination of the JMS server.
          I have a similar problem, but using tho different kynd of Receiver.
          Now in my case I created two different type of client
          Asynchronous and synchronous .
          The first type registered himself as MessageListener and also as ExceptionListener on the connection. When I bring down the managed server in which the client was connected the call back method onException is called as the bea documentation explains.
          The second client instead registered himself as ExceptionListener but not as MessageListener on the connestion. It called in different execution thread the receive method on the receiver created using the connection.
          In this case when i bring down the managed server in which the client is connect the call back method onException was NOT called, instead the client received the JMSException on all the call "receive()".
          This is true? I expected instead that the behaviour of the 2 type of client was the same!

Similar Messages

Tom Help needed in JMS Clustering!!!!!!!!!

Hi Tom,
          I have a typical problem with JMS Clustering,i amtrying to implement an automatic failover by registering the connection and the session with the exception listener and then inside onexception method i have reconnect logic.
          My application has an applet and the downloading page directly loads the MyApplet jar and weblogic thin client jars and then when i switch of the server using in CTRl-C in windows environment with a single server onException gets fired.Now for clustering we have moved to enterprise archive setup(.ear) and my applet jar and thinclient jars are bundled with in the war(web archive) and the war is inside the ear.In this scenario when i shut down one of the managed servers the onexception does not get invoked and then i shut down both the servers then also its not getting invoked, plz help me i dont understand what is wrong with this,when the servers are on onMessage works fine and my real time blotters also get updated.
          My clustering set up has 2 managed servers,2 JMS servers targeted to each managed server and a distributed topic.
          In a noraml scenario when the servers are running my onMessage gets called, but when i shutdown the servers the onException does not get called from the EAR.
          Pls help me on how to proceed.i cant put the thick weblogic.jar as down loading from my applet cannot handle it.
          Regards,
          Suresh

Sorry Suresh -
          I don't know what is going wrong - my suspicion is that you've found a bug in WebLogic thin-client IIOP.
          Since the problem started when you moved to SP5, you can try continuing to use the SP4 jar on the client.
          And sometimes this type of problem is with with Sun JDK libraries (which supplies most of the thin client IIOP stack), so there's a small chance switching to a 1.5JVM for the client would work (I don't know if BEA supports this).
          You might also try posting to the rmi-iiop newsgroup. (Andy just loves it when I push problems off to him! Well maybe not.)
          Tom

Reg : JMS Clustering

          Hai,
          I am facing one problem in JMS Clustering. can any one throws a light on that?
          it will be very helpful to
          me.
          i configured WebLogic Cluster with node1 and node 1 as Managed Servers.
          i created jmsserver1 and jmsserver2.
          i created queue1 and queue2 in jmsserver1 and jmsserver2 respectively.
          i created one distributed destination by adding queue1 and queue2 as members.
          i targetted jmsserver1 to node1 and jmsserver2 to node2.
          i wrote one program that send the messages to distributed destination using it's
          jndi name.
          i have send some messages to distributed queue.
          after i shutdown the any one of the managed server ex: node1. after that while
          i am trying to send the message to
          distributed destination, it is throwing the exception that no such a jndi name.
          i have checked with JNDI tree.
          jndi name of distributed destination is not there?
          is there any configuration missing or some thing else?
          can any one help me to solve this problem?
          regards
          cg


Sounds like you've set things up correctly. Post your config.xml
          and I'll take a quick look. Please also include the JNDI
          name of the distributed dest your client is looking up.
          cg wrote:
          > Hai,
          > I am facing one problem in JMS Clustering. can any one throws a light on that?
          > it will be very helpful to
          > me.
          >
          > i configured WebLogic Cluster with node1 and node 1 as Managed Servers.
          > i created jmsserver1 and jmsserver2.
          > i created queue1 and queue2 in jmsserver1 and jmsserver2 respectively.
          > i created one distributed destination by adding queue1 and queue2 as members.
          >
          >
          > i targetted jmsserver1 to node1 and jmsserver2 to node2.
          >
          > i wrote one program that send the messages to distributed destination using it's
          > jndi name.
          >
          > i have send some messages to distributed queue.
          > after i shutdown the any one of the managed server ex: node1. after that while
          > i am trying to send the message to
          > distributed destination, it is throwing the exception that no such a jndi name.
          > i have checked with JNDI tree.
          >
          > jndi name of distributed destination is not there?
          >
          > is there any configuration missing or some thing else?
          >
          >
          > can any one help me to solve this problem?
          >
          >
          > regards
          > cg
          >
          >

Jms clustered license

hi,
          Do you I need to obtain a separate license for testing jms clustering (distributed queues DQ)?
          I've downloaded weblogic9.2 from the Internet and in documentation there is information that I should have such a license.
          Do you think that it applies to so evaluating the product?
          I'm encountering strange problems with DQ hence my question.

Grzegorz (Greg) Stasica <> wrote:
          > hi,
          >
          > Do you I need to obtain a separate license for testing jms clustering
          > (distributed queues DQ)? I've downloaded weblogic9.2 from the Internet and
          > in documentation there is information that I should have such a license.
          > Do you think that it applies to so evaluating the product? I'm
          > encountering strange problems with DQ hence my question.
          As far as I know you can use it with your 'evaluation' version or developer
          version.
          B
          Schelstraete Bart
          [email protected]
          http://www.schelstraete.org
          http://www.linkedin.com/in/bschelst

ECR/ECO problem with automated transactions

Hi Friends,
I have problem with automated close of ECR.
Description:
I have change number with one object - Inspection Plan.
In CC32 when "Incorrect Change" is set and I click "Erro Corrected" - nothink happen
(it should show popup with information that transaction cc06 was automated started)
After that when i choose "Release Change" - also nothing happen.
(it should shop popup and set status - "Close ECO")
Everything works ok on sandbox system but on Dev/Test/Prod it doesn't work.
Anybody now where could be a problem?
Thank you for any advice.

Hi
Pls check this Link
SAP-ECM and PPPI Integration-Solution
Thanks in advance

Need Help on Weblogic JMS Clustering

Hi All
Our code is moving to a clustered environment (2 OSB managed servers), in order to support JMS clustering i have already done the below, I just need your advice whether i have done it correctly or not. Please advise
1) Created 2 JMS Servers, targeted one JMS Server on OSB MS 1 and second JMS Server on OSB MS 2.
2) Created distributed destinations (Queues and Topics) subdeployment on both JMS Servers.
3) Targeted all connection factories to OSB Clsuter. Load Balancing and Server Affinity is enabled by default. Should server affinity be disabled for proper load balancing to occur? Please advise on this
3) JMS Proxy and business services use cluster URL's now (jms://serverA:7001,serverB:7001/CF/QueueOrTopic). I Hope its correct? Please advise
Is there any other setting that i need to do or i have missed out? Please let us know.
Also, one more thing we are calling SOA Composites via SOA-Direct protocol in OSB. The SOA Servers owned by some other team will also be load balanced. Since this is a t3 call, HTTP load balancer would not come into picture here, right? How do i load balance this outgoing call from business service (2 options bellow)
1) t3://server1:8001,server2:8001/default/ABCProduct!1.0/ABCService_DirectBinding
2) Specifying two individual endpoints and selecting load balancing algorithm as Round Robin
t3://server1:8001/default/ABCProduct!1.0/ABCService_DirectBinding
t3://server2:8001/default/ABCProduct!1.0/ABCService_DirectBinding
what is the diff between the above 2 options? Also, if one of the SOA nodes go down, than which option would automatically redirect to other node. We have to ensure this as the HTTP load balancer ensures this thing. Thanks
Edited by: Amit Sachdev on Jun 13, 2012 12:16 AM

Hi Amit,
The first part looks correct.
Create two jms servers (jmsosb1, jmsobs2)
Create data source and jndi location
create foreign connection factory under JmsModule, create destination and connection factory.
the cluster business service end point will be
jms:///<<ForeignConnectionFactory Name>>/<<destination local jndi name>>
The second part SOA endpoint will be in cluster environment as follows:
http://<< cluster name>>/soa-infra/services/default/<<composite name>>/<<servicename>>
example:
http://test.ch/soa-infra/services/default/cm.conn.bp.test/test_client_ep
or if you want to invoke two nodes directly you use below url as well.
http://<<SOAservername1>>:<<port>>,<<SOAservername2>>:<<port>>//soa-infra/services/default/<<composite name>>/<<servicename>>
Regards,
Padmanabham

Jms clustering with spring

Hi
i have created the jms clustering configuration in weblogic 10.3.3 that i am facing issues in the connection queue like this
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queueConnectionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Unable to resolve 'QueueConnectionFactory'. Resolved ''; remaining name 'QueueConnectionFactory'
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1401)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
and i have configured servers below
clustered the managed servers MS-1 and MS-2
Servers Targets
JMS Server Admin server
JMS Module cluster
connection queue cluster
queue JMSServer
i have tried with the 2 different JMS servers for managed servers
Servers Targets
JMS Server - 1 MS-1
JMS Server - 2 MS-2
JMS Module cluster
connection queue cluster
queue JMSServer - 1 and JMSServer - 2
so, please help us to configure the JMS clustering with spring.
Note : please find the spring - applicationContext.xml below thats is used to configure the connection factory and jms queue.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
     <bean id="invoiceListener" class="com.spring.jms.InvoiceMDB" />
     <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
          <property name="environment">
               <props>
                    <prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
                    <prop key="java.naming.provider.url">t3://localhost:6001,localhost:6003,localhost:6005</prop>
               </props>
          </property>
     </bean>
     <bean id="queueConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
          <property name="jndiTemplate"><ref bean="jndiTemplate" /></property>
          <property name="jndiName"><value>QueueConnectionFact</value></property>
     </bean>
     <bean id="invoiceQueueTemplate" class="org.springframework.jms.core.JmsTemplate">
          <property name="connectionFactory"><ref bean="queueConnectionFactory" /></property>
          <property name="destinationResolver"><ref bean="jmsDestinationResolver" /></property>
     </bean>
     <bean id="jmsDestinationResolver" class="org.springframework.jms.support.destination.JndiDestinationResolver">
          <property name="jndiTemplate"><ref bean="jndiTemplate" /></property>
          <property name="cache"><value>true</value></property>
     </bean>
     <bean id="jmsInvoiceSender" class="com.spring.jms.InvoiceQueueSender">
          <property name="jmsTemplate"><ref bean="invoiceQueueTemplate" /></property>
     </bean>
     <bean id="invoiceQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
          <property name="jndiTemplate"><ref bean="jndiTemplate"/></property>
          <property name="jndiName"><value>MyQueue</value></property>
     </bean>
     <bean id="Invoicelistener" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
     <property name="concurrentConsumers" value="5" />
     <property name="connectionFactory" ref="queueConnectionFactory" />
     <property name="destination" ref="invoiceQueue" />
     <property name="messageListener" ref="invoiceListener" />
     <property name="sessionAcknowledgeModeName" value="AUTO_ACKNOWLEDGE" />
<property name="sessionTransacted" value="true" />
     </bean>
</beans>

Are you sure you have defined the correct JNDI-name in the Spring config file?
An example set-up of a domain can be found here - http://middlewaremagic.com/weblogic/?p=7795 (the script presented in the create domain section)
This is basically the same set-up you have, except that a distributed queue is being used that is targeted to JMS Servers through a subdeployment.
The Spring configuration looks as follows:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
    <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
        <property name="environment">
            <props>
                <prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
                <prop key="java.naming.provider.url">t3://192.168.1.50:9001,192.168.1.50:9002</prop>
            </props>
        </property>
    </bean>
    <bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
        <property name="jndiTemplate" ref="jndiTemplate"/>
        <property name="jndiName" value="jms/ConnectionFactory"/>
    </bean>
    <bean id="destination" class="org.springframework.jndi.JndiObjectFactoryBean">
        <property name="jndiTemplate" ref="jndiTemplate"/>
        <property name="jndiName" value="jms/CompanyQueue"/>
    </bean>
    <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
        <property name="connectionFactory" ref="connectionFactory"/>
        <property name="defaultDestination" ref="destination"/>
    </bean>
    <bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
        <property name="workManagerName" value="java:comp/env/default"/>
        <property name="resourceRef" value="true"/>
    </bean>
    <bean class="org.springframework.jms.listener.SimpleMessageListenerContainer">
        <property name="connectionFactory" ref="connectionFactory"/>
        <property name="destination" ref="destination"/>
        <property name="messageListener" ref="receiver"/>
        <property name="taskExecutor" ref="taskExecutor"/>
    </bean>
    <bean id="sender" class="model.logic.JMSSender">
        <property name="jmsTemplate" ref="jmsTemplate"/>
    </bean>
    <bean id="receiver" class="model.logic.JMSReceiver"/>
</beans>To test create a servlet, for example,
public class TestServlet extends HttpServlet {
    protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
        JMSSender jmsSender = SpringUtilities.getJMSSender();
        jmsSender.sendMessage();
        System.out.println("message send by the testservlet");
}and web.xml as
<web-app ...>
    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>classpath:spring-config.xml</param-value>
    </context-param>
    <listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>
    
    <resource-ref>
        <res-ref-name>default</res-ref-name>
        <res-type>commonj.work.WorkManager</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    
    <resource-ref>
        <res-ref-name>tm/default</res-ref-name>
        <res-type>commonj.timers.TimerManager</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <servlet>
        <servlet-name>TestServlet</servlet-name>
        <servlet-class>test.TestServlet</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>TestServlet</servlet-name>
        <url-pattern>/testservlet</url-pattern>
    </servlet-mapping>
</web-app>with this set-up the JMS clustered and Spring is able to use it on both servers.

Jms clustering and application clustering

Hello:
          Suppose an application that contains mdb is deployed in a cluster cl.
          Should the jms clustering be done in the same cluster or can it be a
          seperate cluster.
          regards,
          ravi


JMS distributed destinations are optimized
          for the use case where the MDB is on the same
          server as the destination. If you are not
          using distributed destination this is less
          of an issue. In either case, MDBs can
          be run in a seperate cluster than JMS -
          sometimes this can simplify administration.
          Read the JMS Performance Guide white-paper
          for more information.
          http://dev2dev.bea.com/technologies/jms/index.jsp
          Ravi Krishnamurthy wrote:
          > Hello:
          > Suppose an application that contains mdb is deployed in a cluster cl.
          > Should the jms clustering be done in the same cluster or can it be a
          > seperate cluster.
          >
          > regards,
          > ravi
          >

JMS clustering

Does weblogic5.1 support JMS clustering? If it doesn't when it is going to
          be.
          -Muruga


JMS is available as a cluster wide service today. You have a single node
          that is a JMS provider for the entire cluster.
          In a future release, we plan to fully cluster our JMS service.
          For more information, I suggest contacting your sales representative who can
          provide you with a bit more detail.
          Thanks,
          Michael
          Michael Girdley
          Product Manager, WebLogic Server & Express
          BEA Systems Inc
          Muruga Chinnananchi <[email protected]> wrote in message
          news:8fsqbu$he0$[email protected]..
          > Does weblogic5.1 support JMS clustering? If it doesn't when it is going to
          > be.
          >
          > -Muruga
          >
          >

Weblogic JMS clustering

Hi All,
I need help understanding weblogic JMS clustering. I read few documents regarding this but not very clear about it.
Hope to get help/suggestion here.
I have following setup
box1 - adminserver, osbserver1
box2- osbserver2
osbserver1 and osbserver2 are clustered together
I have a JMS server created each one for each managed server (OSB server) in the cluster. These JMS servers are non-persistent. persistent store is "None".
I have one JMS module created with connection factory, distributed Qs and are associated with a subdeployment that is targeting to the cluster
I have all the servers(admin server and both OSB servers) are in running state
To monitor JMS server I go to services->JMS Servers
I see jmsserver1 which is targeted to osbserver1 has "Health" is marked as "OK"
jmserver2 which is targeted to osbserver2 has no "health" check
If I go to environment->servers , I see all the 3 servers are marked as "RUNNING" with "Health" OK
As a note I created managed server in the second box before creating the JMS server and resources.
And I do not have any nodemanager setup at this point.
How would I know the JMSserver in both servers are active and have no issues ?
Do I need to do anything to start JMSServer in OSBServer2 ?
Edited by: 818591 on Feb 11, 2011 8:27 AM
Edited by: 818591 on Feb 11, 2011 9:31 AM

Should the JMS Server/JMS modules already be created so that the remote managed server will get configuration of these setup?No. This is not how resorces are created. Pack/unpack is used for creating the domains, ONCE. Later on you may very well use Weblogic admin console to create the resources and target/untarget those.
As a note I do not have node managed setup yet. It is recommended that you use node manager in environments where servers may be installed on different machines -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13740/toc.htm
To me, it seems a network/cluster communication issue. If you have Oracle Support, better raise a SR with them to find out the exact issue as they would be in better position to understand your architecture and analyzing logs. You may also raise a thread in Oracle Weblogic forum to get a suggestion from a Weblogic expert -
WebLogic Server - Clustering
Regards,
Anuj

Problem in automating category properties

Hi All,
i m facing problem in automating category properties that i define for node,hierarchy and version.
Scenario : Lets say i create a simple property called storage type and give a drop down for it as ASO and BSO. I have also defined it in the flat file that i use for automator import.When i run the automator, with all necessary components selected,this doesnt get reflected in the node/hierarchy...
This has also been the case with even the description also. (Though I am following the correct syntax ).
I couldnt find any system preferences that needs to be changed for this purpose.
Any help on this regard is appreciated.
Regards,
nishanth

Hi Etrafanob, Experts,
I was wondering if this issue has been resolved, and if yes - how. Having the same here after an Upgrade from 4.0 to 7.0.
Thank you very much!
Best Regards

JMS/clustering design and configuration question

Hi:
          Any help or feedback much appreciated cos' this topic (no pun intended)
          seems to be complicated.
          I have an application that uses stateless session beans for mainline
          business functionality (heavy database writing) that is say then
          audited. The auditing is taken care of asynchronously by the SS bean's
          business method (after completing whatever it is doing) using a JMS
          connection factory to write to a queue which is consumed by a MDB. So,
          control is returned to the user ostensibly before the auditing is done
          for performance reasons. No transactional semantics are expected between
          the mainline business logic and the audit of same. So, our main use of
          JMS/MDB is for asynchrous operation. This design seems to be fine on a
          single server as long as a persistent store is configured.
          Now the hard part. We need to cluster - again for load-balancing and
          performance. As I've read thru this newsgroup and experimented some,
          I've quickly realized that it's not as simple as just configuring a
          cluster of just EJBs.
          Since the queues are basically used for asynch processing, would the
          following work?
          1) Set up a JMS server config for each WL server in the cluster targeted
          only for each WL server
          2) Set up a different queue for each JMS server with prefixed JNDI name
          (myserver1_someJNDIname)
          3) Configure/code the producer SS EJBs so that they ask the connection
          factory for a connection with a prefixed JNDI name (e.g
          myserver1_someJNDIname) based on the server they are running on (known
          perhaps from a property file local to each server)
          4) Target MDBs to be deployed on all servers in the cluster just like
          regular EJBs
          5) Finally, deploy the MDBs unjarred on each WL server and edit the
          weblogic-ejb-jar.xml on each server to set the -destination name-
          prefixed by the server on which it is deployed (e.g.
          myserver1_someJNDIname)
          Will the above basically accomplish what I'm after, which is a cluster
          of machines each equally capable of locally offloading asynchronous
          processing? I understand that for the most part WL server will use local
          EJBs, etc if they are available. I'm not particularly interested in
          failover at either EJB or JMS level, but rather HttpSession level so
          that if a WL server goes down another could pick up perhaps by by the
          user re-requesting whatever operation failed.
          If this is not possible because of the way clustering works (homogenous)
          then is there some other way to solve this problem. I basically do not
          want a cluster where there is a single point of failure (other than DB
          server) for any given piece of functionality.
          Thanks for any help.
          Alex


First and easiest,
          Just create a set of JMS tables for each server in your db. You can specify
          a JMS tablename prefix in your weblogic properties for eash server using
          weblogic.jms.tableNamePrefix=W5
          as long as the prefix is only two chars. This worked great for us until we
          decided to drop JMS because of its memory leaks. We were having to restart
          our servers every 8 hours.
          Second, get rid of JMS. Dirty little secret:You don't need JMS to do
          asynchronous work! You can use threads inside of J2EE and not break J2EE.
          Can't tell you how for proprietary reasons but you can.
          Mica Cooper

Problem with Automated Tasks

Hi all,
At this moment I'm testing a cartridge deployed in OSM7 that is installed in Solaris Spark. The cartridge contains processes that include Automated Tasks with XQuery Sender Automator Internal to send a message to a queue JMS. In some of the Automated Task, when try to execute de XQuery Sender doesn't occur anything, the message is not putted in the queue and in the log doesn't appear any error.
I created 3 orders in OSM, and checking all the WebLogic console I can see the next:
1. In the worklist of OSM appear the 3 orders with column "State=Received" and doesn't have anything in the column "User", (I think this mean that the automator has not started).
2. In the WebLogic console -> JMSModules -> "oms_jms_module" -> "oms_events" ->Monitoring, I can see 3 messages "Pending" that correspond to each order created.
3. The Orchestration Plan "Seen in the osmwebui" is OK.
Note1: When I test the same cartridge deployed in OSM7 installed in Windows I don't have the problem.
Note2: This doesn't occur always, sometimes the JMS Message is putted in the queue and the flow of the order continues in the right way.
Thanks a lot for any suggestion.
Edited by: user2926753 on 17-nov-2011 9:24

Ramiro;
From what you are describing, it sounds as if the automation plugin is not deployed - hence the reason why the task you are intending to automate just stays in the received state.
I would suggest you start by undeploying and then redeploying your cartridge.
Of course this doesn't explain your Note2, but worth trying the above in any case.
Can you tell me how you are submitting the order and what release of OSM you are on?
Thanks,
Brian.

Automation failing in OSM clustered env and getting -unread block data

One of the customer is getting following exceptions while trying to place orders on the clustered environment. The same issue is also reported by other two and is discussed in communities (https://communities.oracle.com/portal/server.pt?open=514&objID=187443&mode=2&threadid=367195)
<04-Jun-2012 11:20:11,369 ICT AM> <ERROR> <message.ClusterMessageHandlerBean> <ExecuteThread: '37' for queue: 'oms.automation'> <Failed to process cluster request for order ID [100739]>
java.lang.IllegalStateException: unread block data
     at java.io.ObjectInputStream$BlockDataInputStream.setBlockDataMode(ObjectInputStream.java:2376)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1360)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
     at weblogic.rmi.extensions.server.CBVInputStream.readObject(CBVInputStream.java:64)
     at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:261)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
     at com.mslv.oms.security.base.OMSRequestBalancer_y7pdy3_EOImpl_1033_WLStub.routeRequestToRemoteJMSDestination(Unknown Source)
     at com.mslv.oms.automation.plugin.l.a(Unknown Source)
     at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
     at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
     at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
<Jun 4, 2012 11:20:11 AM ICT> <Error> <oms> <BEA-000000> <message.ClusterMessageHandlerBean: Failed to process cluster request for order ID [100739]
java.lang.IllegalStateException: unread block data
     at java.io.ObjectInputStream$BlockDataInputStream.setBlockDataMode(ObjectInputStream.java:2376)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1360)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
     Truncated. see log file for complete stacktrace
>

Logs clearly indicates that OSM is running in legacy mode. “OMSRequestBalancer_y7pdy3_EOImpl_1033_WLStub.routeRequestToRemoteJMSDestination” will not come in picture in case of optimized mode.
Please make sure below settings:
1)     Studio – optimized mode.
2)     Cartridge target version 7.0.3

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

Problem in Automated Failover in JMS Clustering

Similar Messages

Maybe you are looking for