JMS implementation in OSB

Hi,
I am beginner in OSB . I am trying to create a sample application that uses JMS queue. I went through documentation on OSB and Weblogic, however couldn't create it.
Could you pls help in creating a sample application that uses JMS queue or point me to an URL where such sample is available?
Thanks,
Vijay

Yes there are but not as straight forward as using JCA transport with AQ adapter in OSB.
JMS-JMS integration: JMSQ OC4J--->Foreign JMS Q (Weblogic)---->JMS Transport inbound.
JMS-JMS integration: AQ JMS interface --->Foreign JMS Q (Weblogic)---->JMS Transport inbound.
BPEL-OSB integration: JMSQ OC4J--->BPEL--->Invoke OSB Proxy--->Your custom logic
JMS
Normally application are designed other way around. OSB interfaces with AQ and then routes to other process/transport as required.
Endpoint A ----OSB --------Endpoint B It makes more sense to use OSB for all end points (connectivity) where it adds maximum value in routing to various end points
I'm sure you have valid reason to decide using OSB like AQ-->OC4J JMS-->OSB rather than AQ-->OSB--->Endpoint . Based on your architecture there are other integration options like JMS Bridge etc
Thanks
Manoj
Edited by: mneelapu on Dec 24, 2009 2:52 PM

Similar Messages

JMS Dequeue issue -- OSB

Hi,
We have created a JMS Queue in WLS 10.3.0 and OSB (10.3.1) process is using proxy service - JMS transport to dequeue messages.
WLS JMS Queue -->OSB Proxy --> Business Service (JCA Db adapter) to insert data into a table
IF error in db --> Invoke OSB error handler and write to a file
Case - Success
Messages are deleted from the queue
Case - Failure
Messages are not deleted from the queue. Error handler is invoked in OSB and messages are written to a file.
This is creating an issue since OSB retries and number of files are created. We have tried setting retry settings in OSB, but in vain.
Please provide inputs, this is a bit of emergency.
Regards,
AP
Edited by: ARPL on Oct 15, 2009 3:41 AM

Am also dumb...
You need to create a new proxy service (and select the message type which suits your process, anysoap any xml, wsdl, etc), on the second tab you can select the transport.
In here select jms from the listbox and for the endpoint insert "jms://yourhost:yourpost/yourconnectionfactory/yourqueue"
thats all what is needed to let your proxy service pick up the messages from the queue.
eventually you want to route this message to something else, so for that you need to decide what sort of business service you use (webservice wsdl based, or just some other jms endpoint,or file...you name it)
@@JMS implementation in OSB
OSB concepts are really hard to digest if u r SOA developer from start. Proxy Service will act as a Inbound for JMS. It still shows the "Destination type" in JMS Transport Config tab
Really Confussing....
Sushil
Edited by: Sushil Deshpande on Jan 26, 2011 2:22 AM

WS reliable messaging implementation in OSB

Hi All,
I have to implement relaible messaging through OSB service. I want to know
1. how reliable messaging can be implemented in OSB with proxy and bussiness service and how it can be tested?
2. The advantages of using WS transport to implement reliable messaging over JMS queues ?
3. How WS transport ensures guaranteed delivery?
please post your valuable ideas.
Thanks
Harini

WSRM is not fully supported in ALSB.

Oracle 8i vs 9i JMS implementation?

Hi,
We are thinking about using 9i instead of 8i.
We know that 8i is not 100% JMS compliant but the question is - is 9i?
In short, does it support the onMessage method, more than one session per connection and JNDI lookup? Oh, and do you still need to downcast to subscribe to topics?
If anyone out there knows the answers you could save us some time and effort.
Any other comments would also be welcome.
Many Thanks
Kevin.

Hi,
I was wondering what you have learned about this issue, Oracle 9i JMS implementation. My specifics are that I am trying to learn whether or not Message driven beans are supported, and if not, what the recommended method is for managing many Async message listeners to a topic. I think that 9i only supports J2EE 1.1 which would imply no MDB support.
Thanks,
Peter

