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

Similar Messages

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

Newsfeed error - The operation failed because the server could not access the distributed cache.

Recently installed SharePoint 2013 RTM, on the newsfeed page an error is displayed, and no entries display in the following or everyone tabs.
"The operation failed because the server could not access the distributed cache."
Reading through various posts, I've checked:
- Activity feeds and mentions tabs are working as expected.
- User Profile Service is operational and syncing as expected
- Search is operational and indexing as expected
- The farm was installed based on the autospinstaller scripts.
- Don't believe this to be a permissions issue, during testing added accounts to the admin group to verify
Any suggestions are welcomed, thanks.
The full error message and trace logs is as follows.
SharePoint returned the following error: The operation failed because the server could not access the distributed cache. Internal type name: Microsoft.Office.Server.Microfeed.MicrofeedException. Internal error code: 55. Contact your system administrator
for help in resolving this problem.
From the trace logs there's several messages which are triggered around the same time:
http://msdn.microsoft.com/en-AU/library/System.ServiceModel.Diagnostics.TraceHandledException.aspxHandling an exception. Exception details: System.ServiceModel.FaultException`1[Microsoft.Office.Server.UserProfiles.FeedCacheFault]: Unexpected exception in
FeedCacheService.GetPublishedFeed: Object reference not set to an instance of an object.. (Fault Detail is equal to Microsoft.Office.Server.UserProfiles.FeedCacheFault)./LM/W3SVC/2/ROOT/d71732192b0d4afdad17084e8214321e-1-129962393079894191System.ServiceModel.FaultException`1[[Microsoft.Office.Server.UserProfiles.FeedCacheFault,
Microsoft.Office.Server.UserProfiles, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]], System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089Unexpected exception in FeedCacheService.GetPublishedFeed: Object
reference not set to an instance of an object..
at Microsoft.Office.Server.UserProfiles.FeedCacheService.Microsoft.Office.Server.UserProfiles.IFeedCacheService.GetPublishedFeed(FeedCacheRetrievalEntity fcTargetEntity, FeedCacheRetrievalEntity fcViewingEntity, FeedCacheRetrievalOptions fcRetOptions)
at SyncInvokeGetPublishedFeed(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)System.ServiceModel.FaultException`1[Microsoft.Office.Server.UserProfiles.FeedCacheFault]: Unexpected exception in FeedCacheService.GetPublishedFeed: Object reference not
set to an instance of an object.. (Fault Detail is equal to Microsoft.Office.Server.UserProfiles.FeedCacheFault).
SPSocialFeedManager.GetFeed: Exception: Microsoft.Office.Server.Microfeed.MicrofeedException: ServerErrorFetchingConsolidatedFeed : ( Unexpected exception in FeedCacheService.GetPublishedFeed: Object reference not set to an instance of an object.. ) : Correlation
ID:db6ddc9b-8d2e-906e-db86-77e4c9fab08f : Date and Time : 31/10/2012 1:40:20 PM
at Microsoft.Office.Server.Microfeed.SPMicrofeedThreadCollection.PopulateConsolidated(SPMicrofeedRetrievalOptions retOptions, SPMicrofeedContext context)
at Microsoft.Office.Server.Microfeed.SPMicrofeedThreadCollection.Populate(SPMicrofeedRetrievalOptions retrievalOptions, SPMicrofeedContext context)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.CommonGetFeedFor(SPMicrofeedRetrievalOptions retrievalOptions)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.CommonPubFeedGetter(SPMicrofeedRetrievalOptions feedOptions, MicrofeedPublishedFeedType feedType, Boolean publicView)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.GetPublishedFeed(String feedOwner, SPMicrofeedRetrievalOptions feedOptions, MicrofeedPublishedFeedType typeOfPubFeed)
at Microsoft.Office.Server.Social.SPSocialFeedManager.Microsoft.Office.Server.Social.ISocialFeedManagerProxy.ProxyGetFeed(SPSocialFeedType type, SPSocialFeedOptions options)
at Microsoft.Office.Server.Social.SPSocialFeedManager.<>c__DisplayClass4b`1.<S2SInvoke>b__4a()
Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeed: Microsoft.Office.Server.Microfeed.MicrofeedException: ServerErrorFetchingConsolidatedFeed : ( Unexpected exception in FeedCacheService.GetPublishedFeed: Object reference not set to an instance of
an object.. ) : Correlation ID:db6ddc9b-8d2e-906e-db86-77e4c9fab08f : Date and Time : 31/10/2012 1:40:20 PM
at Microsoft.Office.Server.Microfeed.SPMicrofeedThreadCollection.PopulateConsolidated(SPMicrofeedRetrievalOptions retOptions, SPMicrofeedContext context)
at Microsoft.Office.Server.Microfeed.SPMicrofeedThreadCollection.Populate(SPMicrofeedRetrievalOptions retrievalOptions, SPMicrofeedContext context)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.CommonGetFeedFor(SPMicrofeedRetrievalOptions retrievalOptions)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.CommonPubFeedGetter(SPMicrofeedRetrievalOptions feedOptions, MicrofeedPublishedFeedType feedType, Boolean publicView)
at Microsoft.Office.Server.Microfeed.SPMicrofeedManager.GetPublishedFeed(String feedOwner, SPMicrofeedRetrievalOptions feedOptions, MicrofeedPublishedFeedType typeOfPubFeed)
at Microsoft.Office.Server.Social.SPSocialFeedManager.Microsoft.Office.Server.Social.ISocialFeedManagerProxy.ProxyGetFeed(SPSocialFeedType type, SPSocialFeedOptions options)
at Microsoft.Office.Server.Social.SPSocialFeedManager.<>c__DisplayClass4b`1.<S2SInvoke>b__4a()
at Microsoft.Office.Server.Social.SPSocialUtil.InvokeWithExceptionTranslation[T](ISocialOperationManager target, String name, Func`1 func)
Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeed: Microsoft.Office.Server.Social.SPSocialException: The operation failed because the server could not access the distributed cache. Internal type name: Microsoft.Office.Server.Microfeed.MicrofeedException.
Internal error code: 55.
at Microsoft.Office.Server.Social.SPSocialUtil.TryTranslateExceptionAndThrow(Exception exception)
at Microsoft.Office.Server.Social.SPSocialUtil.InvokeWithExceptionTranslation[T](ISocialOperationManager target, String name, Func`1 func)
at Microsoft.Office.Server.Social.SPSocialFeedManager.<>c__DisplayClass48`1.<S2SInvoke>b__47()
at Microsoft.Office.Server.Social.SPSocialUtil.InvokeWithExceptionTranslation[T](ISocialOperationManager target, String name, Func`1 func)

