It looks like Veracode does not like executing queries using the
ResourceResolver.findResource() method. ResourceResolver doesn't have a
parameterized version. Has anyone been able to resolve this issue? The
customer I am working fore requires that all Very High to Low risk
assessments are removed.
That is what I was afraid of. The client has a lot of sites and authors
are dumping large numbers of assets, many could be duplicates so the
search in the sidekick for assets takes a very long time to return
results. Limit would help where assets are found, but not in the case
where it takes a long time to complete. That is the biggest problem is
limiting queries that take very long to complete. The user might leave
the page but the queries run on, consuming CPU cycles that are no longer
I have a client that is on AEM 6.2 and I am being asked to set timeouts
on xpath searches. Looking at the documents for
javax.jcr.query.QueryManager, I don't see any way to do this.Is there a
way to watch a query's execution time and kill the thread after X number
Found it. There was a component in the header that had a data-sly-unwrap
attribute but didn't have anything to unwrap. It probably broke the
document structure. 6.1 must not have cared but it was a big deal in
6.3. i removed the attribute and the edits all work as expected.
A client of ours is porting their site from 6.1 to 6.3. There are some
components for which the edit frame and edit icon do not display when
clicking inside them in edit mode. I can get to the configuration from
the content tree in the sidebar but authors cannot access the
configuration from the touch UI like other components. It isn't specific
to any particular component s but they are components added to a page
component in the content.xml file and are simple added as follows:There
is a touch ...
I think I have it working now. In all of the documents it has you load
the dispatcher with:LoadModule dispatcher_module
/usr/local/libexec/mod_dispatcher.soThen configure it with:DispatcherConfig
3DispatcherDeclineRoot 0DispatcherUseProcessedURL 1DispatcherPassError
0I changed the to be
and it looks like the configuration was actually loaded.
I have the dispatcher running now but I am receiving the
following:[dispatcher:warn] [pid 62956] Dispatcher set as handler, but
not configured in server [10.45.9.173].Searching the web is coming up
with nothing so far.
I think I have everything set up according to the documentation but when
I start the httpd, I see this error from the dispatcher. There is a
dispatcher.any file set up and in the configuration folder.
[dispatcher:notice] [pid 60245] Server [10.45.9.173] has no dispatcher
0DispatcherDeclineRoot 0DispatcherUseProcessedURL 1DispatcherPassErr...
PuzanovsP wrote... Have seen this issue when downloaded wrong .so file
which was not compiled for my OS. For mac Mid 2015 you should use:
dispatcher-apache2.4-darwin-x86-64-4.2.2.tar.gzMac OSX (Darwin) x86
64bit Regards, Peter That is the one I'm using. I've also read all of
the documents on installing the dispatcher as well. I am on the latest
version of OSX(Seira). Maybe part of the problem is that they don't a
library for that version. Who knows. The httpd seems to start fine
without the disp...
Following the documents I've downloaded the Dispatcher but when trying
to run the Apache HTTP server, I am encountering the following error.
Any ideas of what I need to change to get the library to be recognized
and loaded? The version of the daemon is 2.4.23.Syntax error on line 172
of /private/etc/apache2/httpd.conf: Can't locate API module structure
`dispatcher-module' in file /usr/local/libexec/mod_dispatcher.so:
dlsym(0x7fec7b7000f0, dispatcher-module): symbol not found