ALSB Proxy services deployment management

Hi all,
I have a problem now.
We have many proxies services running in a ALSB domain.
Some of them need to transfer hundreds MB XML data very frequently. They are listening to a JMS queue. And when they are working, they will cause the whole system too heavy-loaded to work.
So we want to add a new server into this ALSB domain to run the data transfer proxy services.
Because the data transfer proxy services have too much dependencies to separate, our thought is to deploy the all the projects to the new server and control the data transfer proxies only run on the new server.
Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?
Thanks in advance.
Garriot Zhang

Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?No. When a proxy is deployed it gets deployed to all servers. OSB does not give explicit control on which server a proxy should be deployed.
Manoj

Similar Messages

Remove SOAP Header Element from ALSB Proxy Service Response

I've got a client of one of my ALSB Proxy services that needs the SOAP header element removed from the response. I'm struggling to find a way to do that with a WSDL-based proxy service. Do I need to change my service to an Any XML Service or is there an easier way?

At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
My client is expecting a soap response and the backend gives back only the XML Response
Thanks in advance!!
~Swagat

ALSB Proxy Service

Hi all,
We are not able to invoke ALSB proxy service from BPEL ? Please help me on this issue.
Thanks & Regards,
Bharathy.

Can u make me clear , how to use business service in OSB pipeline ?http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/concepts/wwimages/msgflow_layers.gif
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/concepts/wwimages/msgprocess.gif
1)Client ----->2)Transport End Point -------->3)Pipeline---4) ServiceCallout/Publish/Route-----5) BS--------->6)Transport End Point----7) Service
2&3 combined is Proxy definition; BS is abstraction of the actual end-point outside of OSB. BS cannot be directly invoked. BS can only be invoked from the pipeline.
How to invoke this proxy service from BPEL ? Depending on your use-case. Simplest would be to use http transport. Get some WSDL, create proxy using the wsdl. From this proxy create get an effective WSDL
http://HOSTNAME:7001/websvctestproject/cmplx_proxy_svc?wsdl. Use this WSDL to invoke the proxy. You can also use BPEL transport or any other transport JMS, ftp etc

ALSB Proxy Service error calling Business service

