DW CS3 site cache problem

I upgraded to CS3 with no problems except I now find that if
I attempt to delete a word of pdf file that I know is linked to an
htm page, DW no longer gives me a warning message. This means that
If I do a sync. any updated word or pdf files do not get uploaded
to the server. If I do re-create the site cache the files still do
not get "re-linked". Anybody got an idea what is going on? I have
an awful lot of pdfs and docs linked from my site.
Thanx in advance

I figured out if I drag the file window to the left it will
stay on the left. I thought
before in previous version when you select files to be on the
left the preferences menu they would go to the left. Problem
solved.
RazorTrak

Similar Messages

DW CS3 Site Management Problem.

I just loaded DW CS3. Under > Edit > Preferences >
Site > there is a section to always
show local files on the Left or Right. I select left and the
files still show on the right.
I want them on the left. Any suggestions?
RazorTrak

I figured out if I drag the file window to the left it will
stay on the left. I thought
before in previous version when you select files to be on the
left the preferences menu they would go to the left. Problem
solved.
RazorTrak

Safari problems w/java, reading sites & cache problems.

A recently upgraded to Tiger about the time lots of people in discussions reported problems with Safari & Yahoo Mail. From what I can read it's something to do with changes at Yahoo & Java within Safari. I'm having trouble using Safari & my work site. After nearly a month working with IT, it boils down to the way Safari/Java are working. Yesterday Apple Care had me reinstall Tiger after trying to determine what software updates I had done. Checking to see if I'd installed the lasted Java updates. For some reason the update list showed only 2004 items. They had me reinstall Tiger, download all the updates again. That changes the update list although it didn't change the original problem with my job site working. So I have to use FireFox now.
However, no matter what I do I can not clear the cache. What I want to do is clear the addresses that are saved in the web addess list. I thought clearing the cache, resetting Safari and dumping the history would clear the address list. Yet, the list is still there. Any hints on how to do that?
Not sure if that would effect the way a web site is opened, but there should no reason I can't clear the web sites visited.
Any help for a newbie is greatly appreciated

ibosie:
Thx for the reply. Iv only been a Mac user for a year so something are somewhat new. One thing I don't always know the right term when explaining things. I checked about 25% of the addresses in the address field that come up as I type. Some web addresses I haven't used in months & months. So it can't really be an issue related to what's saved in bookmarks. What is even stranger is that they are still there at all. I clear the cache, reset Safari, clear cookies usually every 2-3 days if not daily. Yet, all those web addresses are still there. Am I right in saying that the addresses saved is the cache?
The webmaster for my employer seems to think that one reason I can no longer view the company site might be the cache. That instead of pulling info from the recently changed programme the computer is trying to pull info from on old link saved in the computer. In any case I don't under stand why those saved addressed won't remove.
Any ideas?

Dreamweaver CS3 Site Manager Problem

I am using Dreamweaver CS3 and when I define my sites in the
Site Manager, for some reason now when I definte the Host
Directory, which looks like this:
"//caflsd/share/DEPTS/BIOSCI/BSWeb/ " (note the two "/" at the
beginning) once I hit the done button and try to connect, I get an
FTP error, and when I go back in to the Site Manager, I will see
that one of the slashes in front of the Host Directory Address is
removed, so it looks like this "/caflsd/share/DEPTS/BIOSCI/BSWeb/"
which misses the first slash. When I put it in manually while in
the Site Manager and test the connection while in the Site Manager,
it works fine...however, when I hit OK and Done, it always cuts out
the extra "/" and then the site will not connect outside of the
Site Manager. How can I get it to stop this?

i posted a reply. sorry new to this forum. the only message I receive is that there is no repsonse from the server. Initially I can connect fine and downloand all remote files. It is only when I go to upload that I get disconnected. I can upload fine with an older version of DW. I do not know if I can upload to other sites.
I called my server and was told everything on their end was fine and they tested it and was able to upload. So I am thinking it must be DW CS3

DW CS3 not importing entire site cache from DW8