Thanks Thuan,
I've restarted to the Distrubiton Cache servicem and the error is still occuring.
The AppFabric Caching Service is running under the service apps account, and does appear operational based on:
> use-cachecluster
> get-cache
CacheName            [Host]
                     Regions
default
DistributedAccessCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedActivityFeedCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedActivityF [SERVER:22233]
eedLMTCache_1e9f4999 LMT(Primary)
-0187-40e8-aa92-f830
8d47d6e9
DistributedBouncerCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedDefaultCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedLogonToke [SERVER:22233]
nCache_1e9f4999-0187 Default_Region_0538(Primary)
-40e8-aa92-f8308d47d Default_Region_0004(Primary)
6e9                  Default_Region_0451(Primary)
DistributedSearchCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedSecurityTrimmingCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9
DistributedServerToAppServerAccessTokenCache_1e9f4999-0187-40e8-aa92-f8308d47d6e9

JMS Server is not Migrating to other Managed Server using Databse Leasing

Hi,
WLS 10.3 on Linux Itanium.
I Tried JMS Server migration but its not working.
Below is the Configuration Details :-
1. Cluster with three managed servers( MS1,MS2,MS3 )
2.JMS Server is targeted on MS1(migratable)
3.created Persistant store as JDBC store for JMS Server and targeted it to MS1(migratable)
4.Environment -> Cluster->Migration Tab
-Migration Basis :- Database
-DataSource For Automatic Migration -> DS1
     -Auto Migration Table Name:(ACTIVE)
5.Created a table ACTIVE as per schema given in WL_HOME/server/db/dbname/leasing.ddl (I am using Oracle database at backend and Database is running and accessible)
6.Created Jms module (say module1)
-target module1 to Cluster.
7.Create Subdeployment(say "sub1") and target to JmsServer
8.Create Queue.and select subdeployment as "sub1" which was created above.
9.I am using default JMSXAconnectionfactory
10.Environment -> Migratable Targets->Select MS1(Migratable)->Migration tab
-Service Migration Policy->Auto Migration Exactly Once Service
               -Constrained Cadidate Servers :-
               Selected all the servers in that cluster
