Jms error handling

Hi,
          I send an xml-file on a jms-queue... When the xml-file is invalid, (eg. blabla), the xml-file is redirected to an error-jms-queue...
          I've a listener on this queue. I want to receive the incoming message, but all I get to see, (I think) are a few characters... I supose it's some kind of address...
          Has anyone an idea how I can get, the data that the user has send? This is very trivial...
          Here is the code of my listener of my error-jms-queue
          * @ejbgen:message-driven
          * clients-on-same-server="true"
          * destination-jndi-name="test.error"
          * ejb-name = MdbError
          * destination-type = javax.jms.Queue
          public class MdbError
          extends GenericMessageDrivenBean
          implements MessageDrivenBean, MessageListener
          private static Logger log = Logger.getLogger("wlw.Error");
          public void onMessage(Message msg) {
          try {
          msg.acknowledge();
          BytesMessage mesg = (BytesMessage)msg;
          } catch (Exception e ){
          System.out.println("exception... => " + e);
          Thx in advance...
          Ann

Hi,
          this gives a ClassCastException.
          I've this test in my errorHandling:
          if (msg instanceof TextMessage)
          System.out.println("TextMessage: " + ((TextMessage) msg).getText());
          else if(msg instanceof ObjectMessage)
          System.out.println("ObjectMessage: " + ((ObjectMessage)msg).getObject());
          else if(msg instanceof StreamMessage)
          System.out.println("StreamMessage: " + ((StreamMessage)msg).readString());
          else if(msg instanceof BytesMessage)
          char t = ((BytesMessage)msg).readChar();
          System.out.println("BytesMessage: " + ((BytesMessage)msg).readUTF());
          else if(msg instanceof MapMessage)
          System.out.println("MapMessage: " + ((MapMessage)msg).getString("msg"));
          I always gets a message of type BytesMessage.
          Thx in advance

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.

  • JMS adapters and error handling

    Dear all,
    1. I have a scenario in which XI will be getting messages from Two JMS servers located in different locations. The messages from the two servers have no relation but XI has to check if messages are present in any of the servers and poll them. So can anyone suggest me a better approach. I can use two sender adapters and use a BPM. Is there any other way to do it avoiding BPM?
    2. How do I delete the message from the JMS Queue once it is processed?
    3. In the Reciever side I have to send messages to two different target systems based on a condition. From the sender side a field (value) is passed which will check these conditions. If the value contains one of the target system names, the message has to go to that particular system and if the value contains both the target system names, the message has to go to both the target systems. I think this can be done in BPM but please recommend an approach for this.
    4. I need to do error handling both in the adapter side and in mapping level. Kindly give suggestions for the same.
    Expecting your replies soon,
    Harikumar. S

    Hi ,
    Refer to following blogs ,
    JMS Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20the%20content%20conversion%20module%20with%20the%20xi%203%20j2ee%20jms%20adapter
    /thread/217893 [original link is broken]
    JMS adapter -Message format pre-requisites
    /people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    Thanks ,
    Suvarna
    Award pts if ans helps .

  • How to stop execution after generating error message in an error handler?

    I am working on ALSB 3.0.I have a proxy consisting of 2 stages in a pipeline pair. I have error handlers for each of the stages. The first stage contains schema validation action. Whenever the schema validation fails,control should transfer to error handler.
    The error handler has a publish action and in request action I am calling an xquery transformation to generate error message.Publish action should publish message to a jms based business service configured. My questions are:
    1. After getting into the error handler, the first alert msg configured inside request action (of publish action) is generated.Subsequent actions to generate error xml message and to replace the contents of errorXml in $body are not executed.And so no error message is generated or published.
    2. I have also configured a reply with failure. Inspite of that,the control shifts to next stage in request pipeline and execution continues.
    Can anyone tell me where I need to do the corrections.
    Cheers.
    Edited by: arrajago on Jun 15, 2009 11:55 PM

    Got the answer.Generate error xml outside publish action.Replace action has to placed inside Publish's request action.To stop execution,use Reply action after Publish.

  • Error handling for distributed cache synchronization

    Hello,
    Can somebody explain to me how the error handling works for the distributed cache synchronization ?
    Say I have four nodes of a weblogic cluster and 4 different sessions on each one of those nodes.
    On Node A an update happens on object B. This update is going to be propogated to all the other nodes B, C, D. But for some reason the connection between node A and node B is lost.
    In the following xml
    <cache-synchronization-manager>
    <clustering-service>...</clustering-service>
    <should-remove-connection-on-error>true</should-remove-connection-on-error>
    If I set this to true does this mean that the Toplink will stop sending updates from node A to node B ? I presume all of this is transparent. In order to handle any errors I do not have to write any code to capture this kind of error .
    Is that correct ?
    Aswin.

    This "should-remove-connection-on-error" option mainly applies to RMI or RMI_IIOP cache synchronization. If you use JMS for cache synchronization, then connectivity and error handling is provided by the JMS service.
    For RMI, when this is set to true (which is the default) if a communication exception occurs in sending the cache synchronization to a server, that server will be removed and no longer synchronized with. The assumption is that the server has gone down, and when it comes back up it will rejoin the cluster and reconnect to this server and resume synchronization. Since it will have an empty cache when it starts back up, it will not have missed anything.
    You do not have to perform any error handling, however if you wish to handle cache synchronization errors you can use a TopLink Session ExceptionHandler. Any cache synchronization errors will be sent to the session's exception handler and allow it to handle the error or be notified of the error. Any errors will also be logged to the TopLink session's log.

  • Reporting Action in Error handler

    We have a requirement to use Reporting action in the Service Error Handler to capture some details for the reports. We are using the JMS Messaging Proxy and in that transport options, we are using "Transaction" as Enabled to retry the failed messages.
    Now when ever there the flow fails and is goes to the service error handler and there are no reports getting generated in the "Opeations->Messaging Reports". But when the "Transaction" option in the Transport option is disabled in the Proxy, we are getting the reports.
    Is there any way to get the Reports generated with the "Transaction" option enabled ?

    Then your reporting provider is handled within the same XA transaction as your proxy. Either both commit or both rollback. If you want to report error than you can still use XA transaction for your proxy, but you can't use it for your reporting provider.

  • Query related to error handling

    hi All,
    In my proxy flow i have stage level error handler which is configured to an alert pointing to an JMS error queue. When i added service level error handler with same alert.
    I am getting duplication of the same error message by stage and service error handler.
    For every error i am receiving 2 error messages at the error queue.
    Is there any option in ALSB which allows me stop the duplication.

    Pls check the following script --
    SQL>
    SQL> create or replace package uu_test
      2  is
      3  begin
      4    test
      5  end;
      6  /
    Warning: Package created with compilation errors.
    SQL>
    SQL> select * from user_errors
      2  where type = 'PACKAGE';
    NAME                           TYPE           SEQUENCE       LINE   POSITION
    TEXT
    UU_TEST                        PACKAGE               1          3          1
    PLS-00103: Encountered the symbol "BEGIN" when expecting one of the following:
       end function package pragma private procedure subtype type
       use <an identifier> <a double-quoted delimited-identifier>
       form current cursorHope this will fullfill your requirement.
    Regards.
    Satyaki De.

  • How to catch/read mal-formed xml at Error Handler.

    I have added Error Handler at starting node of Message Flow in a Proxy Service and its(Proxy Service) listenning to a JMS queue.
    So when i am putting a mal-formed XML into the JMS queue, getting "Failure while unmarshalling message: Failed to parse XML text" error at ALSB server log.
    But i am not able to capture the mal-formed xml inside Error Handler node.
    Can any one help me how to capture input mal-formed xml in Message Folw.
    Thanks in Advance.
    Regards.
    Deba

    Re: How to catch malformed xml using error handling mechanism in from a proxy? Had a solution for similar issue. It appears that in-case of malformed XML, $body will not be populated with faulty xml snippet. One way out of this solution is, design your service as Text service and create another service isXML as explained in my above reply.
    Thanks
    Manoj

  • Log format of SAF error handler

    Is there any link/document available that gives an idea of the format to provide in the "log format" while creating SAF error handler?

    Here's a little more detail that should help:
    Using the same JMS module that contains the configuration for the original imported destination, create another imported destination with the exact same targets as the imported destination. Let’s call this destination the “SAF error dest”. Configure the remote destination for this SAF error destination so that it references some JMS Server queue (call it the “error queue”).
    Ideally for performance and simplicity, this error queue should run local to the "SAF error dest" -- so, for example, if there are 3 SAF Agents on three JVMs that host the imported destinations, there should also be three JMS servers on these same JVMs that use the same persistent store as the SAF agents, and the error Q should be a "uniform distributed queue" that's targeted to the three JMS servers (using advanced "subdeployment" targeting).
    Configure the original imported destination to use the “SAF error dest” as its error destination.

  • How to take control back from service error handler in osb

    I am using osb to send data to multiple services at the same time.since x query is a procedural language if any single operation fails the flow goes to service error handler which calls a BPEL webservice and logs the error in a database but the control doesnt comes back to my code I have tried everything including RESUME,REPLY operations but all in vain similarly i cannot use service callout call to my business service because its not allowing to select my BPEL wsdl operation

    If your statement "the control doesnt comes back to my code" means you expect that your xquery will continue in processing than your expectations are just too high. :-)
    Resume action is supposed to resume the next action in the message flow. It means the action that follows the action which caused an error.

  • LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

    [LV 7.1 Pro on WinXP for Tablet PC's]
    I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File.  I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
    Subsequent investigation revealed:
    Neither AEH option in Options>Block Diagrams were checked.
    Network problems had occurred around the time that the app had hung.  All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
    My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled.  The error out cluster of New File in my subvi is wired.
    My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled.  Nor does any of their calling VI's.  All three instances also have their error out cluster wired.
    A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true.  That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
    As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions.  As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
    In other words I can find no reason why I should have gotten the problem AEH dialog...
    I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
    Any ideas?

    Very good.
    Write Characters to File.vi>Open/Create/Replace File.vi>New File
    New File throws the error.  Open/Create/Replace strips the hierarchy from the source of the error.  Write Characters passes it to the General Error Handler.  I never looked above O/C/R file in the hierarchy except for enable automatic error handling property.  The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that. 
    The real irony is that Write Characters was being used to log error cluster data to an error log file...
    Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
    Thanx (a bunch)

  • JMS Error when using OJMS/AQ in OC4J 9.0.2 but not in OC4J 9.0.3

    Hi,
    I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
    JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
    During the start-up of 9.0.2 container, it successfully connects with Oracle AQ, finds queues in AQ but finally comes back with an error message saying "JMS Error: invalid arguments in call". It does not provide any more information about the error.
    Does any one have got any clue why this error message occur during startup? Any assistance is appreciated.
    The following is the definition of Resource provider in config/application.xml:
    <resource-provider class="oracle.jms.OjmsContext" name="ispojms">
    <description> OJMS/AQ </description>
    <property name="url" value="jdbc:oracle:thin:@Hduna1.corporatetesth.nsw.edu.au:1527:ISP"></property>
    <property name="username" value="ISPDBA"></property>
    <property name="password" value="******"></property>
    </resource-provider>
    The user ISPDBA is given all privileges for AQ in Oracle DB.
    The Message Driven Bean's definition in deployment descriptors:
    Ejb-jar.xml:
    <ejb-jar>
    <enterprise-beans>
    <message-Long postings are being truncated to ~1 kB at this time.

    Hi Balaji,
    What most likely is happening is that you have mismatched versions of apapi.jar (client side) and the database, thus the reason for the "invalid arguments in call" error you're seeing.
    If you're using 9.0.1.3 of the database it should be patched with patch #2416054. Go to Metalink and do a search for this patch to find it. You can then use the apapi.jar that comes with the patched version of the DB or the apapi.jar that comes with v9.0.3.
    By the way, v9.0.3 and 9.0.1.3 + patch is a J2EE 1.3 compatible JMS server.
    I'm guessing that you used the apapi.jar that came with v9.0.2 with the v9.0.1.3 database and that you've probably already applied the above patch. If you have then just take the apapi.jar that came with v9.0.3 and use it in your v9.0.2 environment.
    In short:
    v9.0.3 apapi.jar matches with v9.0.1.3 + patch
    v9.0.3 apapi.jar also matches with v9.0.1.4
    v9.0.2 apapi.jar matches with v9.0.1.3
    Hope this helps...
    John
    Hi,
    I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
    JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
    During the start-up of 9[i]Long postings are being truncated to ~1 kB at this time.

  • Error handling in process chain-doubts

    Hi ,
    I have some doubts in error handling of process chains.
    1) I have  aprocess load infopackeage and subsequent process is update fromPSA.
    process load infopackage got failed  , so i loaded  the IP manually and repeated the next i.e process update from PSA .
    How to correct the process chain from now?
    2) I have  aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed  , so i loaded  the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
    Plz  help me  as this is urgent and daily i have to deal with this  issues. If any documents on error handling is greatly appreciated.
    My mail id is [email protected]
    Regards,
    Pavan

    Hi Pavan,
    Hope the following links will give u a clear idea about process chains and clear ur doubts.
    Business Intelligence Old Forum (Read Only Archive)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Errors in monitoring of process chains can be categorized into 4 different sections...
    Master data - Full Update
    Master data - Delta Update
    Transaction data - Full Update
    Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
    Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
    There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
    In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
    For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
    U can even look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    ****Assign Points if Helpful****
    Regards,
    Ravikanth.

  • Error handling function: ORA-20001: get_dbms_sql_cursor error:ORA-00942: table or view does not exist  is not trapped. Why?

    Why APEX 4.1 Error handling function does not trap  the error of missing table?
    Say, I create simple application with single IR report page and I also assign standard simple error handling function.
    Function works perfectly, except but this case:
    If I just drop a table used by report page and then refresh the page I am getting usual APEX error message:
    ORA-20001: get_dbms_sql_cursor error ORA-00942: table or view does not exist
    and error handling function is not invoked at all.
    Is this a feature or a bug?

    Hi,
    Check the corrections given in the note 990764:
    Reason and Prerequisites
    Up to now, using a characteristic with its own master data read class as the InfoProvider was not supported. This is now released but it is not available for all modelings. Using the attributes in the query is not supported for characteristics that have their own master data read class. Using the attributes in the query causes a termination. The following errors may occur in this case:
    ORA-00942: table or view does not exist
    Fehler in CL_SQL_RESULT_SET  Include NEXT_PACKAGE
    RAISE_READ_ERROR in CL_RSDRV_VPROV_BASE
    Solution
    SAP NetWeaver 2004s BI
               Import Support Package 11 for SAP NetWeaver 2004s BI (BI Patch 11 or SAPKW70011) into your BI system. The Support Package is available once Note 0914305 "SAPBINews BI 7.0 Support Package 11", which describes this Support Package in more detail, has been released for customers.
    In urgent cases you can implement the correction instructions.
    The correction instructions contain the tightened inspection for characteristics.
    Regards,
    Anil Kumar Sharma .P

  • Issue with SRDemo error handling

    Hi All,
    Glad the forums are back up and running. In debugging some error-handling issues in our own application, I found an issue in the error handling code of SRDemo. I thought I'd post the issue here, as many of us (myself included) use some SRDemo code as the basis for our own applications.
    The issue can be found in the oracle.srdemo.view.frameworkExt.SRDemoPageLifecycle class, specifically in the translateExceptionToFacesErrors method. I'll show the code that has the issue first, and explain the issue afterwards:
            if (numAttr > 0) {
                Iterator i = attributeErrors.keySet().iterator();
                while (i.hasNext()) {
                    String attrNameKey = (String)i.next();
                     * Only add the error to show to the user if it was related
                     * to a field they can see on the screen. We accomplish this
                     * by checking whether there is a control binding in the current
                     * binding container by the same name as the attribute with
                     * the related exception that was reported.
                    ControlBinding cb =
                        ADFUtils.findControlBinding(bc, attrNameKey);
                    if (cb != null) {
                        String msg = (String)attributeErrors.get(attrNameKey);
                        if (cb instanceof JUCtrlAttrsBinding) {
                            attrNameKey = ((JUCtrlAttrsBinding)cb).getLabel();
                        JSFUtils.addFacesErrorMessage(attrNameKey, msg);
                }Now, this bit of code attempts to be "smart" and only show error messages relating to attributes if those attributes are in fact displayed on the screen. It does so by using a utility method to find a control binding for the attribute name. There are two issues with this code, one obvious, and one that is a bit more subtle.
    The obvious issue: if there is a binding in the page definition, it doesn't necessarily mean that the attribute is shown on the screen. It's a good approximation, but not exact.
    The other issue is more subtle, and led to errors being "eaten," or not shown, in our application. The issue comes if you are using an af:table to display and update your data. In that case, the findControlBinding will not find anything for that attribute, since the attribute is contained within a table binding.
    Just posting this as a word to the wary.
    Best,
    john

    somehow, this message got in the wrong thread....
    Hi Frank,
    Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
    It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
    At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
    John
    it was supposed to be something like:
    Hi Frank,
    Thanks for the reply. I was simply posting this here so that people who use the SRDemo application techniques as a basis for developing the same functionality in their own apps (like me) can be aware of the issue, and avoid lots of head-scratching to figure out "what happened to the error message?"
    John

Maybe you are looking for

  • Can I use Mac Book at same time as watching something on Apple TV?

    Hi I recently purchased a Mac Book Pro along with Apple TV. I purchased a movie via Lovefilm (UK based site) on a "watch it now" basis.  I then proceeded to watch using Airplay and "mirroring".  However doing it this way I quickly realised that while

  • Setting Colors on GeometryArray

    I have created a scene using VRML97 that creates a GeometryArray. I would like to be able to change the colors of the vertices using setColor but Java3D is reporting the error that GeometryArray has no color. Do I have to include color values in the

  • How to erase a Partition?

    I want to erase the secon partition of 32gb that is been used for windows, I changed to VMware Fusion so I dont need to have a second partition.(I think) So I want to have in just one. But How to erase that 32gb Partition? on Disk utilities doesn't l

  • Server Admin not responding after upgrade to 10.5.6

    Mac OS X 10.5.6 Server Upgraded from 10.5.5 to 10.5.6. When you open Server Admin and click on the server in the right hand side list. It will not show any information. Removing the server and re-adding it solves nothing. Connecting from another comp

  • Condition Table creation for Taxes (TAXINN)

    I want to create a condition table for Taxing procedure with application <b>TX</b>  with the following fields : <b>Plant , Control Code</b> Kindly tell me the SPRO path where i can create a condition table for Taxes. Regards Jyotsna