Hi;
I upgraded to the CS3 web premium suite from studio 8. My
site caches were
imported but the log on info for each was not. Is there a fix
for this ?
Thanks;
Pat

I dunno. Go into DW8 and EXPORT the site definitions with
their login info.
Import them into CS3.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Pat Jones" <[email protected]> wrote in message
news:f4pkcp$1rb$[email protected]..
> Hi Murray;
>
> DW8 is still there and they're both on the same drive.
Only the log on
> info is missing. A while ago, DW8 was having problems
losing the last used
> site's log on due to IE7 (as I understand the cause). I
downloaded a patch
> for that. Any connection?
>
> Thanks;
>
> Pat
>
>
> "Murray *ACE*" <[email protected]>
wrote in message
> news:f4pjkd$111$[email protected]..
>> The site defs should have migrated forward. Did you
install on the same
>> drive? Did you uninstall DW8 before installing CS3?
>>
>> --
>> Murray --- ICQ 71997575
>> Adobe Community Expert
>> (If you *MUST* email me, don't LAUGH when you do
so!)
>> ==================
>>
http://www.dreamweavermx-templates.com
- Template Triage!
>>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>>
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
>> ==================
>>
>>
>> "Pat Jones" <[email protected]> wrote in
message
>> news:f4pj04$7h$[email protected]..
>>> Hi;
>>>
>>> I upgraded to the CS3 web premium suite from
studio 8. My site caches
>>> were imported but the log on info for each was
not. Is there a fix for
>>> this ?
>>>
>>> Thanks;
>>> Pat
>>>
>>
>
>

CS3 DW freezes recreating site cache

I have a brand new iMac (2GB RAM) and just installed CS3
yesterday. I imported my old sites (exported to .ste files from my
PC) and when I go to point DW to my site's files on my local
fileserver (Windows server) all seems to go well until DW starts
recreating the site cache. It counts all the files in the site,
then on about the 2nd or 3rd file it freezes. I've deleted all the
sites I've created and tried to recreate one at a time, but still
no joy. Anyone else seen this?
Thanks,
Wm

Wm,
DW could be choking on a particular file. Try moving all of
your files
to a different folder to see if you can open the site. If so,
then start
moving them back 1 folder at a time to try to isolate the
problem.
HTH,
Randy
> I have a brand new iMac (2GB RAM) and just installed CS3
yesterday. I imported
> my old sites (exported to .ste files from my PC) and
when I go to point DW to
> my site's files on my local fileserver (Windows server)
all seems to go well
> until DW starts recreating the site cache. It counts all
the files in the site,
> then on about the 2nd or 3rd file it freezes. I've
deleted all the sites I've
> created and tried to recreate one at a time, but still
no joy. Anyone else seen
> this?

DW8 hangs at 'loading site cache'

I have been running DW8 on a Vista successfully for several months. Last night I ran DW8 and it got as far as 'loading site cache' and just hung. I've tried rebooting and reinstalling and still it hangs. There was another thread here about deleting files in the configuration folder -- I tried that and still no success.
My PC is a Dell Studio with 8 GB of RAM. I've never had this problem before.
Any thoughts?
Thanks!
Clay

Use Google.
e.g.
http://windows.microsoft.com/en-AU/windows-vista/Using-Last-Known-Good-Configuration

Crash when updating site cache? MM_Username1?

