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

Similar Messages

Custom Objects in JNDI Not Being Replicated in Cluster

I know this is going to end up being something really simple, but I can't find
any docs or other posts on it.
I have a simple two node weblogic 7.0 cluster. In a startup class that is deployed
to the cluster I check for and create a subcontext. This subcontext will just
hold custom objects when a node comes up. When a node does come up, one of the
web applications binds a non-RMI custom object to the subcontext created via the
startup class.
Once both nodes in the cluster are up I can see via the weblogic console's "View
JNDI tree" feature that the custom object bound on node 1 is only visible in the
JNDI tree of node 1. Similarly the object bound on node 2 is only visible in
the JNDI tree of node 2.
Is the JNDI tree that is visible via the console the JNDI specific to the node
and not the clusterwide JNDI tree? Do I have to do something special to get access
to the cluster wide JNDI tree (for instance when creating an InitialContext)?
Is there a way to view the cluster wide JNDI tree?
Thanks for any information.

Hi Matt,
how did you compile t3 stubs,there are -clusterable or something like this
option shat should make replicatable-aware stubs.
"Matt" <[email protected]> wrote:
>
I know this is going to end up being something really simple, but I can't
find
any docs or other posts on it.
I have a simple two node weblogic 7.0 cluster. In a startup class that
is deployed
to the cluster I check for and create a subcontext. This subcontext
will just
hold custom objects when a node comes up. When a node does come up,
one of the
web applications binds a non-RMI custom object to the subcontext created
via the
startup class.
Once both nodes in the cluster are up I can see via the weblogic console's
"View
JNDI tree" feature that the custom object bound on node 1 is only visible
in the
JNDI tree of node 1. Similarly the object bound on node 2 is only visible
in
the JNDI tree of node 2.
Is the JNDI tree that is visible via the console the JNDI specific to
the node
and not the clusterwide JNDI tree? Do I have to do something special
to get access
to the cluster wide JNDI tree (for instance when creating an InitialContext)?
Is there a way to view the cluster wide JNDI tree?
Thanks for any information.

Security Permissions from Management Console Not Being Replicated on SQL Server Database

Hi Everyone,
We have been encountering issues with access to Reporting Services for most console users since we upgraded to SCCM 2012 R2. We have observed that since the R2 upgrade, security permissions
that are set in the console are not being replicated on the SQL database. Users/Groups that had access prior to the R2 upgrade are now only able to access Reports via the web interface. All new users/groups are not able to get access at all.
We are not sure what the problem could be and would appreciate any guidance.
We have tried the following without success:
Manually adding new users/groups to the database
Reinstalling the the Reporting Service point and Reporting Service, Removing all of the security groups from the console and from the database, and Adding the security groups back
to the console.
Our current environment:
SCCM 2012 R2
1 Site
Primary Site:
OS: Server 2008 R2
Roles: Site Server / Software Update Point / Management
Point
SQL Server
OS: Server 2008 R2
SQL Version: Microsoft SQL Server 2008 R2
Roles: Site Database Server / Reporting Services Point

