Service Bus Forward From Topic to Queue using wcf

I’m trying to send a message to a topic and have it forwarded to a queue (which I have a wcf service connected to the queue). 
If I send the message directly to the queue it works fine, however if I send it to a topic which has a subscription that forwards it to the queue, it just sits in the queue. 
Is there something I’m missing in the configuration for the wcf service to receive the forwarded messages?

Doing a wcf trace I was seeing a filter mismatch.  Not sure why it works when I send it directly to a queue and doesn't when it's forwarded from a topic.  But by setting the AddressFitlerMode to any seemed to let me do forwarding with wcf. This
doesn't seem like the clean solution but it works for now.

Similar Messages

  • Access Oracle Service Bus objects from within a PBL program

    Followed instructions from Studio Reference documentation for cataloging Oracle Service Bus objects and embedded sample code but encountered http 404 not found error. Is there anyway to trace the call made to the Service Bus? I change the log message severity level for Workspace application to debug but the call is not logged. The following is the output from the log:
    ================Oracle® BPM - WorkSpace================
    RUNTIME:fuego.papi.exception.ActivityFailedException: Activity '/ExpenseReport#Default-1.0/GlobalCreation[CreateExpenseReport]' task '' could not execute successfully.
    RUNTIME:Detail:Method: '', Exception: 'The method 'CIL_createExpenseReportCreateExpenseReportIN' from class 'oracle.ExpenseReport.Default_1_0.Instance' could not be successfully executed.'
    RUNTIME:
    RUNTIME:     at fuego.papi.exception.ActivityFailedException.create(ActivityFailedException.java:66)
    RUNTIME:     at fuego.server.AbstractProcessBean.createActivityFailedException(AbstractProcessBean.java:3561)
    RUNTIME:     at fuego.fengine.FEngineProcessBean.createActivityFailedException(FEngineProcessBean.java:371)
    RUNTIME:     at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2968)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
    RUNTIME:     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
    RUNTIME:     at fuego.lang.JavaObject.invoke(JavaObject.java:227)
    RUNTIME:     at fuego.component.Message.process(Message.java:585)
    RUNTIME:     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
    RUNTIME:     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
    RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
    RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
    RUNTIME:     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
    RUNTIME:     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
    RUNTIME:     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
    RUNTIME:     at fuego.component.CustomExecution.next(CustomExecution.java:176)
    RUNTIME:     at fuego.papi.impl.rmi.RMIExecution.next(RMIExecution.java:109)
    RUNTIME:     at fuego.web.execution.InteractiveExecution.process(InteractiveExecution.java:177)
    RUNTIME:     at fuego.web.execution.impl.WebInteractiveExecution.process(WebInteractiveExecution.java:54)
    RUNTIME:     at fuego.web.execution.InteractiveExecution.process(InteractiveExecution.java:223)
    RUNTIME:     at fuego.web.papi.TaskExecutor.runApplicationTask(TaskExecutor.java:349)
    RUNTIME:     at fuego.web.papi.TaskExecutor.execute(TaskExecutor.java:95)
    RUNTIME:     at fuego.workspace.servlet.ExecutorServlet.doAction(ExecutorServlet.java:117)
    RUNTIME:     at fuego.workspace.servlet.BaseServlet.doPost(BaseServlet.java:229)
    RUNTIME:     at fuego.workspace.servlet.BaseServlet.doGet(BaseServlet.java:220)
    RUNTIME:     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    RUNTIME:     at fuego.workspace.servlet.AuthenticatedServlet.service(AuthenticatedServlet.java:83)
    RUNTIME:     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    RUNTIME:     at fuego.web.filter.SingleThreadPerSessionFilter.doFilter(SingleThreadPerSessionFilter.java:64)
    RUNTIME:     at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    RUNTIME:     at fuego.web.filter.CharsetFilter.doFilter(CharsetFilter.java:48)
    RUNTIME:     at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
    RUNTIME:     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    RUNTIME:     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    RUNTIME:     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    RUNTIME:     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    RUNTIME:     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    RUNTIME:     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    RUNTIME:     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    RUNTIME:     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
    RUNTIME:     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
    RUNTIME:     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
    RUNTIME:     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
    RUNTIME:     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
    RUNTIME:     at java.lang.Thread.run(Unknown Source)
    RUNTIME:Caused by: fuego.lang.ComponentExecutionException: The method 'CIL_createExpenseReportCreateExpenseReportIN' from class 'oracle.ExpenseReport.Default_1_0.Instance' could not be successfully executed.
    RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:519)
    RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:273)
    RUNTIME:     at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:219)
    RUNTIME:     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
    RUNTIME:     at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:401)
    RUNTIME:     at fuego.server.execution.GlobalTaskExecution.invoke(GlobalTaskExecution.java:146)
    RUNTIME:     at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:513)
    RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:697)
    RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:657)
    RUNTIME:     at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:154)
    RUNTIME:     at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:116)
    RUNTIME:     at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:96)
    RUNTIME:     at fuego.server.execution.microactivity.GlobalCreationMicroActivity.execute(GlobalCreationMicroActivity.java:109)
    RUNTIME:     at fuego.server.execution.microactivity.GlobalInteractiveMicroActivity.execute(GlobalInteractiveMicroActivity.java:73)
    RUNTIME:     at fuego.server.AbstractProcessBean$44.execute(AbstractProcessBean.java:2961)
    RUNTIME:     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
    RUNTIME:     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
    RUNTIME:     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
    RUNTIME:     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
    RUNTIME:     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
    RUNTIME:     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
    RUNTIME:     at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2954)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
    RUNTIME:     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
    RUNTIME:     at fuego.lang.JavaObject.invoke(JavaObject.java:227)
    RUNTIME:     at fuego.component.Message.process(Message.java:585)
    RUNTIME:     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
    RUNTIME:     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
    RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
    RUNTIME:     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
    RUNTIME:     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
    RUNTIME:     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
    RUNTIME:     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
    RUNTIME:Caused by: fuego.lang.RuntimeCILExecutionException: <?xml version="1.0" encoding="UTF-8" ?>
    RUNTIME:<string>return code: 404
    RUNTIME:&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Draft//EN&quot;&gt;
    RUNTIME:&lt;HTML&gt;
    RUNTIME:&lt;HEAD&gt;
    RUNTIME:&lt;TITLE&gt;Error 404--Not Found&lt;/TITLE&gt;
    RUNTIME:&lt;META NAME=&quot;GENERATOR&quot; CONTENT=&quot;WebLogic Server&quot;&gt;
    RUNTIME:&lt;/HEAD&gt;
    RUNTIME:&lt;BODY bgcolor=&quot;white&quot;&gt;
    RUNTIME:&lt;FONT FACE=Helvetica&gt;&lt;BR CLEAR=all&gt;
    RUNTIME:&lt;TABLE border=0 cellspacing=5&gt;&lt;TR&gt;&lt;TD&gt;&lt;BR CLEAR=all&gt;
    RUNTIME:&lt;FONT FACE=&quot;Helvetica&quot; COLOR=&quot;black&quot; SIZE=&quot;3&quot;&gt;&lt;H2&gt;Error 404--Not Found&lt;/H2&gt;
    RUNTIME:&lt;/FONT&gt;&lt;/TD&gt;&lt;/TR&gt;
    RUNTIME:&lt;/TABLE&gt;
    RUNTIME:&lt;TABLE border=0 width=100% cellpadding=10&gt;&lt;TR&gt;&lt;TD VALIGN=top WIDTH=100% BGCOLOR=white&gt;&lt;FONT FACE=&quot;Courier New&quot;&gt;&lt;FONT FACE=&quot;Helvetica&quot; SIZE=&quot;3&quot;&gt;&lt;H3&gt;From RFC 2068 &lt;i&gt;Hypertext Transfer Protocol -- HTTP/1.1&lt;/i&gt;:&lt;/H3&gt;
    RUNTIME:&lt;/FONT&gt;&lt;FONT FACE=&quot;Helvetica&quot; SIZE=&quot;3&quot;&gt;&lt;H4&gt;10.4.5 404 Not Found&lt;/H4&gt;
    RUNTIME:&lt;/FONT&gt;&lt;P&gt;&lt;FONT FACE=&quot;Courier New&quot;&gt;The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.&lt;/p&gt;&lt;p&gt;If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.&lt;/FONT&gt;&lt;/P&gt;
    RUNTIME:&lt;/FONT&gt;&lt;/TD&gt;&lt;/TR&gt;
    RUNTIME:&lt;/TABLE&gt;
    RUNTIME:
    RUNTIME:&lt;/BODY&gt;
    RUNTIME:&lt;/HTML&gt;
    RUNTIME:</string>
    RUNTIME:
    RUNTIME:     at fuego.components.ScreenFlow.rethrowUserException(ScreenFlow.java:274)
    RUNTIME:     at fuego.components.ScreenFlow.propagateParentException(ScreenFlow.java:239)
    RUNTIME:     at xobject.Fuego__AutoGen__Screenflows__.__SubmitReport.Begin_Invocator(__SubmitReport.xcdl:13)
    RUNTIME:     at oracle.ExpenseReport.Default_1_0.Instance.CIL_createExpenseReportCreateExpenseReportIN(Instance.xcdl:3)
    RUNTIME:     at oracle.ExpenseReport.Default_1_0.Instance.CIL_createExpenseReportCreateExpenseReportIN(Instance.xcdl)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    RUNTIME:     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    RUNTIME:     at java.lang.reflect.Method.invoke(Unknown Source)
    RUNTIME:     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:512)
    RUNTIME:     ... 35 more

    You are receiving a 404 error which means that the binding to the SB is not correct or there is a problem with the SB end part of the integration.
    Are you able to test this successfully from an automatic activity for example aside from trying to use it within a screenflow ?
    Thanks !
    eduardoc.

  • Reading old message from Topic or queue

    How i can read old message from jms topic or queue?

    It depends on what you mean by "old" and what your JMS implementation is. Old as in expired or as in previously delivered?
    Sending expired or previously delivered messages with DropboxMQ is as simple as moving the message files around using a shell or file explorer.
    http://dropboxmq.sourceforge.net
    Dwayne

  • Cannot Start Service Bus Domain from ANT script

    Hi,
    I am preparing a script which buils service bus domain using wlst script and then makes a jar file of the newly build domain and transfer it to the target location where it need to run.
    Once the jar file is in target location is jar is expanded in a folder.
    The above mentioned process if working fine. If i try to start the domain from that location either by double clicking startWebLogic.cmd or from dos prompt it does start the domain wihtout any error.
    However if i try to start the domain from with the same ANT script either using <wlserver> or <java classname="weblogic.WLST"> using startServer ('AdminServer','mydomainname','weblogic','weblogic','t3://localhost:7001') the domain startup does start but failes with same weblogic.management.deployment exception.
    complaining about all alsb specific applications error i.e.
    java.lang.ClassNotFoundException: com.bea.wli.sb.init.MarkerAppListener/com.bea.wli.sb.init.FrameworkStarter ..... under weblogic.management.deloymentexception.
    had anyone manager to start domain like this? any help?
    thanks
    salman

    I faced a similar issue when all ALSB specific applications were failing with ClassNot Found error when the managed servers were started using node manager. This was fixed by setting up the right Server Classpath for the WLS server.
    The issue was fixed after setting up the CLASSPATH to use when starting up the server as below, where E:/APPS/STAGE/OSB103 is the BEA_HOME
    E:\APPS\STAGE\OSB103\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_cie670\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_alsb1031\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\JROCKI~1\lib\tools.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\weblogic_sp.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\weblogic.jar;E:\APPS\STAGE\OSB103\modules\features\weblogic.server.modules_10.3.0.0.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\webservices.jar;E:\APPS\STAGE\OSB103\modules\ORGAPA~1.5/lib/ant-all.jar;E:\APPS\STAGE\OSB103\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\features\osb.server.modules_10.3.1.0.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\flow\sb-flow.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\com.bea.core.jaxen_1.0.1.0_1-1-1.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\version.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\alsb.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-ant.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-common.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-core.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-dameon.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\classes;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\com.bea.core.apache.commons.logging_1.1.0.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\jca-binding-api.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\bpm-infra.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\E:\APPS\STAGE\OSB103\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_cie670\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\patch_alsb1031\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\APPS\STAGE\OSB103\JROCKI~1\lib\tools.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\weblogic_sp.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\weblogic.jar;E:\APPS\STAGE\OSB103\modules\features\weblogic.server.modules_10.3.0.0.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\webservices.jar;E:\APPS\STAGE\OSB103\modules\ORGAPA~1.5/lib/ant-all.jar;E:\APPS\STAGE\OSB103\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\features\osb.server.modules_10.3.1.0.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\flow\sb-flow.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\com.bea.core.jaxen_1.0.1.0_1-1-1.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\version.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\alsb.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-ant.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-common.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-core.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\lib\j2ssh-dameon.jar;E:\APPS\STAGE\OSB103\osb_10.3\3rdparty\classes;E:\APPS\STAGE\OSB103\WLSERV~1.3\..\modules\com.bea.core.apache.commons.logging_1.1.0.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\jca-binding-api.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\bpm-infra.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\log4j_1.2.8.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\xmlparserv2.jar;WL_HOME\server\ext\jdbc\oracle\orai18n.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\xqrl.jar;jca\log4j_1.2.8.jar;E:\APPS\STAGE\OSB103\osb_10.3\lib\transports\jca\xmlparserv2.jar;WL_HOME\server\ext\jdbc\oracle\orai18n.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;E:\APPS\STAGE\OSB103\WLSERV~1.3\server\lib\xqrl.jar;
    -Atheek

  • Oracle Service Bus - Alert Destination on JMS Queue

    Hi Guys, I have been trying to create Alert destination with email destinations and have been successful. The problem that I am facing now is when I am trying to create an Alert Destination to a JMS Queue. I am using the correct format that you generally use for a JMS URI. -- jms://<host>:port/<factoryJNDIName>/<QueueJNDIName>
    This, is the scenario. I have an Alert Rule specified in one of my proxy services, which basically sends out the fault to the Alert Destination as configured above. This alert will be triggered
    when the error count in the Proxy Service exceeds 3. But I do not seem to be getting the messages into my queue which I am monitoring from weblogic console.
    However, I do get all the messages that I trigger from a separate biz service that I had made just to test the authenticity of my JMS Configuration.
    Any one experienced this before? Specifically related to SLA Alerts/Alert Destinations configuration on JMS Queues?

    Thank you for your response. Well, Let me see if I can explain in a clearer way.
    As you already know, Alert Destination (used for SLA Alerting for example) in OSB have two destinations that you can configure. One - an email recipient(s), who will get the email when the alert (configured in your proxy service and bounded to this alert destination is triggered) . Two - a jms queue, where the same "alert" can be pushed to.
    My question is - I have configured the JMS Destination on the Alert Destination configuration page as such - jms://localhost:7001/testConnFact/testQueue
    (testConnFact and testQueue being the JNDI names of the connection factory and queue respectively configured in weblogic server)
    When the alert (configured in the proxy service) is triggered, (like maybe, due to the error count being more than 3), I should be getting the message pushed into the queue, because, that's the destination I have set in this ALERT DESTINATION.
    I am NOT getting it however.
    On a diff note, when I am creating a business service in OSB on a JMS protocol giving the URI of the queue created in weblogic, I AM getting the messages into the Queue. This, I had done, to test whether my configuration for the queue is correct or not.
    So it seems that Queue configuration on weblogic is correct, however, the alert destination is simply not pushing the messages to the queue.
    Hope this was clear.

  • Message Bridge - from Topic to Queue

    Hi all,
              Can I set up a message bridge in Weblogic 8.1 sp3 to "redirect" message from a topic to a queue? i.e. The source is set to Topic while the target is to queue consumed by a MDB located in the same instance as the queue.
              I tried to configure but I couldn't get any subscriber to subscribe the said topic. Would it be a configuration problem or would the proposed bridge work?
              Thanks,
              Vincent

    Sure, there's no reason why the bridge can't go from a topic to a queue, or from a queue to a topic. I don't know what specific problem you were having, but you can do this.

  • Weblogic Server Crash on accessing service bus console from remote

    Please help me out here. Thanks.
    Error Message:
    <2009-01-28 16:05:50 CET> <Warning> <netuix> <BEA-423430> <The portal <directive.page> element has been deprecated. You can set the page encoding on the <netuix:desktop> element.>
    <2009-01-28 16:05:51 CET> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is jsp/login/index.jsp.>
    ===== BEGIN DUMP =============================================================
    JRockit dump produced after 0 days, 00:04:03 on Wed Jan 28 16:05:56 2009
    Additional information is available in:
    /home/efidev/dev/bea92/domains/alsb/jrockit.8808.dump
    No snapshot file (core dump) will be created because core dumps have been
    disabled. To enable core dumping, try "ulimit -c unlimited"
    before starting JRockit again.
    If you see this dump, please open a support case with BEA and
    supply as much information as you can on your system setup and
    the program you were running. You can also search for solutions
    to your problem at http://forums.bea.com in
    the forum jrockit.developer.interest.general.
    Error Message: Illegal memory access. [54]
    Signal info : si_signo=11, si_code=1 si_addr=0x2598
    Version : BEA JRockit(R) R26.4.0-63_CR302700-72606-1.5.0_06-20061127-1104-linux-ia32
    GC : System optimized over throughput (initial strategy singleparpar)
    : GC strategy for GC 0 was singleparpar
    : GC strategy for GC 1 was genparpar
    : GC strategy for GC 2 was genparpar
    : GC strategy for GC 3 was genparpar
    : mmHeap->data = 0x8100000, mmHeap->top = 0x28100000
    : The nurserylist starts at 0x8ba1998 and ends at 0xa29d4d8
    : mmStartCompaction = 0x22100000, mmEndCompaction = 0x24100000
    CPU : Intel Core (HT) SSE SSE2 Core EM64T
    Number CPUs : 2
    Tot Phys Mem : 3442233344 (3282 MB)
    OS version : lenny/sid
    Linux version 2.6.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008 (i686)
    Thread System: NPTL
    State : JVM is running
    Command Line : -Xms512m -Xmx512m -Xverify:none -da -Dplatform.home=/usr/local/app/bea92/weblogic92 -Dwls.home=/usr/local/app/bea92/weblogic92/server -Dwli.home=/usr/local/app/bea92/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/usr/local/app/bea92/patch_weblogic921/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer_ALSB -Djava.security.policy=/usr/local/app/bea92/weblogic92/server/lib/weblogic.policy weblogic.Server
    java.home : /usr/local/app/bea92/jrockit90_150_06/jre
    j.class.path : :/home/efidev/dev/bea92/domains/alsb/lib/commons-collections-3.2.jar:/home/efidev/dev/bea92/domains/alsb/lib/commons-configuration-1.4.jar:/home/efidev/dev/bea92/domains/alsb/lib/commons-lang-2.3.jar:/home/efidev/dev/bea92/domains/alsb/lib/commons-logging-1.1.jar:/home/efidev/dev/bea92/domains/alsb/lib/commons-pool-1.3.jar:/home/efidev/dev/bea92/domains/alsb/lib/ip-code-translator-1.0.jar:/home/efidev/dev/bea92/domains/alsb/lib/IPHeaderAPI.jar:/home/efidev/dev/bea92/domains/alsb/lib/ip-logging-1.0.jar:/home/efidev/dev/bea92/domains/alsb/lib/kodo-4.1.2.jar:/home/efidev/dev/bea92/domains/alsb/lib/openjpa-0.9.6.jar:/home/efidev/dev/bea92/domains/alsb/lib/persistence-api-1.0.jar:/home/efidev/dev/bea92/domains/alsb/lib/serp-1.11.0.jar:/home/efidev/dev/bea92/domains/alsb/lib/velocity-1.4.jar:/usr/local/app/bea92/patch_weblogic921/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/local/app/bea92/jrockit90_150_06/lib/tools.jar:/usr/local/app/bea92/weblogic92/server/lib/weblogic_sp.jar:/usr/local/app/bea92/weblogic92/server/lib/weblogic.jar:/usr/local/app/bea92/weblogic92/server/lib/webservices.jar::/home/efidev/dev/bea92/domains/alsb/template_alsb/lib/config:/usr/local/app/bea92/weblogic92/servicebus/L10N:/usr/local/app/bea92/weblogic92/servicebus/lib/sb-public.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/sb-common.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/sb-internal.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/sb-core.jar:/usr/local/app/bea92/weblogic92/integration/common/lib/mfl-common.jar:/usr/local/app/bea92/weblogic92/platform/lib/p13n/p13n_system.jar:/usr/local/app/bea92/weblogic92/common/p13n/lib/p13n_common.jar:/usr/local/app/bea92/weblogic92/server/lib/wlxbean.jar:/usr/local/app/bea92/weblogic92/server/lib/apachexmlbeansutil.jar:/usr/local/app/bea92/weblogic92/server/lib/xquery.jar:/usr/local/app/bea92/weblogic92/server/lib/binxml.jar:/usr/local/app/bea92/weblogic92/common/lib/log4j.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/uddi_library.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/uddi_client_v3.jar:/usr/local/app/bea92/weblogic92/servicebus/lib/version.jar::/usr/local/app/bea92/weblogic92/common/eval/pointbase/lib/pbembedded51.jar:/usr/local/app/bea92/weblogic92/common/eval/pointbase/lib/pbupgrade51.jar:/usr/local/app/bea92/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/usr/local/app/bea92/weblogic92/server/lib/xqrl.jar::
    j.lib.path : /usr/local/app/bea92/jrockit90_150_06/jre/lib/i386/jrockit:/usr/local/app/bea92/jrockit90_150_06/jre/lib/i386:/usr/local/app/bea92/jrockit90_150_06/jre/../lib/i386:/usr/local/app/bea92/patch_weblogic921/profiles/default/native:/usr/local/app/bea92/weblogic92/server/native/linux/i686:/usr/local/app/bea92/weblogic92/server/native/linux/i686/oci920_8
    JAVA_HOME : /usr/local/app/bea92/jrockit90_150_06
    JAVAOPTIONS: <not set>
    LD_LIBRARY_PATH: /usr/local/app/bea92/jrockit90_150_06/jre/lib/i386/jrockit:/usr/local/app/bea92/jrockit90_150_06/jre/lib/i386:/usr/local/app/bea92/jrockit90_150_06/jre/../lib/i386:/usr/local/app/bea92/patch_weblogic921/profiles/default/native:/usr/local/app/bea92/weblogic92/server/native/linux/i686:/usr/local/app/bea92/weblogic92/server/native/linux/i686/oci920_8
    LD_ASSUME_KERNEL: <not set>
    C Heap : Good; no memory allocations have failed
    StackOverFlow: 0 StackOverFlowErrors have occured
    OutOfMemory : 0 OutOfMemoryErrors have occured

    Upgrading to latest version is a good choice. You can also consider increasing the heap size from -Xms512m -Xmx512m to -Xms1024m -Xmx1024m and confirm if this crash was due to insufficient heap.

  • 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

  • Service bus performance using AMQP

    Hi,
    I am checking the performance of the service bus on the AMQP link.
    Using qpid-proton-c 0.8 on my Linux machine Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz (8 cores) with 8 GB of memory, sending a message can take up to 200 milliseconds.
    I was surprised by this performance. I was expecting a shorter delay (like 50 ms).
    Is there a way to improve/optimize this performance?
    Many thanks.

    Indeed, I am not measuring the first Sent (it was 400 msec). 
    It was random. For example, in my test, the 4th, 9th, 12th, 13th, 20th (...) took 900 milliseconds.
    Other messages was sent in within 120 milliseconds, which is still in my opinion high comparing the size of the message I am sending.
    The message contains:
     - content-type: set to dummy type
     - message ID: 16 Bytes
     - correlation ID: 16 Bytes
     - Subject: 12 Bytes
     - content: 14 Bytes.

  • BizTalk 2013 R2: SB-Messaging Windows Service Bus On Premise 1.1 (Not Windows Azure)

    Let me preface this by saying that I have been able to connect to the destination Service Bus Topics and Queue using traditional .NET methods (e.g. System.ServiceBus.Messaging namespace) and the applications using those components are running fine on the
    same local VM.  This uses the connection string that is provided from GET-SBAuthorizationRule.
    Development Environment:
    Windows Server 2012
    SQL Server 2014
    BizTalk 2013 R2
    Local VM that is not on the Domain (but can connect to computers on the network)
    I am trying to create a simple BizTalk 2013 R2 Messaging Solution that will use the SB-Messaging adapter features with Windows Service Bus On-Premise.  My solution is using a Static One-Way Send Port to send messages to an existing topic on with Windows
    Service Bus 1.1 using the SB-Messaging Adapter.  After using the programmatic approach, the configurations were not as intuitive, but I believe I am close to the resolution.  I have tried several combinations of key data but I am still not able to
    connect.  This seems like I am missing something small that is causing the problem but I am at a loss for the moment.  The error I receive is below:
    A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<SERVERNAME>/NsServiceBus/collateraltopic" is suspended.
    Error details: System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at Microsoft.ServiceBus.TokenProviderHelper.TokenRequestAsyncResult.<GetAsyncSteps>b__8(TokenRequestAsyncResult thisPtr, IAsyncResult r)
    at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
    --- End of inner exception stack trace ---
    Server stack trace:
    Exception rethrown at [0]:
    at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
    at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationToken(String appliesTo, String action)
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext)
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.GetOverheadSize()
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender..ctor(String path, SbmpMessagingFactory messagingFactory, SbmpMessageCreator messageCreator, RetryPolicy retryPolicy)
    at Microsoft.ServiceBus.Messaging.Sbmp.CreateSenderLinkSettings..ctor(SbmpMessagingFactory messagingFactory, String entityName, Nullable`1 entityType, String transferDestinationEntityName, RetryPolicy retryolicy)
    at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginCreateMessageSender(String transferDestinationEntityName, String viaEntityName, TimeSpan timeout, AsyncCallback callback, Object state)
    at Microsoft.ServiceBus.Messaging.MessagingFactory.CreateMessageSenderAsyncResult.<GetAsyncSteps>b__52(CreateMessageSenderAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
    at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
    at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
    Exception rethrown at [0]:
    at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
    at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.<>c__DisplayClass4`1.<Begin>b__3(IAsyncResult r, T& output)
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OperationComplete(IAsyncResult result)
    at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.BeginOperation()
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OpenComplete(IAsyncResult result)
    at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1..ctor(OpenOnceManager openOnceManager, TimeSpan openTimeout, AsyncCallback callback, Object state, Func`3 beginOperation, EndOperation`1 endOperation)
    at Microsoft.ServiceBus.Messaging.OpenOnceManager.Begin[T](AsyncCallback callback, Object state, Func`3 beginOperation, Func`2 endOperation)
    at Microsoft.ServiceBus.Messaging.MessagingFactory.BeginCreateMessageSender(String transferDestinationEntityPath, String viaEntityPath, Boolean tryPairSender, TimeSpan timeout, AsyncCallback callback, Object state)
    at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult.CreateFactoryComplete(IAsyncResult result)
    at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
    at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult..ctor(ServiceBusOutputChannel outputChannel, TimeSpan timeout, AsyncCallback callback, Object state)
    at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open()
    at Microsoft.BizTalk.Adapter.SBMessaging.SBMessagingOutputChannelFactory.OnCreateChannel(EndpointAddress address, Uri via)
    at System.ServiceModel.Channels.ChannelFactoryBase`1.InternalCreateChannel(EndpointAddress address, Uri via)
    at System.ServiceModel.Channels.ChannelFactoryBase`1.CreateChannel(EndpointAddress address, Uri via)
    at System.ServiceModel.Channels.ServiceChannelFactory.ServiceChannelFactoryOverOutput.CreateInnerChannelBinder(EndpointAddress to, Uri via)
    at System.ServiceModel.Channels.ServiceChannelFactory.CreateServiceChannel(EndpointAddress address, Uri via)
    at System.ServiceModel.Channels.ServiceChannelFactory.CreateChannel(Type channelType, EndpointAddress address, Uri via)
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)
    at System.ServiceModel.ChannelFactory`1.CreateChannel()
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.GetChannel[TChannel](IBaseMessage bizTalkMessage, ChannelFactory`1& cachedFactory)
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendMessage(IBaseMessage bizTalkMessage)
    MessageId: {28428716-88C2-437B-953F-D471DA00C5A6}
    InstanceID: {18C48B89-D9C0-47A8-ADF0-0CA62746FBB1}
    Below are my Send Port Adapter Configurations:
    URI is blacked out
    /Namespace/Topic/ are next in the path
    Can someone confirm that the Issuer Name is the Namespace and the Issuer Key is the Primary Key from the get-SBAuthorizationRule?  I also tried Shared Access Signature (SAS) but that service was connecting to a default port and do not believe that is
    how I need to connect.
    Also, there is nothing on the Properties Tab as I do not have anything custom for the initial step.
    Any and all help is appreciated.

    Glenn,
    Thank you very much for the response, I will go down this route in further detail.  A couple of quick questions for you to help further my understanding.
    Where is the SAS limitation documented?  I am sure I glossed over it and it did not register, but your help in where to look next time will be helpful.
    Also, can I change the default Port for which it is listening on the BizTalk Server or the Service Bus Location?  The connection string I get from get-SBAuthorization Rule is as follows:
    Endpoint=sb://{ServiceBusLocation}/NsServiceBus;StsEndpoint=https://{ServiceBusLocation}:7355/NsServiceBus;RuntimePort=7354;ManagementPort=7355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey={KeyValue}
    The exception I get is:
    A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<ServiceBusLocation>/NsServiceBus/collateraltopic" is suspended.
    Error details: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://<ServiceBusLocation>:9354/. The connection attempt lasted for a time span of 00:00:04.0250873. TCP error code 10061: No connection could be made because the target machine actively refused it <IPAddress>:9354. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
    at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
    at System.ServiceModel.Channels.SocketConnectionInitiator.ConnectAsyncResult.OnConnect(IAsyncResult result)
    --- End of inner exception stack trace ---
    It looks like it is going to 9354 for the authentication when the Service Bus is configured for
    7355.  I believe I have opened the ports on both ends but do not think it will matter since it looks like it is sending the
    request to a different location.
    Thank you

  • What are the differences between Oracle Service Bus 10g and WLI 10g?

    Hi,
    To me both Oracle Service Bus 10g R3 and Weblogic Integration 10g seem to offer the same functionalities for implementing an enterprise middleware.
    I would be grateful if someone could:
    1. provide me with the two products' differences.
    2. describe what their roadmap is?
    3. what are their positioning in the Oracle product catalog? Are they both members of Oracle SOA Suite? Fussion Middleware?
    Thanks a lot,
    Best regards,
    Babis.

    Thanks everyone for taking the time to reply,
    Eduardo: the answer to your questions are that all the flows will be short-lived but if we can make long-lived flows then we might consider developing them. We would need to persist the state of the flow somehow.
    I understand that some of our requirements would be better accomodated by WLI or bpel but we don't have an option but only to use OSB.
    So, do you think we could overcome the stateless nature of OSB by:
    1. writing to appropriate tables and reading from there and calling plsql procedures from the flows
    2. using JMS queues.
    In detalis:
    1. Regarding the writing/reading from Databases (in our case it would be oracle 10g R2 - probably RAC), is there something like a Database control in WLI, which we could use in OSB? What i have seen are using xquery execute-sql function or a JCA DB adapter but both of them seem to me not very easy to use. Is there another option?
    2. Regarding the JMS, in case that i want:
    a service that writes to a JMS queue what are the servicetype and transport that i should use?
    a service that reads from a JMS queues what are the service type and transport that we should used?
    Any information that you may share with me in the design and implementation of the above would be great.
    Thanks a lot.

  • Connect Azure Pack to Service Bus for Windows Server with Custom DNS

    Hello! I'm trying to configure Azure Pack to use Service Bus for Windows Server 1.1 with Custom DNS.
    All runs on one virtual machine (Windows Server 2012 R2) in Windows Azure.
    I following this post:
    roysvork.wordpress.com/2014/06/14/developing-against-service-bus-for-windows-1-1
    Replace FramDNS "servicebus" to "mymachine.cloudapp.net", and create certificate:
    SelfSSL /N:CN=mymachine.cloudapp.net /V:1000 /T
    On Windows Azure Virtual Machine:
    1.I'll set publuc DNS: mymachine.cloudapp.net
    2.Open ports: 10354,10355,10356,10359,10000-10004
    3.In hosts file: 127.0.0.1 mymachine.cloudapp.net
    4.Create certificate:
    SelfSSL /N:CN=mymachine.cloudapp.net /V:1000 /T
    PowerShell:
    Stop-SBFarm –Verbose
    Set-SBFarm -FarmDns 'mymachine.cloudapp.net'
    Update-SBHost –Verbose
    Start-SBFarm –Verbose
    New-SBAuthorizationRule -NamespaceName ServiceBusDefaultNamespace -Name MainRule -Rights Manage, Send, Listen
    Afther that i can connect to my ServiceBusDefaultNamespace with SAS.
    It's work perfect. But, When I try to create Service Bus Namespace from Azure Pack Tenant portal - in Log an Exception:
    Namespace Provisioning Exception. TrackingId: . SystemId: . Namespace: SomeNamespace.
    Method: Activating. Exception: System.Net.Http.HttpRequestException: An error occurred while
    sending the request. ---> System.Net.WebException: The underlying connection was closed:
    Could not establish trust relationship for the SSL/TLS secure channel. --->
    System.Security.Authentication.AuthenticationException: The remote certificate is invalid according
    to the validation procedure.
    And status of namespace - Activating.
    Please help!

    Hi Alexander,
    According to the log, it seems that the validation process of the certificate failed.
    Please make sure that the certificate is installed in the client properly.
    Usually, self-signed certificate should be installed in the Computer Account-->Trusted Root Certificate Authorities.
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Service Bus Send/Receive - REST API

    I need to use the Azure Service Bus REST API for sending messages to Service Bus Topics. On the receiving side I'm using the Azure Service Bus SDK.
    Message on the sender side:
    POST https://your-namespace.servicebus.windows.net/HttpClientSampleQueue/messages?timeout=60 HTTP/1.1
    Authorization: SharedAccessSignature sr=your-namespace&sig=Fg8yUyR4MOmXfHfj55f5hY4jGb8x2Yc%2b3%2fULKZYxKZk%3d&se=1404256819&skn=RootManageSharedAccessKey
    BrokerProperties: {"Label":"M1","State":"Active"}
    Content-Type: application/atom+xml;type=entry;charset=utf-8
    Host: your-namespace.servicebus.windows.net
    This is a message.
    When reading the message body as message.GetBody<string> an error message is given  serialization exception.
    I already searched the web and found a possible solution:
    Stream stream = message.GetBody<Stream>();
    StreamReader reader = new StreamReader(stream);
    string str = reader.ReadToEnd();
    or as an alternative (instead of converting to string) converting the stream into an XmlDocument
    Are hese recommended ways to handle this issue?
    Thanks.

    @Serkant & Paolo: Thanks for the answers.
    The client I use is Postman (Chrome plug-in).
    The message below works fine, but as I mentioned on the server side (.NET with Azure Service Bus SDK/API) until now I used:
    Stream stream = message.GetBody<Stream>();
    StreamReader reader = new StreamReader(stream);
    string str = reader.ReadToEnd();
    But I'll now try with 
    var body = msg.GetBody<string>(new DataContractSerializer(typeof(string)));
    POST /testtopic/messages HTTP/1.1
    Host: namespace.servicebus.windows.net
    Authorization: SharedAccessSignature sr=https%3a%2f%2namespace.servicebus.windows.net%2ftesttopic&sig=HUl2y3BTw%2bx3tSmUYZtpnfmzyxKfK1lqwIudfVY1UJg%3d&se=65025728850&skn=ManageAccessKey
    Content-Type: application/atom+xml;type=entry;charset=utf-8
    BrokerProperties: {"Label":"M1","State":"Active"}
    MessageNumber: 1
    Cache-Control: no-cache
    Postman-Token: bf68bdef-2b5a-70ed-5fc3-96dbce720a7c
    {"temp":40}

  • C# - Find the number of service bus namespaces programatically

    How can we retrieve the number of provisioned service bus namespaces from a subscription programmatically. Are there any published libraries (NUGET packages) from Microsoft to get this information.
    Thanks,
    Sankaranarayanan MG

    Hi,
    You could use Powershell to get all servicebus name space:
    Get-AzureSBNamespace [-Name]
    Retrieve the list of namespaces
    If there is an error when specifying a name, we should make the HTTP call to get the list and check if it exists in the list.
    see this page:
    https://github.com/Azure/azure-sdk-tools/wiki/Microsoft-Azure-Service-Bus-Cmdlets
    Also, you could try this library:
    https://www.nuget.org/packages/Microsoft.WindowsAzure.Management.ServiceBus/0.15.2-preview
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Tuxedo 11gR2 and Oracle Service Bus

    Windows platform (2008 r2)
    Hi
    I am looking to call a number of web services on an Oracle Service Bus.
    Do I need to use SALT? If so, is there a license cost associated wth this?
    What other options do I have?
    Thanks in advance.
    M

    Hi MI,
    Well the general usage of OSB involves creating service definitions as the services themselves (business services as they are called in OSB) are actually someplace else. OSB acts as an intelligent proxy for those services. So for the client side, i.e., the caller of the service, you define a proxy service that the client can then call using whatever transport was chosen. So if you need to have a web services (SOAP/HTTP) client call a service, you define a web services proxy. Likewise if you need a JMS client to call the service, you create a JMS based proxy service. On the server side, you then create a business service which tells OSB how to call the actual service. A pipeline is then defined that describes how the proxy service is connected to the business service. This "connection" may define payload transformations, synch to asynch mediation, routing, failover, etc. that need to occur. The pipeline also describes the reply path as well, so transformation, message enhancement, etc., can all occur on the service reply message.
    There used to be examples that shipped with OSB, and I assume there are still some. The Tuxedo Transport ones may have been moved to OTN. Try searching this forum or the web for OSB Tuxedo Transport samples if you need them.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

Maybe you are looking for