Missing Message Attributes: URL/HTTP Destination

Hello,
following scenario:
There is a sync. interface between SAP PI ante the Paypal API within the HTTP adapter calling a dynamic URL.
The dynamic URL is created as mentioned in this blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7264. [original link is broken]
Also the HTTP adapter is configured as described (Adapter Specific Message Attributes and URL are flagged).
Following error occours when testing the call:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_MISSING_URL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Dynamic Header - Missing Message Attributes: URL/HTTP Destination</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there sth. special I have to consider in the HTTP Adapter?
Thanks in advance,
André

Hi Michal,
I´m passing the URL to the attribut "TargetURL" by using a UDF in my mapping.
In the adapter I have flagged "URL".
So the value of TargetURL set in mapping shoul be used as destination in the adapter.
Please have a look onto my UDF used in MM:
http://img408.imageshack.us/i/udf.jpg/
Adapter settings:
http://img691.imageshack.us/i/adaptersetting1.jpg/
http://img339.imageshack.us/i/adaptersetting2.jpg/
How can I check that the TargetURL is successfully set as a dynamic parameter?
Thanks,
André

Similar Messages

Error using XI HTTP adapter specific message attribute URL parameters

Hi XI gurus, in our XI 7.0 SPS11,
we have problem using URL parameters of plain HTTP receiver adapter.
If I set Adapter specific message Properties in communication channel and activate switch for Apply URL parameters (using Parameter 1 to 5) filling them using message mapping, we have no effect; instead we have error "Dynamic Header - Missing Message Attributes: Fields/Parameters".
We carried out this test:
1. not using adapter specific message attribute and setting
a static URL target with fixed parameters it runs correctly.
2. using adapter specific message attribute for target
URL and URL parameters both doesn't runs correctly.
3. using adapter specific message attribute only for target
URL doesn't run correctly.
These attribute key used for URL parameters:
URLParamOne
URLParamTwo
URLParamThree
URLParamFour
URLParamFive
Namespace: http://sap.com/xi/XI/System/HTTP
Can you solve this issue? Are there oss notes, corrections, ...
Thanks in advance.
Marco Tricase

Some other test done with TCP gateway.
Activated adapter specific message properties for
*URL
*HTTP Header fields (one header field named "lisca")
*URL Parameters (one param named "objectType")
The HTTP message catched by TCP Gateway
POST /csl/cslinker HTTP/1.0
content-type: text/xml; charset=UTF-8
content-length: 318
connection: close
accept: /
user-agent: SAP Web Application Server (1.0;700)
host: 10.10.43.94:54000
accept-encoding: gzip
<?xml version="1.0" encoding="UTF-8"?>
seems nothing has been generated, and obviusly URL and params have been set in message mapping.
Hope some guru has been solved the issue ...
Pasquale Rossiello

How to access Adapter Specific Message Attribute in my own adapter module

Hi,
I'm developing a mail adapter customer module. Now I have a requirement about getting the CC information from mail. Even if I
checked the option of "use mail package" when configing sender Mail Adapter, I still can not get CC information in my module
because it is not included in mail package.
I got to know CC information is included in ASMA(Adapter Specific Message Attribute), but how can I access ASMA in my module?
Till now I know there are two ways to access ASMA
1. use AF_Modules/DynamicConfigurationBean XI standard module to access ASMA.I did it as below:
add this module in front of my own module, then set key: write http://sap.com/xi/XI/System/Mail SHeaderCC and value :
message.refToMessageId(which message property should be put here?). I'm trying to get it by message.getRefToMessageId() in my
own module. But what happens is not as I expected, I get null instead of CC information. Which step I did wrong?
2. use mapping api
 DynamicConfiguration conf = (DynamicConfiguration) container
 .getTransformationParameters()
 .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
 DynamicConfigurationKey key = DynamicConfigurationKey.create(
 http://sap.com/xi/XI/System/Mail,
 SHeaderCC);
but how can I get container object in my module?
Is there any other way to access ASMA in customer module?
Thanks

hi,
>>>>but how can I access ASMA in my module?
have a look at this blog:
/people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
and try getMessageProperty
it's also here:
in Adapter-Specific Message Attributes link
http://help.sap.com/saphelp_nw04/helpdata/en/17/50d440e14f8431e10000000a1550b0/frameset.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Need to post to HTTP destination with a dynamic URL

