JMS Server Bytes Pending Negative?

          To my understanding bytes Pending in WLS Console indicates JMS message has been
          sent but JTA Tx has not commited or message has been received by Tx is not commited
          We have seen negative numbers in WLS Console for JMS Server.
          When / Why would this happen
          Thanks
          Harish

Negative JMS stats indicates a WL bug in statistics - likely
          there is already a fix for it. Contact customer support.
          Harish Tejwani wrote:
          > To my understanding bytes Pending in WLS Console indicates JMS message has been
          > sent but JTA Tx has not commited or message has been received by Tx is not commited
          >
          > We have seen negative numbers in WLS Console for JMS Server.
          >
          > When / Why would this happen
          >
          > Thanks
          >
          > Harish

Similar Messages

'Bytes' & 'Bytes pending ' showing negative

          Hi,
          Some times I see negative number in 'Bytes' and 'Bytes Pending' columns in weblogic
          console.
          Although all the messages were processed and acknowledged successfully.
          Can some one explain what does it mean ?
          thanks
          - saurabh


That would be a bug in the statistics code. Contact customer
          support for the fix.
          Tom, BEA
          Saurabh Kumar wrote:
          > Hi,
          >
          > Some times I see negative number in 'Bytes' and 'Bytes Pending'
          columns in weblogic
          > console.
          > Although all the messages were processed and acknowledged successfully.
          > Can some one explain what does it mean ?
          >
          > thanks
          > - saurabh

Error starting JMS-Server

I get an exception in starting OC4J (oc4j_extended_1013_dp4.zip file, version 10.1.3)
java -jar oc4j.jar
(SEVERE) Failed to set the internal configuration of the OC4J JMS Server with:
XMLJMSServerConfig[file:/C:/oc4j_1013/j2ee/home/config/jms.xml]
Error starting JMS-Server...
On my computer I succeeded to start the same OC4J ok, but on other 2 computers I get the same exception.
What can be the problem?
Thanks.

The OC4J instance that is having the problem may have .lock file issues. Some quotes from the JMS chapter of the services guide:
If OC4J terminates normally, then the lock files are cleaned up automatically. However, if OC4J terminates abnormally, for example, a kill -9 command, then the lock files remain in the file system. OC4J can usually recognize leftover lock files. If not, you must manually remove lock files before restarting OC4J after abnormal termination.
JMS persistence lock files are tagged with (contain) server and persistence directory location info. If the lock file exists when the JMS server starts, and the lock file was created by the same server (having the same ip address) and using the same persistence directory location, then the JMS server will assume control of the lock file and start up successfully.
If, for some reason, the jms.state file itself is corrupted, then the only recourse is to delete it, with the attendant loss of all pending transactions - that is, transactions that have been committed, but the commits not yet performed by all individual destination objects participating in the transactions.
Note that the use of an IP address can cause issues if you have abnormal terminations and are using DHCP (so next time you start OC4J you also have a new IP address). There was also an issue in the dev preview versions if you are running on MS-Windows where the .lock files would not be automatically deleted on normal shut down - even if you have since moved to the release version, the old .lock files may still be there.

JMS Server Message Buffer Size & Thresholds and Quotas settings

On WLS10MP1,
For persistent messages:
1.Does "JMS Server Message Buffer" setting serve the same purpose as "Bytes Threshold High" under Threshold ?
2.If no, can someone explain the difference pls.
Many thanx,

Message Buffer Size relates to the number of message the JMS server keeps in the memory. The value of this determines when the server should start paging the message out of memory to a persistence store. So this is directly related with the memory/storage issue and the size of messages.
Bytes Threshold High relates to the performance of the JMS server. When this limit is reached JMS server starts logging the message and may even instruct he producer to slow down the message input.
So the if you get Bytes Threshold High messages that means you should check on your consumer (MDB who is picking up messages from the que), and try to increase its performance.
However if your Message Buffer Size is crossing limits then you should think of increasing the momory so that more messages can be kept in memory and disck IO can be reduce.
Anyone wants to add something more to it?

