JMS server affinity doubt

          Hi,
          I have two weblogic instances in the cluster and have configured two JMS servers
          one for each instances. Have created a connection factory with server affinity
          enabled. Now if some messages are submitted from server A, does server affinity
          ensures that all messages are processed by jms server A for sure? Even in case
          of JMS server B is idle?
          Any pointer for more info about this is appreciated.
          Thanks,

Yes It is true. I have tested it.
 "Kiran Kumar" <[email protected]> wrote:
 >
 >Hi,
 >
 >I have two weblogic instances in the cluster and have configured two
 >JMS servers
 >one for each instances. Have created a connection factory with server
 >affinity
 >enabled. Now if some messages are submitted from server A, does server
 >affinity
 >ensures that all messages are processed by jms server A for sure? Even
 >in case
 >of JMS server B is idle?
 >
 >Any pointer for more info about this is appreciated.
 >
 >Thanks,

Similar Messages

WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file

WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file
 We are using WLS 7.0.4 - One of JMS connection factory setting in admin console we selected "Server Affinity" options.
 We see this messages appear in Weblogic log file,
 ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster> <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000123> <Conflict start: You tried to bi
 nd an object under the name sbetrmi2 in the JNDI tree. The object you have bound from liberatenode2.dc2.adelp
 hia.com is non clusterable and you have tried to bind more than once from two or more servers. Such objects ca
 n only deployed from one server.>
 and then,
 ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster> <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000125> <Conflict Resolved: sbetrmi2 for
 the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2 in the JNDI tree.>
 Should we use 'load balancing option' instead of 'server affinity' ?
 Any thuoghts?
 Thanks in adv.
 Vijay

Test Reply
 <Vijay Kumar> wrote in message news:[email protected]..
 > WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
 > file
 >
 > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
 > console we selected "Server Affinity" options.
 >
 > We see this messages appear in Weblogic log file,
 > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
 > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000123> <Conflict start: You tried to bi
 > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
 > bound from liberatenode2.dc2.adelp
 > hia.com is non clusterable and you have tried to bind more than once from
 > two or more servers. Such objects ca
 > n only deployed from one server.>
 >
 > and then,
 > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
 > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000125> <Conflict Resolved: sbetrmi2 for
 > the object from liberatenode5.dc2.adelphia.com under the bind name
 > sbetrmi2 in the JNDI tree.>
 >
 >
 > Should we use 'load balancing option' instead of 'server affinity' ?
 >
 > Any thuoghts?
 >
 > Thanks in adv.
 > Vijay

WLS 7.0.4 - JMS connection Factory for RMI queues - server affinity issues help pls

We are using WLS 7.0.4 - One of JMS connection factory setting in admin
console we selected "Server Affinity" options.
We see this messages appear in Weblogic log file,
####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
<liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000123> <Conflict start: You tried to bi
nd an object under the name sbetrmi2 in the JNDI tree. The object you have
bound from liberatenode2.dc2.adelp
hia.com is non clusterable and you have tried to bind more than once from
two or more servers. Such objects ca
n only deployed from one server.>
and then,
####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
<liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000125> <Conflict Resolved: sbetrmi2 for
the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2
in the JNDI tree.>
Should we use 'load balancing option' instead of 'server affinity' ?
Any thuoghts?
Thanks in adv.
Vijay

Test Reply
 <Vijay Kumar> wrote in message news:[email protected]..
 > WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
 > file
 >
 > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
 > console we selected "Server Affinity" options.
 >
 > We see this messages appear in Weblogic log file,
 > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
 > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000123> <Conflict start: You tried to bi
 > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
 > bound from liberatenode2.dc2.adelp
 > hia.com is non clusterable and you have tried to bind more than once from
 > two or more servers. Such objects ca
 > n only deployed from one server.>
 >
 > and then,
 > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
 > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000125> <Conflict Resolved: sbetrmi2 for
 > the object from liberatenode5.dc2.adelphia.com under the bind name
 > sbetrmi2 in the JNDI tree.>
 >
 >
 > Should we use 'load balancing option' instead of 'server affinity' ?
 >
 > Any thuoghts?
 >
 > Thanks in adv.
 > Vijay