Hi,
All of a sudden, tonight, DW8.0.2 will no longer open or load
one of my
sites, crashing when "Updating Site Cache". The site is ASP
linked to an SQL
database.
Checking the file that the cache gets to, I notice that the
problem file is
within a sub-directory of the site, called "/admin". Thing is
though, it's
not always the same file, but it IS always a file within the
/admin
sub-directory.
Within this sub-directory I altered, by hand, the Login User
code and
Restrict Access to Page code to create and use the session
variable
MM_Username1 as opposed to the default MM_Username.
Could this be the reason for the sudden trouble with the site
cache? I am
puzzled because the site was working fine for a few weeks
now, with this
sub-directory included, and I didn't create the MM_Username1
issue today
either, it has also been working fine for a good few weeks
now. I've also
not added anything new to the site, that I am aware of.
When I remove the sub-directory from the site, the Updating
Site Cache works
fine, so I am 100% sure there is a problem with the files
within this
sub-directory. How will I know which one though?
I've tried this, as recommended by Adobe, but I still get a
freeze-up when
re-creating the cache:
1. Try renaming the Dreamweaver user configuration folder, so
that
Dreamweaver will automatically generate a new user
configuration folder the
next time Dreamweaver launches. The Configuration folder is
located here:
C:\Documents and Settings\<username>\Application
Data\Macromedia\Dreamweaver
8\Configuration
2. Recreate your Dreamweaver user settings in the registry as
follows:
Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
Rename the "Dreamweaver 8" key to "DreamweaverOLD", so that
Dreamweaver will
automatically generate a new user settings key the next time
you launch it.
3. Recreate your Dreamweaver site definitions in the registry
as follows.
The steps below will delete your site definitions in
Dreamweaver.
4. Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
Rename the "Sites" key to "SitesOLD", so that Dreamweaver
will automatically
generate a new Sites key the next time you launch it.
Any further advice?
Regards
nath.

