WEBLOGIC JMS performance ?

hi ,
          I tried to find some numbers , about how much messages (in the diffrerent
          categories - ptp or pub/sub) can a weblogic server
          can stand - messages / sec , or some benchmarks,
          but i didn't find any on the web ..
          any one has any idea / link for such benchmark / performance test ???
          I would appriciate any answer !
          thanks!

1) Start with the "WebLogic JMS Performance Guide" white-paper
          on dev2dev.bea.com. This guide has no numbers, but
          it has general guidelines. Performance is not just
          numbers...
          2) General note:
          In 7.0+ JMS file stores, BEA provides 3 disk write policies.
          The default is "cache-flush", as that is transactionally safe
          in all cases. The policy may have a dramatic effect
          on performance. (WL JMS defaults to "cache-flush", IBM MQ
          always uses "direct" - as far as I know, and many smaller
          JMS players default to "disabled".)
          3) The book
          "J2EE Performance Testing with BEA WebLogic Server"
          by Peter Zadrozny, Philip Aston, Ted Osborne
          contains JMS numbers, and a benchmark tool. Keep
          in mind that the numbers here are all "producer
          limited". All the benchmarks are run with
          a single producer, so the numbers often show little
          scaling. (Most apps increase producer counts
          as they scale.)
          Tom, BEA
          Amir Ben-Amots wrote:
          > hi ,
          >
          > I tried to find some numbers , about how much messages (in the diffrerent
          > categories - ptp or pub/sub) can a weblogic server
          > can stand - messages / sec , or some benchmarks,
          >
          > but i didn't find any on the web ..
          >
          > any one has any idea / link for such benchmark / performance test ???
          >
          > I would appriciate any answer !
          >
          > thanks!
          >
          >

Similar Messages

Weblogic/jms/backend/BEMessageReference

Hi ,
I have a severe OOM problem in production as my servers are crashing very often.. I have 32 GB unix box and I have put -Xmx 3072 -Xms 3072 as MEM_ARGS for Managed1 and Managed3 ... eventhen I am getting OOM ...
Can anybody suggest me best MEM_ARGS with -Xx:MaxPermsize for Admin ,Managed1 and Managed3 server instances...
I have put Heap dump options analyzed the heap dump file showing 63% is weblogic/jms/backend/BEMessageReference.. Can anybody tell me whats the rootCause of this .
using weblogic 8.1 sp6 and jdk 1.4.2_16 version.
Thanks
Sanjana