Thanks for your feedback.
Permissions
We have two main types of users: Full Administrators and local departmental IT administrators. (Local IT Admins only have full control over their own departmental collections. They have Read/Add to All Systems.)
The only account that's currently able to run Reports from both the console and web is the admin account used to perform the R2 upgrade.
Full Administrator
Role: Full Administrator
Scope: All instances of the objects that are related to the assigned security roles.
Local Departmental Administrator
Role: Full Administrator & Read/Add
Scope: Main Departmental Collection (Full Admin) & All Systems, All Users, and All User Groups (Read/Add)
Report Service Execution
On the database, we have tried assigning the Report Service Execution Account to the built-in Network Service Account, Local Service Account, and to a separate AD role account.
Error Messages
Console: We are able to select reports from the Console however nothing appears when we click on Run.
Web: Generating Reports from the Web works for only the Full Administrators. Nothing appears for a Local Departmental Admin.
This is a partial output from srsrp.log:
Set configuration   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Check state   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Check server health.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Successfully created srsserver   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Reporting Services URL from Registry [http://132.205.120.154/ReportServer/ReportService2005.asmx]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Reporting Services is running   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Retrieved datasource definition from the server.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[SCM-SQL.concordia.ca] [CM_SCM] [ConfigMgr_SCM] [SCM-SQL.CONCORDIA.CA]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[MSSQLSERVER] [1] [] [CONCORDIA\SVC-SCM_REPORT]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[1] [0]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Confirmed version [10.50.2811.0] for the Sql Srs Instance.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Retrieved datasource definition from the server.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_SCM   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Loading localization resources from directory [E:\SMS_SRSRP\SrsResources.dll]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Looking for 'English (United States)' resources   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Looking for 'English' resources   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Found resources for 'English'   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Confirmed the configuration of SRS role [ConfigMgr Report Users].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the configuration of SRS role [ConfigMgr Report Administrators].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/ConfigMgr_SCM].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/ConfigMgr_SCM/Asset Intelligence].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)

Indexes not being replicated

Greeting:
Problem: I create a new index on the master instance and it not replicating to the consumer instance. Also previously existing indices are not being replicated. There are no error messages regarding replication
Direcotory Server 6.3
Actions:
** I created the consumer instance via DSCC
** I create blank suffixes on the new consumer instance
** I enable replication on consumer
** I create replication agreement on master
** I initialize replication from consumer
The indices existing on master are showing on the consumer and newly added index are also not showing up.
Please help and thanks
Ahsan

Your observation is correct. Index configuration is not replicated but is on a per-server basis. This is probably to allow various instances on the topology to serve different purposes while not being forced to maintain unnecessary indices.

DbControl not working in clustered environment

Hi all,
I have a situation here with Oracle dbcontrol -it is not working in clustered environment. It is working on one node but fails on other node. Any suggestions ?
Thanks in advance !

http://download.oracle.com/docs/cd/B28359_01/server.111/b28319/emca.htm
in this article Oracle has given example with RAC. so thats why i asked that question.Exactly, with RAC. If you specify -cluster option, you should have a running cluster, isn't it ?

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

JNDI bindings not being replicated across servers in a cluster

According to the Weblogic Server documentation, JNDI bindings are
          automatically replicated across the servers in a cluster.
          http://www.weblogic.com/docs45/classdocs/weblogic.jndi.WLContext.html#REPLIC
          ATE_BINDINGS
          This is not proving to be true in my testing. Perhaps it's "just broken", or
          perhaps my cluster isn't correctly configured...
          Here is a reproducible case. Install the following on two or more servers in
          a cluster. You'll need to change line 26 of test1 to reference one of the
          servers explicitly.
          Test 1 works fine, since both web servers connect to the same server for
          JNDI usage. The test should return the last host to hit the page, along with
          the current host name. Alternating between servers in the cluster will
          alternate the results. However, the fact that I'm specifically naming a
          server in the cluster breaks the whole point of clustering -- if that server
          goes down, the application ceases to function properly.
          Test 2, which is supposedly the right way to do it, does not work, an error
          message is logged:
          Tue Jan 04 08:17:15 CST 2000:<I> <ConflictHandler> ConflictStart
          lastviewhost:java.lang.String (from
          [email protected]:[80,80,7002,7002,-1])
          And then both servers begin to report that they have been the only server to
          hit the page. Alternating between servers will have no effect -- both
          servers are looking solely at their own copies of the JNDI tree. No
          replication is occurring.
          What is up with this? Any ideas?
          Tim
          [test1.jsp]
          [test2.jsp]


1. yes
          <JMSConnectionFactory AllowCloseInOnMessage="false"
          DefaultDeliveryMode="Persistent" DefaultPriority="4"
          DefaultTimeToLive="0"
          JNDIName="xlink.jms.factory.commerceFactory"
          MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
          OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
          2. No I am just using the jndi name of the queue.
          This is an example of how I send a message:
               Context ctx = new InitialContext();
          QueueConnectionFactory qconFactory;
          QueueConnection qcon;
          QueueSession qsession;
          QueueSender qsender;
          Queue queue;
          ObjectMessage msg;
          qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
          qcon = qconFactory.createQueueConnection();
          qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
          qsender = qsession.createSender(queue);
          msg = qsession.createObjectMessage(reportExecutorContainer);
          qcon.start();
          qsender.send(msg);
          qsender.close();
          qsession.close();
          qcon.close();
          3. I don't know those setting (wl 6.1sp7)

JMS adapter: JNDI not able to connect to TIBCO server.

Hi All,
We are facing a strange problem here related to JMS adapter. We are trying to connect to TIBCO using JMS adapter.
We have 3 different Business Services, all the three using JMS channels. All the JMS channels are connecting to the same server on same port 7222. We have every thing same in all the JMS channels except the Que Name and the queue/log on user.
All the channels under 1 particular services are working fine while under the other two are giving below error:
===========================================
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: <Interface name> on node: <server node> having object id:<Object ID>: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to any server at: tcp://<host1>:7222, tcp://<host2>:7222<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:135)<br>
=============================================
Below are the basic JMS configuration:
1. QueueConnectionFactory
2. com.tibco.tibjms.naming.TibjmsInitialContextFactory
We are on PI 7.0 and working with both Sender and Receiver JMS adapters.
Looking for your help.
Regards,
Rahul

HI,
Please reply me for this question, or to the other one JNDI not able to connect . Both aer one and the other are same.
--Khaleel

JNDI lookup in a clustered environment

          Hi,
          I have deployed my application on a clustered environment containing one admin
          server and two managed servers. The application is deployed on the managed servers.
          We have a DNS for these two managed servers.
          Currently, I am using t3:localhost:portnumber to get an initial context for JNDI
          lookup.
          But this will not provide perfect load balancing, since each server side component
          (EJB) will lookup for a needed component on the same server itself.
          Is there any way to get the Initial Context by using the DNS name?
          I tried t3:DNSName (Our DNS is created till the port number. e.g. http://DNS points
          to http://Managedserver1:portnumber and http://Managedserver2:portnumber
          It works, but is random. Sometimes, it gives me the following exception:
          Root exception is java.net.ConnectException: t3://DNS Name: Destination not
          reachable using: 't3'
          Could someone help me figure out a way to do this in a better way?
          Thanks,
          Aparna


          If you don't want or have money to use external load balancers you should be using
          the DNS entry as t3://server1:port,server2:port (you indicated you are using http.
          Also make sure your network elements between the client and the servers allow
          t3 protocol if there is packet filtering).
          S
          "Aparna" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have deployed my application on a clustered environment containing
          >one admin
          >server and two managed servers. The application is deployed on the managed
          >servers.
          >We have a DNS for these two managed servers.
          >
          >Currently, I am using t3:localhost:portnumber to get an initial context
          >for JNDI
          >lookup.
          >But this will not provide perfect load balancing, since each server side
          >component
          >(EJB) will lookup for a needed component on the same server itself.
          >
          >Is there any way to get the Initial Context by using the DNS name?
          >
          >I tried t3:DNSName (Our DNS is created till the port number. e.g. http://DNS
          >points
          >to http://Managedserver1:portnumber and http://Managedserver2:portnumber
          >
          >It works, but is random. Sometimes, it gives me the following exception:
          > Root exception is java.net.ConnectException: t3://DNS Name: Destination
          > not
          >reachable using: 't3'
          >
          >Could someone help me figure out a way to do this in a better way?
          >
          >Thanks,
          >Aparna

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.

Contacts folder in Outlook 2010 (Exchange server) is not being updated on my iPhone.

Hello
I am using Exchange email account with Contacts on Outlook 2010..
Updated contacts are not being updated to my iPhone and vice versa.
The iPhone software is the latest 7.01
iCloud is deactivated and iTunes is not being used.
Any ideas how to resolve this bug?
Interesting, it is working with my iPad.
Many thanks!

Hi alpinespace,
If you are having issues syncing your contacts between your iPhone and Outlook 2010, you may find the following article helpful:
Apple Support: Troubleshooting Sync Services on Windows with Microsoft Outlook 2003, Outlook 2007, or Outlook 2010
http://support.apple.com/kb/TS2776
Regards,
- Brenden

Deletions and changes not being replicated from handset to Exchange 2003 server for one user

Good afternoon,
We have an issue where-by one of our Q10 handsets isn't replicating deletions and moving of mail back to Exchange 2003. If the user marks mail as read or deletes in Outlook, the change appears straight away on his Q10. His previous Q10 worked correctly, as do all of our other v10 devices.
Regards,
Steve

Hi,
In addition to TP’s comment, you can go through beneath article for information.
Terminal Server and Printer Redirection
http://blogs.technet.com/b/askperf/archive/2007/08/24/terminal-server-and-printer-redirection.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

JMS bridge is not working in clustered env

          We have set up a JMS bridge between WLS7SP3 and WLS8.1. It works very well in
          stand alone server env (testing env). However, we cannot get it to work on clustered
          env (preprod env). Anyone has experienced working with clustered env? If so,
          please help!
          Thanks.


I forgot to say, we are using WLS8.1 SP1
          "Pete Inman" <[email protected]> wrote in message
          news:[email protected]...
          > If you are in a clusterd environment and you deploy a bridge to the WHOLE
          > cluster it does not work and will not find the adapter. If you deploy to
          the
          > INDIVIDUAL cluster members it will work.
          >
          > We have a cluster with 4 managed servers, deploy to whole cluster - no
          > bridge working, deploy to Server1,2,3,4 bridges work fine.
          >
          > I have a case logged with BEA on this topic.
          >
          > "Tom Barnes" <[email protected]> wrote in message
          > news:[email protected]...
          > > "Not working" is too little information. I suggest
          > > that you start with the messaging bridge FAQ. There is
          > > a link to it here:
          > >
          > > http://dev2dev.bea.com/technologies/jms/index.jsp
          > >
          > > Then post with traces, exceptions, configuration, etc, if
          > > you are still having trouble.
          > >
          > > Tom, BEA
          > >
          > > jyang wrote:
          > >
          > > > We have set up a JMS bridge between WLS7SP3 and WLS8.1. It works very
          > well in
          > > > stand alone server env (testing env). However, we cannot get it to
          work
          > on clustered
          > > > env (preprod env). Anyone has experienced working with clustered env?
          > If so,
          > > > please help!
          > > >
          > > > Thanks.
          > >
          >
          >

Queue JNDI lookup in a clustered environment

Hey all,
          I know in a 6.1 cluster, the queues/JMS servers can only reside on one
          server.
          How can i lookup a queue from internal code from one of the off servers? The
          JNDI lookup doesn't grab it, throws an object not found exception. Do I need
          to
          be using the createQueue() method in the QueueSession class?
          It's fairly critical to know this to get our app up on the cluster, so
          any help would
          be very appreciated!
          Thanks,
          Greg


          A dumb question - how do I specify JNDINameReplicated=false? I am using WLS 6.1
          SP3 and in my config.xml I have
          <JMSTopic Name="topicA" JNDIName="topicA" JNDINameReplicated="false" />
          but WebLogic does not like it.
          Eric Ma
          Tom Barnes <[email protected]> wrote:
          >The parameter name "JNDINameReplicated" parameter is only available in
          >a patch
          >on top
          >of SP2 or SP3, and is "true" by default. I doubt that you are using
          >it.
          >
          >Greg Kaestle wrote:
          >
          >> Thanks much,
          >> Where is this parameter set in config.xml?
          >>
          >> Greg
          >>
          >> "Shean-Guang Chang" <[email protected]> wrote in message
          >> news:[email protected]...
          >> > If you want the queue to be found from other server in the same cluster
          >> then
          >> > you should not set "JNDINameReplicated" to false. This
          >> > will make the JNDI name of the queue known to the local server which
          >is
          >> > hosting the JMS queue. The purpose to use "JNDINameReplicated=false"
          >> > is to have multiple queues with the same JNDI name and then use some
          >sort
          >> of
          >> > load balancer to spread load among different JMS servers in the cluster.
          >> >
          >> >
          >> > "Greg Kaestle" <[email protected]> wrote in message
          >> > news:[email protected]...
          >> > > Hey all,
          >> > >
          >> > > I know in a 6.1 cluster, the queues/JMS servers can only reside
          >on
          >> one
          >> > > server.
          >> > > How can i lookup a queue from internal code from one of the off
          >servers?
          >> > The
          >> > > JNDI lookup doesn't grab it, throws an object not found exception.
          >Do I
          >> > need
          >> > > to
          >> > > be using the createQueue() method in the QueueSession class?
          >> > >
          >> > > It's fairly critical to know this to get our app up on the cluster,
          >> so
          >> > > any help would
          >> > > be very appreciated!
          >> > >
          >> > > Thanks,
          >> > > Greg
          >> > >
          >> > >
          >> >
          >> >
          >

Deploytool problem: Tools- Server Configuration not being displayed

I am having the above titled problem when following the instructions from section 7.2.2 of the JMS tutorial.
Please help
Owen.

Typically, when I start J2EE, I get the following:
C:\j2sdkee1.4\logs>j2ee -verbose
J2EE server listen port: 1050
Naming service started: 1050
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@1250ff2
Binding DataSource, name = jdbc/_ejb_container, url = jdbc/_ejb_container__xa
Binding DataSource, name = jdbc/_ejb_container__xa, dataSource = COM.cloudscape.
core.XaDataSource@1b6235b
Starting JMS service...
Initialization complete - waiting for client requests
Starting JMS via Resource Adapter
Deploying jmsra.rar in C:\j2sdkee1.4\lib\system_apps\jmsra.rar
ResourceAdapter jmsra.rar started...
Initializing Coyote HTTP/1.1 on port 8000
Initializing Coyote HTTP/1.1 on port 7000
Loaded registry information 1432 ms
Starting service J2EE(TM) Web Server
Apache Tomcat/5.0
Missing application web.xml, using defaults only StandardEngine[Standard-Engine]
.StandardHost[localhost].StandardContext[]
Added certificates -> request attribute Valve
Starting Coyote HTTP/1.1 on port 8000
Starting Coyote HTTP/1.1 on port 7000
JACC:Policy Repository set to C:\j2sdkee1.4\repository\policy
Added certificates -> request attribute Valve
Configured an authenticator for method FORM
J2EE Web Admin Tool started
JAXR:Installing JAXR RA
Deploying jaxr-ra.rar in C:\j2sdkee1.4\lib\system_apps\jaxr-ra.rar
Binding Connection Factory, name = QueueConnectionFactory
Binding Connection Factory, name = jms/TopicConnectionFactory
Binding Connection Factory, name = TopicConnectionFactory
Binding Connection Factory, name = jms/QueueConnectionFactory
Binding Connection Factory, name = eis/JAXR
Cannot create Destination jms/Topic since it already exists
Binding Administered Object, name = jms/Topic
Cannot create Destination jms/Queue since it already exists
Binding Administered Object, name = jms/Queue
Starting EJB Timer Service...
J2EE server startup complete.
I do not see any reason in the above as to why deploytool might not be working as I think it should. Maybe others have an idea?
Owen.

JMS Server JNDI not being replicated? (clustered environment)

Similar Messages

Maybe you are looking for