Found it! Jeesh.
I had a querystring value in my UPDATE redirect URL which was
coded
incorrectly!!!
I am frustrated that, rather than just highlighting the error
or, at the
very least, producing an error when opening the specific
file, this type of
thing crashed the entire DW programme.
The time I spent in Notepad today changing MM_Username1 back
to
MM_Username!! Turns out that was nothing to do with it.
<groan> Yeah,
that's right, laugh it up! :o)
Anyway, solved now. A misplaced ", %, ), (, <, >, &
etc can cause you no
end of grief! :o(
Nath.
"tradmusic.com" <[email protected]> wrote in
message
news:[email protected]...
> Hi,
> All of a sudden, tonight, DW8.0.2 will no longer open or
load one of my
> sites, crashing when "Updating Site Cache". The site is
ASP linked to an
> SQL database.
> Checking the file that the cache gets to, I notice that
the problem file
> is within a sub-directory of the site, called "/admin".
Thing is though,
> it's not always the same file, but it IS always a file
within the /admin
> sub-directory.
>
> Within this sub-directory I altered, by hand, the Login
User code and
> Restrict Access to Page code to create and use the
session variable
> MM_Username1 as opposed to the default MM_Username.
> Could this be the reason for the sudden trouble with the
site cache? I
> am puzzled because the site was working fine for a few
weeks now, with
> this sub-directory included, and I didn't create the
MM_Username1 issue
> today either, it has also been working fine for a good
few weeks now.
> I've also not added anything new to the site, that I am
aware of.
>
> When I remove the sub-directory from the site, the
Updating Site Cache
> works fine, so I am 100% sure there is a problem with
the files within
> this sub-directory. How will I know which one though?
>
> I've tried this, as recommended by Adobe, but I still
get a freeze-up when
> re-creating the cache:
>
> 1. Try renaming the Dreamweaver user configuration
folder, so that
> Dreamweaver will automatically generate a new user
configuration folder
> the next time Dreamweaver launches. The Configuration
folder is located
> here: C:\Documents and
Settings\<username>\Application
> Data\Macromedia\Dreamweaver 8\Configuration
>
> 2. Recreate your Dreamweaver user settings in the
registry as follows:
>
> Launch the Registry Editor by clicking the Start button,
choose Run, then
> type "regedit". In the Registry Editor, navigate to this
folder:
> HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
> Rename the "Dreamweaver 8" key to "DreamweaverOLD", so
that Dreamweaver
> will automatically generate a new user settings key the
next time you
> launch it.
>
> 3. Recreate your Dreamweaver site definitions in the
registry as follows.
> The steps below will delete your site definitions in
Dreamweaver.
>
> 4. Launch the Registry Editor by clicking the Start
button, choose Run,
> then type "regedit". In the Registry Editor, navigate to
this folder:
>
> HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
>
> Rename the "Sites" key to "SitesOLD", so that
Dreamweaver will
> automatically generate a new Sites key the next time you
launch it.
>
> Any further advice?
> Regards
> nath.
>

Dreamweaver CC 2014 crashes when updating site cache

Hi everyone,
I'm using Dreamweaver CC 2014 on the Mavericks operating system for mac. Dreamweaver attempts to update a site cache for one of my sites but then it pauses for a few minutes and then crashes. I thought it could have been a corrupted cache file so I deleted the MacFileCache-********.dat file inside the Dreamweaver configuration folder but this didn't work. I tested again and I got the same result.
I just wondered if anyone has had this problem or whether there's a workaround?
Appreciate any advice.

I do have one workaround that worked for MOST of my folders. It is NOT the best option--but it helped me get a little more of my website recognized. (This is working on a mac with the latest version of Mavericks. Who knows WHAT Yosemite will do!)
I dragged my biggest folders out of the larger 'site' folder and on to the desktop. I ignored them and just began with the dreamweaver site manager--creating my site by pointing to the first few folders that had been listed under 'site'. Then, I added the folders on the desktop a few at a time. It worked until I got to a larger, complicated folder...then it froze again. I worked on this all day-- and I'm done for now. But I'm not giving up. With Adobe, there is always a good outcome. Sometimes, it just takes a little longer.
If I get all the kinks out, I'll let you know. Meantime, the more people who ask the question, perhaps the more likely it is to get a little help.
THANKS.

Regular Site Cache Recreation Needed

I keep seeing this problem on these boards, and no response
from the developers. Very sad.
It seems that every few days I need to re-create site caches
for my sites, and every few weeks, DW MX simply won't open. I know
how to fix it by monkeying with the Configuration directory, but
that hardly seems like the proper way for such an expensive and
presumably professional software package to operate.
Does any DW user here (or god forbid, a developer!) have a
solution that makes the site cache more stable?

>I have DW MX2004, and I'm afraid to upgrade to 8 because
of the massive bug
> list and lack of improvements over MX2004 (particularly
this one!)
Where are you getting this misinformation? Lack of
improvements? Good
grief - in CSS alone, there are too many dramatic
improvements to count, not
to mention the server-behavior improvements, the PHP support
improvements,
the overall UI improvements, and on and on.
> Anyway, to the point: I know I need to recreate the site
cache because it
> tells me in a popup window: "The cache will now be
re-created because the
> cache
> file is missing or damaged."
OK - where is your local site physically located? Is it on a
remote network
shared drive?
> I suspect it may have to do with sharing files between 2
sites
Yes - I suspect you are correct. Give me the details of your
setup for
this, please?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"NickAvallone" <[email protected]> wrote in
message
news:[email protected]...
>I have DW MX2004, and I'm afraid to upgrade to 8 because
of the massive bug
> list and lack of improvements over MX2004 (particularly
this one!)
>
> As for the developers not checking these boards, I
didn't realize that
> it'd be
> unusual. But if I were a software developer, Priority
Number One would be
> finding out what causes my otherwise excellent software
to suck. And what
> better way than to listen to the people who use it every
day in a variety
> of
> situations/configurations?
>
> Anyway, to the point: I know I need to recreate the site
cache because it
> tells me in a popup window: "The cache will now be
re-created because the
> cache
> file is missing or damaged."
>
> I suspect it may have to do with sharing files between 2
sites, though I
> can't
> imagine why DW would object. I have to maintain
identical files on 2
> different
> servers -- something DW doesn't support -- and the only
way to do it is to
> define 2 sites, and do site sync on them both. (It's a
lot of files &
> subdirectories.)
>

How to Boot DW5 without loading Site Cache?

Is there a way to start/open Dreamweaver 5 without the site cache loading first? I realize it loads because i have the "enable cache" checked, but I'm in a weird situation where the cache takes six hours to load. I need a way to bring up DreamWeaver so i can disable the "eable cache."
Any suggestions are appreciated.
Im runnig Windows 7 professional, if it matters.
Thanks

the cache takes six hours to load
6 hours to load? Literally? How large is the site? What are the computer specs? All the latest updates? 32bit/64bit? Anything more?
I know this isn't a KB article directly related to your problem, but try #12, 4 and 13.
http://kb2.adobe.com/cps/405/kb405604.html

OD Master and MCXD Cache Problem

Hi,
has someone an idea how to solve a mcxd Cache Problem?
Always when I sate up the OD Master after a new installation of Mac OSX 10.4.11 Server, I get the mcxd problem after the reboot. After the reboot I have always this massage, see system.log in our system.
SYSTEM.LOG
Mar 5 21:45:23 mainserver /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetLocallyHostedNodeNames(): dsFindDirNode() == -14008
Mar 5 21:45:23 mainserver /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetSearchPath(): DSGetLocallyHostedNodeNames() == -14956
Mar 5 21:45:23 mainserver /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCurrentConfigInfo(): DSGetSearchPath() == -14956
Mar 5 21:45:23 mainserver /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCacheInfo(): DSGetCurrentConfigInfo() == -14956
Mar 5 21:45:23 mainserver /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: * MCXD.getComputerInfo: Couldn't get cache info -14956
How can I solve this problem?
This problem makes my crazy since 3 weeks.
And is this problem known under Mac OSX Server 10.5?
To our server system:
One XServer G5 is the DNS Server and
A second XServer G5 is the OD Master.
Thanks for your help!

Hi
+"Is the replica truly read only?"+
It should be. However I've come across a similar situation. At a site I support the local admin was creating users and editing passwords on the Replica rather than the Master. He kept getting the usual "dsDirectoryetc" errors but he persisted and eventually got the settings to 'take'. Querying the databases on both Master and Replica produced similar results to yours. It was difficult then to go back to the Master and 'redo' properly what he'd done as he'd not kept track of the changes he made. To 'fix' I simply demoted/repromoted the Replica which worked for me. Although time will tell if it turns out to be a permanent fix?
Tony

Caching problem w/ primary-foreign key mapping

I have seen this a couple of times now. It is not consistent enough to
create a simple reproducible test case, so I will have to describe it to you
with an example and hope you can track it down. It only occurs when caching
is enabled.
Here are the classes:
class C1 { int id; C2 c2; }
class C2 { int id; C1 c1; }
Each class uses application identity using static nested Id classes: C1.Id
and C2.Id. What is unusual is that the same value is used for both
instances:
int id = nextId();
C1 c1 = new C1(id);
C2 c2 = new C2(id);
c1.c2 = c2;
c2.c1 = c1;
This all works fine using optimistic transactions with caching disabled.
Although the integer values are the same, the oids are unique because each
class defines its own unique oid class.
Here is the schema and mapping (this works with caching disabled but fails
with caching enabled):
table t1: column id integer, column revision integer, primary key (id)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Because the ids are known to be the same, the primary key values are also
used as foreign key values. Accessing C2.c1 is always non-null when caching
is disabled. With caching is enabled C2.c1 is usually non-null but sometimes
null. When it is null we get warnings about dangling references to deleted
instances with id values of 0 and other similar warnings.
The workaround is to add a redundant column with the same value. For some
reason this works around the caching problem (this is unnecessary with
caching disabled):
table t1: column id integer, column id2 integer, column revision integer,
primary key (id), unique index (id2)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id2"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id2"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Needless to say, the extra column adds a lot of overhead, including the
addition of a second unique index, for no value other than working around
the caching defect.

Tom-
The first thing that I think of whenever I see a problem like this is
that the equals() and hashCode() methods of your application identity
classes are not correct. Can you check them to ensure that they are
written in accordance to the guidelines at:
http://docs.solarmetric.com/manual.html#jdo_overview_pc_identity_application
If that doesn't help address the problem, can you post the code for your
application identity classes so we can double-check, and we will try to
determine what might be causing the problem.
In article <[email protected]>, Tom Landon wrote:
I have seen this a couple of times now. It is not consistent enough to
create a simple reproducible test case, so I will have to describe it to you
with an example and hope you can track it down. It only occurs when caching
is enabled.
Here are the classes:
class C1 { int id; C2 c2; }
class C2 { int id; C1 c1; }
Each class uses application identity using static nested Id classes: C1.Id
and C2.Id. What is unusual is that the same value is used for both
instances:
int id = nextId();
C1 c1 = new C1(id);
C2 c2 = new C2(id);
c1.c2 = c2;
c2.c1 = c1;
This all works fine using optimistic transactions with caching disabled.
Although the integer values are the same, the oids are unique because each
class defines its own unique oid class.
Here is the schema and mapping (this works with caching disabled but fails
with caching enabled):
table t1: column id integer, column revision integer, primary key (id)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Because the ids are known to be the same, the primary key values are also
used as foreign key values. Accessing C2.c1 is always non-null when caching
is disabled. With caching is enabled C2.c1 is usually non-null but sometimes
null. When it is null we get warnings about dangling references to deleted
instances with id values of 0 and other similar warnings.
The workaround is to add a redundant column with the same value. For some
reason this works around the caching problem (this is unnecessary with
caching disabled):
table t1: column id integer, column id2 integer, column revision integer,
primary key (id), unique index (id2)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id2"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id2"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Needless to say, the extra column adds a lot of overhead, including the
addition of a second unique index, for no value other than working around
the caching defect.
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

I am facing a caching problem in the Web-Application that I've developed us

Dear Friends,
I am facing a caching problem in the Web-Application that I've developed using Java/JSP/Servlet.
Problem Description: In this application when a hyperlink is clicked it is supposed to go the Handling Servlet and then servlet will fetch the data (using DAO layer) and will store in the session. After this the servlet will forward the request to the view JSP to present the data. The JSP access the object stored in the session and displays the data.
However, when the link is clicked second time then the request is not received by our servlet and the cached(prev data) page is shown. If we refresh the page then request come to the servlet and we get correct data. But as you will also agree that we don't want the users to refresh the page again and again to get the updated data.
We've included these lines in JSPs also but it does no good:
<%
response.setHeader("Expires", "0");
response.setHeader("Cache-Control" ,"no-cache, must-revalidate");
response.setHeader("Pragma", "no-cache");
response.setHeader("Cache-Control","no-store");
%>
Request you to please give a solution for the same.
Thanks & Regards,
Mohan

However, when the link is clicked second time then the request is not received by our servlet Impossible mate.. can you show your code. You sure there are no javascript errors ?
Why dont you just remove your object from the session after displaying the data from it and see if your page "automatically" hits the servlet when the link is clicked.
cheers..
S

Bridge update does not fix caching problems.

Dear Adobe,
The 5.0.1.23 update for Bridge CS6 does NOT fix the problem of constantly re-caching layered TIF files.
I originaly reported the problem here on May 16, 2012.
http://forums.adobe.com/thread/1007560
At that time I also submitted a bug report via photoshop.com, and received an e-mail response from Adobe support confirming the problem had been replicated in their lab and promising a fix in the next update.
I've since tracked several other reports of this bug and related cache problems.
I assume that, at best, we will have to wait another 6 months or more for the next update. How can I assure this bug will be addressed?

redcrown on guard wrote:
The 5.0.1.23 update for Bridge CS6 does NOT fix the problem of constantly re-caching layered TIF files.
At that time I also submitted a bug report via photoshop.com, and received an e-mail response from Adobe support confirming the problem had been replicated in their lab and promising a fix in the next update.
Thank you for this bit of information. Maybe it means I can stop the deactivations/uninstall/reinstall/reactivate cycle to try yet another solution. And hopefully, this will stop the re-caching problem with other than tif files.
regards
*S*

DW CS3 site cache problem

Similar Messages

Maybe you are looking for