Hi,
What's most likely happening is that the application did not configure JMS quotas and/or flow control, plus its inserting messages faster than they can be processed. It may also be the case that JMS paging hasn't been configured. If so, then an examination of JMS statistics on the WebLogic console should help make the root cause obvious, and, since you're on 8.1, I'd recommend reading the old [ WebLogic JMS Performance Guide | http://ftpna2.bea.com/pub/downloads/WebLogicJMSPerformanceGuide.pdf ] white-paper for ideas about how to address the issue.
Tom
PS. In the future, please post to the JMS newsgroup instead of the General newsgroup.

WebLogic JMS high memory usage and frequent full GCs

Hi Team,
            We have below set up in production (and all the lower environment).
1. WLS: 10.3.6 (64 bit)
2. Java: HP JDK 1.7.0.06 (64 bit)
3. Two Manage server instances in cluster with one Migratable target
4. one JMS server with Persistence store targeted to Migratable target
5. Messages are persisted in DB
6. about 37 distributed queues/topics are hosted on one JMS server
7. .Net JMS clients and WebLogic JMS clients connect to respective JMS distributed Queues/topics to either produce message or consume.
Since last month, we see that WebLogic Manage server hosting JMS server keeps on chewing memory "even with small (of the order of 28 messages in 4/5 days) load", GC indicates that objects are shifted from PSYoung space to ParOldGen during minor GCs but ParOldGen space keeps on filling up in smaller chunks. After x number of days (where x ranges from 5-7 days), even Full GC is not able to bring down memory significantly and that's when frequent full GCs start with long pauses making JMS highly unstable.
We don't have JMS Quotas configured but I think something else going on as it is not high on load. Any additional hints or troubleshooting steps is much appreciated?
Here is first and last GC log just to give an idea...
Heap after GC invocations=661 (full 0):
{Heap before GC invocations=1 (full 0):
PSYoungGen      total 1225728K, used 1050624K [9fffffff09c00000, 9fffffff5f400000, 9fffffff5f400000)
eden space 1050624K, 100% used [0x9fffffff09c00000,0x9fffffff49e00000,0x9fffffff49e00000)
from space 175104K, 0% used [0x9fffffff54900000,0x9fffffff54900000,0x9fffffff5f400000)
to   space 175104K, 0% used [0x9fffffff49e00000,0x9fffffff49e00000,0x9fffffff54900000)
ParOldGen       total 2797568K, used 0K [0x9ffffffe5f000000, 0x9fffffff09c00000, 0x9fffffff09c00000)
object space 2797568K, 0% used [0x9ffffffe5f000000,0x9ffffffe5f000000,0x9fffffff09c00000)
PSPermGen       total 49152K, used 47453K [0x9ffffffe1f000000, 0x9ffffffe22000000, 0x9ffffffe5f000000)
object space 49152K, 96% used [0x9ffffffe1f000000,0x9ffffffe21e57630,0x9ffffffe22000000)
2014-12-24T09:04:45.118-0700: 15.651: [GC [PSYoungGen: 1050624K->118221K(1225728K)] 1050624K->118293K(4023296K), 0.32600
15 secs] [Times: user=0.07 sys=0.00, real=0.33 secs]
{Heap before GC invocations=661 (full 0):
PSYoungGen      total 1367168K, used 1364256K [9fffffff09c00000, 9fffffff5f400000, 9fffffff5f400000)
eden space 1333376K, 100% used [0x9fffffff09c00000,0x9fffffff5b220000,0x9fffffff5b220000)
from space 33792K, 91% used [0x9fffffff5d300000,0x9fffffff5f128030,0x9fffffff5f400000)
to   space 33664K, 0% used [0x9fffffff5b220000,0x9fffffff5b220000,0x9fffffff5d300000)
ParOldGen       total 2797568K, used 2654825K [0x9ffffffe5f000000, 0x9fffffff09c00000, 0x9fffffff09c00000)
object space 2797568K, 94% used [0x9ffffffe5f000000,0x9fffffff0109a5c0,0x9fffffff09c00000)
PSPermGen       total 151552K, used 147591K [0x9ffffffe1f000000, 0x9ffffffe28400000, 0x9ffffffe5f000000)
object space 151552K, 97% used [0x9ffffffe1f000000,0x9ffffffe28021cd8,0x9ffffffe28400000)
2014-12-29T08:18:08.798-0700: 429216.418: [GC [PSYoungGen: 1364256K->33632K(1329792K)] 4019081K->2752791K(4127360K), 0.8
254362 secs] [Times: user=0.10 sys=0.00, real=0.83 secs]
Regards,

Thanks Luz. I have been collecting gclogs and heap dumps (whenever app server is high on memory and frequent GCs with long pauses are seen). So far heap dumps haven't revealed anything specific (may be I am not able to read heap dumps properly ) but looking at GC confirms that app server is consuming allocated heap.I was following Oracle WebLogic server support Patter as you have indicated. I thought about opening a ticket with HP but on high level JVM is doing what is suppose to do i.e allocating memory space as needed and performing GC therefore didn't go that path.
Any other suggestions that might be useful. One of the things I forgot to mention ( and I will add it to original message), that one of the .Net consumers is not asynchronously connecting to its queue (to consume messages) rather it is synchronously connects and then if it doesn't find messages it disconnects and process goes on every few seconds. I was reading somewhere that frequent JNDI look ups should be avoided. Can this cause memory issue if so then it is strange as this same set up has been there over a year and we never has problem then?
Regards,

Any kind of integration experience with Weblogic JMS and Oracle AQ?

Hi,
In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
Any comments, references, documentation, sample code, url will be most welcomed :)
Thank you very much!
Tonguc
[email protected]
References I found upto now;
Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
(Packages; javax.jms & oracle.jms)
Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
Part IV
Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
Chapter 11, "Introducing Oracle JMS"
Chapter 12, "Oracle JMS Basic Operations"
Chapter 13, "Oracle JMS Point-to-Point"
Chapter 14, "Oracle JMS Publish/Subscribe"
Chapter 15, "Oracle JMS Shared Interfaces"
Chapter 16, "Oracle JMS Types Examples"
A Sample Code from Otn
http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
Hope the above gives you a different perspective.
Eric

Slow JMS Performance

          Hi,
          I'm using WL7.1 SP2 for a JMS based application. The database is SQLServer 2000,
          and the JMS queues are persistent on this DB.
          A client outside the Weblogic Server connects and fires lots of JMS messages to
          the application. These messages are consumed by a pool of MDB's.
          I don't think it's performing as well as it could.
          For example, if I un-deploy my application, and fire 80,000 JMS messages at the
          server, it takes around 10 minutes to persist these messages to the queues. All
          good so far.
          However, with the application deployed, the same number of messages take around
          3 hours. The messages are consumed and processed as fast as they can be persisted
          to the JMS queue. It's almost as if the messages are being synchronysly put on
          the queue, ie. control is not returned to the client until the message is consumed
          and processed. Unless I'm misunderstanding this, as soon as the messages is successfully
          persisted to the JMS queue, control should be passed back to the client.
          What I'd expect to happen is that the client would take around the same time post
          the messages to the JMS Queue, ie. about 10 minutes - and the Pending Message
          count to increase on the WL Server. Once all 80,000 messages were on the queue,
          the Pending Message count would gradually go down as the messages were processed.
          If I'm misunderstanding the way this works, please let me know. If you need any
          further info, please ask and I'll post the answers.
          Thanks,
          Richard Kenyon
          EDS - UK


No problem.
          Performance is one of my hot-buttons, so I can't help but
          noting that when it comes to queueing, or even asynchronous
          invokes in general, slowing down the requester is often
          goodness. It helps put "back-pressure" on the requesting
          application, and so helps prevent a permanently growing
          request backlog that the slower request handling
          applications could never dig their way out of.
          Tom
          P.S. An updated version of the JMS performance
          guide will be released in the next few weeks. It has
          corrections, adds information about 8.1 features, and
          expands information in a number of areas. I'll post
          a link in the newsgroup when it comes out.
          Richard Kenyon wrote:
          > Thanks Tom,
          >
          > I suspected (and hoped!) that this would be the answer. I just needed
          > clarification that I wasn't being stupid :-)
          >
          > I'll have a look at the Performance guide you mentioned.
          >
          > Thanks,
          > Richard Kenyon
          > EDS - UK
          >
          > "Tom Barnes" <[email protected]> wrote in message
          > news:[email protected]...
          >
          >>When the application is active, it is forcing the server to do
          >>other work as well. In effect you are sharing a limited
          >>resource. Transactions (if applicable), your
          >>application code, your application receives, etc.
          >>In effect, the sender is slowed down because it
          >>is competing with the MDB application for resources.
          >>I suggest you read the JMS Performance
          >>Guide white-paper on dev2dev.bea.com.
          >>
          >>Tom
          >>
          >>Richard Kenyon wrote:
          >>
          >>>Hi,
          >>>
          >>>I'm using WL7.1 SP2 for a JMS based application. The database is
          >>
          > SQLServer 2000,
          >
          >>>and the JMS queues are persistent on this DB.
          >>>
          >>>A client outside the Weblogic Server connects and fires lots of JMS
          >>
          > messages to
          >
          >>>the application. These messages are consumed by a pool of MDB's.
          >>>
          >>>I don't think it's performing as well as it could.
          >>>
          >>>For example, if I un-deploy my application, and fire 80,000 JMS messages
          >>
          > at the
          >
          >>>server, it takes around 10 minutes to persist these messages to the
          >>
          > queues. All
          >
          >>>good so far.
          >>>
          >>>However, with the application deployed, the same number of messages take
          >>
          > around
          >
          >>>3 hours. The messages are consumed and processed as fast as they can be
          >>
          > persisted
          >
          >>>to the JMS queue. It's almost as if the messages are being synchronysly
          >>
          > put on
          >
          >>>the queue, ie. control is not returned to the client until the message
          >>
          > is consumed
          >
          >>>and processed. Unless I'm misunderstanding this, as soon as the messages
          >>
          > is successfully
          >
          >>>persisted to the JMS queue, control should be passed back to the client.
          >>>
          >>>What I'd expect to happen is that the client would take around the same
          >>
          > time post
          >
          >>>the messages to the JMS Queue, ie. about 10 minutes - and the Pending
          >>
          > Message
          >
          >>>count to increase on the WL Server. Once all 80,000 messages were on the
          >>
          > queue,
          >
          >>>the Pending Message count would gradually go down as the messages were
          >>
          > processed.
          >
          >>>If I'm misunderstanding the way this works, please let me know. If you
          >>
          > need any
          >
          >>>further info, please ask and I'll post the answers.
          >>>
          >>>Thanks,
          >>>Richard Kenyon
          >>>EDS - UK
          >>>
          >>
          >
          >

Weblogic JMS Cluster

Hi,
          I have a 6.1 cluster that has a JMS server A and a JMS Server B
          deployed and running on each of the managed nodes. As destination I
          created a topic with the same name for each JMS Server. The connection
          factories I deployed to the cluster only.
          My problem is, when I start the second managed server, I get the
          following error:
          <Error> <Cluster> <Conflict start: You tried to bind an object under
          the name
          com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          have bound
          from 169.59.5.26 is non clusterable and you have tried to bind more
          than once
          from two or more servers. Such objects can only deployed from one
          server.>
          When I understand correctly, this happens because the JNDI tree gets
          distributed to all nodes of the cluster, so there would be two object
          with the same name. How do I solve this situation? Do I have the
          specify different names for topics in different JMSServer running in a
          cluster? How would the load balancing work?
          Please help. Thanks in advance
          Juerg


Tom,
          Thanks for your help so far, I installed the patch and got things
          working. However I still have some open points where you might be able
          to help.
          Let's assume I don't have these smart forwarders and I have four
          topics per JMSServer deployed to two managed nodes. Connection
          factories deployed to the cluster. When I connect N publishers
          through the cluster, messages from one publisher end up in the
          appropriate topic on nodeA, messages from another publisher end up in
          the appropriate topic on nodeB. Now when I connect a durable
          subscriber via the cluster I only get messages from topics from one of
          the managed nodes, right? (This is exactly what I am seeing in my
          tests) Connecting durable subscribers to each managed node is not
          possible because of JNDI (throws exception like
          InstanceAlreadyExists). How would I connect a subscriber so that it
          subscribes to the right topics on the right node ( one the works with
          the previously described publisher)?
          All this leads me to the conclusion, that without the forwarders, a
          JMS cluster with Weblogic 6.1 is not so powerful, it basically does
          just load balacing.
          Is this correct or am I missing something important here?
          Thanks a lot and have a nice weekend
          Juerg
          Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > Juerg Staub wrote:
          > > Tom,
          > >
          > > Thanks a lot. Bascially I did everything right, just need the patch.
          > >
          > > In the other hand I'd like to know what the benefits of the smart
          > > forwarders would be. When I understand correctly, every message would
          > > be forwarded to the appropriate topic in the different JMS servers.
          > > What would that bring in the case of a failure(one node of a cluster
          > > goes down)? As far as I can see, I still would need to 're-establish'
          > > the connection factory, topic session, topic and publisher in order to
          > > publish messages again?
          > >
          >
          > Yep. I think we are on the same page:
          >
          > The "smart-forwarders" would do what the 7.0 distributed topic
          > forwarders do for you. They would forward messages bound to
          > a particular physical topic to all instances of the topic.
          > This can be implemented via a durable subscription on a
          > member topic by each remote member topic's host.
          > MDBs could be used to service the durable subscription,
          > as they already have the reconnect logic built in.
          > (Durable subscriptions are used if you wish to guard against
          > lost messages). The forwarders
          > need to change a property on the message to indicate
          > that the message is already forwarded, and forward
          > only messages that have'nt been forwarded (to prevent
          > endless loops!).
          >
          >
          > > Thanks
          > >
          > > Juerg
          > >
          > > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > >
          > >>I suggest you read the "emulating 7.0 distributed destinations"
          > >>section of the JMS performance white-paper available on dev2dev.bea.com.
          > >>You will need to apply the referenced enhancement patch on top of SP3 to
          > >>disable JNDI replication (or update to 6.1SP4).
          > >>
          > >>If you need to create a true distributed topic, you will also need to
          > >>write your own "smart-forwarders" to forward messages
          > >>between the different physical instances of the topic. Or simply
          > >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
          > >>
          > >>Tom
          > >>
          > >>Juerg Staub wrote:
          > >>
          > >>>Hi,
          > >>>
          > >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
          > >>>deployed and running on each of the managed nodes. As destination I
          > >>>created a topic with the same name for each JMS Server. The connection
          > >>>factories I deployed to the cluster only.
          > >>>
          > >>>My problem is, when I start the second managed server, I get the
          > >>>following error:
          > >>>
          > >>><Error> <Cluster> <Conflict start: You tried to bind an object under
          > >>>the name
          > >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          > >>>have bound
          > >>>from 169.59.5.26 is non clusterable and you have tried to bind more
          > >>>than once
          > >>>from two or more servers. Such objects can only deployed from one
          > >>>server.>
          > >>>
          > >>>
          > >>>When I understand correctly, this happens because the JNDI tree gets
          > >>>distributed to all nodes of the cluster, so there would be two object
          > >>>with the same name. How do I solve this situation? Do I have the
          > >>>specify different names for topics in different JMSServer running in a
          > >>>cluster? How would the load balancing work?
          > >>>
          > >>>
          > >>>Please help. Thanks in advance
          > >>>
          > >>>Juerg
          > >>

Weblogic JMS Automigration issue

Hi,
Let me first tell you about my server details. Currently we are using weblogic 10.3.3.0. We have 1 admin server and 2 manage server(MS_1 and MS_2).
Currently we are implementing the JMS auto migration in our server. For that we follow the below steps:
1. First cluster needs to be configured for automatic server migration:
Home->Cluster->configuration ->Migration -> Lock and Edit ->Choose Migratable machine for automatic server migration ->Data Source For Automatic Migration(Choose Datastore for automatic server migration) -> Click on Save
2. Environment -> Migratable target -> click on the migratable target -> Click on Migration -> select the Constrained Candidate Servers -> select service migration policy as "Automatic Migrate Failure Recovery services" -> Save and activate changes
3. Need to create a table called ACTIVE in the DB and the ddl script is located under($WL_SERVER/wl_server_10.3/server/db/oracle/920) query name:leasing.ddl
4. Create a Non XA data source(While selecting the driver you should select the Non XA driver) and in the transaction tab of the data source uncheck the global transaction option. Also the data source should point to cluster.
5. The data source created in the step 4 should be used in the JDBC Persistence store and also can be used in Cluster data source. The JDBC persistence store should be used in the JMS server and the JMS Server should be used in the JMS Queue.
After that I deploy my Java application to read from the JMS distributed queue. and the Java service is reading from the JMS queue.
But when I am restarting the manage server the below error is thrown and the deployed java application status is getting failed:
========================
<Apr 29, 2015 2:42:15 AM IST> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmsResQueueUG' defined in ServletContext resource [/WEB-INF/spring-jms-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Unable to resolve 'MTNNDQ'. Resolved ''; remaining name 'MTNNDQ'.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmsResQueueUG' defined in ServletContext resource [/WEB-INF/spring-jms-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Unable to resolve 'MTNNDQ'. Resolved ''; remaining name 'MTNNDQ'
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1113)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:431)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:254)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:251)
        Truncated. see log file for complete stacktrace
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'MTNNDQ'. Resolved ''; remaining name 'MTNNDQ'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
        at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
        Truncated. see log file for complete stacktrace
