Trouble with a JMS proxy listening to a distributed topic

Hi all,
I've setup an ALSB cluster with 1 admin instance and 2 managed instances (m01 and m02).
I've also configured 1 distributed topic A and defined the two below proxies:
- proxy P1 is a http proxy that publishes a message into the distributed topic A. The proxy uses a business service with jms protocol and endpoint uri:
jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
- proxy P2 is a JMS proxy listening to
jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
that logs the received message and writes it to file.
The strange behaviour is that on the managed m01 log file I see the message received from P2 but also on the managed m02 log file I see the message received from P2.
So I'm sending out 1 message and receiving 1 x managed that is total = 2.
This strange behaviour is also confirmed from the fact that I see on the file system 2 files and not only 1.
I thought it was a problem concerning the config of business service that publishes message into the distributed topicA; but I tried with an external 'normal' java JMS subscriber that listens to t3://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303 and it works properly: it receives only 1 message.
I'm trying to understand where is my fault.
Do you have any idea ?
Thanks in advance
Patrizio

If you publish a message to a topic, all the proxy that subscribed to this topic will receive the message. If you want the message to be processed by only one managed server you can publish to a queue instead.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Similar Messages

  • Report and Alert don't executed in the error handler with a JMS proxy service

    Hi,
    I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
    My error handler contains two main elements :
    - a Report action
    - an Alert with a JMS destination defined
    When the business service failed the message remain in the queue. It's the expected behavior.
    The problem is :
    - the report is missing
    - the alert is raised but missing in the JMS destination defined in the Alert setting.
    I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
    Unfortunately the message don't remain in the JMS queue.
    What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
    I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
    This solution is not convenient and I hope another solution is possible.

    Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
    wiki article on preparing your workgroup environment may require you to visit each machine individually.
    For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
    on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
    but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
    As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Trouble with CFLOCATION and Proxy Servers

    Hi,
    Trying to troubleshoot an annoying issue and wondering if
    anyone has had any experience with this - haven't had much luck
    Googling for info. Using up-to-date CF 6.1 and current version of
    Apache 2.0. Client is accessing our CF webapps via a clustered
    proxy server/firewall archicture. Each time client users HTTP POST
    through one of our applications, the page they are redirected to
    only displays a small portion of unprocessed raw source page
    content, the remaining page content never seems to make it to the
    client's browser. The only way they can a valid version of the page
    is to refresh the browser. I verified that small portion of raw
    source content is returned by the application during these
    redirects using an HTTP sniffer, however my office PC still
    redirects to the correct page. We are using <CFLOCATION> tags
    to move users between pages after submitting.
    I suspect this problem has to do with their proxy server(s)
    holding HTTP 302 responses to the literal standard, which
    (paraphrasing) basically states that while the URI has been moved,
    it is up to the client to continue the actual redirect. I believe
    HTTP 303 responses would be the "correct" implementation. Having
    said that, we've never run into this issue with any other client
    users before.
    Has anyone ever run into similar issues before? Any help is
    greatly appreciated.
    Thanks,
    DTS

    Replace
    byte[] buf = null;with
    byte[] buf = new byte[ 256 ];Other problems may happen if this sample was not tested properly.
    The problem is that the DatagramPacket requires you to supply a non-null buffer, as per:
    DatagramPacket
    public DatagramPacket(byte[] buf, int length)
    Constructs a DatagramPacket for receiving packets of length length.
    The length argument must be less than or equal to buf.length.
    Parameters:
    buf - buffer for holding the incoming datagram.
    length - the number of bytes to read.
    Edited by: baftos on Jul 18, 2008 3:38 PM

  • IChat/Adium trouble with a college proxy network.

    I'm at college on a wireless network, and there is a proxy in place to access the internet, but unfortunately, iChat and Adium no longer want to connect, even with the proxy details in place within each program.
    Can anyone help me out?
    Cheers, Karl.

    You may want to look into installing authoxy on your mac to get around certain proxy problems.
    http://www.hrsoftworks.net/Products.html

  • Trouble with Basic Reverse Proxy to an IIS machine

    Hi All,
              I am a bit new at this, so bear with me. I am attempting to use Weblogic 8.1 SP3 as a Reverse Proxy to an IIS server. I have configured the HttpProxyServlet and it is the default servlet in my server.
              The kicker here is that it works to google.com or cnn.com, but it fails with a 404 to my internal IIS server. Could IIS be doing something to prevent this?
              My web.xml looks like this:
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
              <web-app>
              <display-name>HttpProxyServlet</display-name>
              <description>HttpProxyServlet</description>
              <servlet>
              <servlet-name>HttpProxyServlet</servlet-name>
              <display-name>HttpProxyServlet</display-name>
              <servlet-class>weblogic.t3.srvr.HttpProxyServlet</servlet-class>
              <init-param>
              <param-name>redirectURL</param-name>
              <param-value>http://www.myiis.com</param-value>
              </init-param>
                   <init-param>
              <param-name>Debug</param-name>
              <param-value>ON</param-value>
              <description>Proxy server verbose output.</description>
              </init-param>
              <init-param>
              <param-name>DebugConfigInfo</param-name>
              <param-value>ON</param-value>
              <description>Debug proxy server configuration. Access via /?__WebLogicBridgeConfig</description>
              </init-param>
              </servlet>
              <servlet-mapping>
              <servlet-name>HttpProxyServlet</servlet-name>
              <url-pattern>/</url-pattern>
              </servlet-mapping>
              </web-app>

    Yes, you are able to do this using IIS.
              have you checked the settings on your IIS Server?
              also i notice in your proxy servlet that you don't have url mapping for web page extensions? Will this affect it?
              <servlet-mapping>
              <servlet-name>ProxyServlet</servlet-name>
              <url-pattern>/</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>ProxyServlet</servlet-name>
              <url-pattern>*.jsp</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>ProxyServlet</servlet-name>
              <url-pattern>*.htm</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>ProxyServlet</servlet-name>
              <url-pattern>*.html</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>ProxyServlet</servlet-name>
              <url-pattern>*.asp</url-pattern>
              </servlet-mapping>

  • OSB JMS Proxy

    Hi ,
    can i use a Proxy service with out a Business service to write a messge onto a queue.I jus tried a sample on my local and i am able to write a message on to a queue using a proxy service .
    Flow :-
    PS1(http) using publish action invokes -> PS2 (jms uri config)
    I am clue less how this is working.when the PS2 transport has been defined as jms ,how am i able to invoke it from PS1 using publish action?
    My understanding of OSB is ProxyService is for reading message from queue and Business service is for writing or publishing a message onto a queue.
    can some body help me udnerstand how this is working.

    Basically, you're right when it comes to the difference between business and proxy services. Also, you're not the only confused when routing data from http-based proxy to JMS proxy.
    We touched the topic earlier:
    Re: Retry mechanism for HTTP Transport in OSB
    The point is your layout (HTTP PS -> JMS PS) is sound and works even without intermediate business service.

  • JMS Durable Distributed Topics

              Please forgive my ignorance if I am doing something silly. I am new to Weblogic
              and JMS, but learning a lot quickly. Any help will be greatly appreciated.
              I am running weblogic 8.1 with no service packs in a development environment only.
              We are trying to work out what is the expected behaviour for our current JMS Topic
              framework.
              I have a two server cluster with distributed topics configured. The two topics
              are configured to be durable. I have a test which generates about 100 events for
              test purposes. Under normal circumstances, each server processes about 50 messages.
              (Load balancing!)
              When the test is running, I kill one of the servers manually before it finishes.
              (Not a gracefull shutdown). The killed server processes about 20 messages, and
              the running server processes about 50. I can see that tables for the persistent
              topics have something (I don't know what) representing about all 100 events sent.
              When I bring the killed server back up, nothing happens. I would expect, from
              the documentation that I read, that the remaining 30 or so events will be put
              on the topic to be processed by our MDBs.
              Why don't all the events get placed on the topic of the killed server when it
              starts back up?
              What is the expected behaviour here?
              Is something wrong with my topic setup?
              Thanks in advance for any help...
              regards,
              Patrick Parato
              

    Hi Patrick,
              Note 1: If you desire MDB to be transactional. Make sure
              the assembly descriptor in ejb-jar.xml is set to
              "Required" in addition to making the transaction-type
              "Container" as you have already done.
              <assembly-descriptor>
              <container-transaction>
              <method>
              <ejb-name>YOUREJBNAME</ejb-name>
              <method-name>onMessage()</method-name>
              </method>
              <trans-attribute>Required</trans-attribute>
              </container-transaction>
              </assembly-descriptor>
              Note 2: Your MDB is non-durable. It needs to be durable
              to cause messages to persist. Add the following line
              in the message-driven-destination clause of your ejb-jar.xml:
              <subscription-durability>Durable</subscription-durability>
              See the JMS FAQ on dev2dev.bea.com (or the JMS Performance
              Guide white-paper) for information on how to make
              sure a message is persistent.
              Note 3: Only one durable subscriber MDB will
              be able to attach to a given durable subscription, MDB's
              on other servers won't be able to, so even if the MDB
              is targeted at the cluster only one MDB will be able
              to process messages. This is the nature
              of durable subscriptions. I'm attaching some personal
              notes on the subject.
              Note 4: Durable subscriptions must refer to
              the JNDI name of member destinations, not to
              the distributed destination. WL does not support
              durable subscriptions directly on a distributed topic.
              Note 5: If you do not want message replication I'm not
              sure why you are using a distributed topic. Use a
              distributed queue.
              Tom
              Patrick Parato wrote:
              > Tom,
              >
              > Thanks for the quick reply.
              >
              > The first thing I want to clarify is that we only have one subscriber (MDB) that
              > is deployed once across multiple servers in a cluster. So this may explain why
              > each server is getting half the messages.
              Its still not clear. Each MDB pool should get each message.
              The individual
              instances in the pool will divide the messages sent to their MDB
              pool's subscription among them.
              >
              >
              >>2) Make sure that you are using durable subscribers. I suspect you
              >>are not. Note that durable subscribers are not supported
              >>for distributed destinations - they must refer directly to a member
              >>destination instead.
              >>
              >
              >
              > We are definitely using a distributed topic. The entry for our MDB in the weblogic-ejb.jar.xml
              > for the <destination-jndi-name> refers to the jndi name of the distributed topic.
              > So if I understand you correctly you are saying that the <destination-jndi-name>
              > should refer to the jndi name of an actual phyiscal topic on one of the servers.
              > By tying an MDB to a regular topic, how do we achieve failover if the JMS server
              > that the topic is associated with should fail?
              >
              >
              >
              > Here is a snippet of our config.xml:
              > (Names have been changed for security reasons)
              >
              > <JMSServer Name="JMS Server1" Store="Event Store1" Targets="myserver1">
              > <JMSTopic CreationTime="1065029382062"
              > JNDIName="distributed.topic@JMS Server1"
              > JNDINameReplicated="false"
              > Name="Distributed Topic@JMS Server1"
              > Template="Distributed Topic" TimeToDeliverOverride="5000"/>
              > </JMSServer>
              >
              > <JMSServer Name="JMS Server2" Store="Event Store2" Targets="myserver2">
              > <JMSTopic CreationTime="1065029382375"
              > JNDIName="distributed.topic@JMS Server2"
              > JNDINameReplicated="false"
              > Name="Distributed Topic@JMS Server2"
              > Template="Distributed Topic" TimeToDeliverOverride="5000"/>
              > </JMSServer>
              >
              >
              > <JMSDistributedTopic JNDIName="distributed.topic" Name="Distributed Topic" Targets="Cluster">
              > <JMSTemplate DeliveryModeOverride="Persistent"
              > Name="Distributed Topic" TimeToDeliverOverride="5000"/>
              > <JMSDistributedTopicMember
              > JMSTopic="distributed.topic@JMS Server1" Name="Distributed Topic@JMS
              > Server1"/>
              > <JMSDistributedTopicMember
              > JMSTopic="distributed.topic@JMS Server2" Name="Distributed Topic@JMS
              > Server2"/>
              > </JMSDistributedTopic>
              >
              >
              > ejb-jar.xml:
              >
              > <message-driven>
              >      <ejb-name>AnMDB</ejb-name>
              >      <ejb-class>package.AnMDB</ejb-class>
              >      <transaction-type>Container</transaction-type>
              >      <message-driven-destination>
              >           <destination-type>
              >                javax.jms.Topic
              >           </destination-type>
              >      </message-driven-destination>
              > </message-driven>
              >
              > weblogic-ejb.jar.xml:
              >
              > <weblogic-enterprise-bean>
              > <ejb-name>AnMDB</ejb-name>
              >      <message-driven-descriptor>
              >      <destination-jndi-name>distributed.topic</destination-jndi-name>
              >      </message-driven-descriptor>
              >      <enable-call-by-reference>True</enable-call-by-reference>
              >      <jndi-name>ejb.AnMDB</jndi-name>
              > </weblogic-enterprise-bean>
              >
              > Thanks for you help and quick reply.
              >
              > regards,
              > Patrick Parato
              >
              A durable topic subscriber MDB uses its name to generate its client-id.
              Since JMS enforces uniqueness on this client-id, this means that if a durable
              subscriber MDB is deployed to multiple servers only one server will be able
              to connect. Some applications want a different behavior where
              each MDB pool on each server gets its own durable subscription.
              The MDB durable subscription id, which must be unique on its topic, comes from:
              1) <jms-client-id>MyClientID</jms-client-id>
              (the weblogic dtd)
              2) if (1) is not set then the client-id
              comes from the ejb name.
              The durable subscription is uniquely identified within a cluster by a
              combination of "connection-id" and "subscription-id". Only one active
              connection may use a particular "connection-id" within a WebLogic cluster.
              The connection id comes from:
              1) The "ClientId" attribute configured on the WebLogic connection factory.
              This defaults to null. Note that if the ClientId is set on a connection
              factory, only one connection created by the factory
              may be active at a time.
              2) If (1) is not set, then, as with the subscriber-id,
              the connection-id is derived from jms-client-id descriptor attribute:
              <jms-client-id>MyClientID</jms-client-id>
              (the weblogic dtd)
              3) If (1) and (2) are not set, then, as with the subscriber-id,
              the connection-id is derived from the ejb name.
              Work-around:
              A) Create a custom connection-factory for each server:
              1) configure "JNDIName" to the same value across all servers
              ("myMDBCF" in this example)
              2) configure "ClientId" to a unique value per server
              3) enable "UserTransactionsEnabled"
              4) enable "XAConnectionFactoryEnabled"
              5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
              6) target the CF at a single WebLogic server
              (Number 5 is required for non-transactional topic MDBs)
              B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
              factory to the JNDI name of the custom connection factories configured in
              (A). Optionally, also specify the subscriber-id via the jms-client-id
              attribute.
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>exampleBean</ejb-name>
              <message-driven-descriptor>
              <connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
              <jms-client-id>myClientID</jms-client-id>
              </message-driven-descriptor>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              C) Target the application at the same servers that have the custom connection
              factories targeted at them.
              Notes/Limitations:
              1) If the MDB is moved from one server to another, the MDB's corresponding
              connection-factory must be moved with it.
              2) This work-around will not work if the destination is not in the same
              cluster as the MDB. (The MDB can not use the local connection factory, which
              contains the connection-id, as connection factories do not work unless they
              are in the same cluster as the destination.)
              3) This work-around will not work for non-WebLogic JMS topics.
              

  • OSB 11g acting as a JMS Proxy

    I was hoping that someone can clear my understanding of OSB and how it interacts with JMS.
    I created a JMS server, connection and topic in WLS. It works great. I am able to subscribe and publish from a java client and from an OSB business service.
    Our use case is to use OSB as a "front end" to JMS if you will. We want JMS clients to be able to connect to OSB and subscribe to our JMS topic (durable). Is it possible to subscribe to a proxy service from a JMS client? How do I do it?
    The next thing we are going to try to do is have an OSB process listen to our JMS topic and invoke a web service when a new message is published. Any guides on this?
    Thanks so much,
    Sam

    We want JMS clients to be able to connect to OSB and subscribe to our JMS topic (durable). Is it possible to subscribe to a proxy service from a JMS client? How do I do it?I don't think subscribing to a proxy service is possible. Instead create a separate queue (or any other storage), for your client application and let OSB pull the message from source queue and pass it to target storage (may be another JMS queue)
    The next thing we are going to try to do is have an OSB process listen to our JMS topic and invoke a web service when a new message is published. Any guides on this?This approach is quite similar to what I mentioned above. Just create a JMS proxy service to let it consume messages from topic and create a Business Service (WSDL based web-service) to invoke the target web-service. In the message flow of JMS proxy you may have transformation if required, and then route the message to business service which will eventually deliver the message to target web-service.
    Regards,
    Anuj

  • JMS proxy and XA connection factory

    Hi all,
    I would like to ask you what is the best practice to adopt about the scenario described below.
    A JMS proxy retrieves a message and processes it.
    Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
    (later another app will check failed messages for fixing & republishing them into ALSB).
    In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
    Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
    Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
    Or XA connection factory is not needed and could I use
    Routing Options with exactly once or both are needed ?
    Thanks
    ferp

    Hi all,
    I did some tests and follow what I've achieved.
    Scenario 1.
    - Precondition
    -- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
    -- A business service BS with XA factory that publishes into MyOutboundQueue
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2.
    - Precondition
    -- As 1. but no error is forced in the pipeline
    -- the MyOutboundQueue destination queue is paused
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2A.
    - Precondition
    -- As 2. with MyOutboundQueue paused and resumed
    - Flow:
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- before all the retries failed the queue is resumed
    --- BS succeeds to publish the message
    Scenario 3.
    - Precondition
    -- A JMS proxy with NO XA factory + Error Destination
    -- A business service BS with NO XA factory
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is NOT rolled back, message NOT redelivered to proxy
    -- so
    --- no message delivered to MyOutboundQueue2 destination
    --- no message delivered to MyRecoveryQueue2 destination
    --- message consumed from MyQueue2 and now is lost!
    To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
    But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
    So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
    So both my proxy service and business service use an XA factory.
    Regards
    ferp

  • Trouble with ZEN MX

    Trouble with ZEN MXWHi,
    I have some issues with my zen mx,? primarily sometimes when I listen to a playlist containing many tracks or "all tracks", my player sometimes shuts of and then have to scan the disk pefore working.
    Secondly there are small pauses during playback, maybe every third track or more, I'm only talking about something like a thenth of a second but it's still very annoying. This also occurs when I have many tracks in my playlist.
    Thirdly I'm not able to access the recovery mode, I've tried following the instructions from the sticky-thread in the forums (Turn on player and hold in the reset butto). However when I do, the screen goes black and no recovery mode appears ever if I hold down the button for a long time.
    Anyone knows how th fix theses issues?
    thanks,
    /Kvick

    Kvick,
    Please follow these steps to access the recovery mode. If this is not working for you, please feel free to contact Customer Support for further assistance.

  • I am having trouble with my bluetooth skipping while its playing music from my Itunes music...I thought that this was an antiquated problem with the new technology?

    I am having trouble with the music from my bluetooth "skipping" on my IPhone 5.  I thought that this was an antiquated problem with the new technology.  It's very frustrating to purchase all of this music and expect great sound and playability and get "skipping".  Any ideas on how to resolve this issue?

    Does the issue occur when listening to the media using the speaker or wired headphones?  If it does, the issue is with the media itself.
    If it does not, it's likely a bad connection or interference.

  • JMS Proxy to Web Service Problem

    Hi All,
    I have a JMS proxy that routes messages to a web service. I have set the delivery failure parameters on the JMS queue. When a message is put onto the queue and there is a problem within the message flow proper, the message is retried the appropriate number of times and put onto the Error Destination queue as necessary. However, if there is a problem calling the web service, message delivery is NOT retried, the message is NOT put onto the Error Destination queue, and the message is lost. The web service itself isn't throwing a SOAP Fault, but the business service can't reach the web service (firewall issue). My Route Error Handler in the message flow is hit and it performs a Reply With Failure.
    Can anyone please explain to me if this is by design and, if so, why? Also, how does a person work around this? I need the message to be retried. I understand that a web service cannot participate in an XA transaction, but it seems to me any failure within the message flow should cause a retry on the JMS queue.
    Thanks.
    Edited by mvcg at 06/11/2008 1:57 PM

    You should remove the Route Node since it should only be used in HttpProxy.
    Instead use just the request pipeline for your routing.
    if (condition1)
    Service Callout (or publish) to Service1
    else if (condition2)
    Service Callout (or publish) to Service2
    else
    Rasie error?
    You shouldn't need to reply with failure. Any errors in the service callout or publish should go to exception handling if you use QoS exactly-once.

  • Remote Resources: "A problem with the system proxy caused the connection to fail: End of file"

    Hi, I am trying to use "Remote Resources" on the current version of the Microsoft Remote Desktop for Android app, I can input the webfeed and it even shows the apps that I have configured on the server for "Remote App", sadly whenever
    I try to load any of the RemoteApps, I receive an error stating " A problem with the system proxy caused the connection to fail. End of File".
    I don't know what I can do to fix this, I've tried many things to no avail, also, normal Remote Desktop connections from the Microsoft Android app work flawlessly to the server.
    The relevant log is the following:
    [2014-Jan-09 04:40:54] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-09 04:40:54] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||ZWaveUtil
    remote.workingdirectory 
    remote.name ZWave Adapter Utility
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=administrator
      redirectionGUID = 
      proxyHost = 200.5.68.10
      proxyPort = 8080
      sessionId = -1
    [2014-Jan-09 04:40:54] RDP (0): Using HttpConnect proxy at 200.5.68.10:8080
    [2014-Jan-09 04:40:54] RDP (0): Using Basic Authentication with username ''
    [2014-Jan-09 04:40:54] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    [2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
    [2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
    ASIOSocketAdapter (9): readSomething error. message: End of file. instance: 0x5d39d5c0
    RpcOverHttp (9): Stream error in endpoint 0x5abbc170 : A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleRead(): exception: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : Failed to read from channel: -1. instance: 0x5d39d5c0
    [2014-Jan-09 04:40:55] RDP (0): Disconnect initiated by client
    RpcOverHttp (9): Exception in endpoint 0x5abbc170 : Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    [2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    [2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-09 04:40:57] RDP (0): ------ END ACTIVE CONNECTION ------

    My problem is that the "proxy" is the proxy set up by my 3G configuration so, I tried connecting to the remote resources through my work wifi and I get the following:
    [2014-Jan-14 16:58:13] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-14 16:58:13] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||chrome
    remote.workingdirectory 
    remote.name Google Chrome
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username Administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=Administrator
      redirectionGUID = 
      proxyHost = 
      proxyPort = 0
      sessionId = -1
    [2014-Jan-14 16:58:13] RDP (0): Not using any proxy
    [2014-Jan-14 16:58:13] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d474090
    RpcOverHttp (9): Stream error in endpoint 0x5d46b678 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d445158
    RpcOverHttp (9): Stream error in endpoint 0x5d49fa30 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Disconnect initiated by client
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-14 16:58:17] RDP (0): ------ END ACTIVE CONNECTION ------
    Now, I know the host can be resolved because: if I connect to the same host but on a full remote desktop (as opposed to just RemoteApp on it) I have no trouble either through 3G OR through my work connection.
    Moreover, I also tried directly inputting the IP as opposed to the web address of my server, I get the same error, that is the Remote Resources tab is able to access the feed (because it shows the available RemoteApps) but when I click an app it says it can't
    find the Host, here's the log for the connection directly to the IP address/rdweb/feed/webfeed.aspx :
    [2014-Jan-14 17:09:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-14 17:09:27] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||chrome
    remote.workingdirectory 
    remote.name Google Chrome
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=administrator
      redirectionGUID = 
      proxyHost = 
      proxyPort = 0
      sessionId = -1
    [2014-Jan-14 17:09:27] RDP (0): Not using any proxy
    [2014-Jan-14 17:09:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d372f28
    RpcOverHttp (9): Stream error in endpoint 0x5dd6b168 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d378de0
    RpcOverHttp (9): Stream error in endpoint 0x5e9cc1f0 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Disconnect initiated by client
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-14 17:09:31] RDP (0): ------ END ACTIVE CONNECTION ------
    I'm really puzzled here, I've tried checking if ports where open, and ports 443 and 3389 are wide open, I don't know what else it could be.

  • Having trouble with sound quality

    I have had this iPod Touch 2nd Generation for almost 2 years now, and I'm starting to have some troubles with it. The headphone sound quality is now starting to deteriorate. Unless the headphones are plugged in a specific way, either one bud goes out, or the sound quality goes down, as there is a lot of static and crackling, and I've had experiences with it actually shocking my ears while I'm listening.
    I have tried a new pair of headphones, and this does nothing.
    My iPod is obviously beyond the manufacturer's warranty, and it's up-to-date with the latest update. Is there anything I can do?

    Sounds like your headphone jack may need replacing.
    Check out the new remodeled MacOSG website! 24-hour Apple-related news & support.
     MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

  • MDB with foreign JMS : WLS 9.23

    For the love of _____ (fill in your own muse of desperation here), is there some categorical statement of whether WLS9.23 actually ***works*** with MDB's and foreign JMS providers? Whereever I search/find, people have trouble with this.
              Some kind BEA sould - please. Please, please please : publish a canonical example of MDB with secured foreign-JNDI provided connx factory, and either a queue or a topic.
              I'm beginning to wonder if this works at all.

    Good morning!
              Categorical Statement: WLS supports JMS spec compliant foreign providers for MDBs, bridges, resource-references, foreign providers. We also support sending a foreign providers message using a WebLogic JMS client.
              For general Tibco integration questions, I recall that the Tibco docs themselves contain WebLogic integration examples. There's also some much mention of Tibco in the out-dated "Using Foreign JMS Providers with WebLogic Server" white-paper on dev2dev.
              That said, there have been definitely been problems with Tibco and MQ's latest release, as they both recently released semi-non-JMS compliant clients that our wrapper code was unprepared to deal with. In short, we were caught unawares when these clients stopped supporting the 1.0.2 APIs even though 1.1 specification clearly requires both 1.1 and 1.0.2 support. Rather than ask Tibco and MQ teams to have them patch their code (an approach we've sometimes taken over the years), we chose this time to enhance our code.
              I think the problems were all fixed by 9.23 - but you may want to contact customer support to see if there are any additional patches required. Alternatively, you can try use a slightly older Tibco client, as presumably their older clients are still able to interoperate with their latest server version (this approach works with MQ).
              Tom

Maybe you are looking for