I have a working interface that posts to a static URL using an HTTP via an SM59 connection.
however i now need to do something similar, but use a dynamic field from the data to post as part of the url...
so it will be something like...
http://host.fqdn:port/path/goes/boldfield1bold/here/to/remove
field1 being a variable in my xml.
i guess i post to a URL with URL Address instead of HTTP destination, and i can use the header fields in adapter specific message attributes... however i do not want to send the xml.... so do i have to map just the single field to my target xml? how do i not send the xml as it is integrated within the URL?
how do i add the field1 within the path: /path/goes/boldfield1bold/here/to/remove into the options within the communication channel?
does that make sense?

Hi Barry,
If I understood well, and you have one part of the target URL fixed, and the other one is going to be dynamic.
You can use, as you said, the ASMA for HTTP adapter, and in the middle of the mapping you can create a simple UDF to create the URL. But as the result of that UDF, you just return the same value that you'd map if the UDF didn't exist.
For example you can use a funcion "setURL" and you can have 2 inputs: "url" and "companyname", but you just return "companyname" that is the value that really has to be mapped.
I hope this helps you.
Juan.

Proxy receiver channel with HTTP destination or URL address?

Hi Experts,
     I have a scenario as below:
     (Webservice Client)SOAP --> PI --> PROXY(SAP ECC).
     A webservice client calls PI using SOAP. PI then sends the request to SAP ECC using PROXY.
    I am using AAE. Therefore I have ICO.
    In the receiver PROXY channel I have given:
   ADAPTER TYPE: SOAP
   Transport Protocol: HTTP
   Message Protocol: XI3.0.
   Under connection parameters:
   Addressing Type dropdown as 2 entries HTTP destination and URL address.
   In what cases i should use HTTP destination and URL address respectively?
   Which option is preferred?
   Do they work same or differently? How?
   When I select HTTP destination where should I create the corresponding RFC destination? In PI ABAP stack using SM59 or PI NWA?
   If this HTTP destination is created in PI ABAP stack using SM59 then what type it should be? H? or G?
Thanks
Gopal

Hi Gopal,
In creating XI receiver communication channel, you have 2 options for Addressing Type:
1. URL Address - no need to create RFC destination. You just have to specify the XI receiver host name, HTTP port, path (/sap/xi/engine?type=receiver), Authentication data (logon details for SAP Client number of the PI system).
2. HTTP Destination - create RFC destination in SXMB_ADM and specify the RFC destination name in your receiver communication channel.
For SAP documentation, see this link:
http://help.sap.com/saphelp_nwpi711/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm?frameset=/en/e1/091640a991c742e10000000a1550b0/frameset.htm&current_toc=/en/43/96cbccb9335b77e10000000a11466f/plain.htm&node_id=5
Regards,
Naveen.

HTTP Destination Missing issue in Application Servers(ERP)

Hi All
When i'm trying to trigger the message from ERP to XI, I'm getting error message as HTTP destination missing in ERP system.
I've created the HTTP Destination & added in SXMB_ADM.
Still I'm facing the problem,
Please let me know the reason.....
Regards
Nandan

Hi Venu,
Thanks for ur replay
I've checked
SLDCEHCK
SLDAPICUST
SXMB_ADM check also working fine.
SPROXY , evrything is working fine, but still i'm encountering the Error,
HTTP destination is missing.
Regards
Nandan
Edited by: Nandan ND on Jul 2, 2010 5:07 PM

HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)

Hi Experts,
I am working on ABAP Proxy -> File scenario. When I trigger message in ECC, it is giving error.
When I go to SXI_Monitor in ECC, the message is shown as red with error message "HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)". But the RFC destination PI_INTEGRATIONSERVER exists and when i tested this connection I got 500 empty request received message.
I have configured in SXMB_ADM the ECC system as application system and mentioned 'dest://PI_INTEGRATIONSERVER' as corresponding integration server.
Could you please help me in resolving this issue?
Thanks and regards,
Prasad

Hi Prasad,
Ensure below items in your ECC system.
1. goto SM59
2. ensure your RFC - PI_INTEGRATIONSERVER has this entry '/sap/xi/engine?type=entry' (without quots)
3. Target Host has value your PI/XI hostname and correct port number (HTTP)
4, for Logon& Security Tab, ensure to use userID PIAPPLUSER and correct password (saved)
or Service user of Integration engine (maintained in Exchange profile)
You can write back to me if any further help required.
Regards
Sekhar
Edited by: sekhar on Dec 24, 2009 6:57 PM