>
<Apr 29, 2015 2:42:16 AM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1430255500850' for task '27'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
        at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
        Truncated. see log file for complete stacktrace
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'MTNNDQ'. Resolved ''; remaining name 'MTNNDQ'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
        at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
        Truncated. see log file for complete stacktrace
>
====================================================
"MTNNDQ" Is the queue name which is configured in the property file. From which the spring-jms-config.xml is reading.
"jmsResQueueUG" is the Spring bean name.
Please note that during server start up deployment the above issue is coming but after the successful restart when I do the deployment the above issue is not coming.
Please suggest.
Thanks in advance.
Regards
Asutosh Kar

Your use case seems like an extremely good fit for the WebLogic "Unit-of-Order" (UOO) feature, which ensures strictly ordered message processing for all messages that are in the same UOO, and is almost trivial to enable. As a bonus, UOO won't have the perf drawbacks that are related to selector filtering. I have a feeling it would greatly simplify your setup and would at least reduce the number of performance related variables that've been introduced due to the relatively complex current setup. If this fits your use case, I recommend:
1 - set up a single MDB with a single Q
2 - configure a custom work manager and assign the MDB to this work manager instead of the default work manager, tune a max-threads-contraint on the WM and set max-beans-in-free-pool to the same value (see the MDB chapter of the Performance and Tuning guide for the exact tunables)
3 - senders sets a UOO on each message that matches the conversation index. There are two ways to do this: (1) configure 32 connection factories, each with different default UOO (one for each sub-ordering) and cache 32 senders or (2) have any sender call "(weblogic.jms.extensions.WLProducer)setUnitOfOrder() before sending each message.
Another approach would be to use topics and a durable subscription per index, plus an MDB per subscriber. This avoids queue scan selector overhead and opens up the opportunity to enable "subscriber indexing" (to familiarize yourself with selectors, I highly recommend reading the JMS chapter of the new book Professional WebLogic.) On the other hand, this approach doesn't release the use case from needing 32 different MDBs...
Tom
PS. Also ensure that senders are cached and re-used (instead of closed and re-opened for each sent message).
Edited by: TomB on Jan 28, 2010 4:19 PM
Edited by: TomB on Jan 28, 2010 4:20 PM