What is the association between JMS Server and JMS Module in weblogic 10?

Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....

Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom

JMS Server on a cluster stores all msgs posted to Distributed Queue on 1 server failure

 Hi
 I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running its own
 JMS server.
 Product version in use is Weblogic SP2.
 Configured a Distributed Queue and deployed it on both the JMS servers.
 Set the load-balancing to round-Robin and Server-Affinity to False on the connection
 factory.
 The producer is an external client which posts 100 messages to the Distributed
 queue.
 Consumers are MDBs pinned to the respective physical queues on the respective
 JMS servers.
 Each server has its own store.
 Once 100 messages are posted to the Distributed Queue. The messages are distributed
 to
 the 2 Physical Destinations equally i.e 50-50 each.
 While the MDBs are processing the msgs, server srvr1 is brought down at a point
 when it has consumed only 10 of its 50 msgs.
 When the srvr1 is brought up again, i am finding that the store for that JMS server
 contains the 40 unprocessed msgs in its physical queue + the msgs on the other
 queue that were unprocessed at the time this server crashed.
 When srvr1 went down, srvr2 was running and it went on to process all its 50 msgs
 completly. Why would those processed msgs show up again when srvr1 is brought
 up ?
 Please provide some input !!
 Ravi.


 The log message is from the distributed destination
 "forwarders". In distributed queues, these forwarders
 automatically move messages from queues without
 consumers to queues that have them (queue
 forwarders are disabled by default). In distributed topics,
 the forwarders serve
 to replicate a published message from the local
 topic member to each of the remote topic members.
 "Raviprasad Athivilli" <[email protected]> wrote:
 >
 >Tom
 >
 >I think you are right. When the server1 is brought up again, its picking
 >up all
 >the messages
 >that were written to the store.
 >
 >But as it starts processing them, i get this exception on the server2
 >that has
 >been running from the beginning.
 >
 ><Oct 10, 2003 6:20:19 PM EDT> <Error> <JMS> <040366> <JMS Distributed
 >Destination
 >member "MyQueue@JMSServer-02" in "MyQueue"
 >unable to accept connection from remote member "MyQueue@JMSServer-01"
 >due to exception
 >weblogic.jms.common.JMSException: can't find
 >queue target jndi table for MyQueue@JMSServer-01 != MyQueue
 >weblogic.jms.common.JMSException: can't find queue target jndi table
 >for MyQueue@JMSServer-01
 >!= MyQueue
 > at weblogic.jms.backend.BEDestination.setupSystemSubscription(BEDestination.java:3466)
 > at weblogic.jms.backend.BEManager.sessionAndTopicSubscriberCreate(BEManager.java:234)
 > at weblogic.jms.backend.BEManager.invoke(BEManager.java:384)
 > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
 > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
 > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncFuture(DispatcherImpl.java:396)
 > at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
 >Source)
 > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
 > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
 > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
 > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
 > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
 >
 >What does this mean ?
 >
 >Ravi.
 >Tom Barnes <[email protected]> wrote:
 >>Seems more than odd. Are you sure that q1 got unprocessed
 >>messages from q2? How did you confirm?
 >>
 >>Perhaps q1 got messages its MDB already processed back again -
 >>an indication that the MDB is throwing Runtime exceptions
 >>or Errors, and the container is rolling back transactions.
 >>
 >>Raviprasad Athivilli wrote:
 >>> Hi
 >>>
 >>> I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running
 >>its own
 >>> JMS server.
 >>> Product version in use is Weblogic SP2.
 >>> Configured a Distributed Queue and deployed it on both the JMS servers.
 >>> Set the load-balancing to round-Robin and Server-Affinity to False
 >>on the connection
 >>> factory.
 >>>
 >>> The producer is an external client which posts 100 messages to the
 >>Distributed
 >>> queue.
 >>> Consumers are MDBs pinned to the respective physical queues on the
 >>respective
 >>> JMS servers.
 >>> Each server has its own store.
 >>>
 >>> Once 100 messages are posted to the Distributed Queue. The messages
 >>are distributed
 >>> to
 >>> the 2 Physical Destinations equally i.e 50-50 each.
 >>>
 >>> While the MDBs are processing the msgs, server srvr1 is brought down
 >>at a point
 >>> when it has consumed only 10 of its 50 msgs.
 >>>
 >>> When the srvr1 is brought up again, i am finding that the store for
 >>that JMS server
 >>> contains the 40 unprocessed msgs in its physical queue + the msgs
 >on
 >>the other
 >>> queue that were unprocessed at the time this server crashed.
 >>>
 >>> When srvr1 went down, srvr2 was running and it went on to process
 >all
 >>its 50 msgs
 >>> completly. Why would those processed msgs show up again when srvr1
 >>is brought
 >>> up ?
 >>>
 >>> Please provide some input !!
 >>>
 >>> Ravi.
 >>
 >