Bytes Pending Problem still Prevails;

          Sorry to say that my byte pending problem is still around.
          There are
          no applications exceptions.
          no runtime exceptions.
          I also made sure that the deployment discriptor declares the TX boundry as NEVER
          The problem that I see at the moment is that once NotificationMDB goes out of commision
          (meaning bytes pending starts increasing) even if I reddeploy the jar file. Message
          on reaching the notification topic do not fire the MDB's
          Could somebody explain possible reasons for this behavior.
          Also I have another process that subscibes to the same topic. but that only takes
          effect when i am communicating with my system sysnchronously.
          Here is the deployment discriptor for
          NotificationMDB-ejb-jar.xml
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>NotificationMDB</ejb-name>
          <ejb-class>mypackage.NotificationMDB</ejb-class>
          <transaction-type>Container</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Topic</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
               <container-transaction>
                    <method>
                         <ejb-name>NotificationMDB</ejb-name>
                         <method-name>*</method-name>
                    </method>
               <trans-attribute>Never</trans-attribute>
               </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          and
          NotificationMDB-weblogic-ejb-jar.xml
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>NotificationMDB</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>200</max-beans-in-free-pool>
          <initial-beans-in-free-pool>200</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>mysystem.jms.notificationTopic</destination-jndi-name>
          <connection-factory-jndi-name>mysystem.jms.notificationFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <jndi-name>mysystem.jms.NotificationMDB</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>


          Hi christian.
          you were right switching to sp2 solved the bytes pending problem on my topic
          thanks for your help
          Christian Buchegger <[email protected]> wrote:
          >Hi,
          >
          >
          >what version of WLS are you using ? Please check if this could be issue
          >061783 as documented at:
          >http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html#1143510
          >and which is fixed with WLS6.1SP2. Otherwise consider to open as case with
          >BEA Support.
          >
          >
          >Regards,
          >Christian Buchegger
          >Developer Relations Engineer
          >BEA Support
          >
          >
          >Mekaiel Hussain schrieb:
          >
          >> Sorry to say that my byte pending problem is still around.
          >>
          >> There are
          >> no applications exceptions.
          >> no runtime exceptions.
          >> I also made sure that the deployment discriptor declares the TX boundry
          >as NEVER
          >>
          >> The problem that I see at the moment is that once NotificationMDB goes
          >out of commision
          >> (meaning bytes pending starts increasing) even if I reddeploy the jar
          >file. Message
          >> on reaching the notification topic do not fire the MDB's
          >>
          >> Could somebody explain possible reasons for this behavior.
          >>
          >> Also I have another process that subscibes to the same topic. but that
          >only takes
          >> effect when i am communicating with my system sysnchronously.
          >>
          >> Here is the deployment discriptor for
          >>
          >> NotificationMDB-ejb-jar.xml
          >>
          >> <ejb-jar>
          >> <enterprise-beans>
          >> <message-driven>
          >> <ejb-name>NotificationMDB</ejb-name>
          >> <ejb-class>mypackage.NotificationMDB</ejb-class>
          >> <transaction-type>Container</transaction-type>
          >> <message-driven-destination>
          >> <destination-type>javax.jms.Topic</destination-type>
          >> </message-driven-destination>
          >> </message-driven>
          >> </enterprise-beans>
          >>
          >> <assembly-descriptor>
          >> <container-transaction>
          >> <method>
          >> <ejb-name>NotificationMDB</ejb-name>
          >> <method-name>*</method-name>
          >> </method>
          >> <trans-attribute>Never</trans-attribute>
          >> </container-transaction>
          >> </assembly-descriptor>
          >>
          >>
          >> </ejb-jar>
          >>
          >> and
          >>
          >> NotificationMDB-weblogic-ejb-jar.xml
          >>
          >> <weblogic-ejb-jar>
          >> <weblogic-enterprise-bean>
          >> <ejb-name>NotificationMDB</ejb-name>
          >> <message-driven-descriptor>
          >> <pool>
          >> <max-beans-in-free-pool>200</max-beans-in-free-pool>
          >> <initial-beans-in-free-pool>200</initial-beans-in-free-pool>
          >> </pool>
          >> <destination-jndi-name>mysystem.jms.notificationTopic</destination-jndi-name>
          >> <connection-factory-jndi-name>mysystem.jms.notificationFactory</connection-factory-jndi-name>
          >> </message-driven-descriptor>
          >> <jndi-name>mysystem.jms.NotificationMDB</jndi-name>
          >> </weblogic-enterprise-bean>
          >> </weblogic-ejb-jar>
          >

JMS server needs restart after client app restarts

Hello everyone,
          I have a client who has two domains - one for JMS and one for client (web service in this case). They are noticing that when the client domain is restarted (for various reasons), the client can make one, and only one, call to the JMS server. After that first call, the topic appears inactive from within the Weblogic console, however the console reports that there are no messages pending. So what happened? there is no error on the side of the client. Client just states that the message was submitted, but no response.
          They are using durable subsribers.
          So the question is, why, after a restart of the client domain, does a query to the JMS topic only work once?
          The workaround we have right now is to restart the domain hosting JMS and everything is fine.
          Thank you
          Chris

Hello Tom,
          To answer your questions:
          1. SOAP over HTTP
          2. The Web Service has a web method that instantiates a listener that is also a Durable Subscriber - that is all I know for now, I can get more details on this.
          3. Client and Server are same version, WLS 10.0.0
          4. There are no exceptions generated whatsoever. I was monitoring the console. After the 2nd call (which there is no response it appears), the ClientID inside WL console is "Failed". And there are no pending messages in the topic. According to the console, all messages had been processed.
          I'm wondering why the ClientID shows up as failed (no error messages though). If we restart the JMS domain, the ClientIDs show up as Active.
          Thanks
          Chris

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

JMS Server Bytes Pending Negative?

Similar Messages

Maybe you are looking for