How to creat an Weblogic JMS configuration with authentication

I have to configure a weblogic jms topic in such a way when a remote sender send a message it has to connect using some authentication. Like when creating the initial context or the connectionFactory. But nowhere I got the steps for configuring it that way. Can you please let me know what is the out-of-the-box steps for achieving it. I am using all out-of the-box tools(no foreign jndi provider).

Simple answer, you are in the WRONG forum, this is the Application Express (APEX) support forum..
Thank you,
Tony Miller
Webster, TX

How to configure a error queue for weblogic jms topic

Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
Mingzhuang

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

Oracle PL/SQL send/receive message in weblogic jms queue

I am looking for a very simple way using oracle plsql to send and receive messages in a weblogic jms queues.
Thanks

Even i am looking for the same . Would be great if someone would help ..The jms setup has to be done in weblogic like the jms server, jms module, Jms connection factory , jms queue and then the jndi names . Now thw Problem here lies to me is that i really dont knw what should be the connection factory targets ,jndi names and where do i give the schema details as in the user name ,password , db name . Also if there is any explaination with eg on how to send /receive messages from a db trigger to jms queues .

Problem in Interacting with Weblogic JMS through Informatica ETL server

Hi All,
We are trying to configure Informatica PowerCenter server to interact with JMS queues created on Weblogic 11gR1 server. We have copied the necessary
jar file - wlfullclient.jar to the classpath of the Informatica server.
Now when i try to read contents of a JMS queue created on Weblogic server through Informatica, i get this error:-
Failed to get the Queue Connection Factory [weblogic.jms.common.DestinationImpl]. Reason: Failed to look up object [While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms'Exception Stack: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms']; remaining name 'common/DestinationImpl'
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:464)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:272)
     at weblogic.jndi.internal.ServerNamingNode_1211_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:418)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at com.informatica.powerconnect.jms.server.common.JNDIConnection.getJNDIObject(JNDIConnection.java:84)
     at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.createConnection(PlginJMSConnection.java:363)
     at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.<init>(PlginJMSConnection.java:90)
     at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.<init>(PlginJMSConnection.java:352)
     at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.create(PlginJMSConnection.java:115)
     at com.informatica.powerconnect.jms.server.reader.JMSReaderSQDriver.createPartitionDriver(JMSReaderSQDriver.java:557)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'