JMS Adapter to remote JMS Server in ESB??

Has anyone successfully setup a JMS adapter in the ESB to talk to a JMS server on a remote host?
We are using OC4J JMS and so I followed the instructions in section 5.2.1.7 in the Adapters guide on this. I updated the oc4j-ra.xml file. The guide didn't state which version of oc4j-ra.xml to update, but I've been told to use the one in:
$ORACLE_HOME/j2ee/<oc4j>/application-deployments/default/
So, I added the XML block as specified in this section and made the JMS Connection JNDI name match that of my JMS Adapter. However, the Adapters guide then states the following:
In addition, you must have the file META-INF/application-client.xml in the
classpath. The contents of the file can be the following:
<application-client/>
To put this file in the classpath, put the specified contents into the file at Oracle_
Home\bpel\system\classes\META-INF\application-client.xml and
restart Oracle BPEL Server.
This is a problem for me because I have an advanced installation with ESB and OWSM on top of OC4J, but I do not have BPEL installed in this location. As such, the file $ORACLE_HOME/bpel/system/classes/META-INF/application-client.xml does not exist. I did a search and did find an application-client.xml at the following location:
$ORACLE_HOME/j2ee/oc4j_esbdt/connectors/JmsAdapter/JmsAdapter/META-INF
But at this point, I don't know what to do with it to ensure it is in the classpath. The Adapters guilde says to cycle the BPEL Server, so I cycled the ESB for good measure, then deployed my project, but no luck! It is still listening to the local jms server and not the remote one.
Has anyone successfully set this up? What am I missing or doing wrong?

The above classpath requirement should only ensure that BPEL module can access the JMS adapter. Otherwise it should be OK.
I would reccommend to try to establish the JMS connection and see if some parts of the Oracle AS will throw any exception or something. It might start working as well.
As I understand, you are trying to access OC4J JMS from another server. As JMS is purely TCP level protocol there should be no problem accessing it from anywhere. Only the addresses and ports must be reviewed and ensure that they point to correct place, that usernames and passwords are correct and that there is a JNDI connectivity available as you use JNDI to get the connection factories.
Rein

Error in JMS server in OSB

Hi All,
I have been using JMS queues for few of my OSB projects.
From what I have noticed, the JMS server fails to queue messages often.
This is solved once the weblogic server is restarted.
I come across this problem atlest thrice a week. Everytime I restart the weblogic server to overcome this issue.
Is there any configuration setting within the JMS to avoid this?
Or is there any other way to overcome this?
Thanks,
Mani

weblogic.messaging.kernel.KernelException: Error persisting message.
But sometimes i dont get any errors. The transaction seems successul.
But the message has not been queued.
Thanks,
Mani