but when I check the Current Server for JMS Server (It should be MS1) which is not displayed. The field in the table is blank.
(Environment->Messaging->JMS Server->here i checked the Current Server for JMS Server )
with the above setting I did it successfully on windows platform. I am able to see Current Server as MS1.and when I shutdown MS1 it changes to either MS2 or MS3
but when I am doing it on Winodows I am explicitly creating connection factory and targeting it to cluster.but on linux platform I am not creating any connection factory(default JMS XA Connection Factory is used)
I have tried a lot to find why its not working but didnt get any idea why so happened?
Required your help
Thanks in Advance ........

I managed to start my managedserver.The issue was with startmanagedserver command.I modified it to my need.

Server Pool not getting created

Hello,
I setup a Oracle VM server on a x64 machine and Oracle VM Manager on another.
Tried to create first Server Pool, by giving IP address of Oracle VM Server, everything went well, but
Server Pools
Select and Restore Edit Delete
Select     Server Pool Name Status     High Availability Status     Servers     Users     Logs
First-Pool     Error Disabled     Total: 1 Total: 1     View Logs
Clicking on View logs I get this
2011-07-15 20:11:25     Check prerequisites to create server pool (First-Pool) succeed
2011-07-15 20:13:01     Create server pool (First-Pool) starting.
basically ServerPool status is Error and view log not showing anything.
what can be going wrong here?
regards, Yora

Have you reviewed your ovm server /etc/hosts yet?
It's documented somewhere: when installed, hostname is poingint to 127.0.0.1 instead of itself.
Modify it to get 127.0.0.1 as localhost, and assigned IP to your hostname .
I think it will work fine then,
Joan.

Moved CA to new server, CRL not properly created.

I need some advice on this one, I moved our CA to a new OES11 server and at the end of the CA import it gave me a page long java error about how it could not create the CRL.
The certificate and CA itself seem to be working fine, iManager updated the server certs without issues.
When I check the CA it *does* show the CRL but when I try to check it, it will hang and eventually show a blank screen.
I'm not sure how to proceed on this one, I don't know if the server hosting the CA requires any special configuration for it to be hosting the CRL as well.
There is a CRL container under our security container but there is not a lot of info in the objects contained within.

Originally Posted by Conz
I need some advice on this one, I moved our CA to a new OES11 server and at the end of the CA import it gave me a page long java error about how it could not create the CRL.
The certificate and CA itself seem to be working fine, iManager updated the server certs without issues.
When I check the CA it *does* show the CRL but when I try to check it, it will hang and eventually show a blank screen.
I'm not sure how to proceed on this one, I don't know if the server hosting the CA requires any special configuration for it to be hosting the CRL as well.
There is a CRL container under our security container but there is not a lot of info in the objects contained within.
No special configuration needed..... you could retry deleting the CA object, and recreating with an import. Maybe try another browser/client where your are doing the iManager import (or if the import fails again/shows the error, possibly another server where you have iManager running).
Just as a reference, FireFox has always worked well for me when moving the eDir CA.
Cheers,
Willem

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
          >>>>>>>
          >>>>>>>
          >>>>>>
          >

Config.sh-Admin server directory is created..but manged soa server is not

Hi,
I have installed weblogic and then soa 11g,nowe creating domain using config.sh on shared storage.
@ nodes and binaries are shared for both the nodes(all installation binaries are shared on a common location which is in turn mounted on both nodes).
After running config.sh ,
it says installation sucessful howevr Admin server directory is created..but manged soa server is not getting created.
Plz any body suggest some resolution..vvvv urgent..
Cheers,
Arshi

Hi Arshi,
Start the Admin server and then managed servers and directory should get created.
Regards,
Anuj