I have checked that this class file exists in the above said location :- "weblogic/jms/common/DestinationImpl.class" within the wlfullclient.jar but still the
code is not able to access the class. Similar error came initially while doing JNDI connection using "weblogic.jndi.WLInitialContextFactory" class but it vanished,
when i explicitly named the jar file on classpth, instead of just the folder containing the jar file.
To all the users/experts/moderators of Weblogic - Could you please help me understand why Weblogic is not able to look up subcontext 'common'
for the class - "weblogic.jms.common.DestinationImpl" ??
Thanks & Regards
Raj
Edited by: user8931188 on May 17, 2012 7:39 AM

You are experiencing a NameNotFoundException, not ClassNotFoundException so it seems there is something wrong about the client connection code or WebLogic config.
Can you share your client connection connection config/code?

Can I turn off weblogic JMS in 5.1

          All,
          Is there a way to turn off JMS in wl51. We are using another 3rd party product
          and would like to optimize the wl51 vm by removing everything from memory that
          we can.
          Regards,
          Todd


<strong response>
          Hi Todd,
          The WL 6.0+ JMS team also has messaging experience.
          We have written multiple queuing products -
          perhaps even some of the same ones you used in the "early 90s". This team
          has many years of experience, plus a dependable company to back them up. We
          have seen competitor products fall-over quite spectacularly in internal testing
          (without much effort). Evaluating scalability, robustness, and features is worth
          a second careful look, and a third -- there are many hidden twisty passages all
          alike in this arena, as you may be aware.
          We aren't even afraid to air our dirty laundry in this very public newsgroup. (Note
          that we know that other vendors track this newsgroup carefully, so now you know, that
          we know, that they know, that we know). :-)
          Note that the vendors you mention don't even support transactions (at least not until
          very recently), so to call them "enterprise" level may be a stretch. (To be fair here,
          Sonic
          is getting there, and we have worked with them directly on this. You can even search
          this newsgroup for some of their posts on the topic.)
          I think we will have to agree to disagree here, but I will of course admit there is
          always
          room for improvement.
          Tom
          P.S. Just to make things clear, I'm a BEA employee.
          </strong response>
          Todd Flora wrote:
          > Tom,
          >
          > Thanks for your reply. I will look at this so maybe I need to do nothing.
          >
          > As far as your BEA Plug goes. We looked at wl6.1 JMS and quite frankly it fell
          > far short of an enterprise solution. Take it from someone that has been working
          > with messaging products since the early 90's BEA's JMS is just mediocre. (Can't
          > spell) I don't know about ver 7.0 haven't looked at it. We are currently using
          > SpiritSoft Wave and what a great product. SonicMQ and Fiorano also had nice products.
          >
          > Regards,
          >
          > Todd
          > Tom Barnes <[email protected]> wrote:
          > >I know very little about WL 5.1 particulars. But, most JVMs do not load
          > >classes into
          > >memory until they are needed. There is usually a JVM option to see what
          > >classes it is
          > >loading. See the white-paper
          > >"Small Footprint Client Options for BEA WebLogic Server" at
          > >http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          > >(WebLogicThinClient.zip)
          > >for a little info on this option.
          > >
          > >Seriously consider WL JMS version 6 or 7. This has a robust,
          > >scalable, fast JMS written (and maintained) by a team that has had experience
          > >developing
          > >multiple enterprise level queuing products, (biased BEA plug.)
          > >
          > >Tom
          > >
          > >Todd Flora wrote:
          > >
          > >> OK Thanks for your reply.
          > >>
          > >> I have not weblogic.jms entries in the property file but the server
          > >is still listening
          > >> for JMS Messages on port 7001. So I don't believe I have succeeded
          > >in reclaiming
          > >> that memory.
          > >>
          > >> Thx.
          > >>
          > >> Todd
          > >> Michael Young <[email protected]> wrote:
          > >> >Hi.
          > >> >
          > >> >I believe all you need to do is comment out all jms related properties
          > >> >(weblogic.jms.*) in the weblogic.properties file. You may also want
          > >> >to comment
          > >> >out any connection pool used to persist jms messages.
          > >> >
          > >> >HTH,
          > >> >Michael
          > >> >
          > >> >Todd Flora wrote:
          > >> >
          > >> >> All,
          > >> >>
          > >> >> Is there a way to turn off JMS in wl51. We are using another 3rd
          > >party
          > >> >product
          > >> >> and would like to optimize the wl51 vm by removing everything from
          > >> >memory that
          > >> >> we can.
          > >> >>
          > >> >> Regards,
          > >> >> Todd
          > >> >
          > >> >--
          > >> >Michael Young
          > >> >Developer Relations Engineer
          > >> >BEA Support
          > >> >
          > >> >
          > >
          [att1.html]

