OSB queuing

Dear OTN,
Recently I've been having a discussion with our architect regarding queueing in OSB.
Our main system is using Tuxedo as an adapter to a Legacy Service.
The service is rather simple and endpoint communication protocol is telnet.
The problem here is that the service is not as efficient as it should and we need to queue messages so we won't lose messages.
So far I haven't fount anything about it on the web/documentation, but my question is if there is any help on OSB side for such task - any java packages etc.?
Of course throttling is not the right solution here.
Regards,
P.

You can use weblogic JMS for intermediate queuing.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/intro.html
Thanks.

Similar Messages

OSB publish action and error queue

Hello there,
where in case of poisened messages, the "publish" action, routes the messages.
I have one proxy which, along its pipeline, publish a message to another proxy and then carry on. Well, I guess this is done some how with internal OSB queues, where in case of error these messages are moved? Is there anyway to specify a specific destination?
Thanks in advance

If there is an error in your proxy service and you want push the messages to the queue you have to handle it manually through error handler. In case of publish if you want to handle the messages you have use routing options and change the quality of service and then in the error handler publish the message to the required queue.
Edited by: 988445 on Mar 18, 2013 6:20 PM

Synchronous message handling between OSB and MQ

Hi,
I have a requirement to have a PS in OSB that gets some XML data from another application.
The PS implementation has to be synchronous.
The interface is like
External Application<->OSB PS<->MQ<->OSB <-> External Application
Can anyone help me with the request-reply implementation(i.e. synchronous call handling) between OSB and MQ.
Required functionality :
OSB will get XML data from the external application,will do the data transformation to make it compatible with MQ interface and will then send data to MQ and will wait for the reply from MQ that it then sends back to the external application after transformation.
Queries:
How to correlate two messages i.e. request msg to mq and reply msg from mq in OSB?
What kind of Proxy Service implementation is required to have such functionality?
If someone can help me with similar kind of implementation,it will be of great help to me.
Thanks in advance

OSB support this pattern out of the box . You can implement the MessageID pattern as specified in this link:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
When you configure the business service to use MessageID as the correlation pattern, the following happens under the hood:
1. Business service sends request to the MQ request queue. The MQ JMS provider sets the message ID on the message and this is returned to the bs. The business service also sets the reply queue details in the JMSReplyTo Header in the request.
2. The business service then waits for a response message which has a correlationID equal to the messageID in the request message.
3. The system which processes the request from the MQ should set the correlation ID of the response to the same value as the Message ID in the request.
4. The business service process the reply if it is received before the timeout interval. No need to purge the queues for message arriving out after timeout since OSB does this automatically for you.
A point to note here is that if you deploy this in a cluster , you need to create 'N' local MQ queues for reply, where N is same as the number of managed servers in the cluster. Else you could lose replies in a scenario where the reply for a request sent by man server 'X" is processed by man server "Y". The request-response correlation tables are maintained internally on man server memory. Since Y had no clue of the requests sent in X it would just discard the reply received.
So create dedicate queues for each man server and specify them in the business service definition.
Another key thing for this to work would be to get right the MQ setup between the queue manager in OSB domain and the remote system which process the MQ requests. A simple setup would be for you to create all reply queues as local queues under your OSB queue manager and create only a transmission queue with the same name as your OSB queue manager in the remote system. You need to ask the remote system to do the MQOpen with the ReplyToQueue and ReplyToQM names for queue and queue manager names. This will put the replies to the transmission queue to your QM and through it can reach the right reply queue.
Edited by: atheek1 on Mar 29, 2010 7:50 AM

Workflows with OSB

Hi Everyone,
I am a newbie to OSB.
Currently I am working on a POC to see if Oracle Apps Workflows can post messages to OSB queue. From then on, the messages should be read by the Java client.
Is it a possible scenario? I have gone through a lot of posts and discussions but could not find a suitable scenario. Can you please guide me with this? Thanks!
Regards
Smitha

Hey -
Sorry, I'm using 6.1.1 as well. For my packaging specs, I have two workflows, Printed and Structural. For Printed, BU = Global OR Consumer OR Pet, and Packaging Item Type = Printed (and structural, Packaging Item Type = Structural). I have something similar for material.
I agree - it should work like yours has. However, even if my Packaging Spec has BU = Global (or consumer, or pet) and Item Type = Structural, it still defaults to its previous workflow and does not show the Structural Workflow as an option.
Could there be something going on at the server level? I'm wracking my brain but I'm pretty sure the workflow itself is configured correctly, and unless I'm using Resolve workflow incorrectly, I don't really understand what is happening.
Appreciate any and all insights!