Error in SXI_CACHE and reading HTTP destination: INTEGRATION_DIRECTORY_HMI

I have been going over many posts etc trying to figure out why this quit working. Basically everything was working fine, and I did a Integration Process Scenario and uploaded that, once that was complete I started getting cache errors that where affecting everything else already configured in XI.
I have tested in SM59 INTEGRATION_DIRECTORY_HMI and when I put in path
/dir/hmi_cache_refresh_service/ext I get back a 200 response on connection test
and put in path /dir/cacheRefresh I get a 500 response which I assume both are fine,
I have also tested by the ping test in sicf using PIISUSER along with the url test of http://<host name>:<port>/dir/hmidiag/ext?method=info all was successful
So the error seems to come when I run sxi_cache
If I do a delta cache it comes up with the following error Prefix number: entry missing for system PIT client 300
If I do a full cache refresh it runs in the background (and while it runs all the other scenario's work) but after the full cache comes back it has Unable to refresh cache contents with the message of Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.
Also once this error is checked all other scenerio's quite working again with the following message
XIServer:UPDATE:Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI
Does anyone have any ideas?
I def award points
Cheers
Devlin

Hi,
I don't know if this is the exactly case we have here... but in our PI DEV and PRD environments it does not happen. In our QAS environment this error occurs everytime we create/change some integration scenario object and activate it. Then, all outbound interfaces start with this error. To solve it we go for a full refresh, delete Adapter Engine cache and restart ICM.
We are trying for a long time to search why this happens only on QAS environment without success... But thanks good it does not happen in PRD
regards.
roberti

Dynamic Configuration of HTTP Destinations in SOAPReceiver

Dear PI Developers
I'll define a dynamic Configuration for my HTTP Destination in SOAPReceiver with XI3.0 Protocol.
The solution for that is to use an Adapter Module to set the dynamic Configuration Value.
Process: ... > SOAP Receiver > MyAdapterModule, set HTTP Destination > SOAP Receiver, send Message to HTTP Destination
URL-Adressing work's fine
This works fine for URL-Adressing, here's my Java Code from my Adapter Module:
Message message = (Message) inputModuleData.getPrincipalData();
message.setMessageProperty(new MessagePropertyKey("TServerLocation", "http://sap.com/xi/XI/System/SOAP"), "http://domain.com/foobar");
HTTP Destination, how it works?
If I'll use HTTP Destination as Adressing Type but the HTTP Destination will not set.
I think the "TServerLocation" Property don't work for the HTTP Destination, but I don't find a Property in:
Configuring the Receiver SOAP Adapter - Advanced Adapter Engine - SAP Library
My Questions
Did someone know the coresponding property name for HTTP Destinations instead of "TServerLocation"?
Are there other Solutions to set the HTTP Destination dynamicaly, for Example with variables %my_http_dest% ?
How can I set my own variables %my_http_dest% in my Adapter Module?
Background
We have a lot of Destinations and a lot of Szenarios and won't create a SOAPReceiver and Routing for each Destination in each Szenario.
The Destination depends on a HTTP Header Parameter from Sender, I'll map this Parameters to the coresponding HTTP Destination in the Adapter Module, that's the same Mapping for all Scenarios. To keep the performance, I cache this Routing Table in the Adapter Module.

Here's a way to misapplay "mesage:{var}" variables:
SAP NetWeaver XI: Variable Substitution with Adapter-Specific Message Attributes via DynamicConfigurationBean
But it is a dangerous solution, I think we use URL-Adressing in place of HTTP Destination

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
 <Data>
 <Mesage>
 <gl_update>
 <header>
 <ean1>
 <ean2>
 </header>
 <gl_update>
 <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

Calling ABAP Web Service at https destination

Hi!
I have created an ABAP Proxy that calls an external web service at an http destination. When trying the same for a service at an https destination I get the error message 
HTTP error (return code 110, message "" when specifying the URL for the WSDL file. I tried one of Thomas Jungs blogs on HTTPS services (/people/thomas.jung3/blog/2005/05/13/calling-webservices-from-abap-via-https), but here he says that "When we begin to get differences (From http setup) is in the setup of the Logical Port". Am I missing something? Some configuration to be done?
Thanks for your input!
-Ole
Message was edited by:
Ole Mugaas

Hi!
Do you mean trying to access the WSDL through an already defined HTTP connection? My problem arises when trying to enter the URL to the WSDL during proxy generation...

Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute

This is a Bursting problem under EBS 5.6.3. In production we have 5.6.2 and since our development system to 5.6.3 has been upgraded, the following error occurs on every single Burst being done using the Concurrent Manager only:
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1502)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1408)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1350)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1180)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
 at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:1340)
 at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:1297)
 at oracle.apps.xdo.batch.DocumentProcessor.process(DocumentProcessor.java:213)
 at xxwel.ebs.xmlp.XXWELBurster.processDocuments(XXWELBurster.java:143)