Inconsistent message publishing times through weblogic JMS client

Hi,
We have a weblogic JMS application which we are deploying in a clustered weblogic enviornment. We are using distributed queues/topics with file store. We have both JMS cliient and server running on separate weblogic clusters. Most of the times it will take about 10 milli seconds to push the message into queue, but 1 in 50 messages takes about anywhere between 0.2 sec to 6 secs. Recently for three days it just took 10 msec for all the messages throught these three days and then started behaving erratically again. I am not able to really figure out why there is lot of deviation in the publishing times. When I monitor both my client and server through admin consiole, I don't see any stuck threads, heap size is normal, cpu load is normal, no problems with network. Please help me to figure out the root cause for abnormal publishing times.
Regards
Koti

Could you check if there are JVM garbage collections during some the publishing times.
In particular check if there are any full garbage collection occuring when you notice such a deviation in the publishing time.

Using WebLogic JMS Wrappers with Spring

Hi,
I was just wondering if anyone used WebLogic JMS wrappers with Spring?
I am using WebLogic configured to have Sonic as my Foreign JNDI Provider. Weblogic provide me with specific entries on the admin console to set information such as the JNDI name of the Sonic Connection Factory. If I specify this JNDI name in the Spring config, and call getConnection() then I will get back a new connection each time.
I don't want this, I want to cache the connection (as connections are expensive in Sonic). This is where the WebLogic JMS wrappers come in, they can handle the pooling for me but the only way I can see to use them is via a resource-ref. It is possible for Spring to get a handle onto these wrappers or should I use Spring's own pooling mechanism instead?
P.S. I've also asked this question on the Spring forum
Thanks for any help
Mandy