OSB JMS Proxy XA Transaction Rollback not occuring to queue

Hi All
We are dequeuing a message from JMS queue via an XA connection factory and then calling a web service. If any error occurs in the web service we catch the error handler, log and notify it and want to send this message back to the queue for retrial (The retry settings are defined at the Queue Level from weblogic console).
Problem is rollback is not occurring, we have tried the below:
1) There is no OSB reply with either success or failure in the error handler (This should have done the trick)
2) We have also tried addiing an explicit Raise Error (Uncaught Error) to roll the message back, but its not working.
This rollback is not occurring because JMS Resource is XA and web service call is NON XA, hence the entire message flow becomes NON XA. Is this understanding correct?
How can we fix this? Please help

Hi atheek1
Thanks for the reply, it worked. Before I mark this question as answered, pls. answer the below queries (Thanks a lot!)
1) Well, i just ticked transaction required and same transaction for response and it started working. I did not add routing options like you mentioned to QOS Exactly Once. Its working without it fine. So, my questions is what is the use of adding this QOS to exactly once. Is it mandatory?
2) I have a couple of OSB services in which rollback is working automatically (XA JMS to JCA FTP Adapter) and (XA JMS to JCA DB adapter XA data source), here rollback works automatically. I dont have to tick transaction required. So my question is, when an XA based connection factory picks a message from the queue, a transaction is started at the container level. So why tick transaction required at the message flow level, when the weblogic has already initiated a transaction. Since you said that HTTP transport commits a transaction even if 500 or 404 occurs, it makes sense to tick is transaction required and same transaction for response in OSB proxy service. But the remaining scenarios work without these options. Hence will it be wise to say that these settings are only required for HTTP transport coz of the way it behaves (commits 404 and 500).
Thanks

Issue in OSB publishing message to openJMS Queue

I am trying to post a message from OSB to openJMS Queue. I am able to post message to openJMSQueue using Java API.
I have created a Foreign Server and then a foreign connection factory.
I am able to see the connection factory in the JNDI Tree as below.
Binding Name:localConnectionFactory
Class:org.exolab.jms.client.JmsConnectionFactory
Hash Code:18168258
toString Results:org.exolab.jms.client.JmsConnectionFactory@11539c2I have used the below URL in business service..
jms://localhost:17000/localConnectionFactory/openJMSQueueBut i am getting error as :
<Aug 22, 2012 11:28:19 AM IST> <Warning> <WliSbTransports> <BEA-381508> <Failed to check whether connection factory localConnectionFactory supports XA. Will assume it does not: javax.naming.NoInitialC
ontextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory]
javax.naming.NoInitialContextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFacto
ry]
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
        at javax.naming.InitialContext.init(InitialContext.java:223)
        at javax.naming.InitialContext.<init>(InitialContext.java:197)
        at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:190)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
        Truncated. see log file for complete stacktrace
>
<Aug 22, 2012 11:28:19 AM IST> <Warning> <JMSPool> <BEA-169807> <There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_1449855884 from within an EJB or
a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory localConnectionFactory failed: javax.nami
ng.NoInitialContextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory]>I have placed all the JARS of openJMS in the lib directory. The Jars are :
castor-0.9.5.jar
concurrent-1.3.4.jar
openjms-0.7.7-beta-1.jar
openjms-common-0.7.7-beta-1.jar
openjms-net-0.7.7-beta-1.jar
openjms-tools-0.7.7-beta-1.jar
spice-jndikit-1.2.jarAny help on this would be much appreciated. My first try on foreign JMS provider connection.
Regards
Sesha

I think you have to add the jars on the CLASSPATH in setDomainEnv.sh(cmd) file...
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893

Messages are not moving to Error Queue in OSB if Error is Raised

Hi All,
My OSB process is as below.
Queue1-->OSB-->Queue2.
OSB Proxy is listening to the Queue1.When messages comes to Queue1 Proxy will pick the message and after applying the business logic it will put the message to Queue2.
If OSB is not able to deliver the message succesfully to Queue2 then it should retry for 2 times.If retry exhausted then the message should move to the error Queue.
I have configured Queue 1 with delivery failure paramaters redelivery limit and redelivery delay.Also the Connection factory is XA enabled.Even if any error happens (i am not using reply activity in the error handler) its retrying infinitely and messages are not coming to the error Queue.If i use reply activity its not retrying its failing at first time and the message is moved out of the main Queue1.
Can any one please help me on this?
Thanks.
Edited by: 892479 on Dec 21, 2011 6:31 AM