Difference between EDN-DB and EDN-JMS implementation

Experts,
Looking for a difference between EDN-DB and EDN-JMS implementation. We have EDN implementation going on, where multiple source systems will be publishing business events. Events can be published using SOA Suite or JMS Bridge from AQ and MQ. In this scenario which implementation approach is suited better ?

Oracle Apps Adapter can be used for many other products other than E-Business Suite (JD Edwards E1, OTM, and others). The apps adapter was mainly used in ERP systems and was strong when you needed have added functionality other than just polling a db for a status / calling a stored procedure... It could connect out to other business services, xml gateways and so-on.
From a technical aspect / development perspective I always thought of that the Oracle Apps Adapter simplifies the development but, may is not flexible. The App Adapter's strength is the services that are difficult to integrate with (business services, xml gateway). If you need to hook in to these types of services, use the APPS adapter. (Again like it is named the "Apps Adapter" its for interacting w/ other applications to enable real-time processing / functionality.
That being said the dbAdapter can be very powerful but, like it is named is database focused (to poll some table to know when to kick off other logic and enable real-time functionality through database interaction.
Looking at the Oracle 12C Roadmap I had heard that there is more planned for the Oracle Apps Adapter moving forward, especially as Anuj said in the "Financial Apps" side of the isle at Oracle. Who knows what is real and what isn't though =]
Hope this helps!
-Luke

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
     at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
     at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
     at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
     at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:198)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

Read message synchronously from JMS queue using OSB

Hi,
Is it possible to read message from the JMS queue using OSB based on the request invocation. I know messages can be read from the queue but it will be polling based.
The requirement is to have an OSB proxy service (HTTP service ) an an interface to the client application. Client application invokes the proxy service and the proxy service need to read message from the JMS queue and provide the message as response to the client.
Let me know if there are any pointers.
Thanks
Sandeep

Hi,
I spent some time trying to do this and apart from creating custom database tables etc. I was not able to achieve this.
We wanted to use in memory JMS queues in our situation.
In the end we developed a Java Web Service which preformed the on-demand read from the queue (using a particular message selector)
This is working for us without a problem
Robert

Does the Weblogic JMS implementation use the Time-To-Live values?

          I am trying to send a message to a Queue with a time-to-live. The only way that
          I can get this to work is by going into the console, and setting a default value
          on either the Queue or the connection factory. But this is not the behavior I
          want. I would like to do this programmatically instead so it can be property
          driven and a Sys Admin can change it easily.
          I downloaded the JMS spec and saw that you are supposed to set the time to live
          when calling the MessageProducer's send message. I did this, but it doesn't work.
          Is anybody else having this problem? Does Weblogic's JMS implementation just
          ignore this value? Or do I have my Queues and other JMS components set up incorrectly?
          P.S. All of my time-to-live overrides are set to -1 in the console, so my time
          to live set in the program should be respected.


          Tom,
          I was able to track it down to a programming error. Thanks for your help.
          Dan
          Tom Barnes <[email protected]> wrote:
          >Hi Daniel,
          >
          >Yes, client-specified message expiration works. I suspect
          >a programming error. First take a look and make sure that you are
          >not making the common mistake of trying to set the value
          >directly on the message, rather than on the producer - as per
          >the JMS spec and JMS javadoc, setting this value directly
          >on message will have no effect as the producer's value
          >will always override it. If this isn't the case,
          >please post your code and I'll take a look.
          >
          >FYI Note that all management fields can be programmatically
          >set as well. Since you want programmatic administrative
          >control, this means that you have the option of
          >programmatically configuring the destination's time-to-live
          >override field if you so wish.
          >
          >Tom
          >
          >Daniel Livesay wrote:
          >
          >> I am trying to send a message to a Queue with a time-to-live. The
          >only way that
          >> I can get this to work is by going into the console, and setting a
          >default value
          >> on either the Queue or the connection factory. But this is not the
          >behavior I
          >> want. I would like to do this programmatically instead so it can be
          >property
          >> driven and a Sys Admin can change it easily.
          >>
          >> I downloaded the JMS spec and saw that you are supposed to set the
          >time to live
          >> when calling the MessageProducer's send message. I did this, but it
          >doesn't work.
          >> Is anybody else having this problem? Does Weblogic's JMS implementation
          >just
          >> ignore this value? Or do I have my Queues and other JMS components
          >set up incorrectly?
          >>
          >> P.S. All of my time-to-live overrides are set to -1 in the console,
          >so my time
          >> to live set in the program should be respected.
          >