Maybe you have already tried the following:
<beans xmlns:jee="http://www.springframework.org/schema/jee" ... >
<jee:jndi-lookup id="connectionFactory" jndi-name="jms.ConnectionFactory">
<jee:environment>
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001
</jee:environment>
</jee:jndi-lookup>
</beans>
an alternative is to use the JNDI template
<beans ... >
<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
<prop key="java.naming.provider.url">t3://localhost:7001</prop>
</props>
</property>
</bean>
<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate" />
<property name="jndiName"><value>jms.ConnectionFactory</value></property>
</bean>
</beans>

Using Weblogic JMS for internal delivery channel

hi,
I want my B2B to talk to back-end application through Weblogic JMS queues. I have configured internal delivery channel for this. I am getting error message 'Max retry exceeded' in b2b_idc_transport.log
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) JMSReceiver.init() started ....
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:10:03:704: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:15:03:428: B2BStarter thread: (ERROR) Max retry exceeded, closing everything
java.lang.Exception: Max retry exceeded
     at oracle.tip.transport.basic.jms.JMSMonitor.reconnect(JMSMonitor.java:833)
     at oracle.tip.transport.basic.JMSReceiver.init(JMSReceiver.java:333)
     at oracle.tip.transport.b2b.B2BTransport.init(B2BTransport.java:379)
     at oracle.tip.adapter.b2b.transport.AppTransportInterface.initialize(AppTransportInterface.java:282)
     at oracle.tip.adapter.b2b.engine.Engine.initialize(Engine.java:512)
     at oracle.tip.adapter.b2b.init.B2BServer.initialize(B2BServer.java:280)
     at oracle.tip.adapter.b2b.init.B2BStarter.startB2B(B2BStarter.java:297)
     at oracle.tip.adapter.b2b.init.B2BStarter.run(B2BStarter.java:143)
     at java.lang.Thread.run(Thread.java:534)