Since the messages are getting retried, it means that messages are getting rolled back to Queue1 when any errors happen. So transactional behavior is configured correctly.
Now the problem yu face is that the messages are not moving to error queue.
Make sure that you have configured following in the delivery failure tab of the queue>
Redelivery Delay Override - delay in miliseconds between retries
Redelivery Limit - number of retries
Expiration Policy - Redirect
Error Destination - Choose the error queue here
After that make sure that the Server is restarted, even though a server restart sign is not mentioned on the config page, some of these settings might not take effect without a restart.

Expiration of messages in Queue + OSB

I am working on a prototype and I have the following scenario :
I have on ALSB (OSB) a JMS based Proxy Service that uses a queue in order to get the messages.
On the queue are put SOAP messages that are secured on message level.
There is a digest expiration on Domain Level that is set to 300 ms by default.
This means that the message once is created and reach the proxy it has to be in this 300 ms time frame.
==> Queue ==>Security Check on JMS Proxy Service ==> Message Flow
Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB (OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception (various reasons that are not important now) the transaction is rolled back and the message "is put back on the queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will expire until the redelivery (ususaly minutes) will be done.
So why a messages that already passed security is checked again on retry ? Can't this be avoided somehow ?
Thank you.

Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not >be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB >(OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....I think message expiration can be setup on a proxy level by setting up a WS Security policy on the WSDL rather than at the domain level.
<wsp:Policy wsu:Id="MessageAge" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401->wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
><wssp:MessageAge Age="300" xmlns:wssp="http://www.bea.com/wls90/security/policy"/>
></wsp:Policy>
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception >(various reasons that are not important now) the transaction is rolled back and the message "is put back on the >queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will >expire until the redelivery (ususaly minutes) will be doneSimple solution would be to configure the JMS Proxy where you have the WS-Security check to be a pass through and pass the message to another jms queue which can be listened to by JMS proxy which does validation and remaining processing.

Expiration of messages in Queue + OSB (part 2)

I am working on a prototype and I have the following scenario :
I have on ALSB (OSB) a JMS based Proxy Service that uses a queue in order to get the messages.
On the queue are put SOAP messages that are secured on message level.
There is a digest expiration on Domain Level that is set to 300 ms by default.
This means that the message once is created and reach the proxy it has to be in this 300 ms time frame.
==> Queue ==>Security Check on JMS Proxy Service ==> Message Flow
Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB (OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception (various reasons that are not important now) the transaction is rolled back and the message "is put back on the queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will expire until the redelivery (ususaly minutes) will be done.
So why a messages that already passed security is checked again on retry ? Can't this be avoided somehow ?
Thank you.

These question look like they are very specific to OSB, rather than basic JMS -- which has no concept of message level encryption -- I suggest reposting to the OSB newsgroup instead.

OSB 10.3 JMS queue problem: JMSCorrelationID is null

Hi everybody,
I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
This is urgent, please help me as soon as possible as possible.
Thanks in advance.
Joy

Sovled it..
OSB 10.3 JMS queue problem: JMSCorrelationID is null

How to create a single business service against multiple Queues in OSB

Can I create one business servcie against multiple jms queues.
and based on content routing i want to pass the queues' JNDIname
for example
jms://localhost:7001/jms.cf/$variable_queueName
and in runtime i want to provide the queue name for variable "variable_queueName" in the above endpoint URI.
is it possible?.
Thanks,
Narasimha.
Edited by: user13154768 on Jun 2, 2010 5:03 AM

You can use routing options action to achieve this.
see Dynamic Service Invocation sample under OSB code samples :
http://www.oracle.com/technology/sample_code/products/osb/index.html
Dynamic Service Invocation Sample:
http://www.oracle.com/technology/sample_code/products/osb/samples/DYNAMIC-DISPATCH.zip

Issue in Synchronous OSB using Jms Queues in OSB11g

Hi,
I am working on building a synchronous OSB using the following steps.
1)     Creating the Synchronous OSB Proxy Service which routes the message to the business service which in turn places a message in the Queue(inqueue) by populating the JMSCorrelationId and waits for the response message to consume from another queue.
2)     A Composite(SOA) will consume the message from this Queue
3)     It will do necessary transformation and Places it in another Queue (Say Response Queue).
4)     OSB Business service waiting in Step 1 will receive the response from this response Queue.
I used a sample Wsdl which has both request and response message types.
I observed that the correlation ID is maintained properly from inqueue to response queue. But the message is not getting picked up by OSB from the response Queue
Twist: It is working absolutely fine in OSB 10g but it is not working in OSB 11g.
I tried using Messaging service as well as using the sample WSDL i.e keepiing the soap message in the queue. Both the cases are working absolutely fine OSB 10g but not in OSB 11g.
Can anyone faced a similar issue or any pointers will be great help in this regard.
Regards,
Ashok

