[NEUTRON-55] 'mvn clean install' results in error of integraiton-test with oraclejdk Created: 13/Jul/15  Updated: 11/Feb/16  Resolved: 11/Feb/16

Status: Resolved
Project: neutron
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Isaku Yamahata Assignee: Isaku Yamahata
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: File log.bz2    
External issue ID: 3990

 Description   

'mvn clean install' results in Error with integrfation-test

The changeset of repo
commit 363f47865479b09918e30977b7580bc130e4f12a

The oracle jdk on ubuntu 14.04

ii oracle-java7-installer 7u80+7u60arm-0~webupd8~1 all Oracle Java(TM) Development Kit (JDK) 7

Although I couldn't reproduce with openjdk7, but this indicates strongly race condition.



 Comments   
Comment by Isaku Yamahata [ 13/Jul/15 ]

Attachment log.bz2 has been added with description: the text log of mvn clean install with oraclejdk. compressed by bzip2

Comment by Flavio Fernandes [ 11/Sep/15 ]

There is a thread in the mailing list on this [ref].
Ryan proposed using jdk8 to work around this issue, but other than
changing timing, I don't think it explains what is happening.

I defer to karaf experts on this, but my suspicion is that there are
other bundle dependencies that either need to be explicitly added, or
an inconsistent loading error happening that prevents L3 extensions from
being loaded.

[ref]: https://lists.opendaylight.org/pipermail/neutron-dev/2015-August/000320.html

Comment by Flavio Fernandes [ 11/Sep/15 ]

Out of memory exception?

2015-07-09 22:53:25,324 | ERROR | ternal.Finalizer | Finalizer | - - | Error cleaning up after reference.^M
java.lang.OutOfMemoryError: PermGen space^M

Comment by Isaku Yamahata [ 11/Feb/16 ]

Now jdk was switched to java8 and we haven't seen this for long time, mark this as worksforme.

Generated at Wed Feb 07 20:25:26 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.