Can anyone help me how to work with jms server in osb?

Hi,
I am new in osb. I have requirement in osb listeners.
I want to put some data in to jms server using osb in one project and then consume that data using osb in diffrent projects.
how to configure jms server to work above scenario?
how to construct business and proxy sevices?
jms protocal format?
My requirement is topic in jms server
Regards,
Raju..

Hi,
The below link will help you to create simple JMS in weblogic
https://blogs.oracle.com/soaproactive/entry/how_to_create_a_simple
How to push message and consume message
http://rangarb.wordpress.com/2012/04/18/working-with-jms-in-osb-11g/
Another example of subscription of jms
http://oraclesoaandoim.blogspot.co.uk/2012/04/oracle-service-11116-consume-jms.html
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.
Thanks,
Vijay

Regarding jms implementation that comes with reference j2ee server from sun

I have a message bean that is trying to read message off the queue, do something, and put a message on to other queue.
The problem: I am loosing a message.
I have tried both the container managed as well as bean managed transaction.
Is there any bug with the reference JMS server? I am using the SimpleQueueSender that comes with the jms tutorial from sun to send message in a persisted mode. I am running the J2EE server that comes from SUN.
I will post the code if someone is willing to take a sincere look.
Thanks
Aman

I can tell you one thing about JMS, I have websphere MQ Series, Even the product like MQ from IBM have limitation when using 2 phase commit(), it supports 2 PC only when websphere and MQ Series are installed on the same box, So i would not be surprised if there is a bug in reference JMS implementation and you are losing messages even though in transaction. Are you using distributed transaction.

License for jms implementation

Hi, I am planning to implement a light-weight JMS implementation to suit my work. I want to know whom to contact for getting a go-ahead regarding the license for specification. Could anyone from Sun team if they have seen this post respond OR anyone who knows the process to be followed.
Thanks
~Venkat

Hi v.
I do not think u need any license for the specification.

IS JMS implementation available for BMQ?

Hi,
          I have an exposure to BMQ middleware and we have been accessing this thru the C libraries and now since we are moving to java, i would like to know if there is JMS support for BMQ and if so where can i find/download the JMS implementation


Hi Dheepak,
          I think you are referring to MessageQ. There is a pure
          java client, although it is not a JMS client. I'm not sure
          how it is packaged or licensed. Contact BEA sales and they
          should be able to track it down for you. If they have trouble,
          feel free to give them my name.
          Tom, BEA
          Dheepak wrote:
          > Hi,
          > I have an exposure to BMQ middleware and we have been accessing this thru the C libraries and now since we are moving to java, i would like to know if there is JMS support for BMQ and if so where can i find/download the JMS implementation

Jms implementation

Hi;
I search :
1- a jms implementation (source code or a example) for realizing the following fonction :
When a message is posted by a client to the queue, my component extracts the trade details and sends them inside of a mail (via javamail).
- Which are the errors not to make whan one uses JMS (I use Jboss) ?
Regards

Almost every JMS example will show you how to consume messages from a queue. There a some at java.sun.com and you could find plenty more if only you weren't too lazy to use google.
Instead of using javamail use the apache commons simple mail package - it's much easier.
In your case I would worry about getting an repeating exception while sending the email which causes your JMS transaction to rollback. By default the message will be automatically redelivered so you'll be stuck in an infinitely loop of
1. read message
2. process message
3. send email <--- EXCEPTION
4. rollback
5. goto 1