To debug this further can you check if the response Q has any active consumers. ? When you use response by correlation ID business service, OSB actually creates MDB's with message selectors under the hood.
This is a sample of the ejb-jar.xml of the MDB created for a business service with response by Correlation ID pattern.
<?xml version='1.0' encoding='UTF-8'?>
<jav:ejb-jar xmlns:jav="http://java.sun.com/xml/ns/javaee">
<jav:display-name>BEA ALSB JMS Outbound Sync-Async Endpoint</jav:display-name>
<jav:enterprise-beans>
<jav:message-driven>
<jav:ejb-name>ResponseEJB-6577847719916437493-3893eeb7.1287d30ba4f.-7fe1</jav:ejb-name>
<jav:ejb-class>com.bea.wli.sb.transports.jms.JmsAsyncResponseMDB</jav:ejb-class>
<jav:transaction-type>Container</jav:transaction-type>
<jav:message-destination-type>javax.jms.Queue</jav:message-destination-type>
<jav:activation-config>
*<jav:activation-config-property>*
*<jav:activation-config-property-name>messageSelector</jav:activation-config-property-name>*
*<jav:activation-config-property-value>JMSCorrelationID LIKE 'ID:424541534594cf52%'</jav:activation-config-property-value>*
*</jav:activation-config-property>*
</jav:activation-config>
<jav:env-entry>
<jav:env-entry-name>service-ref</jav:env-entry-name>
<jav:env-entry-type>java.lang.String</jav:env-entry-type>
<jav:env-entry-value>BusinessService$Test$RequestQ</jav:env-entry-value>
</jav:env-entry>
As you can see the message selector is based on JMSCorrelationID LIKE 'ID:424541534594cf52%'. This means the business service will pick only those messages which has its correlation ID starting with ID:424541534594cf52.
You can see the message selector for your MDB from admin console --> deployments.
Check and confirm if the correlation ID created in the request also starts with this value and the same is send back from the server. Also try deleting and recreating the business service or rename the business service which will create a new MDB under the hood and check the above.

OSB: Configuring business service for JMS Queue

Hi,
I want to produce messages into a JMS queue from OSB proxy service. I have created business service for the JMS queue. I also want to return Status code=200, Status Messgae=Success if the message is successfully inserted into the Queue. Kindly let me know how to do this.
I tried using Service Callout to call the business service but it is not allowing me to use it because my business service is a one-way operation. So, i tried with Publish activity but my doubt is how and where to configure request payload for the publish activity. I could not find any.
And how do i know if the message is successfully inserted so that i can send the Status=200 back to the calling proxy service.
Kindly help in this regard.
Thanks in advance.

As suggested, use QoS=ExactlyOnce as RoutingOption within the Publish to business service. If there was any error it will send the flow to error handler where you can do a reply with failure to return HTTP status code=500 to the caller of the proxy service.
If you do a reply with success the caller will receive HTTP status code=200

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

OSB 11g: Business Service not getting reply back from distributed queue

Here is the scenario:
OSB Domain A has a Business service that does a JMS send to a distributed JMS queue hosted on another WLS domain.
It expects a response from a distributed queue sitting on this same remote WLS domain.
The remote WLS domain is configured as a Foreign JNDI Provider in the OSB Domain with the request and response queues defined. Testing this business service, we see that messages are being posted to the remote request queue fine, and that the message are being picked up and processed. The response was sent to the response queue, but the message just sits there, the OSB business service did not pick it up. I can see 16 active Consumers on the response queue, presumably from the OSB business service?
Using CorrelationID.
URI for request/response queues are using the locally defined JNDI name for the queues and connection factories from the Foreign JNDI Provider definition:
- URI for request queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForRequestQueue]
- URI for response queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForResponseQueue]
Completely stumped at the moment...anybody has any ideas?
Thanks,
Melvin

Hi,
I am also facing the similar kind of issue as below. After placing the message in to request Queue, I need that message Id as response to that Business service. Please provide the solution for the below issue. Thanks in advance.
Thanks,
bharath.

OSB queuing

Similar Messages

Maybe you are looking for