Ant to delete JMS Server

 I am trying to use an Ant script to configure a new domain for weblogic server
 8.1
 Ideally I want to run the script and have it configure all resources I will need
 (jdbc, jms, etc.). Currently I am having issues with the configuring of the JMS
 Server. I am using the following line of code to delete the JMS Server instance
 if it currently exist.
 <delete mbean="${domain.name}:Name=cgJMSServer,Type=JMSServer"/>
 This seems to be ignored by Ant because when I call the create task I get an InstanceAlreadyExist
 error. I assume my delete task is failing but giving no error. I'd like to be
 able to delete the current JMS server if one exist and then recreate it. I was
 wondering what the correct task or syntax would be for deleting the JMS server
 through Ant.
 Additionally, I'd like to use wlserver to create a new Integration Domain. I havent
 seen any documentation on how to specify a template to use when using the wlserver
 task, so I am not sure if this is possible or not.


Hi Allen,
 I think you may need to set the target of the JMS server
 to null first.
 I think the "JMSML" utility on dev2dev does this sort of
 task. You might want to take a look at its source to
 divine what steps it goes through.
 Tom
 Allan wrote:
 > I am trying to use an Ant script to configure a new domain for weblogic server
 > 8.1
 >
 > Ideally I want to run the script and have it configure all resources I will need
 > (jdbc, jms, etc.). Currently I am having issues with the configuring of the JMS
 > Server. I am using the following line of code to delete the JMS Server instance
 > if it currently exist.
 >
 > <delete mbean="${domain.name}:Name=cgJMSServer,Type=JMSServer"/>
 >
 > This seems to be ignored by Ant because when I call the create task I get an InstanceAlreadyExist
 > error. I assume my delete task is failing but giving no error. I'd like to be
 > able to delete the current JMS server if one exist and then recreate it. I was
 > wondering what the correct task or syntax would be for deleting the JMS server
 > through Ant.
 >
 > Additionally, I'd like to use wlserver to create a new Integration Domain. I havent
 > seen any documentation on how to specify a template to use when using the wlserver
 > task, so I am not sure if this is possible or not.

JMS server targeted to several clusters