JMS messaging with OSB

Hi Forum, So far I have not been able to find any useful information hence the question:
1. Is OSB an implementation of JMS?
2. To use JMS with OSB do I need to install separate JMS? If not does JMS install by itself when installing OSB?
Thanks!

JMS (Java Messaging Service) is a transport protocol (like File, FTP, email, HTTP etc.) which is supported by OSB (Oracle Service Bus - which is a service bus product used for transport protocol mediation).
Once you have installed OSB, you may use it to configure services which use JMS transport. Please refer to know more -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/jms.htm#i1051082
http://en.wikipedia.org/wiki/Java_Message_Service
Regards,
Anuj

[OSB10.3.1] err creating JMS stuff in OSB cluster from recorded WLS session

Hi all,
I've setup an OSB cluster with 2 managed servers.
From WLS console I created successfully the below JMS resources:
1. new file store, name and directory: MyFileStore_m01, target: bnk01osbm01 migratable
2. new file store, name and directory: MyFileStore_m02, target: bnk01osbm02 migratable
3. new jms server, name: MyJMSServer_m01, persistent store: MyFileStore_m01, target: bnk01osbm01 migratable
4. new jms server, name: MyJMSServer_m02, persistent store: MyFileStore_m02, target: bnk01osbm02 migratable
5. new jms module, name: MyJMSSystemModule, targets: cluster bnk01osbcluster + all servers in the cluster
6. new xa conn factory, name: MyXAConnectionFactory, jndi name: MyXAConnectionFactory
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ XA Connection Factory Enabled: true
7. new Distributed Queue, name: MyDistributedQueue1, jndi name: MyDistributedQueue1, load balancing policy: round-robin
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ allocate members uniformly: true
and I recorded that into the included recorded_by_wls.py. As said no error has been raised.
Then I removed the above JMS resources and I executed the recorded_by_wls.py from command line getting the error that I reported at the end of the email.
I changed slightly the original py produced by WLS by adding only the below first 5 lines:
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
I included also the recorded_by_wls.py source at the end of the email.
For information I reported also what I saw on WLS console when I created manually my JMS resources.
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?
Any help will be very appreciate.
Thanks in advance.
Regards
ferp
Error:
java weblogic.WLST recorded_by_wls.py Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting the script ...
Connecting to t3://wasdv1r3n1.dev.b-source.net:7031 with userid weblogic ...
Successfully connected to Admin Server 'bnk01osbadm' that belongs to domain 'bnk01osb'.
Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to edit tree. This is a writable tree with
DomainMBean as the root. To make changes you will need to start an edit session via startEdit().
For more help, use help(edit)
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Activation completed
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
This Exception occurred at Mon Sep 07 15:31:33 CEST 2009.
weblogic.application.ModuleException: ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:618)
at weblogic.jms.module.ModuleCoordinator.prepareUpdate(ModuleCoordinator.java:487)
at weblogic.application.internal.flow.DeploymentCallbackFlow$5.next(DeploymentCallbackFlow.java:514)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepareUpdate(DeploymentCallbackFlow.java:280)
at weblogic.application.internal.BaseDeployment$PrepareUpdateStateChange.next(BaseDeployment.java:679)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepareUpdate(BaseDeployment.java:444)
at weblogic.application.internal.SingleModuleDeployment.prepareUpdate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepareUpdate(DeploymentStateChecker.java:221)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepareUpdate(AppContainerInvoker.java:149)
at weblogic.deploy.internal.targetserver.operations.DynamicUpdateOperation.doPrepare(DynamicUpdateOperation.java:130)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045050]A destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has a jms-create-destination-identifier of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1. However, another destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named wlsbJMSServer_auto_2.
at weblogic.jms.backend.BackEnd.addDestination(BackEnd.java:1527)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:195)
at weblogic.jms.backend.udd.UDDEntity.prepare(UDDEntity.java:444)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:936)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:841)
at weblogic.jms.module.JMSModule.access$1500(JMSModule.java:87)
at weblogic.jms.module.JMSModule$JMSModuleListener.prepareUpdate(JMSModule.java:1485)
at weblogic.descriptor.internal.DescriptorImpl$Update.prepare(DescriptorImpl.java:481)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdateDiff(DescriptorImpl.java:195)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdate(DescriptorImpl.java:174)
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:614)
Problem invoking WLST - Traceback (innermost last):
File "/products/software/tmp/recorded_by_wls.py", line 92, in ?
File "<iostream>", line 364, in activate
WLSTException: Error occured while performing activate : Error while Activating changes.ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2 Use dumpStack() to view the full stacktrace
recorded_by_wls.py source
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m01')
cd('/FileStores/MyFileStore_m01')
cmo.setDirectory('MyFileStore_m01')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m02')
cd('/FileStores/MyFileStore_m02')
cmo.setDirectory('MyFileStore_m02')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m01')
cd('/Deployments/MyJMSServer_m01')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m01'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m02')
cd('/Deployments/MyJMSServer_m02')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m02'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSSystemResource('MyJMSSystemModule')
cd('/SystemResources/MyJMSSystemModule')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbcluster,Type=Cluster')], ObjectName))
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createConnectionFactory('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setJNDIName('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/SecurityParams/MyXAConnectionFactory')
cmo.setAttachJMSXUserId(false)
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/TransactionParams/MyXAConnectionFactory')
cmo.setTransactionTimeout(3600)
cmo.setXAConnectionFactoryEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createUniformDistributedQueue('MyDistributedQueue1')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/UniformDistributedQueues/MyDistributedQueue1')
cmo.setJNDIName('MyDistributedQueue1')
cmo.setLoadBalancingPolicy('Round-Robin')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
-- source end --
ON WLS console
Name Type Target
MyFileStore_m01 FileStore bnk01osbm01 (migratable)
MyFileStore_m02 FileStore bnk01osbm02 (migratable)
FileStore_auto_1 FileStore bnk01osbm01
FileStore_auto_2 FileStore bnk01osbm02
WseeFileStore_auto_1 FileStore bnk01osbm01
WseeFileStore_auto_2 FileStore bnk01osbm02
Name Persistent Store Target Current Server
MyJMSServer_m01 MyFileStore_m01 bnk01osbm01 (migratable) bnk01osbm01
MyJMSServer_m02 MyFileStore_m02 bnk01osbm02 (migratable) bnk01osbm02
wlsbJMSServer_auto_1 FileStore_auto_1 bnk01osbm01 bnk01osbm01
wlsbJMSServer_auto_2 FileStore_auto_2 bnk01osbm02 bnk01osbm02
WseeJmsServer_auto_1 Wsee FileStore_auto_1 bnk01osbm01 bnk01osbm01
WseeJmsServer_auto_2 Wsee FileStore_auto_2 bnk01osbm02 bnk01osbm02
Name Type
MyJMSSystemModule System
configwiz-jms System
jmsResources System
WseeJmsModule System
Name Type JNDI Name Subdeployment Targets
MyDistributedQueue1 Uniform Distributed Queue MyDistributedQueue1 Default Targetting bnk01osbcluster
MyXAConnectionFactory Connection Factory MyXAConnectionFactory Default Targetting bnk01osbcluster

Hi Ferp,
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?It should not fail. Each and every successfully (activation has been done without reporting an error/conflict) recorded session will execute on other servers successfully until a unique name constraint gets violated.
In your case this violation has happened. Your script is trying to create a distributed destination "MyDistributedQueue1" under module "MyJMSSystemModule", targetted to JMS Server "wlsbJMSServer_auto_2" but a Distributed Queue with same JNDI name already exists there.
Please check.
Regards,
Anuj

JMS implementation in OSB

Similar Messages

Maybe you are looking for