This may all be a moot point. After the restart last night
manual syncing of LDAP was successful without errors and I was
emailed a proper report. Reports for scheduled publishes are now
appearing correctly too.
I'm still seeing errors in todays log file, but they're
different than before. I'm not sure what to make of them or if
Was this a one time glitch or something I should keep my eye out
for? When I installed I had restarted a couple times to install the
Docx Publish Trigger and such. Not sure why this one made a
difference. I don't restart Cascade all too often, though.
Erik, it doesn't surprise me that restarting fixed the problem
but I'm still not exactly sure what the issue was. From what we
could tell it looked like some kind of class loading problem,
library incompatibility, or Java issue. Basically, an error was
happening that should have been impossible given the version of
Java you were using and the libraries that we ship with Cascade.
That's why we were having you check to see if there were some other
libraries getting loaded from one of the lib directories or if you
were using a non-standard version of Java.
Let's definitely keep an eye out for it going forward and
re-open this ticket should you run into it again.
The logs do contain some unrelated errors with database
publishing. Is this something you're actively using? If not, it
could be some stale data in the database?
Sounds good. I'll let you know if it happens again.
We do actively use database publishing for parts of our site.
Perhaps I need to flush the external database and republish. I just
can't tell if the problem is on the Cascade side or the receiving
I'm sorry to say that this problem has resurfaced. Just noticed today that LDAP is giving errors once more and publish reports are no longer showing correctly. At no time has Cascade been restarted since you had me do this last time. This is a spontaneous recurrence. The discussion was closed so I cannot attach a new log file, but if you re-open it I will send along a new one. I've already re-enabled LDAP debugging on our server just in case.
Here's today's log file. LDAP Debugging was only turned on a bit
ago, but I had to do a couple syncs since then so hopefully it'll
have the info you need.
The only addition we make, as I mentioned before, is the Docx
Trigger. That involves the inclusion of a docx directory containing
associated material at
Beyond that it is a standard install. I can send you that material
if you'd like. I got it from Rahul Bhagnari who created the trigger
The only other thing I can think to mention is that we use an
Apache worker agent configuration to present Cascade via SSL. We do
this to avoid altering Cascade's tomcat configuration and to
present a clean url to end users (by not having to include the port
information). I can't imagine if that would make a difference,
though. Thought I'd mention it just in case.
No problem. Last night I bounced the server again to get
reporting working for us. We're fine for the time being.
On an additional note, late yesterday, before I bounced the
server, I noticed that our weekly LDAP sync happened and I received
a properly formatted email as a result. The trouble seemed to be
constrained to the manual syncs and publish reports. Hope this
Thank for that information Erik. It's beginning to sound like a
race condition and possibly the result of a publish report and an
LDAP report being generated at around the same time. Definitely a
bug in our app, but we're just not sure where yet. We'll keep you
While we don't have a firm grasp on exactly when this issue
surfaces, we have what we believe to be a fix for the problem that
we will release in Cascade 7.0.1 coming out very soon.
We'd really appreciate if you can download and install this
patch and verify that the issue is resolved. There are a lot of
other good fixes in 7.0.1 for users running 7.0 so you'd want to
upgrade to this version when you can either way.
I still may have you try a very isolated fix for this issue in
your environment before upgrading, but I will get back to you on
Thanks for your continued patience and we're sorry you're
experiencing these problems.
Cascade 7.0.1 was released yesterday with a fix for CSI-369. We'd
really appreciate if you can get that installed at some point and
verify that it addresses the issues you were running into with LDAP
and Publish reports.
Are you still running into that issue in your environment?
Thanks for letting me know. I'll install the update this weekend
and will let you know how things go.
Luckily we have not run into the issue again since the last time
I mentioned it. This is our lowest use time for the CMS, however,
so I'm not sure what to read into that. Hopefully with the update
we'll simply never see the issue again. Cross your fingers.
I wanted to let you know that I performed the 7.0.1 upgrade last
Friday. I have not seen this problem recur so far. So far so good.
If it comes back I'll certainly let you know. Thanks so much for
Hi Erick, I noticed that you downloaded Cascade 7.0.3. Sorry if
that's creepy :-), we just like to keep track of clients as they
access more recent releases. I just wanted to give you a heads up
that we actually reverted our fix for CSI-369 (the one
for this discussion) in 7.0.3 as it was contributing to a more
serious we were seeing with Velocity leaking memory (CSI-413). We will
look to address that in a different way in a future patch
Yes, just a little creepy. :) I do appreciate the warning,
though. We also reported the the twitter module bug, so it's a
trade-off, I suppose. We haven't applied the 7.0.3 patch yet, so
I'll consider whether to hold off or live with the consequences.
Either way I look forward to the next patch. Thanks again!