Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Upgrade to RTC 4.0.6 breaking build engines.

 We upgraded our servers to 4.0.6 and now our builds are failing with:

java.lang.UnsatisfiedLinkError: /home/isstspt/.eclipse/com.ibm.team.build.engine.product_3.0.500.v20130502_0139_733680210/configuration/org.eclipse.osgi/bundles/68/1/.cp/os/linux/x86/libunixfile_1_0_0.so (/home/isstspt/.eclipse/com.ibm.team.build.engine.product_3.0.500.v20130502_0139_733680210/configuration/org.eclipse.osgi/bundles/68/1/.cp/os/linux/x86/libunixfile_1_0_0.so: wrong ELF class: ELFCLASS32)
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1030)
at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:990)
at java.lang.System.loadLibrary(System.java:507)
at org.eclipse.core.internal.filesystem.local.unix.UnixFileNatives.<clinit>(UnixFileNatives.java:36)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at org.eclipse.core.internal.filesystem.local.LocalFileNativesManager.isUsingNatives(LocalFileNativesManager.java:42)
at org.eclipse.core.internal.filesystem.local.LocalFileSystem.attributes(LocalFileSystem.java:82)
at com.ibm.team.filesystem.client.internal.ManagedFileStore.<clinit>(ManagedFileStore.java:152)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.team.filesystem.client.internal.FileStorageWrapper.getFileStore(FileStorageWrapper.java:356)
at com.ibm.team.filesystem.client.internal.FileStorageWrapper.exists(FileStorageWrapper.java:455)
at com.ibm.team.filesystem.client.internal.Shareable.exists(Shareable.java:667)
at com.ibm.team.filesystem.client.internal.load.HierarchicalLoadEvaluator.checkForCollision(HierarchicalLoadEvaluator.java:680)
at com.ibm.team.filesystem.client.internal.load.HierarchicalLoadEvaluator.getElementsToLoad(HierarchicalLoadEvaluator.java:342)
at com.ibm.team.filesystem.client.internal.load.HierarchicalLoadEvaluator.doEvaluation(HierarchicalLoadEvaluator.java:177)
at com.ibm.team.filesystem.client.internal.operations.LoadEvaluator.evaluateLoadRequests(LoadEvaluator.java:91)
at com.ibm.team.filesystem.client.internal.operations.LoadOperation.internalEvaluateLoadRequests(LoadOperation.java:473)
at com.ibm.team.filesystem.client.internal.operations.LoadOperation.access$4(LoadOperation.java:443)
at com.ibm.team.filesystem.client.internal.operations.LoadOperation$1.run(LoadOperation.java:662)
at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:76)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:88)
at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:164)
at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:144)
at com.ibm.team.filesystem.client.internal.operations.LoadOperation.execute(LoadOperation.java:695)
at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89)
at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:678)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:238)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:892)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:696)
at java.lang.Thread.run(Thread.java:738)

This error popped up the same day we upgraded to 4.0.6. Suddenly the VM will run out of resources and crashed. Future builds will also crash since the older builds are phantom processes that just hog resources. These are maven based builds that have run for a year without any problem. We tried upgrading the build engines to 4.0.6 which did not change anything. 

Any insight the community can give will be greatly appreciated!

0 votes

Comments

Have you found a resolution?  We are looking at moving to 4.0.6 as well.

Susan



One answer

Permanent link
Has an attempt to create a new build engine / definition been attempted to see if that fixes the issue.  This way we can isolate if the problem is with the upgrade process or with the build engine / definition.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 562
× 35

Question asked: Mar 13 '14, 9:26 a.m.

Question was seen: 5,285 times

Last updated: Apr 03 '14, 9:45 a.m.

Confirmation Cancel Confirm