2008 R2 Replication Problem

Over the weekend I had to replace one of our 43 domain controllers. Pretty standard practice of demoting the old one, waiting for replication and so on.
For the second time in a month I noticed a problem. The DC I demoted was one of two in a site. I demoted it and the other DC in the site saw the demotion. However it never replicated to anywhere else, even after 2.5 hours. (We have 15 minute replication).
I looked and the remaining DC has a replication setup (auto generated) to one of the servers in our main site and it would not replicate even when I selected to replicate now.
I saw this a few weeks ago when I replaced a DC in the main site, the other four in the site saw the change but the replication never left the site for 3 hours in that case.
I ran commands to check replication and all seemed fine.
I never have a problem when I demote the only DC in a site, it replicates out right away to all DCs, only sites that have more than one DC have a significant delay or don't replicate at all.
Does anyone know things to look for when all the replication tools show no problems but something like this happens?

If you look at the DCs in that site, you see connection objects where those DCs replicate FROM another site, that doesn't mean that dose connection objects are used to replicate changes OUT of the site. For this connection objects are setup on other DCs
that replicates FROM the effected site, it is _those_ connection objects that need to be adjusted, and that takes place when the current ones have been detected as stale.
Even if there is multiple replication paths it doesn't mean they are all used.
I recommend the following reading:
How Active Directory Replication Topology Works:
http://technet.microsoft.com/en-us/library/cc755994(v=ws.10).aspx
KCC and Topology Generation:
http://technet.microsoft.com/en-us/library/cc961781.aspx
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Similar Messages

HT203177 I have a MacBook OSX 10.5.8 and a Time Capsule 500GB since July 2008. My problem is (for the 4th time in 4 yrs) the backup gets stuck in "preparing" indefinitely (hours). In the past, wile still under apple care warranty, tech support had me redo

I have a MacBook OSX 10.5.8 and a Time Capsule 500GB since July 2008. My problem is (for the 4th time in 4 yrs) the backup gets stuck in "preparing" indefinitely (hours). In the past, wile still under apple care warranty, tech support had me redo backup (loosing previous backups). Now I'm out of warranty and still having this problem. Any help is greatly appreciated.

I have a MacBook OSX 10.5.8 and a Time Capsule 500GB since July 2008. My problem is (for the 4th time in 4 yrs) the backup gets stuck in "preparing" indefinitely (hours). In the past, wile still under apple care warranty, tech support had me redo backup (loosing previous backups). Now I'm out of warranty and still having this problem. Any help is greatly appreciated.

How can i solve this replication problem between TT and ORACLE

Hi
I have an application that using AWT cashgroup implement the replication between TT (7.0.6.7) and ORACLE(10g);
but i encounter this problem:
16:16:50.01 Err : REP: 2302682: ABM_BAL_WH:meta.c(4588): TT5259: Failed to store Awt runtime information for datastore /abm_wh/abm_bal_ttdata/abm_bal_wh on Oracle.
16:16:50.02 Err : REP: 2302682: ABM_BAL_WH:meta.c(4588): TT5107: TT5107: Oracle(OCI) error in OCIStmtExecute(): ORA-08177: can't serialize access for this transaction rc = -1 -- file "bdbStmt.c", lineno 3726, procedure "ttBDbStmtExecute()"
16:16:50.02 Err : REP: 2302682: ABM_BAL_WH:receiver.c(5612): TT16187: Transaction 1316077016/357692526; Error: transient 0, permanent 1
the isolation level of my date store is read-committed ,and the sys.ODBC.INI file is also set Isolation=1(readcommitted mode)
so ,I still wonder how the error ORA-08177!
how can i solve this replication problem?
thank you.

I suspect this is failing on an UPDATE to the tt_03_reppeers table on Oracle. I would guess the TT repagent has to temporarily use serializable isolation when updating this table. Do you have any other datastores with AWT cachegroups propagating into the same Oracle database? Or can you identify if some other process is preventing the repagent from using serializable isolation? If you google ORA-08177 there seem to be ways out there to narrow down what's causing the contention.

Session in-memory replication problem