Hello,
I am facing a problem with my JMS configuration in weblogic (version 10.3.4.0). I have two clusters. Following the [JMS best practice|http://forums.oracle.com/forums/message.jspa?messageID=9455261#9455261] I have created a JMS server in each Managed server within the clusters. I have created only one JMS Module with a subdeployment. The JMS Module is targeted to all managed servers within both clusters, and the subdeployment is targeted to all JMS servers within the clusters.
At the JMS module I have created a connection Factory targeted to the subdeployment, till there everything is ok.
Afterwards I try to create a uniform distributed queue (UDQ) targeted to the subdeployment and WebLogic throws the following error:
A UDD must be targeted to servers within a single cluster or a single stand-alone server, rather than Cluster ClusterA and Cluster ClusterB
The only solution that I found is to create one JMS Module-subdeployment per JMS Server. Is there a way to have just a JMS Module and use it in all the managed server in several clusters? or I have to set up the same parameters (ConnectionFactories + queue +quota) in each JMS Module.
Thank you very much in advance.
Cheers,
Oscar

Hi Oscar,
The correct way to step-up a UDQ is something like below
C-1 => MS-1 + MS-2
JMSServer-1 => MS-1
JMSServer-2 => MS-2
JMSModule-1 => C-1
Sub_UDQ => JMSServer-1 + JMSServer-2
UDQ => Sub_UDQ
CF => C-1
Where:
======
MS-x are the managed servers
C-x are the Cluster
UDQ is the Uniform Distributed Queue
Sub_UDQ is the Sub-Deployment for UDQ
CF is the Connection Factory
*=>* mean Targeted.
Also to get more information on it you can have a look at the below link which has the step by step instructions which would surely help you out
Topic: Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Regards,
Ravish Mody

How the JMS client detect if the JMS server is still running?

I have a JMS server running on Weblogic and a JMS client running as a standalone application on my local machine. I ran into the problem that if the JMS server is down for a period of time and then get re-started, the JMS client will lose its connection to the server. Since JMS client is just passively listening to the topic it subscribes, it will have no information about the status of the JMS server. Therefore it will not be able to receive any new message if the JMS server is restarted.
I wonder if there is a way I can have the JMS client automatically detect if the connection to the server is lost or reset. I tried to use a while loop in JMS client that does a JNDI loopup every minute to check if the JMS server is up. But if the WL server is down, the JMS client will just catch an exception and crash.

Hi,
You should use an exception listener that allows a client to be notified of a problem asynchronously. As your client only consumes messages, it would have no other way to learn that its connection has failed.
Hence, you should implement the interface ExceptionListener (let says MyExceptionListener) and define your reconnection logic in the method onException(JMSException exception). MyExceptionListener has to be registered with your connection with the method:
public void setExceptionListener(ExceptionListener listener) throws JMSException
Hope it helps,
Arnaud
www.arjuna.com

What is the right behaviour when jms server is down

Hi,
several jms implementation behave differently while trying to connect to the jms server which is not available or when the jms server is suddenly down in the middle.
For example:
iBus Mobile - handles reconnections internally, doesn't throw exceptions. I can only know that i am in the disconnected mode from ExceptionListener.
ActiveMQ and openJMS throw exceptions when they can not connect to the jms provider or when the provider is lost in the middle
Sun MQ has "number of reconnection" parameter which internally tries to reconnect "number" times and after that he throws exception.
While the initial connection failure i can handle in while loop , busy waiting for successful connection, i can not handle the later case, when connection is lost in the middle.
I thought that seemless reconnection is part of jms implementation.
Our application requires smooth working even when there is no connection to jms.
How to handle this issue? I think the behaviour of the most jms described is not so logical in terms of jms requirement.
Slava.

SwiftMq is a commercial product, also it also throws
exception when the broker is not running. Yes, it is a commercial product and high quality. But transparent reconnect is disabled by default in SwiftMQ Router Standard (it is enabled by default in SwiftMQ High Availability Router), hence you get an exception. So always check the docs before you suggest wrong behavior.
To enable transparent reconnect, check these links:
http://www.swiftmq.com/products/router/swiftlets/sys_jndi/introduction/index.html
("JNDI Provider URL" to enabled transparent reconnect for JNDI)
http://www.swiftmq.com/products/router/swiftlets/sys_jms/clients/remote/reconnect/index.html
Since this is a general JMS forum, you might use the SwiftMQ forum if you have specific questions:
http://www.nabble.com/SwiftMQ-JMS-Forum-f15660.html
But keep in mind that SwiftMQ costs money. It is not for free.
I think only iBus is the one who implements
transparent connection and reconnection for 100%Haven't heard from them a couple of years. Are their business still operating? At least their message server wasn't updated since a couple of years.
-- Andreas

ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ

Hi,
I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
 at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
 at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
 at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
 at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
 at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
 at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
 at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
 at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
 at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
 at java.lang.Thread.run(Thread.java:722)
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
 at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
 at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
 at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
 at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
 at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
 at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
 at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
 at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
 at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
 at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
 at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
 at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
 ... 13 moreHowever, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
Request help to resolve this.
Thanks in advance.
Regards
Alexander.

Maybe this can help: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:4018285967344

MDBs failed to connect to remote JMS server

Hi,
 We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
 In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
 <weblogic-enterprise-bean>
 <ejb-name>MyBean</ejb-name>
 <message-driven-descriptor>
 <destination-jndi-name>MyTopic</destination-jndi-name>
 <provider-url>t3://myhost:19009,myhost:19011</provider-url>
 <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
 di-name>
 </message-driven-descriptor>
 </weblogic-enterprise-bean>
 When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
 (t3://myhost:19009) but got the same result.
 When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
 I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
 Any help would be greatly appreciated.
 Thanks,
 Thao

I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?). I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
 >>> Could you elaborate on the known problem?
 9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
 >>> What else I can try?
 Beyond contacting customer support, I'm not sure.
 Tom

How to configure JMS-Server to use username and password

Hi
Maybe this is a real stupid question, but please help me, I'm not very experienced using JMS:
I'm using JMS (provided by OC4J / Application Server 10.1.3). I configured a ConnectionFactory (without username and password) and a Queue and there is also a application, which successfully opens the JMS-Connections.
This works well as long as I do not provide a username und password in the ConnectionFactory (EnterpriseManager: OC4J/Admin/Services/JMS-provider...). If I do this, my application terminates with the following stacktrace:
javax.jms.JMSSecurityException: JMSServer[aplora2:12602]: failed to authenticate "myuser/mypassword", no such user.
 at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1034)
 at com.evermind.server.jms.JMSUtils.toJMSSecurityException(JMSUtils.java:1090)
 at com.evermind.server.jms.JMSServer.getJMSServer(JMSServer.java:1237)
 at com.evermind.server.jms.JMSServer.getJMSServer(JMSServer.java:1213)
 at com.evermind.server.jms.InContainerProxy.getJMSServer(InContainerProxy.java:93)
 at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:103)
 at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:62)
 at com.evermind.server.jms.EvermindQueueConnectionFactory.unprivileged_createQueueConnection(EvermindQueueConnectionFactory.java:98)
 at com.evermind.server.jms.EvermindQueueConnectionFactory.access$000(EvermindQueueConnectionFactory.java:42)
 at com.evermind.server.jms.EvermindQueueConnectionFactory$1.execute(EvermindQueueConnectionFactory.java:78)
 at com.evermind.server.jms.InContainerProxy.doSecureOp(InContainerProxy.java:157)
 at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:75)
 at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:66)
 at sam.model.messages.MessageManager.<init>(MessageManager.java:74)
