JMS-178 Invalid Queue name - (string)

am getting below error
nested exception is oracle.jms.AQjmsException: JMS-178: Invalid Queue name - test.JMS_TEST_QUEUE
When I look deeper into the oracle error message;
JMS-178 Invalid Queue name - (string)
Cause: The queue name specified is null or invalid
Action: Specify a queue name that is not null. The queue name must not be qualified with the schema name. The schema name must be specified as the value of the owner parameter
For this to work does queue must be owned by aqadm if I'm connecting using that account and the queue CAN'T be in test's schema.
DOES queue tables and queue should be in default schema ?
Thanks for all valuable suggetions

Hello,
can you show the corresponding JMS code statement you used here?
Presumably it is a problem concerning missing GRANTs or unqualified (without db schema) access for the JMS user.
Kind regards,
WoG

Similar Messages

  • Invalid Queue name

    Hi,
    I have created a oracle queue and queue table with respective grants like enqueue, and dequeue.
    GRANT ENQUEUE, DEQUEUE  ON Queue_name  TO username;
    And a java application consume those queues.
    The java application is failing with the following error, can one of you please help or shed some light on this?
    JMS-178: Invalid Queue name
    i don't think its DB issue, any insight will be highly appreciated.
    Java folks are complaining its a Grants issue on DB side.
    thanks so much.

    Hello,
    can you show the corresponding JMS code statement you used here?
    Presumably it is a problem concerning missing GRANTs or unqualified (without db schema) access for the JMS user.
    Kind regards,
    WoG

  • JDeveloper - ESB / BPEL - JMS Adapter - prefix queue name with db schema

    When I use the JMS Adapter in ESB to create a new message queue producer or consume using database (AQ) I'm experiencing a problem when selecting the queue.
    I can browse the queue in the database but when I have selected the queue JDeveloper prefix it with the schema name owning the queue.
    Example:
    java:comp/resource/DocumentQueueResourceProvider/Queues/QUEUES.DOCUMENT_IMPORT_QUEUE
    Schema owner is QUEUES and the name of the queue is DOCUMENT_IMPORT_QUEUE.
    The problem is when I try to use it its unable to look up the queue and I have to manually remove the prefix from .wsdl file before deploying it - as with setting mcf.IsTransacted='false'.
    When the resource provider finds the queue and exposes it in the JNDI three it does it without the prefix.
    Question: How do I either:
    a) make the schema prefix be removed by JDeveloper
    b) make the resource provider prefix the queue name with the schema name.
    Anybody?
    Best regards
    Christian Damsgaard

    Try this:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema targetNamespace="http://www.yourcompany.com/msg"
    xmlns:tns="http://www.yourcompany.com/msg"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
    nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD"
    elementFormDefault="qualified" attributeFormDefault="unqualified">
    <xsd:element name="rootnode" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eof}"/>
    </xsd:schema>
    This will result in a single node xml.
    Edited by: user472896 on Sep 22, 2010 10:29 AM

  • Dynamic queue name with JMS Queue XML?

    Hi,
    Is it possible to use dynamic queue name with JMS Queue XML?
    I tried using a variable in the JNDI URL, and supply the value in a package. I specified the following in the JNDI URL in the Topology:
    e.g.
    <JMS_RESOURCE>?d=<DTD_FILE>&s=<SCHEMA>&JMS_DESTINATION=#PROJECT_NAME.dest_var
    I declared and set the variable in a package, then tried to load data from the above data server to database. But executing this package gave me the following error:
    7000 : null : java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
    java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
         at com.sunopsis.jdbc.driver.bg.executeQuery(bg.java)
         at com.sunopsis.jdbc.driver.bh.executeQuery(bh.java)
         at com.sunopsis.jdbc.driver.l.f(l.java)
         at com.sunopsis.jdbc.driver.l.executeUpdate(l.java)
         at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.g.y(g.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)
    Am I doing it wrongly?
    Thanks!

    hi,
    as it's not in Adapter-Specific Message Properties
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    looks like you cannot do it with jms adapter in standard
    use proxy or your own adapter instead
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Invalid column name in query string - using Format function

    In my post just before this one the problem was solved for writing a query string using a date range. The rest of the query string includes the same date field (Call_Date) but formatted as 'MMM-YY'. I get an invalid column name error when I add this field to the query string. Here is the rest of the query string:
    strSql = "SELECT Format(CALL_DATE,'mmm-yy'), " _
    & "HOME_REGION FROM CCC2.CASE_EPRP " _
    & "WHERE (HOME_REGION = 'NCR') AND " _
    "(CALL_DATE >= to_date( '1/1/2002', 'MM/DD/YYYY' )" _
    & "AND CALL_DATE <= to_date( '2/28/2003', 'MM/DD/YYYY' ))"
    In the Access Query tool I can include this field
    Format(CALL_DATE,'mmm-yy')
    and the query runs fine (I just need to make it dynamic using ADO). But in my ADO query string above, I get the invalid column name error. Is there a way I can include
    Format(CALL_DATE,'mmm-yy')
    in my ADO query string? I appologize for not being more familiar with Oracle Sql. Any help greatly appreciated.
    Thanks again,
    Rich

    Thank you very much for your reply. I think I'm getting closer to the solution. Just I got an error message
    "date format not recognized"
    when I add "to_char( call_date, 'mmm-yy' )" to the query string. I tried using all uppercase, but that did not make a difference. Do I need to use to_date inside the to_char maybe?
    to_char(to_date(call_date, 'mmm/yy'), 'mmm-yy')
    Thanks again for your help.
    Rich

  • Help on Dynamic queue name in JMS Adapter

    Hi Experts,
      Could you please explain how to configure dynamic queue name in JMS Adapter.
    My requirement is i would have to add the date and time to JMS Queue Name in receiver JMS Adapter.
    Thanks in Advance
    Chilla

    hi,
    as it's not in Adapter-Specific Message Properties
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    looks like you cannot do it with jms adapter in standard
    use proxy or your own adapter instead
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Passing the queue name to the sender JMS adapter at run time..

    Hello Experts,
    I have a scenario where PI is to pick data from MQ queues. The message type coming from queues is same and the procession needs to be done with PI is also the same.That's the reason why we want to have only one interface processing the data for all the queues.
    My question here is that is there any way where I do not put the queue name in the sender adapter at design time and based on the data availability in the queue let the sender adapter know the queue name to be processed at run time.
    Any suggestions will be greatly appreciated.
    - Rajan

    > My question here is that is there any way where I do not put the queue name in the sender adapter at design time and based on the data availability in the queue let the sender adapter know the queue name to be processed at run time.
    Unfortunately for JMS Sender CC it is not possible, but other way around is possible. I.e. you can dynamically choose the receving queue names by using ASMA "JMSReplyTo" in JMS Sender CC.
    Regards,
    Sarvesh

  • JMS Queue Vs JMS replyTo Queue name for Receiver JMS channel.

    HI,
    I am working with receiver JMS adapter and using the protocol WbeSphereMQ JMS provider.
    Here I could not able to figure out the difference between the following parameter.
    Target tab JMS Queue  and Processing tab-JMS replyTo Queue name.
    I tries the find the same in help.sdn.com but here also not able to find correct information .
    for Processing tab -JMS replyTo Queue name Parameter it is written that "Specify the name of the queue to which the responses are to be sent."
    But what is the use of Target tab JMS Queue Parameter. No information is given against this parameter.
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
    regards,
    Navneet.

    the initial JMS Queue is the queue you will connect too.
    i guess SAP felt an explanation to that was not required....
    SAP does not even bother to explain it here in the specific link to JMS-Provider-Specific Settings (for Webshpere although it does for SonicMQ!).
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/frameset.htm
    I do not use the "ReplyTo" in my current scenarios.

  • JMS ReplyTo Queue Name parameter in the receiver JMS communication channel

    Hi All,
    Can any please explain the use of JMS ReplyTo Queue Name parameter in the receiver JMS communication channel?
    Thanks
    Karthik.

    Hi karthik,
    JMS ReplyTo Queue Name parameter  is used for Specify the name of the queue to which the responses are to be sent.
    Thanks
    Govind.

  • Dynamic Queue names at JMS receiver

    HI All,
                I have a scenario where sender is an RFC and receiver is via JMS  and also get a reply back . JMS is asynchonous but as suggested in other threads it is possible to capture the response by setting some Adapter specific parameters.
                But my problem is the queue name for the response is not constant and it varies from request to request for the response. I have no clue how to achieve this , I tried searching some threads but couldn't come to a conclusion.
                Possibility of dynamic MQ queue selection in one receiver JMS channel
                help on Dynamic queue name in JMS Adapter
    Has anyone come across such a situation ? Please suggest.
    Also In one of threads it was suggested to use Java Proxy?  Please suggest a way forward in this approach too
    Regards,
    Mohan.

    > please refer the link what you provided in section 2.8 mentioned JMS Receiver communication channel will give response back,but i never tried.
    Yest because this document is applicabe for a scenario where request msg will come form sender JMS to XI and then Response will be sent back again to JMS by using receiver JMS adapter. So senario is JMS request --- R3 (via XI) --- R3 response to JMS.
    But here case is different. e.g. RFC --> PI --> JMS  and reply will get back from JMS  to RFC.  So definetly in this case response will come from sender JMS and not from receiver JMS.
    Read sec 2.8 throughly, you will come to know how to set the queue names dynamically for RECEIVER JMS Adapter.
    Regards,
    Sarvesh

  • Column exist but ResultSet.getString(String) return invalid column name

    With oracle 7 db the ResultSet.getString(String) works fine but after the upgrade to oracle 8 db it return invalid column name. ResultSet.getString(int) method works fine.
    Is this a bug in the driver?
    Thanks
    -Reda

    Yes I'm 100 % sure that the columns exist.
    -RedaWell then maybe it's a bug in the Oracle driver. Lord knows it wouldn't be the first time that's happened.

  • Why do the queue names appear to include jms-module name  (+!) ?

    We upgraded our domain from weblogic 8.1 to 10.3.2.
    To get the clustered environment to work, I had to delete the jms-module and recreate (including the FileStore, the Jms-server...).
    After doing all this, When examining the Jms-server Active Destinations,
    (In Settings - Monitoring - Active Destination)
    I see the queue names such as:
    jms-moduleName!queueName
    I can't help but think this is related to this error message in the logs;
    No servers found having jms destination queueName.
    In our single server environment. I did not have to delete and recreate the autogenerated Jms-module and in Active Destinations, the Name shows up as I would expect. In this environment, I do not have the same error as above.
    Is there anyway to stop the prefix, 'jms-moduleName!" from being added to the queue name in Active Destinations?
    How and why is this being added?
    Any comments would be greatly appreciated. THANKS.

    Hi,
    Almost all applications use a destination's JNDI name to look it up (see the JNDI name field for each destination). The "jms-moduleName!queueName" syntax your referenced is generated based on the configured name of the destination, not the JNDI name.
    Some side advice since your setting up a new configuration:
    * If your using distributed destination, I advise taking the opportunity to change your configuration to use the simpler"uniform distributed destination" option. 8.1 and older supported only the older "weighted distributed destination" behavior which requires that each member destination be configured individually -- this is unwieldy, and will (hopefully) be deprecated soon.
    * See [ JMS Configuration Best Practices | http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG ] and [ JMS Performance and Tuning Check List | http://download.oracle.com/docs/cd/E14571_01/web.1111/e13814/jmstuning.htm#PERFM294 ].
    * Always configure quotas and paging, and ensure they are tuned to prevent JVM out-of-memory (as per the JMS Perf and Tuning check list referenced above).
    Hope this helps,
    Tom
    Edited by: TomB on Jun 20, 2010 7:00 PM

  • JNDI Names of JMS server's queue not replicating to cluster

              Am having some trouble configuring a JMS Server and Queues in a clustered development
              environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
              a single machine.
              The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
              names for the Queues appear in the JNDI tree of Server1, but not in Server2.
              When the sending of a message is attempted on Server2, the following occurs:
              javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
              didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
              at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
              This may be a problem with the cluster configuration, but I haven't been able
              to see anything wrong with it.
              Any and all help will be appreciated.
              There is the Config.xml file:
              <?xml version="1.0" encoding="UTF-8"?>
              <Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
              <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
              ListenPort="7001" Name="myserver" NativeIOEnabled="true"
              ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <SSL Enabled="false" HostnameVerificationIgnored="false"
              IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
              <Log Name="myserver" NumberOfFilesLimited="true"/>
              </Server>
              <Security Name="mydomain"
              PasswordPolicy="wl_default_password_policy"
              Realm="wl_default_realm" RealmSetup="true">
              <weblogic.security.providers.authentication.DefaultAuthenticator
              Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authentication.DefaultIdentityAsserter
              ActiveTypes="AuthenticatedUser"
              Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultRoleMapper
              Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultAuthorizer
              Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultAdjudicator
              Name="Security:Name=myrealmDefaultAdjudicator"
              Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
              <weblogic.security.providers.credentials.DefaultCredentialMapper
              Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
              <weblogic.management.security.authentication.UserLockoutManager
              Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
              <weblogic.management.security.Realm
              Adjudicator="Security:Name=myrealmDefaultAdjudicator"
              Auditors="Security:Name=myrealmSTARSIIAuditor"
              AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
              Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
              CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
              DefaultRealm="true" DisplayName="myrealm"
              FullyDelegateAuthorization="true"
              Name="Security:Name=myrealm"
              RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
              <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
              ControlFlag="SUFFICIENT"
              Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
              <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
              ExemptUri="/common/,/images/,/warning.do,/login.do"
              Name="Security:Name=myrealmSTARSIIAuthorizer"
              PolicyDeploymentEnabled="false"
              Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
              <gov.fns.starsii.common.security.audit.STARSIIAuditor
              Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
              </Security>
              <EmbeddedLDAP
              Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
              <SecurityConfiguration
              Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
              Name="mydomain" RealmBootStrapVersion="1"/>
              <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              <FileRealm Name="wl_default_file_realm"/>
              <PasswordPolicy Name="wl_default_password_policy"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII BRSB Pool"
              Password="{3DES}9pslRpr051lR9/NEKdanag=="
              Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
              PoolName="STARSII Store Pool" Targets="MyCluster"/>
              <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
              PoolName="STARSII Store Pool" Targets="MyCluster"/>
              <!--StartupClass
              ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
              DeploymentOrder="250" Name="STARS II Properties Startup Class" Targets="myserver,MyCluster"/>
              <StartupClass
              ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
              DeploymentOrder="500"
              Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
              <StartupClass
              ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
              DeploymentOrder="750"
              Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
              -->
              <MailSession JNDIName="mail/STARSIIMailSession"
              Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Store Pool"
              Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              Targets="MyCluster"
              TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="AffTest" Password=""
              Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
              PoolName="AffTest" Targets=""/>
              <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
              Name="Spy STARSII BRSB Pool"
              Password="{3DES}9pslRpr051lR9/NEKdanag=="
              Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Store Pool 2"
              Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
              PoolName="STARSII Store Pool" Targets=""/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Stars Pool"
              Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
              Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
              Targets="MyCluster"
              TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <Machine Name="MachineA">
              <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
              </Machine>
              <Server Cluster="MyCluster" ExpectedToRun="false"
              ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
              ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
              Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <ServerDebug Name="Server1"/>
              <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
              <KernelDebug Name="Server1"/>
              <Log Name="Server1"/>
              <ServerStart Name="Server1"
              OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
              Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              <WebServer Name="Server1"/>
              <COM Name="Server1"/>
              <IIOP Name="Server1"/>
              <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
              <JTARecoveryService Name="Server1"/>
              </Server>
              <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
              MulticastAddress="226.0.0.244" Name="MyCluster"/>
              <Server Cluster="MyCluster" ExpectedToRun="false"
              ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
              ListenPort="7002" Machine="MachineB" Name="Server2"
              ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <ServerDebug Name="Server2"/>
              <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
              <KernelDebug Name="Server2"/>
              <Log Name="Server2"/>
              <ServerStart Name="Server2"
              Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              <WebServer Name="Server2"/>
              <COM Name="Server2"/>
              <IIOP Name="Server2"/>
              <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
              <JTARecoveryService Name="Server2"/>
              </Server>
              <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
              Notes="This is a system generated default migratable target for a server.
              Do not delete manually." UserPreferredServer="Server1"/>
              <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
              Notes="This is a system generated default migratable target for a server.
              Do not delete manually." UserPreferredServer="Server2"/>
              <Application Deployed="true" Name="STARSII"
              Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
              <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
              <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
              <EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
              <EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
              <EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
              <EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
              <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
              <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
              <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
              <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
              <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
              </Application>
              <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
              StagingMode="nostage" TwoPhase="true">
              <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
              </Application>
              <Application Name="activeportal"
              Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
              StagingMode="nostage" TwoPhase="true">
              <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
              </Application>
              <JTA Name="mydomain" TimeoutSeconds="300"/>
              <JMSServer Name="JobServer" Targets="Server1 (migratable)">
              <JMSQueue CreationTime="1072820642598"
              JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
              <JMSQueue CreationTime="1072820669345"
              JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
              <JMSQueue CreationTime="1088000795852"
              JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
              <JMSQueue CreationTime="1072820687125"
              JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
              <JMSQueue CreationTime="1072820687125"
              JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
              <JMSQueue CreationTime="1072820687225"
              JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
              <JMSQueue CreationTime="1072820687325"
              JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
              <JMSQueue CreationTime="1072820687425"
              JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
              <JMSQueue CreationTime="1072820687525"
              JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
              <JMSQueue CreationTime="1072820687625"
              JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
              <JMSQueue CreationTime="1072820687725"
              JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
              <JMSQueue CreationTime="1072820687825"
              JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
              <JMSQueue CreationTime="1072820687925"
              JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
              <JMSQueue CreationTime="1072820688025"
              JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
              <JMSQueue CreationTime="1072820688125"
              JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
              <JMSQueue CreationTime="1072820688225"
              JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
              <JMSQueue CreationTime="1072820688325"
              JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
              </JMSServer>
              <Machine Name="MachineB">
              <NodeManager DebugEnabled="true" Name="MachineB"/>
              </Machine>
              </Domain>
              

    Internally, many BEA developers and testers use various versions
              of XP with clustering on a daily basis. I don't know what
              is unique about your machine. I suggest raising the issue
              with customer support and/or posting to the clustering newsgroup...
              Andy Frank wrote:
              > It would seems that my OS and the MultiCast config are to blame. The MultiCast
              > test utility worked fine the Win2K machines I tried. Think I will take another
              > look at MS KB article 827536 and/or think about another dev OS.
              >
              > "Andy Frank" <[email protected]> wrote:
              >
              >>Tom,
              >>Thanks for this info.
              >>
              >>My servers don't look like they are running in different subnets (had
              >>a friend
              >>look this over and he concurs).
              >>
              >>My network admin says he hasn't blocked multicast traffic.
              >>
              >>I think the MultiCast test utility is telling me that I have some kind
              >>of multicast
              >>config problem. Output follows:
              >>
              >>------ Begin MultiCast test utility output: ------
              >>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
              >>237.155.15
              >>5.1 -t 15
              >>***** WARNING ***** WARNING ***** WARNING *****
              >>Do NOT use the same multicast address as a running WLS cluster.
              >>
              >>
              >>Starting test. Hit any key to abort
              >>
              >>
              >>Using multicast address 237.155.155.1:7001
              >>Will send messages under the name server200 every 2 seconds
              >>Will print warning every 15 seconds if no messages are received
              >>
              >> I (server200) sent message num 1
              >> I (server200) sent message num 2
              >> I (server200) sent message num 3
              >> I (server200) sent message num 4
              >> I (server200) sent message num 5
              >> I (server200) sent message num 6
              >> I (server200) sent message num 7
              >>java.net.SocketTimeoutException: Receive timed out
              >> at java.net.PlainDatagramSocketImpl.receive(Native Method)
              >> at java.net.DatagramSocket.receive(DatagramSocket.java:680)
              >> at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
              >> I (server200) sent message num 8
              >> I (server200) sent message num 9
              >> I (server200) sent message num 10
              >> I (server200) sent message num 11
              >> I (server200) sent message num 12
              >>------ End MultiCast test utility output: ------
              >>
              >>No "Received message X from server200" messages. I think I need to look
              >>into
              >>configuring multicast communications on my OK (Windows XP Pro, ver 2002
              >>SP1).
              >>I did see MS KB article 827536 about "An IP multicast may not be sent
              >>correctly
              >
              >>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
              >
              >>but
              >>the resolution scared me some.
              >>
              >>Think I will try some things out on another OS and see what that gets
              >>me.
              >>
              >>Any other thoughts on this will be appreciated.
              >>
              >>
              >>Tom Barnes wrote:
              >>
              >>>I too suspect something is going wrong with clustering, I wonder
              >>>if the servers are running in different subnets (even though
              >>>they are on the same box) and/or your network admin has
              >>>blocked multicast traffic.
              >>>
              >>>The MultiCast test utility should help narrow things down:
              >>>
              >>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
              >>>
              >>>Tom
              >>>
              >>>Andy Frank wrote:
              >>>
              >>>
              >>>>Am having some trouble configuring a JMS Server and Queues in a clustered
              >>>
              >>>development
              >>>
              >>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
              >>>
              >>>both on
              >>>
              >>>>a single machine.
              >>>>
              >>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
              >>
              >>>All the JNDI
              >>>
              >>>>names for the Queues appear in the JNDI tree of Server1, but not in
              >>>
              >>>Server2.
              >>>
              >>>>When the sending of a message is attempted on Server2, the following
              >>>
              >>>occurs:
              >>>
              >>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
              >>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
              >>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
              >>>>
              >>>>This may be a problem with the cluster configuration, but I haven't
              >>>
              >>>been able
              >>>
              >>>>to see anything wrong with it.
              >>>>
              >>>>Any and all help will be appreciated.
              >>>>
              >>>>There is the Config.xml file:
              >>>><?xml version="1.0" encoding="UTF-8"?>
              >>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
              >>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
              >>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
              >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              >>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
              >>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
              >>>
              >>>Name="myserver"/>
              >>>
              >>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
              >>>> </Server>
              >>>> <Security Name="mydomain"
              >>>> PasswordPolicy="wl_default_password_policy"
              >>>> Realm="wl_default_realm" RealmSetup="true">
              >>>> <weblogic.security.providers.authentication.DefaultAuthenticator
              >>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
              >>>>
              >>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
              >>>> ActiveTypes="AuthenticatedUser"
              >>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultRoleMapper
              >>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultAuthorizer
              >>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultAdjudicator
              >>>> Name="Security:Name=myrealmDefaultAdjudicator"
              >>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
              >>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
              >>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.management.security.authentication.UserLockoutManager
              >>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.management.security.Realm
              >>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
              >>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
              >>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
              >>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
              >>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
              >>>> DefaultRealm="true" DisplayName="myrealm"
              >>>> FullyDelegateAuthorization="true"
              >>>> Name="Security:Name=myrealm"
              >>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
              >>>>
              >>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
              >>>> ControlFlag="SUFFICIENT"
              >>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
              >>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
              >>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
              >>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
              >>>> PolicyDeploymentEnabled="false"
              >>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
              >>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
              >>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
              >>>> </Security>
              >>>> <EmbeddedLDAP
              >>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
              >>>
              >>>Name="mydomain"/>
              >>>
              >>>> <SecurityConfiguration
              >>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
              >>>> Name="mydomain" RealmBootStrapVersion="1"/>
              >>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              >>>> <FileRealm Name="wl_default_file_realm"/>
              >>>> <PasswordPolicy Name="wl_default_password_policy"/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII BRSB Pool"
              >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
              >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
              >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
              >>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
              >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
              >>>> <!--StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
              >>>> DeploymentOrder="250" Name="STARS II Properties Startup Class"
              >>>
              >>>Targets="myserver,MyCluster"/>
              >>>
              >>>> <StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
              >>>> DeploymentOrder="500"
              >>>> Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
              >>>> <StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
              >>>> DeploymentOrder="750"
              >>>> Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
              >>>>-->
              >>>> <MailSession JNDIName="mail/STARSIIMailSession"
              >>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
              >>>
              >>>Targets="myserver"/>
              >>>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Store Pool"
              >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              >>>> Targets="MyCluster"
              >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="AffTest" Password=""
              >>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
              >>>> PoolName="AffTest" Targets=""/>
              >>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
              >>>> Name="Spy STARSII BRSB Pool"
              >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
              >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
              >>>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Store Pool 2"
              >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
              >>>> PoolName="STARSII Store Pool" Targets=""/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Stars Pool"
              >>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
              >>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
              >>>> Targets="MyCluster"
              >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>> <Machine Name="MachineA">
              >>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
              >>>> </Machine>
              >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
              >>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
              >>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
              >>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
              >>>
              >>>StdoutSeverityLevel="64">
              >>>
              >>>> <ServerDebug Name="Server1"/>
              >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
              >>>> <KernelDebug Name="Server1"/>
              >>>> <Log Name="Server1"/>
              >>>> <ServerStart Name="Server1"
              >>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
              >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              >>>> <WebServer Name="Server1"/>
              >>>> <COM Name="Server1"/>
              >>>> <IIOP Name="Server1"/>
              >>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
              >>>> <JTARecoveryService Name="Server1"/>
              >>>> </Server>
              >>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
              >>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
              >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
              >>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
              >>>> ListenPort="7002" Machine="MachineB" Name="Server2"
              >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              >>>> <ServerDebug Name="Server2"/>
              >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
              >>>> <KernelDebug Name="Server2"/>
              >>>> <Log Name="Server2"/>
              >>>> <ServerStart Name="Server2"
              >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              >>>> <WebServer Name="Server2"/>
              >>>> <COM Name="Server2"/>
              >>>> <IIOP Name="Server2"/>
              >>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
              >>>> <JTARecoveryService Name="Server2"/>
              >>>> </Server>
              >>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
              >>>> Notes="This is a system generated default migratable target
              >>>
              >>>for a server.
              >>>
              >>>>Do not delete manually." UserPreferredServer="Server1"/>
              >>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
              >>>> Notes="This is a system generated default migratable target
              >>>
              >>>for a server.
              >>>
              >>>>Do not delete manually." UserPreferredServer="Server2"/>
              >>>> <Application Deployed="true" Name="STARSII"
              >>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
              >>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
              >>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
              >>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
              >>
              >>URI="../commonSession"/>
              >>
              >>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
              >>>
              >>>URI="../complianceMessage"/>
              >>>
              >>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
              >>>
              >>>URI="../complianceSession"/>
              >>>
              >>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
              >>
              >>URI="../starsiiEntity"/>
              >>
              >>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
              >>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
              >>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
              >>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
              >>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
              >>>> </Application>
              >>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
              >>>> StagingMode="nostage" TwoPhase="true">
              >>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
              >>>> </Application>
              >>>> <Application Name="activeportal"
              >>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
              >>>> StagingMode="nostage" TwoPhase="true">
              >>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
              >>>> </Application>
              >>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
              >>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
              >>>> <JMSQueue CreationTime="1072820642598"
              >>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
              >>>> <JMSQueue CreationTime="1072820669345"
              >>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
              >>>> <JMSQueue CreationTime="1088000795852"
              >>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
              >>>> <JMSQueue CreationTime="1072820687125"
              >>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
              >>>> <JMSQueue CreationTime="1072820687125"
              >>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
              >>>> <JMSQueue CreationTime="1072820687225"
              >>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
              >>>> <JMSQueue CreationTime="1072820687325"
              >>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
              >>>> <JMSQueue CreationTime="1072820687425"
              >>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
              >>>> <JMSQueue CreationTime="1072820687525"
              >>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
              >>>> <JMSQueue CreationTime="1072820687625"
              >>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
              >>>> <JMSQueue CreationTime="1072820687725"
              >>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
              >>>> <JMSQueue CreationTime="1072820687825"
              >>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820687925"
              >>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
              >>>> <JMSQueue CreationTime="1072820688025"
              >>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
              >>>> <JMSQueue CreationTime="1072820688125"
              >>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820688225"
              >>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820688325"
              >>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
              >>>> </JMSServer>
              >>>> <Machine Name="MachineB">
              >>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
              >>>> </Machine>
              >>>></Domain>
              >>>
              >
              

  • Getting destination queue name

    Hi!
    I was wondering if it is possible somehow to retrieve queue destination name (the queue name the message will be sent to) in a JCD?
    So far I have been able to retrieve only the queue name the message is coming from:
    String sFromQueue = input.getMessageProperties().getDestination();JMSOut client otd is only returning "null" when using code: JMSOut.getDestination()

    hi jan,
    1) 1:n queues when it comes to "Queue" ... in ICAN and earlier versions it was possible to connect multiple queues on an outbound connection. the JMS adapter handeled the sending to multiple queues. BUT generally you are right it should be a 1:1 relationship.
    2) JMS Client generally points to ONE server with a default queue that is sent to when doind send(msg) BUT you also can override the destination queue by an api call like sendTo("someotherqueuename") therefore it is not that easy ....
    3) i think this ("API that allows retrieving object names") could be burried deep inside the APis but i would not recommend using it since this will not be stable and consistent over major releases! and you could risk a very hard porting from e.g. CAPS 6 to CAPS 7?
    why do you exactly need this information?
    regards chris
    Edited by: cbrennsteiner on Nov 11, 2008 10:45 AM

  • Javax.jms.InvalidDestinationException: Invalid destination

    Hi!
    Can any one tell me why this error is occured "javax.jms.InvalidDestinationException: Invalid destination" is it because of it unable to find the Destination queue?
    Thanks
    Sreenath

    Yes.. the exception is self explanatory.. check you server admin to see what is the name of destination you are using.

Maybe you are looking for