Hi,
          I am running into some cluster HttpSession replication problems. Here is
          the scenario where replication fails (all servers mentioned here are a
          part of a cluster).
          1a - 2 Weblogic servers (A&B) are running - no users logged in,
          2a - user logs in and a new session in server A is created.
          3a - after several interactions, server A is killed.
          4a - after user makes susequent request, Weblogic correctly fails over
          to server B
          Problem: Not entire session data is replicated. The authentication info
          seems to
          be replicated correctly but there are some collections in the session of
          server A
          that did not make it to the session in server B.
          The interesting part is this: If there is only one server A running to
          begin with and a user
          interacts with it for a while and only then server B is started, when
          after server B starts up
          server A dies - the entire session (which is exactly the same as in the
          failing scenario) is
          corretly replicated in B, including collections that were missing in the
          failing scenario.
          How can this be possible ????
          Thanks for any info on this one - it really puzzles me.
          Andrew


Yes, you are on the right track. Everytime you modify the object you should call
          putValue. We will make it more clear in the docs.
          - Prasad
          Andrzej Porebski wrote:
          > Everything is Serilizable. I get no exceptions. I did however read some old
          > posts regarding
          > session replication and I hope I found an answer. It basically seems to boil
          > down to what
          > triggers session sync-up between servers. In my case , I store an object into
          > session and
          > later on manipulate that object directly wihotu session involvment and the
          > results of those manipulations
          > are not replicated - no wonder if HttpSession's putValue method is the only
          > trigger.
          > Am i on the right track here?
          >
          > -Andrew
          >
          > Prasad Peddada wrote:
          >
          > > Do you have non serializable data by any chance?
          > >
          > > - Prasad
          > >
          > > Andrzej Porebski wrote:
          > >
          > > > Hi,
          > > > I am running into some cluster HttpSession replication problems. Here is
          > > > the scenario where replication fails (all servers mentioned here are a
          > > > part of a cluster).
          > > > 1a - 2 Weblogic servers (A&B) are running - no users logged in,
          > > > 2a - user logs in and a new session in server A is created.
          > > > 3a - after several interactions, server A is killed.
          > > > 4a - after user makes susequent request, Weblogic correctly fails over
          > > > to server B
          > > >
          > > > Problem: Not entire session data is replicated. The authentication info
          > > > seems to
          > > > be replicated correctly but there are some collections in the session of
          > > > server A
          > > > that did not make it to the session in server B.
          > > >
          > > > The interesting part is this: If there is only one server A running to
          > > > begin with and a user
          > > > interacts with it for a while and only then server B is started, when
          > > > after server B starts up
          > > > server A dies - the entire session (which is exactly the same as in the
          > > > failing scenario) is
          > > > corretly replicated in B, including collections that were missing in the
          > > > failing scenario.
          > > >
          > > > How can this be possible ????
          > > >
          > > > Thanks for any info on this one - it really puzzles me.
          > > >
          > > > Andrew
          > >
          > > --
          > > Cheers
          > >
          > > - Prasad
          >
          > --
          > -------------------------------------------------------------
          > Andrzej Porebski
          > Sailfish Systems, Ltd. Phone 1 + (212) 607-3061
          > 44 Wall Street, 17th floor Fax: 1 + (212) 607-3075
          > New York, NY 10005
          > -------------------------------------------------------------

Installing SP3 on MSSQL SERVER 2008 with Replication

Hi there
How would one go about installing SP3 on SQL 2008 with replication? Would i need to turn off replication to avoid schema changes taking place across the line?
Our servers are across the country and wouldn't want all that data to replicate over the tiny line we have.
Instead we would like to install SP3 at the publisher and then at the subscriber.
During testing on the dev instances, after stopping all agents ( log reader and queue reader) then installing and turning them back on didnt seem to work.Are there any whitepapers on the proper process on how to install SP3?
Thanks in advance

Hello,
You should apply the service pack on the distributor first, then the publisher, and finally the subscriber.
To my knowledge, replication should be suspended while the service pack will be applied on the distributor. Transaction will remain on the publisher until the distributor is
available again.
When you apply the service pack on the subscriber, the replicaction from the distributor to the subscriber will be suspended, and transaction will be on the distributor until the subscriber is available again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

DFS Replication Problem

Hi Friends,
I have windows server 2003 domain at two location before somw month back its replication data
and its working fine but now i unable to see replicate data i mean i thing having replication problem
i gotted some evint id error on server
Event id error :- 5002 , 4202 , 1925 ,13568
Please help me .
Thanks,
Madhukar

