JMS Issue
Hi,
I recently set up the JMS in weblogic 9.2(Clustered environment(2 Servers)). I Configured the JMS Server in Server1 and created the JMS queues targetted to both servers.
1. Server2 is using the JMS Sever which is configured in server1 by using the jndi look up to publish the OBA queue.
2. Once the server is started, Using Server2 I am able to publish the messages.
3. Over the period may be after 2 days from the server start, I am getting the below error
"[JMSClientExceptions:055079]Must provide destination to send to error. "
I am not sure what is happening and how the jndi name was not resolved which initially worked .
javax.naming.NameNotFoundException: Unable to resolve 'jms.prodJMS
Please help me to resolve this issue, Thanks in advance
The answer is likely simply that the messages are accumulating in durable subscriptions that your MDBs have created, or that you are using a distributed topic. Messages are cached in their durable subscriptions until the associated MDB restarts and consumes them.
If you are using a non-distributed topic, and don't want messages to accumulate for inactive subscribers, then don't use durable subscriptions.
If you are using a distributed topic, messages will accumulate on the members that are active even if there are no durable subscriptions, as these messages are waiting to be forwarded to the inactive members as soon as the inactive members are restarted. If you don't want such messages to accumulate, then consider setting expiration times for the messages. Expiration times can be set programmatically by the publisher via the standard JMS API, or can be set via configuration on the destination.
Tom
Similar Messages
-
JMS issues when migration from weblogic 9.2 to 10.3.5
We are facing some issues when migration from weblogic 9.2 to 10.3.5
In weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom -
I have a stand alone enterprise java application (not an EJB) that currently runs on several servers (one application per server). This application allows us to do parellel processing for performance reasons. Another important distinction is that we use a JMS Point-to-Point model with multiple consumers receiving messages off a single queue. The application is basically a JMS asynchronous message consumer, meaning it implements the javax.jms.MessageListener interface so it has the onMessage method.
Currently I have been using JBoss 4.0 as our JMS Provider. I have had no issues for awhile now with multiple consumers receiving messages off a single queue. Recently, I have been asked to move to use Netweaver's JMS provider. I was successful in changing the configurations and sending and receiving messages using the Netweaver JMS provider. However, it appears that I cannot get multiple consumers to receive messages off a single queue. I can successfully launch off several of our applications on several servers all listening to the single queue and I can also put multiple messages into that single queue. However, it appears that only one message consumer can receive a message off the single queue at one time (all the other message consumers seem to wait until the one message is done processing).
Again, I changed the configurations back to JBoss and everything worked fine (I also did it for OpenJMS and it worked as well). My quess is that I either did not setup something correctly or I need to make some kind of administative or jms setting. Any help would be greatly appreciated.
Just a side note. If I poll for messages on the single queue instead of using the onMessage() method with multiple message consumers I am able to run parellel processes.We are talking P2P with load balancing and scaling for throughput. Moving this to a pub/sub is a bad performance move as typically pub/sub is more time and resource intensive than P2P.
Just make sure that in your JNDI definition your queue has been marked as shareable. As the JMS spec goes it does not help if the provider side of the queue has the queue marked as not shared. As well if the app reading from the queue through the listener has it opened in exclusive mode all the others are waiting.
This means some investigation may be needed.
A) JNDI verify JMSDestination is defined as shareable
b) programming wise verify that putting the listener to the queue does not make the mode opened as exclusive.
Typically you would have implemented an MDB. You need to check the number of instances that you have defined for the MDB. As well you may define the same destination with multiple JNDI names and thus set different MDBs on the same queue (but same MDB class).
There is a world of solutions out there. Pick the one that works for you
Enjoy
Message was edited by: F.J. Brandelik
SAP's implementation of JMS persistence is through a Database. Make sure locking happens at the record level and not at the page level. -
Hi,
I have following issue..
Following is the architecture:-
System1----->MQ--->OSB----->System2
Now SYSTEM1 is a java client, and OSB have a SOAP proxy service...
Now i m not able to figure out how to make this senario work???
How can a Java Client post a Soap Msg on MQ???Hey thanks for the Reply..but i think i ur not getting my problem...
I have OSB proxy say "CardProxy" and i had a java client that invoke tht Proxy...and it works...
The Problem is :-
now There is a MQ(or it can be JMS) between Java client and OSB proxy.
What i am thinking is If i post a complete soap Envelope on Queue..i will have a "JMS proxy" that will read it from Queue and give it to "CardProxy"...
The main Issue is How do i form this "soap envelope"...I m trying using axis but not able to do it.
???Hope u get my Issue...
Regards,
Rohan -
h1. {color:#000000}Hi Guys, {color}
We are having issues when using multiple JMS queues and Message DrivenBeans. Its Glassfish application server, version 2. The way it currently works is we create some objects add add them to the first JMS queue. The queue destination is a message driven bean when receives the message acknoladges it and then creates several new objects and adds them to another queue when is received by another message driven bean. This means that objects recevied on the first quest generally create 10 - 20 new objects (the first object is normally a URI to a web resource of some kind). The receiver then will create 10 -20 new objects that are downloaded from a server. Each of these objects are then added to a separate queue.
All the functionality of sending messages is all contained in the code below:
private QueueConnectionFactory pconnectionFactory = null;
private Queue pqueue = null;
private QueueConnection queueConnection = null;
private QueueSession queueSession = null;
private QueueSender queueSender = null;
private Queue replyTo = null;
private boolean isQueueOpen = false;
* Sends a JMS object message, if exception occurs, a new connection is started.
public void sendJMSMessage(Serializable object) {
log.trace("JMSProvider:Sending JMS object message");
try
trySendJMSMessage(object);
} catch(JMSException jmsException) {
log.trace("JMSException caught when sending message... attempting to reopen connection");
log.trace(jmsException);
closeJms();
openOnce();
sendJMSMessage(object);
private void trySendJMSMessage(Serializable object) throws JMSException {
ObjectMessage objMsg = queueSession.createObjectMessage(object);
objMsg.setJMSExpiration(0);
if (replyTo != null)
objMsg.setJMSReplyTo(replyTo);
queueSender.send(objMsg);
private void openJms() throws JMSException {
isQueueOpen = true;
log.trace("JMSProvider: Opening JMS connection");
queueConnection = pconnectionFactory.createQueueConnection();
queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queueSender = queueSession.createSender(pqueue);
replyTo = null;
private void closeJms() {
isQueueOpen = false;
log.trace("JMSProvider: Closing JMS connection");
if (queueConnection != null) {
try {
queueConnection.close();
} catch (JMSException e) {
log.trace("JmsProvider: JMSExcetion caught when closeing JMS Connection");
queueConnection = null;
}Iv not used jms before. The first problem that I notice is if I try to send an object message and then imediatly close the connection, when the server is handling large loads of data. I receive messages in the log stating that the connection pool on the server has reached its limit. The JMS connections are P2P and not topic based. There is a single producer and a single consumer, however its on a cluseterd server, meaning multiple threads. Knowning this, we trying not to close queue connections when sending messages and try and use the same queue to send all message to the desired destination using one queue. The problem is that a no point to we know howmany objects we are going to be processing so we do not know at what point to close the connections.
As we cannot close the connections, it is left up to the garbage collected to destroy the connections, this also produces warnings in the log file stating that a connection has been destoyed on an active connection.
The last problem that I we have is that occassionaly I receive an XAException. The exception is listed below in the next post:
[#|2009-12-23T14:39:53.762+0100|SEVERE|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=58;_ThreadName=p: thread-pool-1; w: 50;_RequestID=d953eff9-afe6-4f65-bf08-7ae8328c421a;|endTransaction (XA) on JMSService:jmsdirect failed for connectionId:1621055879205632000 and flags=67108864 due to unkown JMSService server error.|#]
[#|2009-12-23T14:39:53.762+0100|WARNING|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=58;_ThreadName=p: thread-pool-1; w: 50;_RequestID=d953eff9-afe6-4f65-bf08-7ae8328c421a;|MQJMSRA_MC2001: destroy:Previously destroyed-mcId=221|#]
[#|2009-12-23T14:39:53.762+0100|SEVERE|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=58;_ThreadName=p: thread-pool-1; w: 50;_RequestID=d953eff9-afe6-4f65-bf08-7ae8328c421a;|rollbackTransaction (XA) on JMSService:jmsdirect failed for connectionId:1621055879205632000:transactionId=1621055879249863681 due to unkown JMSService server error.|#]
[#|2009-12-23T14:39:53.762+0100|SEVERE|sun-appserver2.1|javax.enterprise.system.core.transaction|_ThreadID=58;_ThreadName=p: thread-pool-1; w: 50;org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe;rollback;_RequestID=d953eff9-afe6-4f65-bf08-7ae8328c421a;|JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe] on Resource [rollback] operation.|#]
[#|2009-12-23T14:39:53.762+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=66;_ThreadName=p: thread-pool-1; w: 82;|- getQueuedUpdateById() called, 1 updates in queue
[#|2009-12-23T14:39:53.762+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=66;_ThreadName=p: thread-pool-1; w: 82;|- All resources handled of Update 1261575585540 - 5 sources
|#]
[#|2009-12-23T14:39:53.762+0100|SEVERE|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=83;_ThreadName=p: thread-pool-1; w: 65;_RequestID=43da22b0-7829-4dff-9483-95d536d7f38a;|startTransaction (XA) on JMSService:jmsdirect failed for connectionId:1621055879205636098 due to unkown JMSService server error.|#]
[#|2009-12-23T14:39:53.762+0100|WARNING|sun-appserver2.1|javax.enterprise.system.core.transaction|_ThreadID=83;_ThreadName=p: thread-pool-1; w: 65;_RequestID=43da22b0-7829-4dff-9483-95d536d7f38a;|JTS5041: The resource manager is doing work outside a global transaction
javax.transaction.xa.XAException
at com.sun.messaging.jms.ra.DirectXAResource.start(DirectXAResource.java:680)
at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:305)
at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:205)
at com.sun.enterprise.distributedtx.J2EETransaction.enlistRes
.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:245)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:76)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
Caused by: com.sun.messaging.jmq.jmsservice.JMSServiceException: startTransaction: connection ID not found: 1621055879205636098
at com.sun.messaging.jmq.jmsserver.service.imq.IMQDirectService.checkConnectionId(IMQDirectService.java:2464)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQDirectService.startTransaction(IMQDirectService.java:1514)
at com.sun.messaging.jms.ra.DirectXAResource.start(DirectXAResource.java:646)
I would be eternally greatfull for any ideas?
Thanks DanThis isn't much information to go on. Some thoughts:
Is your consumer app throwing exceptions or otherwise somehow failing to acknowledge/commit its received messages?
Are there any messages in the server logs?
Have you tried looking at your thread dumps?
I recommend starting your investigation by examining the message count statistics for each destination and each subscriber.
Also, in case you haven't done so already, I highly recommend configuring a quota on each JMS server.
Tom -
Urgent JMS issue with SSL-enabled cluster
Hello, dear All!
We have deployed a SAP WebAS SP13 SSL-enabled cluster (2 servers) and face the following strange behaviour:
When both servers are running our queue-based message driven beans (MDB EJBs) never get any messages.
However, JMS topic subscriber threads (not implemented as MDBs) work fine on both servers and receive JMS broadcasts. As well web-initiated JMS queue browsing works fine.
Then if only one (central) server is up, queue-based MDBs work fine and start receiving messages...
If you know or guess what might be an issue it would be greatly appreciated!
Thank you and best regards,
-YuriHi!
Yes, I solved this problem. You have to set your certificate to the LDAP server and get SSL enabled. You should also add same certificate to your jdk's cacerts file. That should help. :)
Janne -
A must read.
http://www.javaworld.com/javaworld/jw-02-2001/jw-0223-extremescale.html
Quote:
"Overall BEA WebLogic Server 6.0 has the most robust and well
thought-out clustering implementation. HP Bluestone Total-e-Server
2.7.1, Sybase Enterprise Application Server 3.6, and SilverStream
Application Server 3.7 would be the next choices, in that order."
The article however did highlight some weaknesses in WebLogic Server
6.0, namely JMS Topics and Queues. Read for more info.
However, if you compare the "single point of failure" of all the vendors
mentioned, only WebLogic has a single point of failure, those being with
JMS and administration.
Will the issue regarding JMS be addressed? and when?
John
A lot of the JMS limitations were brought up during 6.0 beta. Supposedly
there are plans to address these particular concerns in an upcoming version
(not 6.0).
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Jesus M. Salvo Jr." <[email protected]> wrote in message
news:[email protected]..
> A must read.
>
> http://www.javaworld.com/javaworld/jw-02-2001/jw-0223-extremescale.html
>
> Quote:
>
> "Overall BEA WebLogic Server 6.0 has the most robust and well
> thought-out clustering implementation. HP Bluestone Total-e-Server
> 2.7.1, Sybase Enterprise Application Server 3.6, and SilverStream
> Application Server 3.7 would be the next choices, in that order."
>
> The article however did highlight some weaknesses in WebLogic Server
> 6.0, namely JMS Topics and Queues. Read for more info.
>
> However, if you compare the "single point of failure" of all the vendors
> mentioned, only WebLogic has a single point of failure, those being with
> JMS and administration.
>
> Will the issue regarding JMS be addressed? and when?
>
>
> John
>
-
JMS Issues over NAT IP in weblogc 10.3
Dear Tom B,
We have an issue in connecting to the JMS TOPIC's over NAT IP. Pls note the application has Applets/Swing and hence use Thin Client jars for communicating it with weblogic server. We are getting the following exception when we try to look up using the Natted IP.
Exception at MessagingServiceFactory :::weblogic.jms.common.JMSException: [JMSClientExceptions:055054]Error finding dispatcher: weblogic.messaging.dispatcher.DispatcherException: Could not register a DisconnectListener for [IOR:0000000000000042524d493a7765626c6f6769632e6d6573736167696e672e646973706174636865722e44697370617463686572496d706c3a30303030303030303030303030303030000000000000010000000000000208000102000000000d3137322e31362e31372e313000001f6a000000f800424541080103000000000b74726561737572792d3100000000000000000042524d493a7765626c6f6769632e6d6573736167696e672e646973706174636865722e44697370617463686572496d706c3a303030303030303030303030303030300000000000000432363800000000024245412a0000001000000000000000007667e38aea8d58524245410b00000068000000000000006000005d7765626c6f6769632e6d6573736167696e672e646973706174636865722e4469737061746368657252656d6f74653a7765626c6f6769632e6d6573736167696e672e646973706174636865722e446973706174636865724f6e6557617900000005000000010000002c0000000000010020000000030001002000010001050100010001010000000003000101000001010905010001000000190000003b0000000000000033687474703a2f2f3137322e31362e31372e31303a383034322f6265615f776c735f696e7465726e616c2f636c61737365732f00000000001f000000040000000300000020000000040000000100000021000000580001000000000001000000000000002200000000004000000000000806066781020101010000001f0401000806066781020101010000000f7765626c6f67696344454641554c540000000000000000000000000000000000] for treasury-1
weblogic.jms.common.JMSException: [JMSClientExceptions:055054]Error finding dispatcher: weblogic.messaging.dispatcher.DispatcherException: Could not register a DisconnectListener for [IOR:0000000000000042524d493a7765626c6f6769632e6d6573736167696e672e646973706174636865722e44697370617463686572496d706c3a30303030303030303030303030303030000000000000010000000000000208000102000000000d3137322e31362e31372e313000001f6a000000f800424541080103000000000b74726561737572792d3100000000000000000042524d493a7765626c6f6769632e6d6573736167696e672e646973706174636865722e44697370617463686572496d706c3a303030303030303030303030303030300000000000000432363800000000024245412a0000001000000000000000007667e38aea8d58524245410b00000068000000000000006000005d7765626c6f6769632e6d6573736167696e672e646973706174636865722e4469737061746368657252656d6f74653a7765626c6f6769632e6d6573736167696e672e646973706174636865722e446973706174636865724f6e6557617900000005000000010000002c0000000000010020000000030001002000010001050100010001010000000003000101000001010905010001000000190000003b0000000000000033687474703a2f2f3137322e31362e31372e31303a383034322f6265615f776c735f696e7465726e616c2f636c61737365732f00000000001f000000040000000300000020000000040000000100000021000000580001000000000001000000000000002200000000004000000000000806066781020101010000001f0401000806066781020101010000000f7765626c6f67696344454641554c540000000000000000000000000000000000] for treasury-1
at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:266)
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSConnectionFactory.java:184)
I read your other thread Weblogic JMS port usage! where you have said a special -D property might be required, but I could not get the exact property for us to try it out.
Request your advise.
Regards
Suresh.Hi ,
Would you be able to explain what are you trying to do , what is failing along with tha stack trace please?
Presumably, you have got JMS modules -> JMS Topic created and all assigned/targetted to the Managed server instances? Are you having trouble connecting/subscribing to that topic from your client code? if so, where does your client code execute from .. I mean is that on the same host as weblogic server ?
from the host that has your client code - try ping / nslookup /tracert to weblogic host and see if thats resolved in the first place.
HTH
Sri -
Hi guys,
We are trying to achieve synchronous communication using JMS. The client in Weblogic Domain 1 creates a JMS Message , and sets the JMSReplyTo attribute as queue ‘Reply’ where it waits on for a reply. It waits for a message having correlation id = to the messageid of the message it sent on the ‘reply’ queue. An OSB proxy service picks the message and puts it on a queue on Weblogic Domain 2. A MDB listening to this queue on domain 2, picks the message and creates a reply message with the correlation id of reply as message id of incoming message. At this point when we inspect the JMSReplyTo header value of the request message, it appears as null. Is the JMSReplyTo attribute not retained across Weblogic domains? Or is the proxy service not copying it over.
Our basic aim is to get the request message from a queue on one domain to another domain, and get the reply back on the right queue that the client is pinning on.
Is using OSB not the right approach or we are not configuring it right? Will using Weblogic SAF capability help us?You have to configure a transport header action with "pass all headers through pipeline" option to make this work.
Configuring Transport Headers in Message Flows
The transport header action is a communication type action, and it is available in pipeline stages and error handler stages.
Configuring Global Pass Through and Header-Specific Copy Options for Transport Headers
The following options are available when you configure a transport headers action:
> * The Pass all Headers through Pipeline option specifies that at run time, the transport headers action passes all headers through from the inbound message to >the outbound message or vice versa. Every header in the source set of headers is copied to the target header set, overwriting any existing values in the target >header set. -
Undeployment hangs. JMS issue??
Hi All,
I'm facing an issue that undeployment through WLST hangs. The application module is removed from the console, But still it is not coming out of WLST. I could see that the thread is waiting on the task to complete, but it never comes out. Below is the thread message.
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
weblogic.management.provider.internal.ActivateTaskImpl.waitForCompletion(ActivateTaskImpl.java:437)
weblogic.management.provider.internal.ActivateTaskImpl.waitForTaskCompletion(ActivateTaskImpl.java:377)
weblogic.management.provider.internal.EditAccessImpl.activateChangesAndWaitForCompletion(EditAccessImpl.java:878)
weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.activate(ConfigurationManagerMBeanImpl.java:332)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.mbeanservers.edit.internal.RecordingInterceptor.invoke(RecordingInterceptor.java:199)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.mbeanservers.edit.internal.EditLockInterceptor.invoke(EditLockInterceptor.java:112)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:314)
weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
"weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@1c4816f6 TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
java.lang.Thread.run(Thread.java:619)
"weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@1c544f84 TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
Can anyone Help on this?I'm sorry I'm resurrecting an ancient thread, but I think I've got the same issue.
Using WL 10.3.6 on JDK_1.7.0_40.
Any deployment operation on my webapp (be it "undeploy", "deploy") does the job, but then hangs and never exists (regardless whether it's invoked via weblogic.Deployer, or WLST console). -
I have two Weblogic 8.1 domains configured. One has a local JMS server with some Queues that are receiving messages and the other one has an MDB deployed that is supposed to pull messages from one of the queues. Im trying to use a foreign JMS Server. I set it up (I dont know how to test if the configuration is correct) But when I try to deploy my MDB it tells me that it couldn't find the destination. Has anybody encountered this problem before? Help will be appreciated.
Thanks,
JonatanI've already made sure that the two domains trust each other. If I look at the JNDI tree it seems that the Foreign Destination and Factory are correctly added. It just keeps complaining about Not finding the connection. Anyone seen this before?
-
JMS Client disconnects often randomly in Weblogic10.3 cluster setup
Hi,
It would be very helpful for us if someone can suggest the way to overcome the below jms issue.
Our application recently migrated to Weblogic 10.3 from Weblogic8.1, It is a clustered set up with two managed servers each on different solaris machine.
Client connects to jms using wljmsclient.jar and wlclient.jar with t3 protocol.
When client starts jms connection, it is getting connected to server with no errors, however we often see that client jms connection disconnects in between,
It sometimes calls onException() and some times we do not even see any error message in console log when it disconnects,
When onException() is called, we can see below exception stack trace:
==========================
JMS exception class = weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:2191)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:2120)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4588)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
JMS exception class = java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
weblogic.jms.common.LostServerException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1436)
at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
=======================
When onException() is triggered, TopicConnection and TopicSession gets recreated in program, however jms is not getting reconnected once onException() is called. Some times jms session is lost in between with out any errors in log. We did not see this issue when our app used Weblogic8.1.
We greatly appreciate if someone can help to resolve this issue.Hi,
This is a common issue if you use wljmsclient.jar and wlclient.jar at client side. Many times we get "org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No" Please try using weblogic.jar at client end or even there is a better option to create the "*wlfullclient.jar*" using the jarBuilder utility provided as part of WebLogic.
To create the "wlfullclient.jar" please refer to the following link:
[http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/client/jarbuilder.html#wp1077742|http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/client/jarbuilder.html#wp1077742]
Thanks
Jay SenSharma
http://jaysensharma.woardpress.com -
Websphere Application Server - MQ: JMS
All,
I have an MDB which dequeues a message, does some processing, and inserts data into the database.
Now problem I am having here is, I am running my application on Websphere Application Server 5.1.1.5 using MQ 5.3. When I have under 15,000 messages all is fine. But once this number exceeds 15,000 it tends to process messages at almost 1 message per 20 - 30 min.
I am curious is this a problem with AppServer or a JMS issue? Thanks in advance.
By the way, I do not have any exceptions or anything for you.Haha I just did that as you posted the message here. We are using hibernate for database management. Looks like it is taking up a lot of the cpu.
Also, we are using Hibernate with JDBCTransaction however our MDB is using Bean managed transactions, is it a possibility that the commit is not occuring at the Bean level to get to the next message? -
Accessing JMS from stand-alone client
I'm currently attempting to access EJBs, JMS topics and JMS queues from a swing client running on a different machine to the application server (in this case, Sun App Server 9).
I have added the following jars to the classpath: appserv-rt.jar, javaee.jar and imqjmsra.jar, as well as generated EJB stubs. I have specified the two -D options on the command line:
-Dorg.omg.CORBA.ORBInitialHost=<server>
-Dorg.omg.CORBA.ORBInitialPort=3700
I have tried adding my own jndi.properties with:
java.naming.factory.initial=com.sun.jndi.cosnaming.CNCtxFactory
java.naming.provider.url=iiop://<server>:3700
I have also tried without including a jndi.properties file and using the one supplied by the appserv-rt.jar (this causes more errors than adding my own).
I am able to lookup an EJB using the global JNDI name and successfully invoke methods on the EJB. If I use the java:comp/env context then I receive the same error as I do with the JMS issues which I'm about to describe.
When I attempt to access the JMS factories, topics and queues using both the java:comp/env and the global JNDI name I receive the following error:
javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingCo
ntextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.j
ava:44)
at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
The global JNDI name for the topic factory (for example) is jms/TopicConnectionFactory - I have tried both lookups:
InitialContext context = new InitialContext();
context.lookup("jms/TopicConnectionFactory") //lookup 1
context.lookup("java:comp/env/jms/TopicConnectionFactory") //lookup 2The factory is clearly visible in JNDI under the jms/TopicConnectionFactory when I browse the JNDI from the Sun Admin Console.
I run the application on a separate machine via the standard java.exe -jar myclient.jar (the jar's manifest has the main class and the classpath described above set)
Does anybody see anything that I could be missing to get JMS lookups to work from a thick client. As mentioned I can lookup EJBs with no problems so I am definitely connecting to the app server correctly - I figure I'm missing another jar or something like that.
I have also tried adding application-client.xml and sun-application-client.xml descriptors to myclient.jar/META-INF but that doesn't seem to work either, and when I do I don't think the descriptors are being read because I am unable to lookup the EJB with the java:comp/env JNDI reference - I still need to use the global JNDI name. I would like to use the java:comp/env but I'm not certain how I get the application client jar to load these descriptors, or does something in the appserv-rt.jar do that when it is first accessed (a little unsure of this bit).
My main concern though, even with global JNDI lookups is that the JMS lookups fail and the EJB lookups succeed.
Any help would be greatly appreciated.
I tried again with using the jndi.properties file in the appserv-rt.jar rather than setting anything on the InitialContext. After getting past all of the NoClassDefFound errors by adding more of the app server jars onto the client classpath I managed to get something working, however with the information that was spat out on the client console while performing the lookup I'm pretty certain this isn't exactly what I want - it does work however. My concern is that the messages that are being displayed makes me think I have created my own factory locally (or something weird like that). The messages I received were:
Looking up: jms/TopicConnectionFactory
23/06/2006 16:40:45 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu Mar 2 22:14:05 PST 2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS ResourceAdaapter configuration=
raUID =null
brokerType =REMOTE
brokerInstanceName =imqbroker
brokerBindAddress =null
brokerPort =7676
brokerHomeDir =/u2/sas9/imq/bin/..
brokerVarDir =/u2/sas9/domains/domain1/imq
brokerJavaDir =/usr/java
brokerArgs =null
brokerStartTimeout =60000
adminUsername =admin
adminPassFile =/var/tmp/asmq40969.tmp
useJNDIRmiServiceURL =true
rmiRegistryPort =8686
startRmiRegistry =false
useSSLJMXConnector =true
brokerEnableHA =false
clusterId =null
brokerId =null
jmxServiceURL =null
dbType =null
dbProps ={}
dsProps ={}
ConnectionURL =mq://<server>:7676/
UserName =guest
ReconnectEnabled =true
ReconnectInterval =5000
ReconnectAttempts =3
AddressListBehavior =RANDOM
AddressListIterations =3
InAppClientContainer =true
InClusteredContainer =false
GroupName =null
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: start:SJSMQ JMSRA Connection Factory Config={imqOverrideJM
SPriority=false, imqConsumerFlowLimit=1000, imqOverrideJMSExpiration=false, imqA
ddressListIterations=3, imqLoadMaxToServerSession=true, imqConnectionType=TCP, i
mqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=, imqSSLProvide
rClassname=com.sun.net.ssl.internal.ssl.Provider, imqJMSDeliveryMode=PERSISTENT,
imqConnectionFlowLimit=1000, imqConnectionURL=http://localhost/imq/tunnel, imqB
rokerServiceName=, imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpirati
on=0, imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0, imqAckOn
Acknowledge=, imqConsumerFlowThreshold=50, imqDefaultPassword=guest, imqQueueBro
wserMaxMessagesPerRetrieve=1000, imqDefaultUsername=guest, imqReconnectEnabled=f
alse, imqConnectionFlowCount=100, imqAddressListBehavior=RANDOM, imqReconnectAtt
empts=3, imqSetJMSXAppID=false, imqConnectionHandler=com.sun.messaging.jmq.jmscl
ient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimestamp=false, imqBrokerServi
cePort=0, imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false, imqOverride
JMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueueBrowserRetrieveTimeout=60
000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted=false, imqConnectionFlowL
imitEnabled=false, imqReconnectInterval=5000, imqAddressList=mq://<server>:7676/, i
mqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnectionFactory setPasswor
d
INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnectionFactory setAddress
List
INFO: MQJMSRA_MF1101: setAddressList:NOT setting default value=localhost
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnectionFactory setUserNam
e
INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=1:xacId=4902744336909087232:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=2:xacId=4902744336909100288:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=3:xacId=4902744336909108480:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=4:xacId=4902744336909117696:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=5:xacId=4902744336909126400:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:46 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=6:xacId=4902744336909134336:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:47 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=7:xacId=4902744336909143040:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
23/06/2006 16:40:47 com.sun.messaging.jms.ra.ManagedConnection <init>
INFO: MQJMSRA_MC1101: constructor:Created mcId=8:xacId=4902744336909151488:Using
xacf config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverri
deJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=tru
e, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfigu
redClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imq
JMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http:/
/localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostNam
e=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false
, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefault
Password=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=g
uest, imqReconnectEnabled=true, imqConnectionFlowCount=100, imqAddressListBehavi
or=RANDOM, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=c
om.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimes
tamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsu
merTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueu
eBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted
=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddre
ssList=mq://<server>:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
Looking up: jms/topic/MyTopic
Does anybody know what these messages mean and also whether or not this is what I should be seeing on the client side?Greetings!!
Dear danrak,
Probably u must ahve found a solution to this issue.
I am facing a similar problem.
I can lookup EJBs but not JMS factoriers.
can u please guide me in this respect!
this is my output
Jan 5, 2007 6:09:38 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Jan 5, 2007 6:09:39 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS ResourceAdaapter configuration=
raUID =null
brokerType =REMOTE
brokerInstanceName =imqbroker
brokerBindAddress =null
brokerPort =7676
brokerHomeDir =C:\Sun\AppServer\imq\bin\..
brokerVarDir =C:/Sun/AppServer/domains/domain1\imq
brokerJavaDir =C:/Sun/AppServer/jdk
brokerArgs =null
brokerStartTimeout =60000
adminUsername =admin
adminPassFile =C:\Documents and Settings\Administrator\Local Settings\Temp\asmq36440.tmp
useJNDIRmiServiceURL =true
rmiRegistryPort =1099
startRmiRegistry =true
useSSLJMXConnector =true
brokerEnableHA =false
clusterId =null
brokerId =null
jmxServiceURL =null
dbType =null
dbProps ={}
dsProps ={}
ConnectionURL =mq://FarhanJan:7676/
UserName =guest
ReconnectEnabled =true
ReconnectInterval =5000
ReconnectAttempts =3
AddressListBehavior =PRIORITY
AddressListIterations =3
InAppClientContainer =true
InClusteredContainer =false
GroupName =null
Jan 5, 2007 6:09:39 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: start:SJSMQ JMSRA Connection Factory Config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverrideJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=true, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imqJMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http://localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefaultPassword=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=guest, imqReconnectEnabled=false, imqConnectionFlowCount=100, imqAddressListBehavior=PRIORITY, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimestamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueueBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddressList=mq://FarhanJan:7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}
Jan 5, 2007 6:09:39 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started
Jan 5, 2007 6:09:43 PM com.sun.messaging.jms.ra.ManagedConnectionFactory setPassword
INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
Jan 5, 2007 6:09:43 PM com.sun.messaging.jms.ra.ManagedConnectionFactory setAddressList
INFO: MQJMSRA_MF1101: setAddressList:NOT setting default value=localhost
Jan 5, 2007 6:09:43 PM com.sun.messaging.jms.ra.ManagedConnectionFactory setUserName
INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest
Jan 5, 2007 6:09:45 PM com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl obtainManagedConnectionFactory
SEVERE: mcf_add_toregistry_failed
Jan 5, 2007 6:09:45 PM com.sun.enterprise.naming.SerialContext lookup
SEVERE: NAM0004: Exception during name lookup : {0}
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to register MCF in registry
Your Help will be highly appreciated. -
How can i pass a XmlObject to a JMS Queue
I have a Message Channel which will accept XML. and when i try to pass a Xmlobject
, it says that Cannot send non-TextMessage to Queue which accepts only xml. how
can i send a Xmlobjct from my application to a Jms Queue.
Senthil kumar M R
This is not a WL JMS issue - the message
has been stopped even before JMS is called.
I suggest posting to one of
weblogic.developer.interest.webservices
weblogic.developer.interest.workshop
weblogic.integration.developer
Senthil Kumar M Rangaswamy wrote:
> I have a Message Channel which will accept XML. and when i try to pass a Xmlobject
> , it says that Cannot send non-TextMessage to Queue which accepts only xml. how
> can i send a Xmlobjct from my application to a Jms Queue.
>
> Senthil kumar M R
Maybe you are looking for
-
Upgrade from 4.1.2 to 5.1.2
Hello, We recently upgraded our CCM 4.1.2 to CUCM 5.1.2. The IP Phone services are not working any longer and this is causing big issue with other product. We will relocarte them in the end but my main concerne is to make them disappear from the phon
-
How can I sync my old Ipod without loosing everything? I dont remember my old password and dont have the same email. I have many pics stored on there of many trips we took over the years and songs as well please help...
-
How to find out if a string is all alphabets
Hi, How can I find out if a string contains all alphabets? Please help. Thanks.
-
Financial Reporting and substitution variable
Hello, i have a problem with FR and substitution variable. I create the substitution variable in Essbase for example antYear but i dont'see in dimension layout in FR studio and workspace. Thanks.
-
Funtion module to update Infotype 14
Hi guys, Is ther any function modules to update infotype 14 other than HR_INFOTYPE_OPERATION and HR_MAINTAIN_MASTERDATA...... Thanks, Satya