Version Cue Problems...

I have been testing Version Cue for a couple days now and I am having constant problems with it. Version Cue will only allow me to publish updates a couple times and then fails publishing updates. The problem is that GoLive believes that Version Cue HAS published the updates.

Here is an example log:

2003-11-20 18:04:06,588 [Job-101] ERROR com.adobe.bauhaus.controller.publish - Publish Site failed.
java.lang.NullPointerException
at com.adobe.bauhaus.controller.publish.internal.PublishController.contentProcessAndDeployFile(PublishController.java:1579)
at com.adobe.bauhaus.controller.publish.internal.PublishController.access$600(PublishController.java:132)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.deployBlock(PublishController.java:1394)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.executeItem(PublishController.java:1344)
at com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1410)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1241)
at com.adobe.bauhaus.controller.publish.internal.PublishController.publish(PublishController.java:259)
at com.adobe.bauhaus.controller.golive.PublishCtl$1.executeItem(PublishCtl.java:199)
at
com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.golive.PublishCtl.publish(PublishCtl.java:211)
at com.adobe.bauhaus.controller.golive.PublishCtl.publishSite(PublishCtl.java:74)
at com.adobe.bauhaus.golive.mgr.PublishMgr.publishSite(PublishMgr.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.adobe.bauhaus.controller.core.Job.run(Job.java:151)
at java.lang.Thread.run(Thread.java:554)

After restarting Version Cue I go through the same cycle.

The machine is a Dual 2.0 G5 with 512 RAM and ALL updates. This machine is running no other software other than Version Cue and is a clean install of Panther. I also have 256 allocated to Version Cue.

Any help????

Hi,

its very hard to reproduce that problem, so, I have some questions for you:
- Does this only happens if you use "Upload Modified"?
- Have you tried "Upload All" (this resets the modified tracking) or is it independent from the "Upload"-kind?
- Are there more stack traces (that's what you sent) in the log?
- Did you use some "Strip Options"?
- Did you move/delete some files in the VersionCue Workspace directory? This will definitely break the VersionCue Workspace.

Do you had a closer look into the logfile of the publishing? (You find in the Browser Admin: Advanced->Reports select "Publishing" in Report-popup and choose the publish report with the errors.

So many question, but any answer is very helpful,
Thanks Martin

This is what I see in the stack trace:

2003-11-20 19:25:02,458 [Job-218] FATAL com.adobe.bauhaus.controller.publish - error prepare deploy data
java.io.FileNotFoundException: /Users/mminard/Documents/VersionCue/data/content/7001/0/6/2537 (Too many open files)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at com.adobe.bauhaus.core.io.internal.AsyncOpenFileInputStream.<init>(AsyncOpenFileInputStream.java:47)
at com.adobe.bauhaus.core.io.internal.IOFileHandler.read(IOFileHandler.java:234)
at com.adobe.bauhaus.model.internal.asset.ContentHandler.getContent(ContentHandler.java:145)
at com.adobe.bauhaus.model.internal.asset.AssetVersion.getContent(AssetVersion.java:744)
at com.adobe.bauhaus.controller.publish.internal.PublishController.getContentAsStream(PublishController.java:1653)
at com.adobe.bauhaus.controller.publish.internal.PublishController.contentProcessAndDeployFile(PublishController.java:1497)
at com.adobe.bauhaus.controller.publish.internal.PublishController.access$600(PublishController.java:132)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.deployBlock(PublishController.java:1394)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.executeItem(PublishController.java:1344)
at com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1410)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1241)
at com.adobe.bauhaus.controller.publish.internal.PublishController.publish(PublishController.java:259)
at com.adobe.bauhaus.controller.golive.PublishCtl$1.executeItem(PublishCtl.java:199)
at com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.golive.PublishCtl.publish(PublishCtl.java:211)
at com.adobe.bauhaus.controller.golive.PublishCtl.publishSite(PublishCtl.java:74)
at com.adobe.bauhaus.golive.mgr.PublishMgr.publishSite(PublishMgr.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.adobe.bauhaus.controller.core.Job.run(Job.java:151)
at java.lang.Thread.run(Thread.java:554)

The publish report, however, believes the changes were published ok.

Also, I have just been trying to "Upload Modified" since the site contains so many files. I did NOT use any "Strip Options" and have not moved any files in the VersionCue Workspace.

I will try upload all.

Also, I have well over 1000 log entries in the stack traces.

I will update later today as to what I find today...

I just tried to "Upload All" and here is what happened:

2003-11-21 13:04:42,954 [Job-327] ERROR com.adobe.bauhaus.controller.publish - Publish Site failed.

java.lang.NullPointerException
at com.adobe.bauhaus.controller.publish.internal.PublishController.contentProcessAndDeployFile(PublishController.java:1579)
at com.adobe.bauhaus.controller.publish.internal.PublishController.access$600(PublishController.java:132)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.deployBlock(PublishController.java:1394)
at com.adobe.bauhaus.controller.publish.internal.PublishController$7.executeItem(PublishController.java:1344)
at com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1410)
at com.adobe.bauhaus.controller.publish.internal.PublishController.deployFiles(PublishController.java:1241)
at com.adobe.bauhaus.controller.publish.internal.PublishController.publish(PublishController.java:259)
at com.adobe.bauhaus.controller.golive.PublishCtl$1.executeItem(PublishCtl.java:199)
at com.adobe.bauhaus.controller.core.AbstractControllerCall.execute(AbstractControllerCall.java:239)
at com.adobe.bauhaus.controller.golive.PublishCtl.publish(PublishCtl.java:211)
at com.adobe.bauhaus.controller.golive.PublishCtl.publishSite(PublishCtl.java:74)
at com.adobe.bauhaus.golive.mgr.PublishMgr.publishSite(PublishMgr.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.adobe.bauhaus.controller.core.Job.run(Job.java:151)
at java.lang.Thread.run(Thread.java:554)

The publish report shows a status of OK with 956 published files, 100 ok and 0 errors

Anyone from Adobe around?

Is your email address in your forum registration correct? An Adobe engineer asked me for it in the past day or so. Someone should be getting in contact with you.

John

Hi,

I just asked you - offline - for more details about your installation. They are to extensive to discuss them here.

Thanks,

Sebastian

My email address was INCORRECT in my profile...sorry about this. It was a very old email address.

Anyhow, I have corrected the email address. You can email me at mike@deltagroup.com.

Thank you!

I'm getting similar results when converting a single user site to a Version Cue site. It has trashed my site and returns the error:

CPP_EXCEPTION (-1) A interface method is called with an NULL core pointer

I'm so disgusted with Adobe over the latest round of updates!!!!

It seems that most problems are being caused by a corrupt database file within Version Cue. Here are some things that I can recommend (I will have a further overview tomorrow as 4 people will be using Version Cue at the same time tomorrow).

1. Make sure that within the system preferences of the machine running Version Cue that you set the machine to NEVER sleep. If your machine goes to sleep while Version Cue is running it can corrupt the Version Cue database.

2. To go along with #1 I have set the hard disk(s) to never sleep.

3. If your websites use Unix line breaks make sure you setup all GoLive clients to use Unix line breaks as default prior to connecting to any Version Cue project. I have had GoLive re-write ALL files with Windows/Mac line breaks :(

More to follow tomorrow...

To Michael Machado - I'm not sure what to tell you... have you tried importing into Version Cue as a new project from FTP?

Here is an update...

Version Cue System configuration:

G5 Dual 2.0
512 Mb RAM
OS X 10.3.1 - Bare system install with ALL system updates
Version Cue ONLY software installed
Energy Saver set to Never sleep, to never put the hard disks to sleep, and processor performance to Highest.
Version Cue set to make the workspace visible to others, Small (2-4 people), optimize for Web Media and memory useage to 256Mb

This seems to have done the trick for my problems. I believe I had a corrupt database file which was the root cause of my errors. I also found that if the system goes to sleep while Version Cue is working it will corrupt the Version Cue database as well. I am not sure if this is noted anywhere in the Version Cue documentation. Actually the system completely freezes.

Hope this helps some of you!

I also found that if the system goes to sleep while Version Cue is working
it will corrupt the Version Cue database as well. I am not sure if this
is noted anywhere in the Version Cue documentation. Actually the system
completely freezes.




I have VC installed on a PowerBook G4 which goes to sleep all the time. I have not experienced any problems of the kind you describe.

I am not sure what caused your problems, but I doubt it was that per se.

John

I received a message from a Version Cue manager who said that, in their testing, Adobe had never found any problems with sleep settings affecting data integrity.

The system going to sleep IS what caused Version Cue corruption. For some reason the machine did go to sleep while posting updates from Version Cue to the web server. The machine was set to go to sleep after 10 minutes of inactivity. After waiting for Version Cue to post the files (~3 minutes) we went and checked the machine...sure enough, it was asleep and the Version Cue database was corrupt.

1 - If going to sleep did not cause it, what did?
2 - Why was the machine asleep about 3 minutes after starting to post updates to the web server?
3 - Why have we had NO problems with Version Cue after changing this setting and ONLY this setting?

We did verify that Version Cue had started posting updates by checking the web server log file! Bottom line, the machine DID go to sleep! Why is another question...

Another thought...

If going to sleep will not affect version cue provide another plausable explination for the following facts.

1. Version Cue was posting updates to a web server and had not responded within ~3 minutes.

2. Upon checking the Version Cue machine immediately after #1 it was found that the machine was asleep.

3. The Version Cue machine was set to go to sleep after 10 minutes of inactivity.

4. Upon checking the web server log files it was found that Version Cue had connected to the web server and started posting files via FTP.

5. The machine was a completely clean machine with a new install of 10.3.1 with all updates applied.

6. There was no other software running (or installed) on the machine other then Version Cue.

7. Upon waking-up the machine locked-up HARD.

8. A forced reboot was required and upon re-boot Version Cue would not start.

9. Version Cue did a recover (of something) but the site that was being worked on did not operate correctly...very odd things. Version Cue said files were checked-out that were not and we could not re-set the check-out status within Version Cue. We had to copy the site, delete the old one, and re-name the copy. This brought everything back to normal.

Hopefully this information may be helpful to some...and hopefully Adobe reads this as well.

Hi!

I have massive problems with VC, and they can very well be related to the computer going to sleep.

Using it on my Mac, the greatest letdown was the overall sluggishnes of the VC/Golive CS setup.

Then I experienced random crashes and odd bugs.

The only way I can use it now is to connect to the VC project from Golive CS running on a Wintel...!