Do I need a Foreign JMS Server?

          Initially, I had an exploded web application, an ejb jar, a jms server, a connection
          factory and a queue all deployed under one weblogic instance. I am now trying
          to move the jms configuration to another machine running weblogic. However, I
          am unsure whether I need to configure a Foreign JMS Server on the initial weblogic
          instance. I have tried to do so and I cannot successfully start the connection
          from my web/ejb app (i.e., myQueueConnection.start() throws an exception - weblogic.jms.common.JMSException:
          Connection not found).
          I saw a thread here about changing the names of the JMS Servers, so I configured
          my web server with a foreign jms server (ForeignMessageServer) and I configured
          one foreign connection factory and one foreign destination. The local jndi names
          of these are unique and different from the remote jndi name. The remote jndi names
          match the names of the connection/destination on the app server (my 2nd server).
          I am using the url of the web server as my provider url and the foreign connection
          factory local jndi name to look up the connection.
          I have two questions:
          Is it necessary to use a foreign jms server configuration to implement this structure?
          If a foreign jms server configuration is necessary, am I going about this correctly?
          Thanks,
          John


It certainly will work. Basically, all it does is move information like the
          JNDI provider name and URL from your deployment descriptors into config.xml.
          For a lot of applications, that's a big help. You can use the "Foreign JMS
          Provider" support anywhere you want to create a JNDI entry on your local
          server that points to something else. You can even use it to point to a JMS
          queue, topic, or connection factory in the same cluster, or the same WLS
          server if you want. I do this for testing so I don't have to have different
          versions of my EJB for different environments.
          As for the bridge, it depends on whether you need to interact with the JMS
          provider synchronously or asynchronously. When you use the bridge, you first
          put the message on one JMS queue or topic, and the bridge copies it to the
          other. So, if the foreign provider is down, you can still send messages.
          However, using the bridge adds an extra "hop" which will slow performance.
          greg
          <[email protected]> wrote in message news:[email protected]...
          > Hi Tom,
          >
          > If I have 2 WLS servers: server1 and server2 and they are NOT in the same
          > cluster. server1 wants to send a JMS message to server2. I know I can
          > achieve the desired result using your 3 suggestions below but would
          using
          > foreign JMS server works as well? When should I use foreign JMS server
          > instead of a messaging bridge?
          >
          > Thanks,
          >
          > Vincent
          >
          >
          >
          > "Tom Barnes" <[email protected]> wrote in message
          > news:[email protected]...
          > > If both weblogic servers participate in the same cluster
          > > there is no additional configuration needed.
          > > All servers in cluster share the same JNDI
          > > name space. Simply specifying a JNDI name
          > > (as you already must have done) is enough
          > > for any server in the cluster, or any client connected
          > > to the cluster, to find a JNDI resource that is hosted
          > > on any server in the cluster (such as queue).
          > > This location transparency is one of the primary
          > > benefits of using clusters.
          > >
          > > If the MDB is in a different cluster than its
          > > source destination, then you have three choices
          > > (1) Change the MDB weblogic descriptor to specify
          > > a URL that resolves to any one of the
          > > addresses of a WL server in the remote cluster.
          > > I don't recall the name of the URL field,
          > > but it is in the weblogic descriptor, and
          > > is documented in the EJB (MDB) programmer's
          > > guide.
          > > (2) Configure wrappers that refer to the
          > > remote JMS resources in the cluster, and change
          > > the MDB descriptors to point to the jndi
          > > locations you configured for the wrapped
          > > connection factory and wrapped destination.
          > > (3) Configure a messaging bridge that
          > > moves from the remote destination to
          > > a local destination (which, in turn,
          > > the MDB consumes from).
          > >
          > > Tom
          > >
          > > John Owen wrote:
          > >
          > > > Initially, I had an exploded web application, an ejb jar, a jms
          server,
          > a connection
          > > > factory and a queue all deployed under one weblogic instance. I am now
          > trying
          > > > to move the jms configuration to another machine running weblogic.
          > However, I
          > > > am unsure whether I need to configure a Foreign JMS Server on the
          > initial weblogic
          > > > instance. I have tried to do so and I cannot successfully start the
          > connection
          > > > from my web/ejb app (i.e., myQueueConnection.start() throws an
          > exception - weblogic.jms.common.JMSException:
          > > > Connection not found).
          > > >
          > > > I saw a thread here about changing the names of the JMS Servers, so I
          > configured
          > > > my web server with a foreign jms server (ForeignMessageServer) and I
          > configured
          > > > one foreign connection factory and one foreign destination. The local
          > jndi names
          > > > of these are unique and different from the remote jndi name. The
          remote
          > jndi names
          > > > match the names of the connection/destination on the app server (my
          2nd
          > server).
          > > > I am using the url of the web server as my provider url and the
          foreign
          > connection
          > > > factory local jndi name to look up the connection.
          > > >
          > > > I have two questions:
          > > >
          > > > Is it necessary to use a foreign jms server configuration to implement
          > this structure?
          > > > If a foreign jms server configuration is necessary, am I going about
          > this correctly?
          > > >
          > > > Thanks,
          > > > John
          > >
          >
          >