I have an external webservice on Weblogic 8.1 SP5, and I configured Business Service in ALSB 2.6, that is able to invoke the external webservice. But When I create Proxy Service based on the existing Business service and try to invoke the proxy service I get "no SOAP Action Header" error in WebLogic 8.1 SP5 External webservice.
AxisFault
faultCode: {http://xml.apache.org/axis/}Client.NoSOAPAction
faultSubcode:
faultString: no SOAPAction header!
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:no SOAPAction header!
at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
{http://xml.apache.org/axis/}hostname:ossinv1d
no SOAPAction header!
at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Also I get
com.bea.wli.sb.pipeline.PipelineException in the ALSB.
Is it a known issue ?

The back end service basically complains the SOAPAction http header was not included in the request. Typically this header is added automatically by ALSB if the proxy is of type SOAP and the wsdl contain the SOAPAction value for the operation invoked.
Alternatively you can force the SOAPAction header to be set to the correct value by adding a transport header action in the request part of the routing node.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Proxy Service Deployment in OSB

Hi
I Have a requirement where i wnat to deploy same Proxy services with deferent versions. i dont wnat this to be reflected in my service name. so what i am doing is
creating deferent folders like v1, v2 and deploying the same service in bothe thse folders having endpoint URI deference in v1, v2.
i am bit curious to know if there is any impact to run time proxy instances as bothe of them are same. i just want to confirm before hand that there are no conflicts in run time behaviour of Proxy service.
any sugestions and answeres well appriciated.
thanks in advance
mr

Hi mr,
I don't think you'll be able to do this in the same OSB instance, although I may be mistaken. If both proxy services have the same name, then OSB will try to export both of them with the same name and there won't be any way to distinguish between them. Is the interface the same between the versions? What do you expect the behavior to be, i.e., which service will get called when Tuxedo calls the service?
Regards,
Todd Little
Oracle Tuxedo Chief Architect

OSB Proxy Service deployed in cluster environment FTP issue

Hi,
I have a OSB 11g proxy service based on a FTP JCA adapter. Here are the JCA settings:
<connection-factory location="JNDI_FILE_TOKEN" UIincludeWildcard="FILENAME_TOKEN"/>
<endpoint-activation portType="Get_ptt" operation="Get">
    <activation-spec className="oracle.tip.adapter.ftp.inbound.FTPActivationSpec">
      <property name="DeleteFile" value="true"/>
      <property name="MinimumAge" value="0"/>
      <property name="PhysicalDirectory" value="FOLDER_TOKEN"/>
      <property name="Recursive" value="false"/>
      <property name="PollingFrequency" value="30"/>
      <property name="FileType" value="ascii"/>
      <property name="IncludeFiles" value="FILENAME_TOKEN"/>
    </activation-spec>
</endpoint-activation>
When I deploy this proxy in a cluster (having 2 osb nodes) and place the very first file on FTP server. Both nodes pick the file simultaneously. But after this when I place files on FTP server only one node is picking file. Could you kindly tell where is the issue ?
Thanks and Regards

Hi Mani,
Do check the configuration of ProxyService-2 that it is enabled or not.
Do check the input payload of it, that ProxyService-1 is passing the correct payload to ProxyService-2.
Redeploy the ProxyService-2
There is some issue in your proxyService-2.
Regards,
Richa

Where is the Proxy Service deployed?

Hi
This is about the internals of the service bus.
I want to see the deployment unit that matches the Proxy I have created.
Where is it?
Where in the CONSOLE (not the sbconsole) can i see it deployed?
kind regards
kambiz

Proxy services except of jms transport are not deployed as standard j2ee deployment units - (ear, war, rar etc). Instead these deployment units are xml config files which will be understood only by the osb product j2ee applications. You will not be able separate individual proxy services from this.
Proxy services with jms transport are deployed as MDB's under the hood and you will be able to see these deployments under wls console --> Deployments with random names.

How to invoke ALSB proxy service externaly

Hello,
I.m trying to understand the ALSB and stumble across an issue and hope one of you guys (from BEA) can help out?
I've created the services from the Mortgage services tutorial successfully and now I'm trying to invoke the proxy services externally. By externally I mean as a partner link from within Oracle BPEL. So far this does not work. The error message states a missing protocol in the service URL. I checked this and it is true: the wsdl of the proxy service contains only a relative path (/loan/gateway1), so the protocol and server name and port are missing. Further, I tried to change the URI of the proxy service, but ALSB does only allow a relative URI.
My question is: what am I missing so the proxy service can be invoked externally?
I am on the right solution path to invoke a proxy service instead of a business service, right!?
Thank in advance.
Regards,
Harm Verschuren

I tracked down the problem. The proxy service and the business service it routes to use rpc encoded. The RPC encoded message comes to the proxy service from BPEL which transmits it without modification to the business service. The WLS web service that impements the business service is unable to decode the message persumably because it did not like the way BPEL encoded the message. Below is the message part that BPEL sent: All the xsitype attributes are part of RPC encoding.If you use the alsb test console to pass this message directly to the business service, you will see the decoding error thrown by wls.
<loanRequest xmlns:pns0="java:normal.client"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns0="http://example.org"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<pns0:Name xsi:type="xsd:string">Joe</pns0:Name>
<pns0:SSN xsi:type="xsd:string">123456789</pns0:SSN>
<pns0:Rate xsi:type="xsd:double">3</pns0:Rate>
<pns0:Amount xsi:type="xsd:long">50000</pns0:Amount>
<pns0:NumOfYear xsi:type="xsd:int">20</pns0:NumOfYear>
<pns0:Notes xsi:type="xsd:string">test</pns0:Notes>
</loanRequest>

How to call a ALSB Proxy Service and don't wait for his response. Publish M

Hi,
I have a Proxy Service called PS1 that will invoke and another Proxy service Called PS_ProcessingNode that invokes 10 differents webservices during the orchestration and takes about 2 minuts.
I would like that if invoke PS1 that will invokes PS_ProcessingNode (asyncronously) and immediatly PS1 will return "OK" (don't wait for the response of PS_ProcessingNode) .
For simulate this scenario I am testing with:
- PS_Processing is a WSDL without response that has a JavaCallout with a Sleeper of 10 seconds.
- PS invokes with "Publish action" to PS_ProcessingNode but is waiting for PS_Processsing finish. I don't want this beahivour.
How I can do it for PS doesn't wait for the response of the PS_ProcessingNode?
Thanks.

- PS invokes with "Publish action" to PS_ProcessingNode but is waiting for PS_Processsing finish. I don't want this behavior.
I'm glad you have a solution using JMS. But still Publish action should not wait for response. If you are seeing that behavior, you can contact Support with an SR to get it fixed.
Manoj

JMS Distributed Destinations as proxy service endpoints

We have a cluster of 2 ALSB servers with a proxy service deployed
listening on a JMS queue which is a distributed destination (DD) on a
WLS 8.1 system.
The JMS DD is spread across 4 JMS servers and 4 JVM's.
When ALSB starts up - we only get consumers on 2 of the 4 DD members,
which makes sense as a JMS proxy service is essentially an MDB, and this
is normal MDB/distributed destination behaviour - it will bind to the
queue member where it first makes the connection to the JVM.
How do I make sure my messages are consumed from all 4 DD queue members?
There is a JMS option to forward messages to queues with consumers if no
consumers exist - is that the way to do it?
Someone must have come across this before and I'd be grateful for any
advice.
Also - how do you reduce the consumers on the JMS queue - seems to
default to 16. Perhaps you don't.
Thanks,
Pete

Meghan Pietila wrote:
Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
http://forums.bea.com/thread.jspa?threadID=570001317
I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
MDB, and if you deploy an MDB in the same way, it will only bind to a
single destination, so it's actually behaving as I would expect.
The forward delay on the queue probably won't be an issue for us, as
we're not talking about high volumes and large messages, but for some
sites there will be alot of moving around queues, access jms filestore
etc which you could do without.
I reckon the trick is (as Tom mentioned) to bind to individual
distributed queue members from the proxy service somehow.
I'll let you know what I find out.
Pete

Extracting MIME attachment from email using OSB proxy service - email transport

Hi,
I'm reading email messages(multipart/mixed) with attachments(pdf, zip, xml and csv) from MS Exchange Server 2010 using OSB proxy service email transport.I need to save the attachments to a local folder and process one of the attachments, an XML file. Below is the proxy service config.
Proxy Service Configuration (Test1/Proxy Services/GetEmail)
Actions:
General Configuration
Service Type   Messaging Service
Message Type Configuration
Request Message Type
Text
Response Message Type
None
Transport Configuration
Protocol   email
Endpoint URI   mailfrom:mailserver.net:143
Get All Headers   No
Headers
EMAIL Transport Configuration
Email Protocol   imap
Service Account   Test1/Proxy Services/email_acc
Managed Server   WLS_OSB1
Polling Interval   30
Read Limit   2
Pass By Reference   false
Pass Attachments By Reference   false
Post Read Action   move
IMAP Move Folder   processed
Attachments   archive
Download Directory   \\soasup-stor01\Vacancy\test\download
Archive Directory   \\soasup-stor01\Vacancy\test\archive
Error Directory   \\soasup-stor01\Vacancy\test\error
Request Encoding   iso-8859-1
Message Handling Configuration
Transaction Required   Disabled
Same Transaction For Response   Disabled
Content Streaming   Disabled
The polling is working fine. I've encoded the attachment variable to Base64 using a java callout.$attachments/ctx:attachment/ctx:body/ctx:binary-content has been passed as the byte[] input to the java method and the response is captured in $encodedAttachment. I've created a SaveFile BS(file type) with Request Message Type = Binary and Response Message Type = None. I've tried replacing the node ./ctx:binary-content in body variable with encodedAttachment in the request action of the Publish action to call the BS. One file is getting created with contents of the entire email, MIME headers and boundary parts along with the base64 encoded attachments.
<Contents from the created file>
MIME-Version: 1.0
Content-Type: multipart/related; boundary=MIME_Boundary;
type="binary/octet-stream"
--MIME_Boundary
Content-Type: binary/octet-stream
Content-Transfer-Encoding: 8bit
Thanks & Regards,
Samyajit Talukdar
: [email protected]
-----Original Message-----
From: Samyajit Talukdar
Sent: 10 April 2015 14:11
To: MS MLRP Returns
Subject: FW: 22222
Thanks & Regards,
Samyajit Talukdar
: [email protected]
--MIME_Boundary
Content-Type: application/vnd.ms-excel; name="soainfra_v$session.xls"
Content-Transfer-Encoding: base64
Content-Description: soainfra_v$session.xls
Content-Disposition: attachment; filename="soainfra_v$session.xls";
size=25618; creation-date="Thu, 27 Nov 2014 09:56:35 GMT";
modification-date="Fri, 10 Apr 2015 09:28:23 GMT"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAA
EAAAJgAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////////////
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA=
--MIME_Boundary--
If I put a delete action in the request to Publish action for SaveFile BS to delete the $attachments, the created file contains only the email body part and the attachment boundary part is missing.
I've uploaded the OSB log with full trace enabled.
How can I pass the encodedAttachment to the BS for saving the files?
Would iterating through the $aatachment/ctx:attachment give me the individual attachments for saving and processing, as there are separate binary-content refs in them?
Any help to achieve my requirement is highly appreciated.
Thanks in advance.

Hi Manoj,
Thanks for the quick reply to my query.
The thing is, the link you have provided talks more from changing the business Service configurations i.e. the type of the service etc, but the concern is, that the Business Service is already Implemented and hence the change would not be an appropriate option for me.
Please let me know, if any more information is required.
Thanks & Regards,
Anu

Dynamic orchestration using multiple proxy services

The project I am currently on is using ALSB for service orchestration. For a given orchestration, we would have one orchestration proxy (the control center), that synchronously calls a sequence of alsb proxy services.
Each proxy service in this second level fronts one or more business service calls to perform a specific operation ("Create Account", "Create User", etc.).
So far so good, all this can work just fine (and much of it is already working in production). The trick that I am trying to make happen currently, is to dynamically load the list of second-level proxies and loop through the list to trigger calls.
Loading a list of proxy paths/names is no problem, I have many options there. It's when I try to take that list and loop through it, calling each proxy on the list that I am stuck.
Unfortunately, it appears I could have three routing choices and none of them work:
1. Service Callouts only work with a static service name, not a dynamic one (so even if I had a for-each loop around a Service Callout action, it doesn't do me any good).
2. Dynamic Publish actions are asynchronous only
3. Dynamic Routing actions inside Route nodes work, except that only one can exist per proxy service.
Am I missing anything? Is there some way to get ALSB to accept dynamic synchronous invocation of multiple proxy services from one orchestration proxy service?
Meghan Pietila
Granite Consulting, Inc.
Minnesota

A way of Invoking a dynamically chosen proxy service (PS) synchronously could be the following.
Service Callout actions are synchronous, so ALSB will block in PS2 (PS=proxy service) when it does the invocation of PS1.
Assuming the following very simple scenario (I hope to have understood correctly your case):
OPS = orchestration proxy service
case1: OPS -> PS1 -> PS3 -> ...
case2: OPS -> PS1 -> PS2 -> ...
where each PSi calls one or more business service (I suppose that the business services called in each PSi are called in a predefined order), so what is changing from one case to another is the sequence of PSi to be called.
I've setup the following ALSB project:
- OPS proxy services
- PS1 .. PS4 proxy services
- a proxy called 'step'
- a xquery called 'routing'
The idea is to call, from OPS, another proxy (the 'step' proxy) in a synch way (service callout) passing the information of what proxy should be called dynamically.
In the 'step' proxy then I create the <route><service> XML fragment, for the Dynamic Route action. This <route><service> XML fragment will point to the configuration of yet another proxy service (PSx), that is the PSx that I want to call.
One limitation is that I assume that your OPS always calls for example 2 proxies which name is resolved dynamically.
About the xquery:
<routing>
<case name="1">
<node>PS1</node>
<node>PS3</node>
</case>
<case name="2">
<node>PS1</node>
<node>PS2</node>
</case>
</routing>
OPS performs the following steps:
- chooses what is the case: 1 or 2
- does 2 service callout to the proxy called 'step' passing each time the correct node to be called
$routing/case[@name=data($case)]/node[1]
$routing/case[@name=data($case)]/node[2]
In the 'step' proxy I do a dynamic publish to desidered PS:
<route xmlns="http://www.bea.com/wli/sb/context">
<service isProxy="true">{ $proxyToBeInvoked }</service>
</route>
where the proxyToBeInvoked variable is built from the node received by the caller.
I've used this approach in a solution currently under development but I've found some problems when I want to receive back in OPS the error raised by any PSi: I'm able to catch the error but I'm not able to receive back the detailed error like in an usual stack trace.
I hope that could be useful.
Regards
ferp

OSB Setting SOAP Body Id value in proxy service when calling out to another service

I have a proxy service deployed in OSB. I need to set the Id attribute value on the SOAP Body element to a specific value prior to invoking the business service.
In the service callout I currently has "Configure Payload Document" selected.
Do I need to do an XPath / XQuery transformation in an Insert or Update message processing action in a prior step of the message flow before the callout to the business service?

Suppose below is your request you are passing to Business Service :
<math:input
xmlns:math="http://www.math.org">
    <math:inp1>100</math:inp1>
    <math:inp2>1</math:inp2>
    </math:input>
Now before passing it to BS you need to change the value of inp2 to let say 200.
So just before service callout , add a replace action
Replace [ node contents ] of [ ./math:input/math:inp2 ] in [ body ] with [ 200 ]
Your new request will become:
<math:input
xmlns:math="http://www.math.org">
<math:inp1>100</math:inp1>
<math:inp2>200</math:inp2>
</math:input>
Hope this helps.
Regards,
Karan
Oracle Fusion Middleware Blog

How to be able to view the proxy service's WSDL in the browser

Hello, I created a ALSB proxy service that I have been able to successfully access from a SOAP client. I exported the WSDL from the Project Explorer, Resources Block, Actions column, and it gave me this URL to hit the proxy service:
http://mymachine:7001/OneProxyServiceToOneBusinessService/DoubleItWSFromWL_PRSRV
No problem here. But when I try to access the WSDL from the browser (helpful for SOAP clients in generating the JAX-WS artifacts), using this URL:
http://mymachine:7001/OneProxyServiceToOneBusinessService/DoubleItWSFromWL_PRSRV?wsdl
I get this error HTML message back as a response:
"Error 405--Method Not Allowed
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource"
(Same error message if I omit the "?wsdl" at the end, BTW.)
I don't understand this message--what do I need to do to be able to view the proxy service's WSDL from the browser, or does ALSB not provide that option?
Thanks,
Glen

Click on the Proxy Service in your ALSB project to go to Proxy Service Configuration page. On this page, you will see an endpoint URI, something like /myservice. To get the wsdl in browser, use the URL like http://mymachine:7001/myservice?wsdl

Stuck Thread - JMS Business proxy Service (ALSB 2.5)

Hi All,
We are having a jms proxy service which uses a JMS Business Service to send messages to a jms queue on weblogic 8.1 sp6. The alsb domain runs on weblogic 9.2.The jms proxy service is made single threaded by configuring a suitable work manager.
Now and then, we get a stuck thread issue in production and the proxy service stops consuming the messaging off the jms queue in wls 9.2. These are the errors in the logs:
<[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1235437298516> <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "695" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@5321caf", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-70 "[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, waiting, priority=1, DAEMON> {
-- Waiting for notification on: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
jrockit.vm.Threads.waitForSignal(Native Method)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Native Method)
weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:73)
^-- Lock released while waiting: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:100)
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
weblogic.jms.dispatcher.DispatcherInteropAdapter.dispatchSyncTranFuture(DispatcherInteropAdapter.java:80)
weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:230)
weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:51)
weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1047)
weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
weblogic.jms.client.JMSProducer.send(JMSProducer.java:352)
weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:1009)
weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:157)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:795)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:500)
com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:612)
jrockit.reflect.CompiledMethodInvoker.invoke0(Unknown Source)
jrockit.reflect.CompiledMethodInvoker.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.bea.wli.sb.transports.Util$1.invoke(Util.java:241)
$Proxy39.sendMessageAsync(Unknown Source)
com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:137)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:437)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:328)
com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:503)
com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:415)
stages.publish.runtime.PublishRuntimeStep.processMessage(PublishRuntimeStep.java:106)
com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:327)
com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:100)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:73)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:47)
com.bea.wli.sb.pipeline.Node.processMessage(Node.java:57)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Router.processMessage(Router.java:141)
com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:646)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:645)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:627)
com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:264)
com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:292)
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
weblogic.jms.client.JMSSession.execute(JMSSession.java:4012)
weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
jrockit.vm.RNI.c2java(Native Method)
Any one know the root cause of this issue or ways to prevent this?
Also Is there a way to make the proxy service to reconsume messages off the queue without a server restart?
Thanks,
Atheek

Hi atheek, did you find the solution??
I already got the same/identic issue, do you mind giving me an aid?
Really thanks
Regards,
Mr.K

ALSB Proxy services deployment management

Similar Messages

Maybe you are looking for