I have applied latest patch 7322333.
kindly let me know what is workaround for this? also, how can do debugging of this issue in B2B.
Thanks in advance.
Regards,
Vaibhav
Edited by: vaibs on Sep 26, 2008 12:15 AM

hi Sinkar,
Thanks for reply. I have checked connectivity from b2b server to weblogic server, using java stub. Stub can connect to the Q successfully.
here is my b2b.log
2008.09.24 at 12:09:49:233: main: B2B - (DEBUG) B2B initialize
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) This is Main thread executing..
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start - context started
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG) B2BStarter - This is B2BStarter thread executing..
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG)
Maximum Heap Size = 530907136
Memory Allocated = 8323072
Free Memory = 842560
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) ExecutionContextManager initialization is done
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) User's maxCachedSessions is set to 0
2008.09.24 at 12:09:50:560: B2BStarter thread: B2B - (DEBUG) B2BStarter - Context Initialized
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Start B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Starting B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - configuration oained
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - clear global cache
2008.09.24 at 12:09:51:793: B2BStarter thread: B2B - (DEBUG) XEngine not running. So no need to clear cached objects inside XEngine.
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [0] HL7 over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [1] EDI X12 over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [2] Custom Document over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [3] EDI EDIFACT over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [4] RosettaNet over RNIF
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [5] EDI X12 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [6] Custom Document over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [7] Custom Document over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [8] EDI EDIFACT over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [9] HL7 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (NIFORMATION) Repository:print: [10] Custom Document over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [11] Custom Document over ebMS
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [12] EDI X12 over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [13] EDI EDIFACT over Internet
2008.09.24 at 12:09:51:981: B2BStarter thread: B2B - (DEBUG) Repository:constructCertSQL SELECT cert.ID, cert.CLASSTYPE FROM TIP_Certificate_ra cert, TIP_Party_ra party, TIP_DocumentExchange_ra docex WHERE cert.ID = docex.signingcredential AND cert.tradingpartner = party.ID AND party.ishosted != 'Y'
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Enter
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Envelope
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Message Header
2008.09.24 at 12:09:52:386: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Exit
2008.09.24 at 12:09:52:402: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Enter
2008.09.24 at 12:09:52:433: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Exit
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Enter
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize resetListener = true
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initdcx = true
2008.09.24 at 12:09:52:543: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize TPAProcessor
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Clear TPA Cache
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize DataContext. Pool Size 0
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Treat Response as Request = false
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Exit
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize Transport
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Initialize Transport Logger.
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Transport LogLevel = STATUS
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) Repository:getDeliveryEndPointList: Putting http://localhost
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) oracle.tip.adapter.b2b.transport.TransportInterface:initialize: Props: http://localhost port = 7777
PROTOCOL_ENDPOINT = null
2008.09.24 at 12:09:52:636: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [Wholesale_Transport_Server < http > < Wholesale >]
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize Initialize AppTransport Logger.
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize AppTransport LogLevel = WARNING
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (INFORMATION) Repository:getInternalDeliveryEndPointList: Putting jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize main Endpoint loop jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize looping through transport Endpoint: jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize add jms transport Endpoint: jms://[email protected] {Destination Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.destination_password=weblogic, Connection Factory Location=weblogic.jws.jms.QueueConnectionFactory, jms.receiver.jndi_connection_factory_location=weblogic.jws.jms.QueueConnectionFactory, isTopic=false, Message Type=bytes, jms.receiver.is_topic=false, jms.receiver.factory_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, transport_callout_waittime=30, jms.receiver.jndi_destination_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.polling_interval=10, polling_interval=10, Factory Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.jndi_destination_location=[email protected], jms.receiver.destination_username=weblogic}
2008.09.24 at 12:09:53:713: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2008.09.24 at 12:35:52:276: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
2008.09.24 at 12:35:52:884: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned off, will not listen on IP_OUT_QUEUE for messages
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
Thanks,
Vaibhav
Edited by: vaibs on Sep 28, 2008 3:20 AM

WEBLOGIC JMS performance ?

Similar Messages

Maybe you are looking for