I can run the same file through 5.6.3 ($JAVA_TOP) libraries mounted on my JDev with no problems. Also the same XML file runs fine on Production under 5.6.2 - no problems. I have also checked the XML file using a syntax checker. I know this is not a syntax issue even though it looks like it.
Could someone point me in the right direction - explain what this means. Getting desperate as 5.6.3 will be going into production soon and all Bursting will fail with this error. I can't get the simplest XML File to Burst - NOTE this is only occurring on the EBS system (even running without the CM ie. a standalone java main it fails). I think this has something to do with the XML parser version and the EBS environment.
Please help...

Hi Tim, good thinking - wouldn't have thought to check this file. Anyway can confirm that the problem is happening with multiple burst control files so I haven't checked the files themselves as the problem seems systemic. anyway here is an example.
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/XXWEL_BIP_UNI_INVOICES/LIST_G_CUSTOMER_NUMBER/G_CUSTOMER_NUMBER">
<xapi:delivery>
<xapi:email server="mailwa01" port="25"
from="${ADMIN_EMAIL}" reply-to ="${ADMIN_EMAIL}">
<xapi:message id="111" to="${ADMIN_EMAIL}" attachment="true" subject="Unigas Inv
oice No: ${TRX_NUMBER}">
</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="pdf" delivery="111">
<xapi:template type="rtf" location="/u02/prod/prodappl/wel/11.5.0/interface/bip/templates/uni_invoice_template.rtf">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I will start stripping the control files to make sure they are not the problem in the meantime.

Adapter-specific message attributes for the JMS Receiver adapter

Dear SAP Community,
We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
       TextMessage outMessage = session.createTextMessage();
       MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
       Destination replyTo = (Destination) replyToQ;
       outMessage.setJMSReplyTo(replyTo);
       outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
       outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
       outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
       outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
       outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
This code is working fine.
Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
Any help is greatly appreciated.
Regards,
Gregory PFISTER
SAP XI Analyst - Holcim

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

[svn:bz-trunk] 15217: Bug: BLZ-508 - If server receives message for an unknown destination it shouldn ' t include the destination name in the error message sent back to the client .

Revision: 15217
Revision: 15217
Author:   [email protected]
Date:     2010-04-05 03:43:36 -0700 (Mon, 05 Apr 2010)
Log Message:
Bug: BLZ-508 - If server receives message for an unknown destination it shouldn't include the destination name in the error message sent back to the client.
QA: Yes
Doc: No
Checkintests: Pass
Details: Changed the error message to not include destination id. I'm also checking in a few minor fixes I had locally.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-508
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

Thanx Mete, yeah i did...
but i solved it some other way... not entirely sure this was
it though as i was doing a lot of things at once...
it was fds.swc... possibly it was out of date or missing.

I am getting this error message, " The URL is not valid and cannot be loaded" when I try to go to Firefox home. I have uninstalled add-ons, uninstaleed and reinstalled a fresh new firefox which did not help

I am getting the following error message, " The URL is not valid and cannot be loaded" when I try to go to firefox home. I uninstalled add-ons , uninstalled Firefox and then installed a fresh version. Still have the problem.
Thanks for the help

That issue can be caused by a corrupted or incomplete Visual C++ installation (multiple versions can be installed side-by-side; SxS) that is missing some runtime components (Redistributable Packages) that Firefox depends on (problem with an embedded manifest file that specifies a specific runtime version).
You need to install the missing components (e.g. VisualC++ 2005 Redistrbutable).
* https://www.microsoft.com/download/en/details.aspx?id=5638
*[[/questions/908165]] The URL is not valid and cannot be loaded
*[https://bugzilla.mozilla.org/show_bug.cgi?id=713167 bug 713167] - Microsoft.VC80.CRT SideBySide errors, browsercomps.dll

Missing Message Attributes: URL/HTTP Destination

Similar Messages

Maybe you are looking for