The 4202 is staging quota size is too small.
Run these 2 Power Shell commands to determine the correct Staging Quota size:
$big32 = Get-ChildItem DriveLetter:\FolderName -recurse | Sort-Object length -descending | select-object -first 32 | measure-object -property length –sum
$big32.sum /1gb
Take that resulting number, round it up to the nearest whole integer, mulitply that times 1024 and enter that number on the Staging tab of the Properties of a replicated folder in DFS Mgt.
More info here:
http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx
Run this command to tell you the status of Replication:
wmic /namespace:\\root\microsoftdfs path DfsrReplicatedFolderInfo get replicatedFolderName, State
0: Uninitialized
1: Initialized
2: Initial Sync
3: Auto Recovery
4: Normal
5: In Error
Let us know how that goes.

HELP ME!!! I have a problem regarding SQL Server 2008 R2 Replication! :((((

Good day!
I'm having a big problem in my SQL Server 2008 R2... I can't see the "Local Publication" under the Replication...
About not installing it, I guess that's not true because I checked all the features to install.
Is this a bug? Do I need to re-install my SQL Server 2008 R2? Or simply, do I need to do something simple without re-installing it?
PLEASE HELP....
See Link below:
http://oi59.tinypic.com/4jx3y1.jpg

None. This is a freshly installed SQL Server 2008 R2. After installing, All I did was create a database.
If you want to know how I did it, simply:
1. Open SSMS, connect to local server
2. Open Object Explorer
3. Expand your local server
4. Right+Click on the Database then clicked on to "New Database..."
5. Entered my database name then clicked "OK"

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

SQLCE Agent Replication Problem, maybe related to SQL Server not on default port

I've got a problem getting the SQL Server CE Replication setup on a new server. SQL Server is 2008 R2 but we are running on a non-standard port (not 1433) and I'm not sure where I'd tell the agent that or if I need to. I've turned on full diagnostics and
set the Level to 3. Using the diag option on the agent, I can see that is set.
In the log file, I get this error: Hr=80004005 ERR:OpenDB failed getting pub version 28627 (rest of log is below)
when I try to sync
and the client gets: : 0x80004005
Message : Failure to connect to SQL Server with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the SQL Server, or the password is incorrect.
Minor Err.: 29061
I am pretty certain that the user name / password are correct and I can connect as that user in SQL Server Management Studio. I don't see anything in the SQL Server log file for a failed connection. I do so those if I login through the Management Studio
without entering the password for example so I believe that is setup. The Agent is on the same machine as the database server so I don't believe it is a firewall or network error but this is a new machine / setup so I may be missing something in the
setup.
I am not sure exactly what else to look at to try to understand what is going on.
Agent Log (Partial):
2014/09/30 19:36:51 Hr=00000000 Compression Level set to 1
2014/09/30 19:36:51 Hr=00000000 Count of active RSCBs = 0
2014/09/30 19:36:51 Thread=EC8 RSCB=2 Command=OPWC Hr=00000000 Total Compressed bytes in = 203
2014/09/30 19:36:51 Thread=EC8 RSCB=2 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 385
2014/09/30 19:36:51 Thread=EC8 RSCB=2 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 203
2014/09/30 19:36:51 Thread=EC8 RSCB=2 Command=OPWC Hr=00000000 C:\inetpub\wwwroot\MobileRepService\35.71ACEC98F130_15D653BB-58BD-440A-BE57-C94E24CDCB59 0
2014/09/30 19:36:51 Thread=137C RSCB=2 Command=SYNC Hr=00000000 Synchronize prepped 0
2014/09/30 19:37:08 Hr=80004005 ERR:OpenDB failed getting pub version 28627
2014/09/30 19:37:09 Thread=137C RSCB=2 Command=SCHK Hr=80004005 SyncCheck responding 0
2014/09/30 19:37:09 Thread=137C RSCB=2 Command=SCHK Hr=00000000 Removing this RSCB 0
<STATS Period_Start="2014/09/30 19:32:50" Period_Duration="904" Syncs="2" SubmitSQLs="0" RDAPushes="0" RDAPulls="0" AVG_IN_File_Size="385" AVG_OUT_File_Size="0" Completed_Operations="0"
Incomplete_Operations="2" Total_Sync_Thread_Time="33" Total_Transfer_Thread_Time_IN="0" Total_Transfer_Thread_Time_OUT="0" Total_Sync_Queue_Time="0" Total_Transfer_Queue_Time_IN="0" Total_Transfer_Queue_Time_OUT="0"
/>

Thanks - that got me past that issue - I was passing the wrong database as the Publisher due to a configuration error (we are bringing up a new publication server and missed changing one of the parameters in a configuration file). I've now got another
error but if I can't determine what is wrong with that I'll post a different question.

Crystal Report 13 Visual Studio 2010 SQL Server 2008 R2 ODBC Problem

Hi Everybody,
I am new in Crystal Report.
I developed a web application in Visual Studio 2010, and my Database is SQL Server 2008 R2.
I created reports using Crystal Report 13 in Visual Studio and my Operating System is Windows 7 32-Bit.
I used ODBC Connection System DNS for my application.
It is running fine even after Hosting on my local PC.
But it creates problem when hosted on my Team Leader PC and Test Server.
Their Configurations are same but only difference is "SQL Server 2008" Not R2
The Error I am getting is "Failed to open the connection".
When I Host the same on my another team member PC, I am getting the error like
"Failed to open the connection. Details: [Database Vendor Code: 4060 ] Database Connector Error: ' [Database Vendor Code: 4060 ]' Failed to open the connection. Failed to open the connection. TestVr {CE268132-D2BD-43EC-BE45-0BCD847FBCDA}.rpt Details: [Database Vendor Code: 4060 ]"
I tried various solution to fix this bug.
But i am unable to do this and not getting any idea to fix this issue.
If anyone can guide I will be thankful to him.
All suggestions are appreciable.
Thank you

Hi,
Please use the top right search box. for ex below search which will return many useful kb's, articlea and forum threads where simillar issues are discussed.
[http://www.sdn.sap.com/irj/scn/advancedsearch?query=failedtoopentheconnection|http://www.sdn.sap.com/irj/scn/advancedsearch?query=failedtoopentheconnection]
Most probably the issue is missing database client driver / provider.
Install the driver used to connect the rpt to the db on the server and then create a 32 bit DSN with the same name as the dev machine..
Hope this helps,
Bhushan.

Windows 2008 Server Standard - Problems Printing

I have an issue with a server that we are currently setting up in a bus station.
There are 6 machines in total, one is the server which is running Windows Server 2008 Standard 32bit SP2, the other 5 are the client machines which are all running Windows 7 Pro 64bit SP1.
All 6 machines are all linked together on the same domain and they all speak to each other, i.e all ping each other.
The issue we now have is that we have 5 printers to link to the network, all the prints are plugged directly into the Ethernet sockets on the wall which then go to the switch. The prints all have ips assigned to them and the server will see them but will
not communicate with them. If we try to ping any of the printers it fails.
We have loaded print service/print management on the server and we can set up the printers through that. Again we get the error that it is not communicating with the printer so it asks you to load the driver manually(gives us a huge lists of makes and models).
In the network list through control panel we dont get a list of printers.
If anyone can help that would be great and could let us know what we are doing wrong.
If i have missed anything important out please let me know.
thanks

Until you determine the underlying network transport problem this has nothing to do with printing.
Get the network configured so you can ping or use tracert to the IP of the device. It's possible the printers are not properly configured for your network but once again not a printing issue at this point but a networking issue.
Alan Morris Windows Printing Team

In memory replication problems when I bring up a new server

          I've got in memory replication set up for 6.1. It works fine if I have 2 servers
          up and 1 goes down.
          However, if I have 1 server up and a bring a second server up, the sessions blow
          out.
          E.g. I've got server A and server B.
          Both are up, both have sessions. As new sessions come in, they are replicated over
          to the other server.
          now I bring server B down. All sessions on B fail over to A.
          so far so good.
          However when I bring server A back up some of the sessions fail as soon as the server
          is back up.
          Is this a configuration issue, is this a know problem?
          This worked fine in weblogic 5.1. In 5.1 when I brought an instance back up, everything
          worked fine.


          It turns out the problem was caused by using an old version of the Apache Plugin.
          This problem occurred while using the 5.1 apache plugin with WLS 6.1.
          Once we realized we were using the wrong plugin and swithced to the 6.1 plugin, the
          problem went away.

Oracle 11g R2 to MS Access .mdb (Windows Server 2008 64-bit) problem

I have a need to make connection from Oracle 11g R2 to MS Access database file (mdb). OS is MS Windows Server 2008 64-bit. My configuration is next:
1. I made System DNS mikeacs (using c:\windows\sys_wow6\odbcad32.exe) to my access mdb file;
2. I made initmikeacs.ora file in ora_home\hs\admin folder:
# HS init parameters
HS_FDS_CONNECT_INFO = mikeacs
HS_FDS_TRACE_LEVEL = debug
HS_FDS_SHAREABLE_NAME = c:\Windows
3. Listener.ora file is:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = C:\Oracle\product\11.2.0\dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:C:\Oracle\product\11.2.0\dbhome_1\bin\oraclr11.dll")
(SID_DESC =
(SID_NAME = mikeacs)
(ORACLE_HOME = c:\oracle\product\11.2.0\dbhome_1)
(PROGRAM = dg4odbc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = cspo02)(PORT = 1521))
4. Tnsnames.ora is:
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
MIKEACS =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=cspo02)(PORT=1521))
(CONNECT_DATA=(SID=mikeacs))
(HS=OK)
5. After this, I restarted Listener:
lsnrctl stop;
lsnrctl start;
Given feedback:
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Production
Start Date 20-RUJ-2010 14:47:21
Uptime 0 days 0 hr. 0 min. 3 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\Oracle\product\11.2.0\dbhome_1\network\admin\listener.ora
Listener Log File c:\oracle\diag\tnslsnr\cspo02\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cspo02)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "mikeacs" has 1 instance(s).
Instance "mikeacs", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
6. I created db link: create public database link macs using 'MIKEACS' (connected as sysdba);
7. tnsping mikeacs:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=cspo02)(PORT=1521)) (CONNECT_DATA=(SID=mikeacs)) (HS=OK))
OK (0 msec)
Then, when I try fire query (connected as sysdba): select * from mytable@macs;
get result:
ERROR at line 1:
ORA-28513: internal error in geterogeneous remote agent
ORA-02063: preceding line from MACS;
Although, when I fire the same query, but connected as other user, get next result:
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified {IM002}
ORA-02063: preceding 2 lines from MACS
Where is my problem? Please help. Thanks in advance!