where "myuser" and "mypassword" are the username and password I entered in the ConnectionFactory. (My Application certainly uses the same username and password)
I expected, that by entering username and password here I would configure my Queue to be protected by them. But obviously there are some very basic things I didn't understand. Can anyone give me a hint, how I can protect the (OC4J-) JMS-Server or the Queue by username and password?
Thanks for your help
Frank Brandstetter

Hey Frank -
Assuming you've set up users in the "Security Manager" for your application, you can specify what JNDI resources they can "read" (and thus also connect to) via the orion-application.xml file. Look at the following snippet from the orion-application.xml file:
 <namespace-access>
<read-access>
<namespace-resource root="jms/firstQueue">
<security-role-mapping impliesAll="false" name="jmsSecurity">
<user name="scooter"/>
</security-role-mapping>
</namespace-resource>
</read-access>
<read-access>
<namespace-resource root="delme">
<security-role-mapping impliesAll="false" name="jmsSecurity">
<group name="messagingUsers"/>
</security-role-mapping>
</namespace-resource>
</read-access>
</namespace-access>
This would say that only the user "scooter" that you've set up would have access to the Queue whose JNDI name begins with jms/firstQueue. Anyone you've set up and added to a messagingUsers group would have access to any Queues whose JNDI name begins with "delme". (I'm honestly not sure what exactly this line does: <security-role-mapping impliesAll="false" name="jmsSecurity">)
This is the only way I've found to limit access to a particular Queue.
HTH.
Scott

What does "each JMS server needs to have its own unique store" mean?

Does this mean that each JMS server needs it's own table? I found this info here:
          http://forums.bea.com/bea/message.jspa?messageID=200022411&tstart=0
          I'm attempting to find the root cause of why we're crashing the OS on a highly clustered (14 managed server) implementation whenever a JMS queue (through BEA's JMS JDBC Store) is being hit.
          Thanks!

JDBC stores must be configured to use different database tables (by configuring a different "prefix" for each). Otherwise, they will corrupt each-others data. But I've never heard of this causing an O/S crash. Perhaps you are using native code JDBC drivers that have problems. You might want to try switching drivers, or even simply try switching from JDBC stores to file stores (temporarily) to see if that fixes the problem. You might want to check if you're using a supported JVM, etc. I'm curious about what versions of O/S, driver, JVM, and WebLogic are you using.
          Tom, BEA

JMS server affinity doubt

Similar Messages

Maybe you are looking for