julieth756 / share-extras

Automatically exported from code.google.com/p/share-extras
0 stars 0 forks source link

Audit Dashlet shows Data Error #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Enabled audit for custom content types and also cm:person
2. Create 10-15 contents with special characters in document name like + , 
underscore(_)
3. Enable sub-actions

What is the expected output? What do you see instead?
- it should display proper audit logs, instead I see 'data error'

What version of the add-on are you using? Please provide version of the
downloaded package, or Subversion revision number.
- I am using jar versioned [audit-dashlet-0.43.jar]

What version of Alfresco are you using? On what application server?
- Alfresco 4.0.0 Enterprise Edition
- Tomcat 6.x

What web browser are you using? Please supply browser name and version.
- Crome 20.0
- Firefox 13

Please provide any additional information below.

I am attaching error log file.

Original issue reported on code.google.com by rathod.g...@gmail.com on 18 Jul 2012 at 6:08

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by will.abson on 18 Jul 2012 at 12:57

GoogleCodeExporter commented 9 years ago
Don't have time to work on this right now. Need more info anyways... Ideally 
you would pull the json from the backend webscript, and paste it to e.g. 
http://jsonlint.com , and determine what is invalid in the feed. 

Then i might be able to point you towards a fix.

Original comment by romain.g...@alfresco.com on 19 Jul 2012 at 5:32

GoogleCodeExporter commented 9 years ago
the log only says that the data coming from the backend is invalid, which in 
and of itself isn't very useful. see previous comment. also please post your 
audit application config as well as audit config for the sub-actions.

Original comment by romain.g...@alfresco.com on 19 Jul 2012 at 5:35

GoogleCodeExporter commented 9 years ago
did you get the json feed ? 
Placing this in 'need info'.

Original comment by romaingu...@gmail.com on 27 Jul 2012 at 1:13

GoogleCodeExporter commented 9 years ago
Hi Romain,
Can you tell me which URL should I fire in browser to get that json?

Original comment by rathod.g...@gmail.com on 27 Jul 2012 at 1:15

GoogleCodeExporter commented 9 years ago
Hi, 

Yes please attach the output of : 
http://yourhost:8080/alfresco/service/api/audit/query/YourApplicationName?verbos
e=true&forward=false

replace your host / port as appropriate, as replace YourApplicationName with 
the name of the audit 'application' you have selected in the dashlet. 

Ideally, if you can also post your json feed to jsonlint.com, it should tell 
you why it is invalid. 

Original comment by romaingu...@gmail.com on 27 Jul 2012 at 3:31

GoogleCodeExporter commented 9 years ago
FYI i have just tried to upload a bunch of docs with special characters 
including_, + , etc, with a user that has himself special chars in its name. 
Sub events and cm:person was added too. 

I had no issues reading those events with the dashlet. the json feed was still 
valid and there was no 'data error'. I can't reproduce.

If you find out an invalid json feed, or a set of precise config / actions 
needed to encounter that invalid feed, let me know.

Original comment by romaingu...@gmail.com on 27 Jul 2012 at 4:58

GoogleCodeExporter commented 9 years ago
Hi Romain,
I don't know but, at some instance that error comes, I installed new alfresco 
4.0.0 Enterprise and enabled my log on new instance but its good that no error 
is reported as of now since last 4 days. If anything special I can found in 
json response I will get back to you. Till then you can continue to release 
your new build.
Best of Luck.

- Ghanshyam

Original comment by rathod.g...@gmail.com on 29 Jul 2012 at 5:03

GoogleCodeExporter commented 9 years ago
I have put up a new build (0.44) that possibly adresses the issue you were 
seeing.

I've managed to somehow generate a feed with some erroneous newlines in it. it 
was already guarded against after the evaluation of the server feed, but is now 
also 'cleaned' pre-evaluation to guard against this.

See the changelog for other changes.

Original comment by romaingu...@gmail.com on 31 Jul 2012 at 6:20

GoogleCodeExporter commented 9 years ago
Closing this issue with new status 'CantReproduce', since this was already 
added as a label.

Original comment by will.abson on 11 Sep 2012 at 1:51

GoogleCodeExporter commented 9 years ago
When I configure the application "alfresco-access" on audit dashlet, I also get 
the "data error" message.
Firebug reveals a HTTP/500 when retrieving
http://xxxxx/share/service/components/dashlets/audit-application/entries?applica
tion=alfresco-access
HTTP response (JSON) data is attached. 

I'm on alfresco-4.0.d, audit-dashlet-0.44.jar, Firefox 16.0.1. 
Note:
Output of 
http://xxxx/alfresco/service/api/audit/query/alfresco-access?verbose=true&forwar
d=false validates correctly on jsonlint.com.

Original comment by sergio.d...@gmail.com on 27 Oct 2012 at 9:02

Attachments:

GoogleCodeExporter commented 9 years ago
Hi,

The error log you posted is not sufficient to determine the origin of the 
problem. 

I had several alfresco releases tested with alfresco-access with no issue, 
although i have not tested with your specific release. Therefore i'm not sure 
the problem lies within the dashlet itself.

Have you tried completely clearing your browser cache ? have you tried with 
other browsers ? on a new repo ?
Is there anything useful logged in alfresco.log ? 

Have you tried enabling debug for webscripts scripts ? i.e
log4j.logger.org.alfresco.repo.jscript.ScriptLogger=debug for the repo's 
log4j.properties
log4j.logger.org.springframework.extensions.webscripts.ScriptLogger=debug for 
share's log4j.properties

and see if you get something useful there ? 

audit-application-data-get.js also has some commented out logging that could 
turn on, to log the full json feed at various stages. 

I'm afraid you'll have to do some investigating on your end to determine what 
is invalid within the source or produced json feed (if that is in fact the 
issue) as : 
- there's nothing in the log you posted that indicates where the issue lies
- it's unlikely i'll have some time to work on it for some time. 
- i remember that data source working with various tests last time i tested it. 

I'll need to have more concrete evidence of something we can address in the 
dashlet. 

Regards,
Romain.

Original comment by romaingu...@gmail.com on 27 Oct 2012 at 10:24

GoogleCodeExporter commented 9 years ago
On top of my comment above, i would add that it should be unlikely that the 
dashlet produces an invalid json feed, from an initially valid source json 
feed. 

the output you validated on jsonlint may not be the same one that the dashlet 
saw, in terms of event ranges, limits, value filters etc (depending on what you 
configured in the dashlet config dialog).

The debug logging i suggested to turn on above should tell what exact backend 
audit query the dashlet makes, and you should try to see if that exact feed is 
valid, and , if not, why it isn't.

Original comment by romaingu...@gmail.com on 27 Oct 2012 at 10:41