Could not initialize class java.net.NetworkInterface

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

You are unable to add an application in Crowd. Other parts of Crowd functionality may or may not be affected.

You may see several errors in the atlassian-crowd.log including:

2014-11-12 16:06:03,953 http-bio-8095-exec-15 ERROR [[Catalina].[localhost].[/crowd].[default]] Servlet.service() for servlet [default] in context with path [/crowd] threw exception [java.lang.reflect.InvocationTargetException] with root cause
java.lang.UnsatisfiedLinkError: no net in java.library.path
2014-11-12 16:06:35,022 http-bio-8095-exec-21 ERROR [[Catalina].[localhost].[/crowd].[default]] Servlet.service() for servlet [default] in context with path [/crowd] threw exception [java.lang.reflect.InvocationTargetException] with root cause
java.lang.NoClassDefFoundError: Could not initialize class java.net.NetworkInterface

Diagnosis

When Crowd starts up, it prints information to the logs regarding the Java Virtual Machine (JVM) version, such as the following:

2014-03-20 11:12:46,635 localhost-startStop-1 INFO [com.atlassian.crowd.startup] 	Java Version: 1.7.0_25
2014-03-20 11:12:46,635 localhost-startStop-1 INFO [com.atlassian.crowd.startup] 	Java Vendor: Oracle Corporation
2014-03-20 11:12:46,635 localhost-startStop-1 INFO [com.atlassian.crowd.startup] 	JVM Version: 23.7-b01
2014-03-20 11:12:46,635 localhost-startStop-1 INFO [com.atlassian.crowd.startup] 	JVM Vendor: Oracle Corporation
2014-03-20 11:12:46,635 localhost-startStop-1 INFO [com.atlassian.crowd.startup] 	JVM Runtime: OpenJDK 64-Bit Server VM

The libraries listed as missing should be included in this JVM.

Cause

Changes or updates were made to the JVM while Crowd was running. For example, one customer noted they had made changes to the JVM to protect against the Shellshock Software Bug.

Resolution

  • If you've made changes to the JVM, restart the applications using that JVM.
  • If a restart is not possible, it may be possible to revert the changes made to the JVM. Restarting affected applications is the preferred way to resolve this problem.

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.