JMS Server Target & Deploy error

          Hi All,
          I am getting the error while creating the JMS Server.
          I have created the JMS Server and on Target and Deploy tab,when I select the server
          name as target and hit the Apply button, I get the following error
          An unexpected error occurred while setting Target to mydomain:Name=myserver(migratable),Type=MigratableTarget.
          what could be the reason?
          Thanks
          WD
          

It still seems like it is your app that is throwing the exception.
          If you post the full log message, not just the excerpted text,
          the problem might be self evident.
          WD wrote:
          > The applications code is fine. With the same ear file,I am getting this error
          > intermittently. My suspicions is that sometimes when I redeploy the same application(without
          > anything changed), wls does not deploy it properly. Because when I was getting
          > this error,I just undeployed and deployed the app and it worked.
          > Have you seen this kind of behavior with wls?
          >
          > Thanks
          > WD
          >
          >
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>It is unusual not to have a full stack trace - particularly
          >>for application generated exceptions. My first
          >>suspicions is that your app is creating a producer
          >>without specifying a destination (a non-pinned producer),
          >>and then attempting to send a message without specifying
          >>a destination.
          >>
          >>WD wrote:
          >>
          >>>The only log message I have is the one I posted earlier. It is from
          >>
          >>the log file.
          >>
          >>>
          >>>
          >>>Tom Barnes <[email protected].bea.com>
          >>>wrote:
          >>>
          >>>
          >>>>OK. For this new exception, do you have the full
          >>>>log message/stack trace?
          >>>>
          >>>>WD wrote:
          >>>>
          >>>>
          >>>>
          >>>>>I just left the app alone for the weekend and when I tried to do it
          >>>>
          >>>>again today,it
          >>>>
          >>>>
          >>>>>just worked. I do not know what was wrong with it on friday.
          >>>>>
          >>>>>But now I am running into another weird error. I have deployed my
          >>
          >>application
          >>
          >>>>>and it works fine and MyMDB also works fine. But sometimes I am getting
          >>>>
          >>>>the following
          >>>>
          >>>>
          >>>>>error. It is happening very intermittently.
          >>>>>
          >>>>>Exception in MyMDB.onMessage()Must provide destination
          >>>>>
          >>>>>Thanks
          >>>>>WD
          >>>>>
          >>>>>
          >>>>>Tom Barnes <[email protected].bea.com>
          >>>>>wrote:
          >>>>>
          >>>>>
          >>>>>
          >>>>>>Do you have the full log message/stack trace?
          >>>>>>
          >>>>>>WD wrote:
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>>Hi All,
          >>>>>>>I am getting the error while creating the JMS Server.
          >>>>>>>I have created the JMS Server and on Target and Deploy tab,when
          >>
          >>I
          >>
          >>>>select
          >>>>
          >>>>
          >>>>>>the server
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>>name as target and hit the Apply button, I get the following error
          >>>>>>>
          >>>>>>>An unexpected error occurred while setting Target to mydomain:Name=myserver(migratable),Type=MigratableTarget.
          >>>>>>>
          >>>>>>>what could be the reason?
          >>>>>>>
          >>>>>>>Thanks
          >>>>>>>WD
          >>>>>>>
          >>>>>>>
          >>>>>>
          >
          