Migratable JMS server

Hello!
Weblogic 10.3.6
I just trying to create JMS cluster.
First i have two managed servers (MS1 and MS2) in the same domain (DOMAIN1) and in the same cluster (CLUSTER1). Cluster have not any additional settings related to migration options.
Then i create file store "FS1" with target "MS1 (migratable)".
Then i create one JMS server "JMSS1" with target "MS1 (migratable)" and with file store FS1.
Then i create connection factory "CF1" with target CLUSTER1.
Then i create distributed queue "Q1" with target CLUSTER1.
May i hope with this configuration that Q1 will jump to MS2 in case of fail on MS1?

Hi,
Please follow the below steps for the automatic migration:
1. First cluster needs to be configured for automatic server migration:
Home->Cluster->configuration ->Migration -> Lock and Edit ->Choose Migratable machine for automatic server migration ->Data Source For AUtomatic Migration(Choose Datastore for automatic server migration) -> Click on Save
2. Environment -> Migratable target -> click on the migratable target -> Click on Migration -> select the Constrained Candidate Servers -> select service migration policy as Automatic Migrate Failure Recovery services -> Save and activate changes
3. Need to create a table called ACTIVE in the DB and the ddl script is located under($WL_SERVER/wl_server_10.3/server/db/oracle/920) query name:leasing.ddl
4. Create a Non XA data source(While selecting the driver you should select the Non XA driver) and in the transaction tab of the data source uncheck the global transaction option. Also the data source should point to cluster.
5. The data source created in the step 4 should be used in the JDBC Persistence store and also can be used in Cluster data source. The JDBC persistence store should be used in the JMS server and the JMS Server should be used in the JMS Queue.
Regards
Asutosh Kar

Weblogic Domain not getting created in SOA Suite 11g R2

I have installed the components of SOA Suite 11g R2 (11.1.1.3) on a single Windows XP SP3 machine (32 bit) following recommended procedures. I tried to configure Weblogic server using Domain Configuration utility. After navigating hrough the wizard, no Weblogic server profile is getting created in the doamin folder. Even the WL Admin server is not getting created. The Domain Configuration utility did not throw any errors.
1) Is this problem related to Oracle repository for SOA suite 11g?
2) Can the repository schemas (Oracle) hold multiple weblogic SOA domain information?

Hi,
Weblogic servers directory do not gets created after domain creation or even managed server configuration. It will present itself only when you start the managed server for the first time, that is when it initializes all security attributes, diagnostic attributes (if configured) , etc..
Perform server start and then check if it gets created or not.
## rank answer if it is helpful ##
Thanks,
Ranjan

JMS Adapter to remote JMS Server in ESB??

Has anyone successfully setup a JMS adapter in the ESB to talk to a JMS server on a remote host?
We are using OC4J JMS and so I followed the instructions in section 5.2.1.7 in the Adapters guide on this. I updated the oc4j-ra.xml file. The guide didn't state which version of oc4j-ra.xml to update, but I've been told to use the one in:
$ORACLE_HOME/j2ee/<oc4j>/application-deployments/default/
So, I added the XML block as specified in this section and made the JMS Connection JNDI name match that of my JMS Adapter. However, the Adapters guide then states the following:
In addition, you must have the file META-INF/application-client.xml in the
classpath. The contents of the file can be the following:
<application-client/>
To put this file in the classpath, put the specified contents into the file at Oracle_
Home\bpel\system\classes\META-INF\application-client.xml and
restart Oracle BPEL Server.
This is a problem for me because I have an advanced installation with ESB and OWSM on top of OC4J, but I do not have BPEL installed in this location. As such, the file $ORACLE_HOME/bpel/system/classes/META-INF/application-client.xml does not exist. I did a search and did find an application-client.xml at the following location:
$ORACLE_HOME/j2ee/oc4j_esbdt/connectors/JmsAdapter/JmsAdapter/META-INF
But at this point, I don't know what to do with it to ensure it is in the classpath. The Adapters guilde says to cycle the BPEL Server, so I cycled the ESB for good measure, then deployed my project, but no luck! It is still listening to the local jms server and not the remote one.
Has anyone successfully set this up? What am I missing or doing wrong?

