Nexus 3.9.0: BrowseNodeEntityAdapter$RetryUpsertException: Node already has an asset

548 views
Skip to first unread message

7Books

unread,
Apr 10, 2018, 9:53:38 AM4/10/18
to Nexus Users
Hi,

since I'm using Nexus 3.9.0 I have plenty warnings in the log which look like this one but are related to various different maven-metadata.xml:

2018-04-10 15:39:21,663+0200 WARN  [event-10-thread-453397]  anonymous org.sonatype.nexus.repository.browse.internal.BrowseNodeManager - Problem generating browse nodes for Asset{metadata=AttachedEntityMetadata{schema=asset, document=#11:103030010{bucket:#9:66,format:maven2,last_updated:Tue Apr 10 15:39:19 CEST 2018,attributes:[5],component:null,name:org/codehaus/mojo/maven-metadata.xml,size:20447,content_type:application/xml,created_by:anonymous,created_by_ip:10.233.17.123,blob_ref:orbis-groups@616CB638-51579A2A-47959392-B47F6818-4BCF3D04:74358cf4-c0a4-49f7-9e22-e945f47fc321,last_downloaded:Tue Apr 10 15:39:19 CEST 2018,blob_created:Tue Apr 10 15:39:19 CEST 2018,blob_updated:Tue Apr 10 15:39:19 CEST 2018} v1}, name=org/codehaus/mojo/maven-metadata.xml}
org.sonatype.nexus.repository.storage.BrowseNodeEntityAdapter$RetryUpsertException: Node already has an asset
    DB name="component"
    at org.sonatype.nexus.repository.storage.BrowseNodeEntityAdapter.createAssetNode(BrowseNodeEntityAdapter.java:266)
    at org.sonatype.nexus.repository.storage.BrowseNodeStoreImpl.lambda$1(BrowseNodeStoreImpl.java:132)
    at org.sonatype.nexus.orient.transaction.OrientOperations.lambda$2(OrientOperations.java:63)
    at org.sonatype.nexus.transaction.OperationPoint.lambda$0(OperationPoint.java:53)
    at org.sonatype.nexus.transaction.OperationPoint.proceed(OperationPoint.java:64)
    at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:56)
    at org.sonatype.nexus.transaction.Operations.transactional(Operations.java:200)
    at org.sonatype.nexus.transaction.Operations.run(Operations.java:155)
    at org.sonatype.nexus.orient.transaction.OrientOperations.run(OrientOperations.java:63)
    at org.sonatype.nexus.repository.storage.BrowseNodeStoreImpl.createAssetNode(BrowseNodeStoreImpl.java:132)
    at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
    at org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:270)
    at org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:53)
    at org.sonatype.nexus.repository.browse.internal.BrowseNodeManager.createBrowseNodes(BrowseNodeManager.java:106)
    at org.sonatype.nexus.repository.browse.internal.BrowseNodeManager.createFromAsset(BrowseNodeManager.java:77)
    at org.sonatype.nexus.repository.browse.internal.BrowseNodeEventHandler.on(BrowseNodeEventHandler.java:58)
    at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:91)
    at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:76)
    at org.sonatype.nexus.thread.internal.MDCAwareRunnable.run(MDCAwareRunnable.java:40)
    at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120)
    at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

My question is: Can this warnings be ignored (i.e. I would change the Log Level in this case) or do I need to take further action in order to resolve the problem with the maven-metadata.xml files or is it related to some bug in N3?

Thanks for any further info.

Rok Prodan

unread,
Apr 10, 2018, 1:57:30 PM4/10/18
to 7Books, Nexus Users
Hello,

I am observing the same kind of warnings from time to time on NXRM instance 3.7.1

Regards, Rok Prodan

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/6e03407a-08d3-4f8d-b502-8b36c3c64791%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

mma...@sonatype.com

unread,
Apr 10, 2018, 3:19:01 PM4/10/18
to Nexus Users
Feel free to ignore these warnings. They are related to how the new tree browsing structure is created in parallel and when they occur the other thread which conflicted should generate the correct data. We haven't seen any actual problems with the final tree structure since we released 3.7.1. If for some reason you do see any problems please open a JIRA ticket so we can investigate.

Thanks,

Michael Martz
Sr Software Engineer

Peter Lynch

unread,
Apr 10, 2018, 3:51:40 PM4/10/18
to Michael Martz, Nexus Users
These WARN messages are being tracked here: https://issues.sonatype.org/browse/NEXUS-15557

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users+unsubscribe@glists.sonatype.com.

To post to this group, send email to nexus...@glists.sonatype.com.
Reply all
Reply to author
Forward
0 new messages