Similar Messages

  • JMS server targeted to several clusters

    Hello,
    I am facing a problem with my JMS configuration in weblogic (version 10.3.4.0). I have two clusters. Following the [JMS best practice|http://forums.oracle.com/forums/message.jspa?messageID=9455261#9455261] I have created a JMS server in each Managed server within the clusters. I have created only one JMS Module with a subdeployment. The JMS Module is targeted to all managed servers within both clusters, and the subdeployment is targeted to all JMS servers within the clusters.
    At the JMS module I have created a connection Factory targeted to the subdeployment, till there everything is ok.
    Afterwards I try to create a uniform distributed queue (UDQ) targeted to the subdeployment and WebLogic throws the following error:
    A UDD must be targeted to servers within a single cluster or a single stand-alone server, rather than Cluster ClusterA and Cluster ClusterB
    The only solution that I found is to create one JMS Module-subdeployment per JMS Server. Is there a way to have just a JMS Module and use it in all the managed server in several clusters? or I have to set up the same parameters (ConnectionFactories + queue +quota) in each JMS Module.
    Thank you very much in advance.
    Cheers,
    Oscar

    Hi Oscar,
    The correct way to step-up a UDQ is something like below
    C-1 => MS-1 + MS-2
    JMSServer-1 => MS-1
    JMSServer-2 => MS-2
    JMSModule-1 => C-1
    Sub_UDQ => JMSServer-1 + JMSServer-2
    UDQ => Sub_UDQ
    CF => C-1
    Where:
    ======
    MS-x are the managed servers
    C-x are the Cluster
    UDQ is the Uniform Distributed Queue
    Sub_UDQ is the Sub-Deployment for UDQ
    CF is the Connection Factory
    *=>* mean Targeted.
    Also to get more information on it you can have a look at the below link which has the step by step instructions which would surely help you out
    Topic: Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Regards,
    Ravish Mody

  • Java Server Proxy---Deployment error?

    I am trying the scenario from this blog
    /people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
    I am getting deployment error
    May 30, 2006 1:39:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp57679JPS_EAR.ear
    Deployment exception : Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
    Inner exception was :
    Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
    Help me
    Thanks

    Hi Saru,
    It seems u dont have the correct sdm password or someone has changed the sdm password.It has not accepted the credentials u have given during deployment.
    Check with all Sap enterprise portal settings in the prefernces/NWDS
    The host name,alias,port
    If not done with
    Try to change the sdm password using this Password trouble in SDM
    restart server again after changes
    even try
    - Stop nd restart the sdm from yor NWDS and deploy once again
    Thanks,
    Swathi
    Do offer pts:-)

  • JMS Server targeted to Server cluster

    Hi , Can JMS Server be targeted to Server Cluster? Are there any
              architectural best practices for this?

    Thanks Tom.
              <Tom Barnes> wrote in message news:[email protected]...
              There's no underlying machinery (code) that supports targeting a JMS server
              to a cluster.
              The targeting problem can actually get fairly involved - for a variety of
              reasons, I tend to recommend the following cookie cutter approach.
              This is a cut-and-paste from my notes:
              (1) Create a custom WL store on each server, and target it to a migratable
              target (most of the time you can use the default migratable target that each
              server provides).
              (2) Target the JMS servers to a migratable target each, the same MT as the
              store (don't worry, the JMS server won't wander to a different server
              unless you configure the MT to allow this!)
              (3) Target jms configuration system modules to the cluster (that's it! - not
              to anything else)
              (4) Create one subdeployment per module (and only one), populate the
              subdeployment only with JMS servers from step (2) above.
              (5) When targeting destinations always use advanced targeting to target
              destinations to the subdeployment from above - not the 'default target'.
              If you have both non-distributed and distributed destinations, use two
              different JMS modules. (The idea is to keep things simple to understand -
              each module should yield the same targeting solution for all of its
              component resources. Default targetting can be problematic - it is far too
              easy for destination members to end up on JMS servers that you don't want
              them on.).
              (6) When targeting a CF you have two options (A) use advanced targeting to
              target it to the subdeployment (for access by applications that are remote
              to the cluster) or (B) don't target it all (this will cause it to use the
              module target, which if you recall, we just set to the cluster, (for access
              by applications that run on a server within the cluster). The choice
              actually depends on how you plan to use the CF - use (B) for apps running on
              servers within the cluster, and (A) for apps running remote to the cluster.
              See the otherwise-largely-outdated JMS Performance Guide for the reasoning.
              It may be that you don't have to use migratable targets, as you may not have
              a use for "migration" at the moment - but it'll help in the future if you
              ever plan to use the migration features.
              Tom

  • Offline WLST changes JMS Server Target From a Migratable target

    I have a simple WL 9.2mp2 domain which has 2 managed servers, one JMS Server and two migratable targets (one for each managed server) and the JMS server is targeted to one of the migratable targets. When I read the domain into WLST offline, the JMS server's target is changed from the migratable target to the preferred server defined in the migratable target. Is this a bug in WLST? Am I missing some option on WLST that can fix this?
              I saw a similar posting for 8.1 and no resolution.
              Thanks in advance,
              Mark.

    Hi
              Please find my answers below:
              Q1:
              It depends how you configured the JMSSevers.
              If both the JMSServers are targeted to the same MigratableTarget, then you do the migration only once, that will move both of them to the new active server.
              If not, you have to perform the migration once for each MT.
              Q2:
              No, you dont have to start the Managed Server II, unless otherwise you wanted it to be readily available for the migration next time.
              Q3:
              You can just repeat the migration process by specifying the destination as Maganged Server-I this time. You dont need change the configuration for this, since the MT, shall already have the Candidate servers M1 and M2 and both JMSServers are targeted to MT.
              Q4:
              Yes, as long as the CF is targeted to the cluster, your connection is valid. But your destinations references will become invalid after migration, so you have to have some logic in the exception listeners to reconnect again.
              Hope this helps.

  • Essbase server cube deployment error

    Hi All ,
    I have installed essbase 11.1.2 in windows machine with oracle DB.
    i have tried both the options .
    cube deployment wizard-> data source setting - 1) ODBC (Essbase dynamic create option)
    2) ODBC(DSN name)
    while deploying a cube in server 11.1.2 i m getting following error
    ==========Exception=====================
    com.hyperion.cp.datasources.export.essbase.dimbuild.EssDimensionBuilder.buildDimension(EssDimensionBuilder.java:337)
         at com.hyperion.cp.datasources.export.essbase.EssbaseMain.createEssbaseCube(EssbaseMain.java:777)
         ... 35 more
    Caused by: com.essbase.api.base.EssException: Cannot get async process state. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
         at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
    =====================================
    Query -> 1) Which username and pwd i need to use for DSN configuration - catalog user/pwd (user/pwd in server.properties) or Sample Database user/pwd ?
    2) In both the case i m getting the same error .
    Please help
    Ayush

    Hi All ,
    i set the property server.essbase.streamingCubeBuilding=true and restarted the server.
    Used default option in data source setting - 1) ODBC (Essbase dynamic create option)
    Failed to Establish Connection prioblem is solved .
    While processing Product dimension i m getting below issue for colum name ENGLISHPRODUCTSUBCATEGORYNAME,
    the alias used for this column is ENGLISHPRODUCTSUBCATEGORYNAME CUID , it's more than 30 char long.
    How can i solve this issue as query is created by the studio/server .
    ==========Query=========
    SELECT DISTINCT cp_107."ENGLISHPRODUCTCATEGORYNAME" as "ENGLISHPRODUCTCATEGORYNAME", cp_107."ENGLISHPRODUCTCATEGORYNAME" as "ENGLISHPRODUCTCATEGORYNAME CUID", cp_105."ENGLISHPRODUCTSUBCATEGORYNAME" as "ENGLISHPRODUCTSUBCATEGORYNAME", cp_105."*ENGLISHPRODUCTSUBCATEGORYNAME*" as "*ENGLISHPRODUCTSUBCATEGORYNAME CUID*", cp_114."ENGLISHPRODUCTNAME" as "ENGLISHPRODUCTNAME", cp_114."ENGLISHPRODUCTNAME" as "ENGLISHPRODUCTNAME CUID" FROM "ADVWORKS"."DIMPRODUCTCATEGORY" cp_107 INNER JOIN "ADVWORKS"."DIMPRODUCTSUBCATEGORY" cp_105 ON (cp_107."PRODUCTCATEGORYKEY"=cp_105."PRODUCTCATEGORYKEY") INNER JOIN "ADVWORKS"."DIMPRODUCT" cp_114 ON (cp_105."PRODUCTSUBCATEGORYKEY"=cp_114."PRODUCTSUBCATEGORYKEY")
    ======================
    ==============Exception=============
    Caused by: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
    ==================================
    Thanks
    ayush
    Edited by: user11181162 on Aug 10, 2010 12:39 PM

  • Please help me resolve the Lync server 2013 deployment error: "An error occurred while applying SQL script for the feature BackendStore."

    I am getting an error in "Step 2 - Setup or Remove Lync Server Components" of "Install or Update Lync Server System" step.
    "An error occured while applying SQL script for the feature BackendStore. For details, see the log file...."
    Additionally, all previous steps such as: Prepare Active Directory, Prepare first Standard Edition server, Install Administrative Tools, Create and publish topology are done without any errors. The user that I used to setup the Lync server is member of:
    Administrators
    CSAdministrator
    Domain Admins
    Domain Users
    Enterprise Admins
    Group Policy Creator Owners
    RTCComponentUniversalServices
    RTCHSUniversalServices
    RTCUniversalConfigReplicator
    RTCUniversalServerAdmins
    Schema Admins
    I have tried to re-install all the things and started to setup a new one many times but the same error still occurred. Please see the log below and give me any ideas/solutions to tackle this problem.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
    Initializing DbSetupBase
    Parsing parameters...
    Found Parameter: SqlServer Value lync.lctbu.com\rtc.
    Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Found Parameter: Publisheracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group;RTC Local Administrators;LCTBU\RTCUniversalServerAdmins.
    Found Parameter: Replicatoracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group.
    Found Parameter: Consumeracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group;RTC Local Read-only Administrators;LCTBU\RTCUniversalReadOnlyAdmins.
    Found Parameter: DbPath Value D:\CsData\BackendStore\rtc\DbPath.
    Found Parameter: LogPath Value D:\CsData\BackendStore\rtc\LogPath.
    Found Parameter: Role Value master.
    Trying to connect to Sql Server lync.lctbu.com\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 2100.
    Sql version is acceptable.
    Validating parameters...
    DbName rtcxds validated.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup validated.
    DbFileBase rtcxds validated.
    DbPath D:\CsData\BackendStore\rtc\DbPath validated.
    Effective database Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath.
    LogPath D:\CsData\BackendStore\rtc\LogPath validated.
    Effective Log Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    Checking state for database rtcxds.
    Checking state for database rtcxds.
    State of database rtcxds is detached.
    Attaching database rtcxds from Data Path \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath, Log Path \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    The operation failed because of missing file '\\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath\rtcxds.mdf'
    Attaching database failed because one of the files not found. The database will be created.
    State of database rtcxds is DbState_DoesNotExist.
    Creating database rtcxds from scratch. Data File Path = D:\CsData\BackendStore\rtc\DbPath, Log File Path= D:\CsData\BackendStore\rtc\LogPath.
    Clean installing database rtcxds.
    Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
    Initializing DbSetupBase
    Parsing parameters...
    Found Parameter: SqlServer Value lync.lctbu.com\rtc.
    Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Found Parameter: Serveracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group.
    Found Parameter: DbPath Value D:\CsData\BackendStore\rtc\DbPath.
    Found Parameter: LogPath Value D:\CsData\BackendStore\rtc\LogPath.
    Trying to connect to Sql Server lync.lctbu.com\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 2100.
    Sql version is acceptable.
    Validating parameters...
    DbName rtcshared validated.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup validated.
    DbFileBase rtcshared validated.
    DbPath D:\CsData\BackendStore\rtc\DbPath validated.
    Effective database Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath.
    LogPath D:\CsData\BackendStore\rtc\LogPath validated.
    Effective Log Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    Checking state for database rtcshared.
    Reading database version for database rtcshared.
    Database version for database rtcshared - Schema Version5, Sproc Version 0, Update Version 1.
    Thanks and Regards,
    Thanh Le

    Thanks Lạc
    Phạm 2
    I Had similar issue i end up uninstalling and reinstallting but same issue, then i change the drive but same issue. It was I/O issue. After adjusting my I/O it fix our issue and installation went on without any issue. 
    If any one using KVM here is detail article 
    We just  give this option cache=‘writeback
    using this article http://www.ducea.com/2011/07/06/howto-improve-io-performance-for-kvm-guests/ and http://itscblog.tamu.edu/improve-disk-io-performance-in-kvm/ this fix my issue thanks 

  • JMS Server JNDI not being replicated? (clustered environment)

    Hello,
    First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
    My current production and test environments consist, each one of them, of
    clusters with one admin server (ProdAdmin) and two managed servers (Prod1
    and Prod2). One of the managed servers (Prod1) is the server to which the
    JMS server is deployed and everything works fine.
    Now I'm trying to add another managed server to the cluster. The idea is to
    target the JMS Server (and nothing else) to this node. We don't want the JMS
    server to be running in Prod1 and the new server, named ProdJMS, won't even
    have any deployed beans or the startup class targeted to it. Just the JMS
    server. Here our problems start.
    I'm able to start this ProdJMS node with no problems. However, when I start
    Prod1 it seems that the JMS server is not binded. This is the exception
    we're getting when a message-driven bean is being deployed (I get the same
    exception trying to create other):
    ------- snip -------------
    <May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
    CacheUpdateBean is unable to connect to the JMS
    destination: securityChanges. The EJB container will automatically attempt
    to re-establish the connection with the JMS s
    erver. This warning may occur during WebLogic Cluster start-up if the JMS
    destination is located on another WebLogic Ser
    ver instance. When the JMS server connection is re-established, the
    Message-Driven EJB will again receive JMS messages.
    The Error was:
    weblogic.jms.common.JMSException: Error creating session
    Start server side stack trace:
    weblogic.jms.common.JMSException: Error creating session
    at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ----------- Linked Exception -----------
    weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
    Prod1, javax.naming.NameNotFoundException: Un
    able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
    Unresolved:'S:Prod1' ; remaining name ''
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
    .java:260)
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
    anager.java:307)
    at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ------- snip -------------
    If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
    exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
    actually able to see "weblogic.jms.S:Prod1", which is the name that seems
    not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
    everything works fine. If I deploy the JMS server to a server with only the
    JMS server I get the mentioned JNDI exception.
    I would appreciate if you could give me help me solving this problem.
    Thanks in a dvance for any help.
    Andre Mendonca

    First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
    My current production and test environments consist, each one of them, of
    clusters with one admin server (ProdAdmin) and two managed servers (Prod1
    and Prod2). One of the managed servers (Prod1) is the server to which the
    JMS server is deployed and everything works fine.
    Now I'm trying to add another managed server to the cluster. The idea isto
    target the JMS Server (and nothing else) to this node. We don't want theJMS
    server to be running in Prod1 and the new server, named ProdJMS, won'teven
    have any deployed beans or the startup class targeted to it. Just the JMS
    server. Here our problems start.
    I'm able to start this ProdJMS node with no problems. However, when Istart
    Prod1 it seems that the JMS server is not binded. This is the exception
    we're getting when a message-driven bean is being deployed (I get the same
    exception trying to create other):1. Make sure that you are using a dif multicast address for each cluster
    2. Remove the JMS from Prod1 -- double check this!
    3. Stop Prod1 and Prod2
    4. Start the ProdJMS
    5. Restart Prod1 and Prod2
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Andre Mendonca" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    ------- snip -------------
    <May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
    CacheUpdateBean is unable to connect to the JMS
    destination: securityChanges. The EJB container will automatically attempt
    to re-establish the connection with the JMS s
    erver. This warning may occur during WebLogic Cluster start-up if the JMS
    destination is located on another WebLogic Ser
    ver instance. When the JMS server connection is re-established, the
    Message-Driven EJB will again receive JMS messages.
    The Error was:
    weblogic.jms.common.JMSException: Error creating session
    Start server side stack trace:
    weblogic.jms.common.JMSException: Error creating session
    atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ----------- Linked Exception -----------
    weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
    Prod1, javax.naming.NameNotFoundException: Un
    able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
    Unresolved:'S:Prod1' ; remaining name ''
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
    .java:260)
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
    anager.java:307)
    atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ------- snip -------------
    If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
    exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
    actually able to see "weblogic.jms.S:Prod1", which is the name that seems
    not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
    everything works fine. If I deploy the JMS server to a server with onlythe
    JMS server I get the mentioned JNDI exception.
    I would appreciate if you could give me help me solving this problem.
    Thanks in a dvance for any help.
    Andre Mendonca

  • JMSHelper throws 'JMS server is not targetted' creating distributed queue

    I am trying to use the 8.1 weblogic.jms.extensions.JMSHelper to create a distributed queue. The target JMS servers are all migratable servers. When calling method createDistributedQueueAsync() I get a JMSException thrown compaining that the [first] JMS server is not targetted. Looking at the code provided in [http://forums.bea.com/bea/thread.jspa?messageID=200023386] which is based on the JMSHelper class source, the exception may be thrown because the target MBean is of class MigratableTargetMBean, whereas the JMSHelper is expecting class TargetMBean. Yet, the 9.0 documentation (which at least documents it) suggests that MigratableTargetMBean is derived from TargetMBean
              Does anyone have experience of this issue or its resolution, short of crafting the code by hand as per the above-referenced reply?

    Hi,
    Just to remember the configuration: 2 managed servers configured as cluster that should be deployed on 2 different machine.
    Following summary of the tests:
         - node manager + admin server + 1 managed server running on the first machine --> server failed to init with error "Server is not in the majority cluster partition"
         - node manager + admin server + 2 managed servers running on the one machine --> servers are running without errors
         - node manager + admin server + 1 managed server running on the first  machine / node manager runs on the second machine --> server on the first machine runs without errors without the famous error ' Server is not in the majority cluster partition'.
    Bottom line, seems that if the node manager is not running on the remote machine, the cluster is not in a stable state and so the single managed server failed to initialize.
    Is it according the documentation / expectations ?
    Thanks,
    Yaakov

  • Oracle Application Server 10.1.3 EJB Deployment Error

    Hi ,
    I am keep getting following error when try to deploy my ear files in 10.1.3. standalone env.
    my ejb-jar.xml looks is
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <enterprise-beans>
    <session>
    <description>Session Facade Bean ( Stateless )</description>
    <display-name>FacadeBean</display-name>
    <ejb-name>FacadeBean</ejb-name>
    <home>com.sjrwmd.dmsap.ejb.FacadeBeanHome</home>
    <remote>com.sjrwmd.dmsap.ejb.FacadeBeanRemote</remote>
    <ejb-class>com.sjrwmd.dmsap.ejb.FacadeBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>FacadeBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    Your help appriciated
    Thank You
    Jigar
    2006-02-08 17:13:40.670 NOTIFICATION JMS Router is initiating ...
    2006-02-08 17:13:55.702 NOTIFICATION Application Deployer for dmsap STARTS.
    2006-02-08 17:13:55.733 NOTIFICATION Copy the archive to C:\JDev1013\j2ee\home\applications\dmsap.ear
    2006-02-08 17:13:55.733 NOTIFICATION Initialize ./applications\dmsap.ear begins...
    2006-02-08 17:13:55.733 NOTIFICATION Removing everything under: C:\JDev1013\j2ee\home\.\applications\dmsap
    2006-02-08 17:13:55.733 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\.\applications\dmsap.ear...
    2006-02-08 17:13:55.733 NOTIFICATION Unpacking dmsap.ear
    2006-02-08 17:13:55.733 NOTIFICATION Unjar C:\JDev1013\j2ee\home\.\applications\dmsap.ear in C:\JDev1013\j2ee\home\.\applications\dmsap
    2006-02-08 17:13:55.998 NOTIFICATION Done unpacking dmsap.ear
    2006-02-08 17:13:55.998 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\.\applications\dmsap.ear
    2006-02-08 17:13:56.045 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war...
    2006-02-08 17:13:56.045 NOTIFICATION Unpacking dmsap-web.war
    2006-02-08 17:13:56.045 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war in C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web
    2006-02-08 17:13:56.498 NOTIFICATION Done unpacking dmsap-web.war
    2006-02-08 17:13:56.498 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war
    2006-02-08 17:13:56.498 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar...
    2006-02-08 17:13:56.498 NOTIFICATION Unpacking uploaddirapp.jar
    2006-02-08 17:13:56.498 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar in C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp
    2006-02-08 17:13:56.748 NOTIFICATION Done unpacking uploaddirapp.jar
    2006-02-08 17:13:56.748 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar
    2006-02-08 17:13:56.748 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar...
    2006-02-08 17:13:56.764 NOTIFICATION Unpacking downloadfileapp.jar
    2006-02-08 17:13:56.764 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar in C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp
    2006-02-08 17:13:56.967 NOTIFICATION Done unpacking downloadfileapp.jar
    2006-02-08 17:13:56.967 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar
    2006-02-08 17:13:56.983 NOTIFICATION Initialize ./applications\dmsap.ear ends...
    2006-02-08 17:13:56.983 NOTIFICATION Starting application : dmsap
    2006-02-08 17:13:56.983 NOTIFICATION Initializing ClassLoader(s)
    2006-02-08 17:13:56.983 NOTIFICATION Initializing EJB container
    2006-02-08 17:13:56.983 NOTIFICATION Loading connector(s)
    2006-02-08 17:13:57.295 NOTIFICATION Starting up resource adapters
    2006-02-08 17:13:57.295 NOTIFICATION Processing EJB module: dmsap-ejb.jar
    2006-02-08 17:13:57.405 ERROR J2EE EJB3027 [dmsap] An error occured deploying EJB module: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    2006-02-08 17:13:57.405 NOTIFICATION application : dmsap is in failed state
    Feb 8, 2006 5:13:57 PM com.evermind.server.Application setConfig
    WARNING: Application: dmsap is in failed state as initialization failedjava.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    06/02/08 17:13:57 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    06/02/08 17:13:57      at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:510)
    06/02/08 17:13:57      at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
    06/02/08 17:13:57      at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
    06/02/08 17:13:57      at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
    06/02/08 17:13:57      at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
    06/02/08 17:13:57      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
    06/02/08 17:13:57      at java.lang.Thread.run(Thread.java:534)
    06/02/08 17:13:57 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    06/02/08 17:13:57      at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1056)
    06/02/08 17:13:57      at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:210)
    06/02/08 17:13:57      at com.evermind.server.Application.setConfig(Application.java:391)
    06/02/08 17:13:57      at com.evermind.server.Application.setConfig(Application.java:308)
    06/02/08 17:13:57      at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
    06/02/08 17:13:57      at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
    06/02/08 17:13:57      ... 6 more
    06/02/08 17:13:57 Caused by: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    06/02/08 17:13:57      at com.evermind.server.ejb.exception.ValidationExceptions.unableToLoadEJBClass(ValidationExceptions.java:36)
    06/02/08 17:13:57      at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:298)
    06/02/08 17:13:57      at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.initialize(ExposableBeanDescriptor.java:158)
    06/02/08 17:13:57      at com.evermind.server.ejb.deployment.SessionBeanDescriptor.initialize(SessionBeanDescriptor.java:190)
    06/02/08 17:13:57      at com.evermind.server.ejb.deployment.EJBPackage.initialize(EJBPackage.java:814)
    06/02/08 17:13:57      at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:855)
    06/02/08 17:13:57      ... 11 more
    06/02/08 17:13:57 Caused by: oracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2268)
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.findLocalClass(PolicyClassLoader.java:1457)
    06/02/08 17:13:57      at oracle.classloader.SearchPolicy$FindLocal.getClass(SearchPolicy.java:167)
    06/02/08 17:13:57      at oracle.classloader.SearchSequence.getClass(SearchSequence.java:119)
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1660)
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1621)
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1606)
    06/02/08 17:13:57      at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    06/02/08 17:13:57      at java.lang.Class.forName0(Native Method)
    06/02/08 17:13:57      at java.lang.Class.forName(Class.java:219)
    06/02/08 17:13:57      at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:296)
    06/02/08 17:13:57      ... 15 more
    06/02/08 17:13:57 Caused by: java.lang.UnsupportedClassVersionError: com.sjrwmd.dmsap.ejb.FacadeBean
    06/02/08 17:13:57      at java.lang.ClassLoader.defineClass0(Native Method)
    06/02/08 17:13:57      at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
    06/02/08 17:13:57      at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2224)
    06/02/08 17:13:57      ... 25 more
    2006-02-08 17:13:57.545 NOTIFICATION Application Deployer for dmsap FAILED.
    2006-02-08 17:13:57.545 NOTIFICATION Application UnDeployer for dmsap STARTS.
    2006-02-08 17:13:59.045 NOTIFICATION Removing all web binding(s) for application dmsap from all web site(s)
    2006-02-08 17:13:59.795 NOTIFICATION Application UnDeployer for dmsap COMPLETES.
    2006-02-08 17:13:59.795 WARNING java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
         Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
         Loader: dmsap.root:0.0.0
         Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
         Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
         Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar

    A point of clarification: Using JDK 1.5, it compiles and "tries" to start, but then gives this error : Unable to load ejb-class com.MyTestEJB see section 23.2 of the EJB 2.1 specificationjava.lang.ExceptionInInitializerError: java.lang.NullPointerException
    There are other EJB which are deploying fine.
    I really can't tell why one is deploying but this one is not.
    Thanks

  • Deploying ADF application to a managed weblogic server - ADF security error

    Hi,
    Our group has written an ADF web application, which we are attempting to deploy to a managed weblogic server. Thus far, we have been unsuccessful. The application does successfully deploy to the AdminServer. Our setup:
    Weblogic version is 10.3.0. Domain name is adf_domain. We have installed the ADF (ADF version is 11.1.1.0.0), JSTL(1.2.0.1), and JSF(1.2.7.1) runtime libraries, and they are targeted to both the admin server AND the managed server, which is called CollabServer. This server communicates with the node manager and can be started and stopped via the admin console successfully. The AdminServer is on port 7101, and the CollabServer is on port 7104. We are not using SSL.
    application.xml:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
    version="5" xmlns="http://java.sun.com/xml/ns/javaee">
    <display-name>OracleRetailCollaboration</display-name>
    <module>
    <web>
    <web-uri>orc.war</web-uri>
    <context-root>orc</context-root>
    </web>
    </module>
    </application>
    weblogic-application.xml (as taken from the ear file):
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application.xsd" xmln
    s="http://www.bea.com/ns/weblogic/weblogic-application">
    <listener>
    <listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
    </listener>
    <library-ref>
    <library-name>adf.oracle.domain</library-name>
    </library-ref>
    </weblogic-application>
    weblogic.xml (as taken from the war file):
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ww
    w.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    <security-role-assignment>
    <role-name>valid-users</role-name>
    <principal-name>users</principal-name>
    </security-role-assignment>
    <library-ref>
    <library-name>jstl</library-name>
    <specification-version>1.2</specification-version>
    </library-ref>
    <library-ref>
    <library-name>jsf</library-name>
    <specification-version>1.2</specification-version>
    </library-ref>
    </weblogic-web-app>
    As I said, there are no deployment errors when we deploy to the admin server. However, we always see the following errors when deploying to the managed server:
    java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
    etc.
    This error occurs when deploying via the <wldeploy> ant task included with weblogic, and when deploying the application manually via the admin console.
    So I removed this from weblogic-application.xml:
    <listener>
    <listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
    </listener>
    Which resolved the initial error (I assume there is some sort of bug that causes this workaround to be necessary). The next error is this:
    java.lang.ClassNotFoundException: oracle.adf.share.security.authentication.AuthenticationServlet
    Again, we don't get this error when deploying to the AdminServer - ONLY the managed server CollabServer.
    web.xml:
    <servlet>
    <servlet-name>adfAuthentication</servlet-name>
    <servlet-class>oracle.adf.share.security.authentication.AuthenticationServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>adfAuthentication</servlet-name>
    <url-pattern>/adfAuthentication/*</url-pattern>
    </servlet-mapping>
    I then added some adf jar files to the ear file, finally get this error message:
    java.lang.ClassNotFoundException: oracle.adf.share.jsp.ADFLibUtils
    Any ideas on how to resolve this? Thanks.
    Edited by: user10451099 on Apr 15, 2009 12:10 PM

    Dan,
    thanks fro reminding me :-)
    Here are the steps we had to take to get a managed WLS to run an adf application without copying any jar in the domain/lib directory:
    1. you still have to install the adf runtime to any server you want the adf application to deploy to
    2. open the admin console, select the managed server, and select the 'server start' tab in configutation settings.
    3. add /u01/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:
    /u01/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/jrockit_160_05/lib/tools.jar:/u01/bea/wlserver_103/server/lib/weblogic_sp.jar:
    /u01/bea/wlserver_103/server/lib/weblogic.jar:/u01/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/u01/bea/wlserver_103/server/lib/webservices.jar:
    /u01/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/u01/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/u01/bea/jdeveloper/modules/features/adf.share_11.1.1.jar:
    /u01/bea/wlserver_103/common/eval/pointbase/lib/pbclient57.jar:/u01/bea/wlserver_103/server/lib/xqrl.jar:
    /u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath/weblogic_ext_patch.jar to the classpath edit box you have to change '/u01/bea/' with your bea home. The classpath should be on one line without the CR/LF i put in to make it readable.
    4. add -Xms256m -Xmx512m -da -Dplatform.home=/u01/bea/wlserver_103 -Dwls.home=/u01/bea/wlserver_103/server -Dweblogic.home=/u01/bea/wlserver_103/server
    -Ddomain.home=/u01/bea/user_projects/domains/naa_qs -Doracle.home=/u01/bea/jdeveloper -Doracle.security.jps.config=/u01/bea/user_projects/domains/naa_qs/config/oracle/jps-config.xml
    -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001
    -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=
    -Dweblogic.ext.dirs=/u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/u01/bea/patch_jdev1111/profiles/default/sysext_manifest_classpath:/u01/bea/patch_cie660/profiles/default/sysext_manifest_classpath
    -Dweblogic.management.username=weblogic -Dweblogic.management.password=******** -Dweblogic.Name=GESTIS_QS
    -Djava.security.policy=/u01/bea/wlserver_103/server/lib/weblogic.policy to the 'Arguments' edit box. As with the calsspath change '/u01/bea' to your bea home and change the domain name (in our case 'naa_qs') to your domain name. change the managementuser and passwort to your needs. As whith the classpath I put some CR/LF into the code section to make it readable.
    5. save the changes and restart the server
    Essentially all we copied the arguments from the admin server start script in addition to adding the class path.
    Timo

  • ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ

    Hi,
    I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
    ####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
    Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at line 11
    ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
    The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
         at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
         at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
         at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
         at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
         at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
         at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
         at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
         at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
         at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
         at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
         at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
         at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
         at java.lang.Thread.run(Thread.java:722)
    Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at line 11
    ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
         at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
         at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
         at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
         at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
         at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
         at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
         at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
         at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
         at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
         at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
         ... 13 moreHowever, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
    Request help to resolve this.
    Thanks in advance.
    Regards
    Alexander.

    Maybe this can help: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:4018285967344

  • Deploy error on remote Weblogic Server 10

    Hi, All,
    I try to deploy a simple JSP page with war deploy profile to a remote Weblogic Server 10. but error found:
    C:\jdeveloper10133\jdk\jre\bin\javaw.exe -classpath C:\jdeveloper10133\jdev\lib\ext\weblogic.jar weblogic.Deployer -adminurl http://rst-act3ct2.us.oracle.com:7001 -user weblogic -password **** -debug -verbose -deploy -upload -source C:\jdevWorkspace\WLSApplication\JSPProject\deploy\simpleJSP.ear -name simpleJSP
    java.lang.NoClassDefFoundError: weblogic/utils/Debug
    at weblogic.Deployer.<clinit>(Deployer.java:23)
    I wonder if there is any other jar file I need to add in classpath for deploy on remote weblogic? Thanks in advance.
    Best Regards,
    Bill

    I'm having the same problem. And I'm not ready to give up just yet -- this is a feature I really need to get working.
    This build script works locally:
    <project name="DEPLOY_TEST" default="deploy" basedir=".">
      <path id="classpath">
        <pathelement location="/opt/bea/wlserver_10.3/server/lib/weblogic.jar"/>
      </path>
      <target name="init-wldeploy-10.3">
        <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
           <classpath refid="classpath"/>
        </taskdef>
      </target>
      <target name="deploy" depends="init-wldeploy-10.3">
        <wldeploy action="deploy" source="test.ear" name="test"
                  user="weblogic" password="******" verbose="true" adminurl="t3://localhost:7001" debug="true"
                  upload="true" targets="testCluster"/>
      </target>
    </project>But a similar ant script (replacing localhost with server name) run on my development machine gives:
    java.lang.NoClassDefFoundError: weblogic/utils/DebugAnybody else scratching their head over this one?

  • JMS Server deployed to cluster of servers

    Hey guys,
    I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
    I read the following passage in the weblogic documents:
    Obtain a Clustered JMS Licence
    In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
    If i'm just building a model does this apply to me?
    Thanks

    continued reading to clarify. Problem solved, thanks for looking

  • Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

    Hi
    This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
    * Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
    * Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
    * Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
    * The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
    Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
    <Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
    weblogic.jms.common.JMSException: Destination not found
    weblogic.jms.common.JMSException: Destination not found
    at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
    at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
    at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
    at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
    at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
    at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
    at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
    at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
    at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
    at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
    at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
    at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
    at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
    at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
    at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    Edited by: user8773992 on Sep 2, 2009 11:31 AM

    1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
    2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
    3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
    I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
    Tom

Maybe you are looking for