The above classpath requirement should only ensure that BPEL module can access the JMS adapter. Otherwise it should be OK.
I would reccommend to try to establish the JMS connection and see if some parts of the Oracle AS will throw any exception or something. It might start working as well.
As I understand, you are trying to access OC4J JMS from another server. As JMS is purely TCP level protocol there should be no problem accessing it from anywhere. Only the addresses and ports must be reviewed and ensure that they point to correct place, that usernames and passwords are correct and that there is a JNDI connectivity available as you use JNDI to get the connection factories.
Rein

Jms server

Hello:
          In a cluster with nodes from different subnet ( with weblogic 7.0 sp1)
          there is an application deployed with mdb's. The jms server is not
          clustered and is targetted only on one server in the cluster.
          When the second node is starting, it is not able to comminicate with the
          jms server running in the other node. The connection factories are
          clustered.
          What I may be doing wrong.
          regards,
          Ravi


I suggest reading the cluster documentation,
          and posting questions to the clustering or jndi newsgroup.
          Cluster configuration is outside the scope of JMS per se.
          Ravi Krishnamurthy wrote:
          > Hello:
          > If the cluster multicast address is set to default it works fine. When it is
          > set to 239.192.24.123 it does not work.
          >
          > regards,
          > Ravi
          >
          > Ravi Krishnamurthy wrote:
          >
          >
          >>Hello:
          >>In a cluster with nodes from different subnet ( with weblogic 7.0 sp1)
          >>there is an application deployed with mdb's. The jms server is not
          >>clustered and is targetted only on one server in the cluster.
          >>
          >>When the second node is starting, it is not able to comminicate with the
          >>jms server running in the other node. The connection factories are
          >>clustered.
          >>
          >>What I may be doing wrong.
          >>
          >>regards,
          >>Ravi
          >
          >

Content server is not running.

All,
I have rather peculiar issue. The external 10.1.3.1 content server is setup against EBS 12.1.3.The content server is running fine and I was able to upload content using it. I fail to upload content all of the sudden until EBS is bounced. Nothing changes on content server side and again it works for day or two and stops and throws "Content server is not running" error. Is there any EBS configuration that can cause this behavior? I do not even see the request being logged in default-web-access-<date>.log on content server that indicates that it is not even reaching content server. It works fine in TEST environment and in PROD it is behaving in this manner. This is a new setup.
Any pointers are appreciated.
Thanks,
Faisal

The fact that bouncing EBS fixes the issue temporarily indicates that the problem is most likely on the EBS end, but we haven't encountered that specific issue. What OS are you using to host EBS? Are you purging the J2EE cache when you bounce the services?
Feel free to reach out to Anne or myself if you'd like to dive into this. We could test with an alternate content server to see if that helps isolate the problem.
Best,
John Hobart

HELP SMTP_SUBMIT server is not responding

All 4 of my inbound mail servers (MTA) are throwing SMTP_SUBMIT server is not responding errors!
These are all Solaris 9 boxes using
Sun Java(tm) System Messaging Server 6.2-3.03 (built Jun 27 2005)
libimta.so 6.2-3.03 (built 01:16:06, Jun 27 2005)
SunOS msgmta-4 5.9 Generic_122300-38 sun4u sparc SUNW,Netra-240
I found other postings like this on this site, but they don't seem to apply to my servers. I checked the job_controller.log,
and it's empty.
The default log shows:
[23/Aug/2010:10:30:10 -0800] msgmta-4 msprobe[28092]: General Critical: SMTP_SUBMIT server is not responding
[23/Aug/2010:10:35:10 -0800] msgmta-4 msprobe[28545]: General Error: function=getserverresponse|port=587|error=failed to get server banner
I did the obvious thing and stopped msg and restarted it, however, this did not resolve the problem.

thank you. I found out from a co-worker that this was not the showstopper that I thought might have been the problem which turned out to be a hung process on one of the other servers. I thought that there was a way to mark this as resolved, but for some reason I am not finding it right now.

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

Similar Messages

Maybe you are looking for