That's the problem. DG4ODBC on 64bit Windows is 64bit and thus it also requires a 64bit ODBC driver.
If you don't find one - maybe you can install DG4ODBC 32bi on a 32bit platform (please do NOT install it on the 64bit Windows machine) and then use this 32biit DG4ODBC with the 32bit ODBC driver.
Another option would be to purchase a commercial ODBC driver or a bridged ODBC driver.

JNDI replication problems in WebLogic cluster.

I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.

It is not a good idea to use JNDI to replicate application data. Did you consider
using JMS for this? Or JavaGroups (http://sourceforge.net/projects/javagroups/) -
there is an example of distibuted hashtable in examples.
Alex Rogozinsky <[email protected]> wrote:
I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.--
Dimitri

2008 macbook overheating problems. SOS!

I have had macbook 2008 aluminum body since November 2008. It was a dream for two years until it started overheating & slowing down whenever I'd be browsing the internet on safari, firefox or opera with the cooling fans working overtime. It also occurs when I use a MSOffice applications, Preview, etc., leaving me with a very fancy machine with very limited use. Also, extended use of my macbook with the heating problem tends to cause it to go into sleep mode without much warning (imagine suddenly seeing a black screen & irresponsive mac in your lap!) & it has to be left to "cool off" for about 10-15 minutes before it is usable again.
I've been told it's a hardware glitch that needs to be fixed & it is also the reason why the base of the macbook to sink/curve slightly upwards. This problem is said to occur in white 2008 macbooks as well, which I came to know while discussing with a few friends of mine who own that particular model.
Any help on the matter (i.e. solutions) will be welcome. I live in Pakistan.

Hey
Try a laptop cooling stand mate, they are quite effective. Also, never use your Mac on a soft surface like a pillow or your lap. And the most important thing is to make sure there isn't anything blocking the air vents.
Run an OS X update to check for fixes.
You could also try resetting the SMC.
http://support.apple.com/kb/ht3964
That may fix your fans incase they aren't cooling properly.
Hope I helped and good luck

2008 R2 Replication Problem

Similar Messages

Maybe you are looking for