Improve Article
Save Article
Like Article
Improve Article
Save Article
Like Article
An unexpected, unwanted event that disturbed the normal flow of a program is called an Exception.
There are mainly two types of exception in Java:
1. Checked Exception
2. Unchecked Exception
ExceptionInInitializerError is the child class of the Error class and hence it is an unchecked exception. This exception is rise automatically by JVM when JVM attempts to load a new class as, during class loading, all static variables and static initializer block are being evaluated. This exception also acts as a signal that tells us that an unexpected exception has occurred in a static initializer block or in the assignment of value to the static variable.
There are basically two cases when ExceptionInInitializerError can occur in a Java Program:
1. ExceptionInInitializerError While Assigning Value To The Static Variable
In the below example we assign a static variable to 20/0 where 20/0 gives an undefined arithmetic behavior and hence there occurs an exception in the static variable assignment and ultimately we will get ExceptionInInitializerError.
Java
class
GFG {
static
int
x =
20
/
0
;
public
static
void
main(String[] args)
{
System.out.println(
"The value of x is "
+ x);
}
}
2. ExceptionInInitializerError While Assigning Null Value Inside A Static Block
In the below example we have declared a static block inside which we create a string s and assign a null value to it, and then we are printing the length of string, so we will get NullPointerException because we were trying to print the length of a string that has its value as null and as we see that this exception occurs inside the static block, so we will get ExceptionInInitializerError.
Java
class
GFG {
static
{
String s =
null
;
System.out.println(s.length());
}
public
static
void
main(String[] args)
{
System.out.println(
"GeeksForGeeks Is Best"
);
}
}
How to Resolve Java.lang.ExceptionInInitializerError ?
- We can resolve the java.lang.ExceptionInInitializerError by ensuring that static initializer block of classes does not throw any Runtime Exception.
- We can resolve also resolve this exception by ensuring that the initializing static variable of classes also doesn’t throw any Runtime Exception.
Last Updated :
03 Mar, 2022
Like Article
Save Article
Introduction to Runtime Errors & Exceptions
Unlike compile-time errors which are detected during compilation [1], runtime errors occur during program execution, i.e. runtime. Java’s runtime error hierarchy is somewhat complicated compared to other programming languages, but at the basic level there are two main categories: runtime errors and runtime exceptions, the latter of which being further divided into checked and unchecked exceptions (see Figure 1 below). Unchecked exceptions are also lumped into the somewhat confusingly named RuntimeException
superclass, while all runtime errors are also considered to be unchecked. The term “unchecked” refers to errors and exceptions that Java doesn’t require to be caught or otherwise specified in the code [2]. Runtime Java errors and exceptions are otherwise jointly referred to as throwables, as per the name of the Throwable
class—the parent class of all errors and exceptions in this language [3].
ExceptionInInitializerError Error: What, Why & How?
After successfully compiling a program, the Java Virtual Machine (JVM) performs dynamic loading, linking, and initializing of classes and interfaces, broadly known as the class loading process [5]. This process includes the evaluation of all static initializer blocks and variable assignments present in the compiled code. If, during this evaluation, any unexpected exception occurs, the JVM throws an ExceptionInInitializerError
runtime error, points to the specific exception that caused the error, and subsequently exits the program.
The ExceptionInInitializerError
error occurs every time there is an unchecked (and uncaught) exception taking place inside a static initializer or a static variable assignment. The JVM wraps this exception inside an instance of the java.lang.ExceptionInInitializerError
class (which itself is a subclass of the more generic java.lang.LinkageError
class of errors [6]) and maintains a reference to it as the root cause.
How to handle the ExceptionInInitializerError Error
To avoid this error, simply ensure that:
- static initializers of classes do not throw any unchecked exception, and that
- static class variable initializations do not throw any unchecked exceptions.
ExceptionInInitializerError Error Examples
Unchecked exception during static variable initialization
Figure 2(a) shows how an unchecked exception such as an instance of the java.lang.ArithmeticException
triggers the ExceptionInInitializerError
error. The error message denotes the division by zero arithmetic exception as the cause for the error and points to the specific class and line of code where it happened. Eradicating this arithmetic error, as shown in Figure 2(b), solves the issue.
(a)
package rollbar;
public class EIIE {
private static int x = 20 / 0;
public static void main(String... args) {
System.out.println(x);
}
}
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.ArithmeticException: / by zero
at rollbar.EIIE.<clinit>(EIIE.java:4)
(b)
package rollbar;
public class EIIE {
private static int x = 20 / 10;
public static void main(String... args) {
System.out.println(x);
}
}
2
Unchecked exception inside static initializer
Having an unchecked exception thrown inside a static initializer will inevitably trigger the ExceptionInInitializerError
runtime error. Figure 3(a) shows how invoking the String::length
method on a non-initialized String
variable (whose value defaults to null
) throws the NullPointerException
, which in turn triggers the ExceptionInInitializerError
error, because the exception occurred inside the static initializer of the class. To handle this type of scenario, one can implement a simple null guard (Figure 3(b)), or use a try-catch
block to explicitly catch and handle the exception (Figure 3(c)). Note that these approaches assume that there is no logical error in the rest of the code, and that the desired functionality is correctly implemented.
(a)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
package rollbar;
public class EIIE2 {
private static String str;
private static long len;
static {
len = str.length();
}
public static void main(String... args) {
System.out.println("String: " + str);
System.out.println("Length: " + len);
}
}
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.NullPointerException: Cannot invoke "String.length()" because "rollbar.EIIE2.str" is null
at rollbar.EIIE2.<clinit>(EIIE2.java:8)
(b)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
package rollbar;
public class EIIE2 {
private static String str;
private static long len;
static {
len = str == null ? -1 : str.length();
}
public static void main(String... args) {
System.out.println("String: " + str);
System.out.println("Length: " + len);
}
}
String: null
Length: -1
(c)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
package rollbar;
public class EIIE2 {
private static String str;
private static long len;
static {
try {
len = str.length();
} catch (NullPointerException e) {
len = -1;
}
}
public static void main(String... args) {
System.out.println("String: " + str);
System.out.println("Length: " + len);
}
}
String: null
Length: -1
Checked exception inside static initializer?
Since it is impossible to throw checked exceptions from a static block (this is not allowed and will result in a compile-time error), it is good practice to wrap them inside an ExceptionInInitializerError
instance manually, as shown in Figure 4. This is a clean way of handling checked exceptions in static initializers where their use is warranted, and it stays true to the design principles of the language. For completeness, if the checked exception in question doesn’t get thrown, the ExceptionInInitializerError
isn’t thrown either and the code executes normally (Figure 4(b)).
(a)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
package rollbar;
import java.lang.reflect.Field;
public class EIIE3 {
private static Field fieldInfo;
static {
try {
fieldInfo = EIIE3.class.getDeclaredField("x");
} catch (NoSuchFieldException e) {
throw new ExceptionInInitializerError(e);
}
}
public static void main(String... args) {
System.out.println(fieldInfo.getName());
System.out.println(fieldInfo.getType());
}
}
Exception in thread "main" java.lang.ExceptionInInitializerError
at rollbar.EIIE3.<clinit>(EIIE3.java:12)
Caused by: java.lang.NoSuchFieldException: x
at java.base/java.lang.Class.getDeclaredField(Class.java:2569)
at rollbar.EIIE3.<clinit>(EIIE3.java:10)
(b)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
package rollbar;
import java.lang.reflect.Field;
public class EIIE3 {
private static Field fieldInfo;
static {
try {
fieldInfo = EIIE3.class.getDeclaredField("x");
} catch (NoSuchFieldException e) {
throw new ExceptionInInitializerError(e);
}
}
private static double x;
public static void main(String... args) {
System.out.println(fieldInfo.getName());
System.out.println(fieldInfo.getType());
}
}
x
double
Conclusion
Runtime errors occur during the execution of a program and as such are more difficult to prevent than compile-time errors. In Java, some of these errors are triggered during the class loading process, or in colloquial terms, when the program is starting up. This allows for a certain category of errors to be detected at a very early stage, despite the program having been successfully compiled. One such error is the ExceptionInInitializerError
error which signals that an unexpected exception has occurred during the evaluation of a static initializer or the initialization of a static variable. This error serves as a runtime wrapper for the underlying exception and halts the JVM until the underlying exception is resolved.
Track, Analyze and Manage Errors With Rollbar
![Rollbar in action](https://rollbar.com/wp-content/uploads/2022/04/section-1-real-time-errors@2x-1-300×202.png)
Managing errors and exceptions in your code is challenging. It can make deploying production code an unnerving experience. Being able to track, analyze, and manage errors in real-time can help you to proceed with more confidence. Rollbar automates error monitoring and triaging, making fixing Java errors easier than ever. Sign Up Today!
References
[1] Rollbar, 2021. How to Fix «Illegal Start of Expression» in Java. Rollbar Editorial Team. [Online]. Available: https://rollbar.com/blog/how-to-fix-illegal-start-of-expression-in-java/. [Accessed Jan. 7, 2022]
[2] Oracle, 2021. Unchecked Exceptions — The Controversy (The Java™ Tutorials > Essential Java Classes > Exceptions). Oracle and/or its affiliates. [Online]. Available: https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html. [Accessed Jan. 7, 2022]
[3] Oracle, 2021. Throwable (Java SE 17 & JDK 17). Oracle and/or its affiliates. [Online]. Available: https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/Throwable.html. [Accessed Jan. 7, 2022]
[4] M. Sanger, 2018. Java Exception Hierarchy. Manish Sanger. [Online]. Available: https://www.manishsanger.com/java-exception-hierarchy/. [Accessed Jan. 7, 2022]
[5] Oracle, 2021. Chapter 5. Loading, Linking, and Initializing. Oracle Corporation and/or its affiliates. [Online]. Available: https://docs.oracle.com/javase/specs/jvms/se17/html/jvms-5.html. [Accessed Jan. 7, 2022]
[6] Oracle, 2021. LinkageError (Java SE 17 & JDK 17). Oracle and/or its affiliates. [Online]. Available: https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/LinkageError.html. [Accessed Jan. 7, 2022]
Every time I encounter this exception in IntelliJ, I fix it trivially and forget the fix easily.
Code:
package whatever;
import org.junit.Test;
public class TestClass
{
@Test
void test() {}
}
Scenario:
- Add new
TestClass
. - Right-click
TestClass
. - Select «Run ‘TestClass'» to run test cases.
The «Messages Build» pane shows:
Information:javac 9-ea was used to compile java sources
Information:Module "dummy" was fully rebuilt due to project configuration/dependencies changes
Information:8/16/17 11:35 PM - Compilation completed with 1 error and 0 warnings in 1s 663ms
Error:java: java.lang.ExceptionInInitializerError
What can possibly go wrong?
What are the likely issues in this simple scenario?
IntelliJ: COMMUNITY 2017.1 (idea-IC-171.4424.56)
asked Aug 16, 2017 at 15:54
uvsmtiduvsmtid
4,1774 gold badges38 silver badges64 bronze badges
To fix the issue, I do:
- File -> Project Structure… -> Project Settings / Project -> Project SDK.
- Change from «9-ea» to «1.8».
DETAILS
Apparently, the issue is discrepancies in selected JDK-s to build (java 9) and run (java 8).
I’m not sure how «9-ea» gets re-selected there for the same project — neither IntelliJ itself runs in «9-ea» JRE (according to Help -> About) nor JAVA_HOME
env var is set to it nor other possible settings (like Maven -> Runner) suggest any «9-ea».
I also didn’t manage to run the test under the same JDK (java 9) which it gets compiled under. However, it’s unclear what JDK tests are run under because IntelliJ reports only about JDK for compilation.
answered Aug 16, 2017 at 16:14
uvsmtiduvsmtid
4,1774 gold badges38 silver badges64 bronze badges
2
If you use Lombok: For me it was a solution to set the newest version for my maven lombok dependency in the pom.xml.
*<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
<version>1.18.8</version>
</dependency>*
answered Aug 6, 2019 at 14:38
SJXSJX
99113 silver badges15 bronze badges
I was facing same error when i tried to run my application in IntelliJ-2019.2 version. Below are the steps i followed to resolve this issue.
Versions:
IntelliJ : IDEA-IntelliJ-2019.2
Java : jdk1.8_221
- Go to below path in IntelliJ
File -> Project Structure -> Project -> Project SDK -> (select java version which you want to use )
(In my case under ‘project SDK’ java-11 was selected, I changed it to ‘java8’)
- Click on ‘Apply’ and then ‘OK’.
I feel I ran into this issue because IntelliJ was trying to compile my java classes using in-built java-11 whereas my java classes are built on java-8. So when i explicitly configured java-8 in IntelliJ, It worked!! Hope this helps.
answered Nov 6, 2019 at 9:35
Tapan HegdeTapan Hegde
1,2221 gold badge8 silver badges25 bronze badges
I started seeing this exception once I installed Java 11 in my machine. JAVA_HOME
was by default pointing to Java 11 and my project was still in Java 8. Changing JAVA_HOME
to Java 8 jdk fixed the issue for me.
If you have multiple projects each running on a different JDK, use this command to temporarily change the Java version per command.
JAVA_HOME=/path/to/JVM/jdk/Home mvn clean install
answered Aug 12, 2019 at 15:23
If you have recently updated your IDE then you can try these steps.
- Delete .idea directory for the idea project/workspace
- Then go to File -> Invalidate Caches / Restart…
- Once Idea is restarted re-add/import your module(s)
answered Apr 18, 2019 at 15:29
I faced a similar issue with JARs and Jena (while run from IntelliJ it works).
I was using Apache Jena v4.0.0 in my project and have built a JAR (with a main class for the JAR to act as a console app).
The JAR builts successfully with IntelliJ but when run throws java.lang.ExceptionInInitializerError ... Caused by: java.lang.NullPointerException
. NPE suggests that something was not initialized properly.
The jar built with previous version Jena 3.17.0 works perfectly.
What I did to fix it
I’ve opened both the JARs, compared their META-INF
folders and encountered the difference in
my.jarMETA-INFservicesorg.apache.jena.sys.JenaSubsystemLifecycle
The new version (jena v4.0.0) contains only one line:
org.apache.jena.tdb.sys.InitTDB
The old version (jena v3.17.0) contains two different lines:
org.apache.jena.riot.system.InitRIOT
org.apache.jena.sparql.system.InitARQ
I’ve added the old two lines to the file and repacked new JAR with it:
org.apache.jena.tdb.sys.InitTDB
org.apache.jena.riot.system.InitRIOT
org.apache.jena.sparql.system.InitARQ
It resolved my issue.
Update: recent Jena v4.4.0 builts with the same «bug».
I’m not an expert and there is probably a better way than patching a JAR by hand.
But I still hope that this solution will help someone like me.
answered Apr 2, 2022 at 9:08
SamantraSamantra
651 silver badge8 bronze badges
Автор оригинала: Ali Dehghani.
1. Обзор
В этом кратком руководстве мы увидим, что заставляет Java выбрасывать экземпляр ExceptionInInitializerError исключение.
Начнем с небольшой теории. Затем мы увидим несколько примеров этого исключения на практике.
2. Ошибка exceptioninitializererror
ExceptionInInitializerError указывает, что в статическом инициализаторе произошло непредвиденное исключение . В принципе, когда мы видим это исключение, мы должны знать, что Java не удалось вычислить статический блок инициализатора или создать экземпляр статической переменной.
Фактически, каждый раз, когда какое-либо исключение происходит внутри статического инициализатора, Java автоматически обертывает это исключение внутри экземпляра класса ExceptionInInitializerError . Таким образом, он также поддерживает ссылку на фактическое исключение в качестве основной причины.
Теперь, когда мы знаем причину этого исключения, давайте рассмотрим его на практике.
3. Блок Статического Инициализатора
Чтобы иметь неудачный инициализатор статического блока, мы намеренно разделим целое число на ноль:
public class StaticBlock { private static int state; static { state = 42 / 0; } }
Теперь, если мы инициализируем инициализацию класса с помощью чего-то вроде:
Тогда мы увидим следующее исключение:
java.lang.ExceptionInInitializerError at com.baeldung...(ExceptionInInitializerErrorUnitTest.java:18) Caused by: java.lang.ArithmeticException: / by zero at com.baeldung.StaticBlock.(ExceptionInInitializerErrorUnitTest.java:35) ... 23 more
Как упоминалось ранее, Java создает исключение ExceptionInInitializerError , сохраняя при этом ссылку на первопричину:
assertThatThrownBy(StaticBlock::new) .isInstanceOf(ExceptionInInitializerError.class) .hasCauseInstanceOf(ArithmeticException.class);
Также стоит упомянуть, что метод является методом инициализации класса в JVM.
4. Инициализация статической Переменной
То же самое происходит, если Java не инициализирует статическую переменную:
public class StaticVar { private static int state = initializeState(); private static int initializeState() { throw new RuntimeException(); } }
Опять же, если мы запустим процесс инициализации класса:
Затем происходит то же самое исключение:
java.lang.ExceptionInInitializerError at com.baeldung...(ExceptionInInitializerErrorUnitTest.java:11) Caused by: java.lang.RuntimeException at com.baeldung.StaticVar.initializeState(ExceptionInInitializerErrorUnitTest.java:26) at com.baeldung.StaticVar.(ExceptionInInitializerErrorUnitTest.java:23) ... 23 more
Аналогично статическим блокам инициализатора, первопричина исключения также сохраняется:
assertThatThrownBy(StaticVar::new) .isInstanceOf(ExceptionInInitializerError.class) .hasCauseInstanceOf(RuntimeException.class);
5. Проверенные исключения
В рамках спецификации языка Java (JLS-11.2.3) мы не можем выбрасывать проверенные исключения внутри блока статического инициализатора или инициализатора статической переменной. Например, если мы попытаемся сделать это:
public class NoChecked { static { throw new Exception(); } }
Компилятор потерпит неудачу со следующей ошибкой компиляции:
java: initializer must be able to complete normally
В качестве соглашения мы должны обернуть возможные проверенные исключения внутри экземпляра Исключение ininitializererror когда наша статическая логика инициализации выдает проверенное исключение:
public class CheckedConvention { private static Constructor constructor; static { try { constructor = CheckedConvention.class.getDeclaredConstructor(); } catch (NoSuchMethodException e) { throw new ExceptionInInitializerError(e); } } }
Как показано выше, метод getDeclaredConstructor() вызывает проверенное исключение. Поэтому мы поймали проверенное исключение и завернули его, как предполагает конвенция.
Поскольку мы уже возвращаем экземпляр Исключение ininitializererror исключение явно, Java не будет заключать это исключение в еще одно Исключение ininitializererror пример.
Однако, если мы создадим любое другое непроверенное исключение, Java выдаст другое ExceptionInInitializerError :
static { try { constructor = CheckedConvention.class.getConstructor(); } catch (NoSuchMethodException e) { throw new RuntimeException(e); } }
Здесь мы заключаем проверенное исключение в непроверенное. Поскольку это непроверенное исключение не является экземпляром ExceptionInInitializerError, Java снова обернет его, что приведет к этой неожиданной трассировке стека:
java.lang.ExceptionInInitializerError at com.baeldung.exceptionininitializererror... Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: ... Caused by: java.lang.NoSuchMethodException: com.baeldung.CheckedConvention.() at java.base/java.lang.Class.getConstructor0(Class.java:3427) at java.base/java.lang.Class.getConstructor(Class.java:2165)
Как показано выше, если мы будем следовать соглашению, то трассировка стека будет намного чище, чем это.
5.1. OpenJDK
В последнее время это соглашение даже используется в самом исходном коде OpenJDK. Например, вот как AtomicReference использует этот подход:
public class AtomicReference implements java.io.Serializable { private static final VarHandle VALUE; static { try { MethodHandles.Lookup l = MethodHandles.lookup(); VALUE = l.findVarHandle(AtomicReference.class, "value", Object.class); } catch (ReflectiveOperationException e) { throw new ExceptionInInitializerError(e); } } private volatile V value; // omitted }
6. Заключение
В этом уроке мы увидели, что заставляет Java выбрасывать экземпляр ExceptionInInitializerError exception.
Как обычно, все примеры доступны на GitHub .
Неизвестное нежелательное событие, нарушившее нормальный ход выполнения программы, называется исключением.
В Java есть в основном два типа исключений:
1. Проверяемое исключение
2. Непроверенное исключение
ExceptionInInitializerError — это дочерний класс класса Error и, следовательно, это непроверенное исключение. Это исключение автоматически создается JVM, когда JVM пытается загрузить новый класс, поскольку во время загрузки класса оцениваются все статические переменные и блок статического инициализатора. Это исключение также действует как сигнал, который сообщает нам, что непредвиденное исключение произошло в блоке статического инициализатора или при присвоении значения статической переменной.
В основном есть два случая, когда ExceptionInInitializerError может возникнуть в программе Java:
1. ExceptionInInitializerError при присвоении значения статической переменной
В приведенном ниже примере мы назначаем статической переменной 20/0, где 20/0 дает неопределенное арифметическое поведение, и, следовательно, возникает исключение в назначении статической переменной, и в конечном итоге мы получим ExceptionInInitializerError.
Ява
class
GFG {
static
int
x =
20
/
0
;
public
static
void
main(String[] args)
{
System.out.println(
"The value of x is "
+ x);
}
}
2. ExceptionInInitializerError при присвоении нулевого значения внутри статического блока
В приведенном ниже примере мы объявили статический блок, внутри которого мы создаем строку s и присваиваем ей нулевое значение, а затем печатаем длину строки, поэтому мы получим исключение NullPointerException, потому что мы пытались распечатать длину строка, значение которой равно нулю, и, как мы видим, это исключение возникает внутри статического блока, поэтому мы получим ExceptionInInitializerError.
Ява
class
GFG {
static
{
String s =
null
;
System.out.println(s.length());
}
public
static
void
main(String[] args)
{
System.out.println(
"GeeksForGeeks Is Best"
);
}
}
Как разрешить Java.lang.ExceptionInInitializerError?
- Мы можем разрешить java.lang.ExceptionInInitializerError, убедившись, что статический блок инициализатора классов не генерирует никаких исключений времени выполнения.
- Мы также можем разрешить это исключение, убедившись, что инициализирующая статическая переменная классов также не генерирует никаких исключений времени выполнения.
Вниманию читателя! Не прекращайте учиться сейчас. Ознакомьтесь со всеми важными концепциями Java Foundation и коллекций с помощью курса «Основы Java и Java Collections» по доступной для студентов цене и будьте готовы к работе в отрасли. Чтобы завершить подготовку от изучения языка к DS Algo и многому другому, см. Полный курс подготовки к собеседованию .
Evening
I installed forge on my minecraft, but when I tried to launch the game, i get an error message Error: java.lang.ExceptionInInitializerError: null
Time: 17/02/20 17:19 Description: Initializing game java.lang.ExceptionInInitializerError: null at java.lang.J9VMInternals.ensureError(J9VMInternals.java:148) ~[?:2.9 (11-06-2019)] {} at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:137) ~[?:2.9 (11-06-2019)] {} at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:121) ~[?:?] {re:classloading} at net.minecraftforge.fml.ModLoader.get(ModLoader.java:146) ~[?:?] {re:classloading} at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:97) ~[?:?] {re:classloading,pl:runtimedistcleaner:A} at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2070.000000004EB18740.run(Unknown Source) ~[?:?] {} at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:113) ~[?:?] {re:classloading,pl:runtimedistcleaner:A} at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2071.000000004E8E67C0.run(Unknown Source) ~[?:?] {} at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:97) ~[?:?] {re:classloading,pl:runtimedistcleaner:A} at net.minecraft.client.Minecraft.<init>(Minecraft.java:393) ~[?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A} at net.minecraft.client.main.Main.main(SourceFile:166) ~[1.15.2-forge-31.1.0.jar:?] {re:classloading} at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] {} at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0] {} at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0] {} at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0] {} at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) ~[forge-1.15.2-31.1.0.jar:31.1] {} at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$400.000000004C59AC40.call(Unknown Source) ~[?:?] {} at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-5.0.0-milestone.4.jar:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-5.0.0-milestone.4.jar:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-5.0.0-milestone.4.jar:?] {} at cpw.mods.modlauncher.Launcher.run(Launcher.java:81) [modlauncher-5.0.0-milestone.4.jar:?] {} at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) [modlauncher-5.0.0-milestone.4.jar:?] {} Caused by: java.lang.IllegalStateException: Failed to resolve consumer event type: net.minecraftforge.fml.network.simple.SimpleChannel$$Lambda$2078/000000004EB1D630@cfc2fc3d at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:194) ~[eventbus-2.0.0-milestone.1-service.jar:?] {} at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:161) ~[eventbus-2.0.0-milestone.1-service.jar:?] {} at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:156) ~[eventbus-2.0.0-milestone.1-service.jar:?] {} at net.minecraftforge.eventbus.EventBus.addListener(EventBus.java:151) ~[eventbus-2.0.0-milestone.1-service.jar:?] {} at net.minecraftforge.fml.network.NetworkInstance.addListener(NetworkInstance.java:65) ~[?:?] {re:classloading} at net.minecraftforge.fml.network.simple.SimpleChannel.<init>(SimpleChannel.java:56) ~[?:?] {re:classloading} at net.minecraftforge.fml.network.simple.SimpleChannel.<init>(SimpleChannel.java:49) ~[?:?] {re:classloading} at net.minecraftforge.fml.network.NetworkRegistry$ChannelBuilder.simpleChannel(NetworkRegistry.java:409) ~[?:?] {re:classloading} at net.minecraftforge.fml.network.NetworkInitialization.getHandshakeChannel(NetworkInitialization.java:38) ~[?:?] {re:classloading} at net.minecraftforge.fml.network.FMLNetworkConstants.<clinit>(FMLNetworkConstants.java:48) ~[?:?] {re:classloading} ... 20 more A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Render thread Stacktrace: at java.lang.J9VMInternals.ensureError(J9VMInternals.java:148) at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:137) at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:121) at net.minecraftforge.fml.ModLoader.get(ModLoader.java:146) at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:97) at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2070.000000004EB18740.run(Unknown Source) at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:113) at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2071.000000004E8E67C0.run(Unknown Source) at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:97) at net.minecraft.client.Minecraft.<init>(Minecraft.java:393) -- Initialization -- Details: Stacktrace: at net.minecraft.client.main.Main.main(SourceFile:166) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$400.000000004C59AC40.call(Unknown Source) at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) at cpw.mods.modlauncher.Launcher.run(Launcher.java:81) at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) -- System Details -- Details: Minecraft Version: 1.15.2 Minecraft Version ID: 1.15.2 Operating System: Linux (amd64) version 4.15.0-76-generic Java Version: 1.8.0_231, IBM Corporation Java VM Version: IBM J9 VM (JRE 1.8.0 Linux amd64-64-Bit Compressed References 20191106_432135 (JIT enabled, AOT enabled) OpenJ9 - f0b6be7 OMR - 18d8f94 IBM - 233dfb5), IBM Corporation Memory: 19020792 bytes (18 MB) / 321191936 bytes (306 MB) up to 2147483648 bytes (2048 MB) CPUs: 4 JVM Flags: 11 total; -Xoptionsfile=/usr/lib/jvm/java-ibm-x86_64-80/jre/lib/amd64/compressedrefs/options.default -Xlockword:mode=default,noLockword=java/lang/String,noLockword=java/util/MapEntry,noLockword=java/util/HashMap$Entry,noLockword=org/apache/harmony/luni/util/ModifiedMap$Entry,noLockword=java/util/Hashtable$Entry,noLockword=java/lang/invoke/MethodType,noLockword=java/lang/invoke/MethodHandle,noLockword=java/lang/invoke/CollectHandle,noLockword=java/lang/invoke/ConstructorHandle,noLockword=java/lang/invoke/ConvertHandle,noLockword=java/lang/invoke/ArgumentConversionHandle,noLockword=java/lang/invoke/AsTypeHandle,noLockword=java/lang/invoke/ExplicitCastHandle,noLockword=java/lang/invoke/FilterReturnHandle,noLockword=java/lang/invoke/DirectHandle,noLockword=java/lang/invoke/ReceiverBoundHandle,noLockword=java/lang/invoke/DynamicInvokerHandle,noLockword=java/lang/invoke/FieldHandle,noLockword=java/lang/invoke/FieldGetterHandle,noLockword=java/lang/invoke/FieldSetterHandle,noLockword=java/lang/invoke/StaticFieldGetterHandle,noLockword=java/lang/invoke/StaticFieldSetterHandle,noLockword=java/lang/invoke/IndirectHandle,noLockword=java/lang/invoke/InterfaceHandle,noLockword=java/lang/invoke/VirtualHandle,noLockword=java/lang/invoke/PrimitiveHandle,noLockword=java/lang/invoke/InvokeExactHandle,noLockword=java/lang/invoke/InvokeGenericHandle,noLockword=java/lang/invoke/VarargsCollectorHandle,noLockword=java/lang/invoke/ThunkTuple -Xjcl:jclse29 -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Launched Version: 1.15.2-forge-31.1.0 Backend library: LWJGL version 3.2.2 build 10 Backend API: AMD CAICOS (DRM 2.50.0 / 4.15.0-76-generic, LLVM 9.0.0) GL version 3.1 Mesa 19.2.8, X.Org GL Caps: Using framebuffer using OpenGL 3.0 Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'forge' Type: Client (map_client.txt) CPU: 4x Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
I think I have the right Java Version (Java Version: 1.8.0_231).
I downloaded the right installer for Forge.
I’m lost.
-
#1
Description: There was a severe problem during mod loading that has caused the game to fail net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from TheScraGullWorld (tsgw) Caused by: java.lang.ExceptionInInitializerError at com.nikkomwordlling.thescragullworld.proxy.CommonProxy.preInit(CommonProxy.java:32) at com.nikkomwordlling.thescragullworld.TSGW.preInit(TSGW.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraftforge.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:629) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:91) at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:150) at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:76) at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399) at com.google.common.eventbus.Subscriber.dispatchEvent(Subscriber.java:71) at com.google.common.eventbus.Dispatcher$PerThreadQueuedDispatcher.dispatch(Dispatcher.java:116) at com.google.common.eventbus.EventBus.post(EventBus.java:217) at net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:218) at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:196) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:91) at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:150) at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:76) at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399) at com.google.common.eventbus.Subscriber.dispatchEvent(Subscriber.java:71) at com.google.common.eventbus.Dispatcher$PerThreadQueuedDispatcher.dispatch(Dispatcher.java:116) at com.google.common.eventbus.EventBus.post(EventBus.java:217) at net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:135) at net.minecraftforge.fml.common.Loader.preinitializeMods(Loader.java:627) at net.minecraftforge.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:245) at net.minecraft.client.Minecraft.init(Minecraft.java:513) at net.minecraft.client.Minecraft.run(Minecraft.java:421) at net.minecraft.client.main.Main.main(Main.java:118) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraftforge.gradle.GradleStartCommon.launch(GradleStartCommon.java:97) at GradleStart.main(GradleStart.java:25) Caused by: java.lang.NullPointerException at com.nikkomwordlling.thescragullworld.objects.tools.ToolPickaxe.<init>(ToolPickaxe.java:29) at com.nikkomwordlling.thescragullworld.init.ItemInit.<clinit>(ItemInit.java:68) ... 49 more A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- System Details -- Details: Minecraft Version: 1.12.2 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_181, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 214555056 bytes (204 MB) / 475529216 bytes (453 MB) up to 954728448 bytes (910 MB) JVM Flags: 0 total; IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: MCP 9.42 Powered by Forge 14.23.4.2705 5 mods loaded, 5 mods active States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored | State | ID | Version | Source | Signature | |:----- |:--------- |:------------ |:-------------------------------- |:--------- | | UCH | minecraft | 1.12.2 | minecraft.jar | None | | UCH | mcp | 9.42 | minecraft.jar | None | | UCH | FML | 8.0.99.99 | forgeSrc-1.12.2-14.23.4.2705.jar | None | | UCH | forge | 14.23.4.2705 | forgeSrc-1.12.2-14.23.4.2705.jar | None | | UCEE | tsgw | 1.0 | bin | None | Loaded coremods (and transformers): GL info: ' Vendor: 'ATI Technologies Inc.' Version: '4.5.13474 Compatibility Profile Context 22.19.162.4' Renderer: 'AMD Radeon HD 7700 Series'
-
#2
Смотри в этих классах:
at com.nikkomwordlling.thescragullworld.proxy.CommonProxy.preInit(CommonProxy.java:32)
at com.nikkomwordlling.thescragullworld.TSGW.preInit(TSGW.java:34)
at com.nikkomwordlling.thescragullworld.objects.tools.ToolPickaxe.<init>(ToolPickaxe.java:29)
at com.nikkomwordlling.thescragullworld.init.ItemInit.<clinit>(ItemInit.java:68)
-
#3
Caused by: java.lang.NullPointerException at com.nikkomwordlling.thescragullworld.objects.tools.ToolPickaxe.<init>(ToolPickaxe.java:29)
Скорее всего — передаёшь null значение для материала инструмента.
-
#4
Начал запускаться, но блоки и предметы почему-то не показывает =(
-
#5
Наверное не регистрируешь предметы и блоки, или креативная вкладка создаёться после регистрации предметов и блоков.
-
#6
public void preInit(FMLPreInitializationEvent event) { Config.init(event); TSGWTabs.init(); ItemInit.init(); BlockInit.init(); addOreDictionary(); MwordllingAPI.registerEvent(new ArmorAbilityEvent());
-
#7
Не могу знать точно, в чём у тебя проблема.
-
#8
А нечего, что тут моддинг под iOS ?
-
#10
Дядя, вы разделы перепутали.
-
#11
Перенес в соответствующий раздел. Читайте название раздела, перед тем как создавать в нем тему.
Java
-
Search
-
Search all Forums
-
Search this Forum
-
Search this Thread
-
-
Tools
-
Jump to Forum
-
-
#1
Jan 18, 2022
Shack_-
View User Profile
-
View Posts
-
Send Message
- Out of the Water
- Join Date:
1/19/2022
- Posts:
2
- Member Details
I’ve recently discovered modded minecraft, and I’m having some troubles figuring out what’s causing it to crash when I start it up. If anyone can make sense of this crash report, I’d appreciate it.
—- Minecraft Crash Report ——— Minecraft Crash Report —-// You’re mean.
Time: 1/18/22, 10:30 PMDescription: Initializing game
java.lang.ExceptionInInitializerError: null at potionstudios.byg.client.textures.ColorManager.onItemColorsInit(ColorManager.java:29) ~[Oh%20The%20Biomes%20You’ll%20Go-forge-1.18.1-1.3.5.1.jar%23117!/:1.3.5.1] {re:mixin,re:classloading} at net.minecraft.client.color.item.ItemColors.handler$zek000$addBYGItemColors(ItemColors.java:516) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:byg.mixins.json:client.MixinItemColors,pl:mixin:A,pl:runtimedistcleaner:A} at net.minecraft.client.color.item.ItemColors.m_92683_(ItemColors.java:89) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:byg.mixins.json:client.MixinItemColors,pl:mixin:A,pl:runtimedistcleaner:A} at net.minecraft.client.Minecraft.<init>(Minecraft.java:482) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:flywheel.mixins.json:PausedPartialTickAccessor,pl:mixin:APP:flywheel.mixins.json:ShaderCloseMixin,pl:mixin:APP:immersiveengineering.mixins.json:accessors.client.MinecraftAccess,pl:mixin:APP:physicsmod.mixins.json:MixinMinecraft,pl:mixin:APP:physicsmod.mixins.json:cloth.MixinMinecraft,pl:mixin:APP:physicsmod.mixins.json:fabricapi.MixinMinecraft,pl:mixin:APP:terrablender_forge.mixins.json:client.MixinMinecraft,pl:mixin:APP:create.mixins.json:WindowResizeMixin,pl:mixin:A,pl:runtimedistcleaner:A} at net.minecraft.client.main.Main.main(Main.java:169) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:classloading,re:mixin,pl:runtimedistcleaner:A,pl:mixin:A,pl:runtimedistcleaner:A} at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] {} at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] {} at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] {} at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] {} at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:45) ~[fmlloader-1.18.1-39.0.44.jar%2323!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:149) [bootstraplauncher-1.0.0.jar:?] {}Caused by: java.lang.IllegalArgumentException: Could not construct item from block! at potionstudios.byg.common.item.BYGItems.createItem(BYGItems.java:1235) ~[Oh%20The%20Biomes%20You’ll%20Go-forge-1.18.1-1.3.5.1.jar%23117!/:1.3.5.1] {re:mixin,re:classloading} at potionstudios.byg.common.item.BYGItems.<clinit>(BYGItems.java:30) ~[Oh%20The%20Biomes%20You’ll%20Go-forge-1.18.1-1.3.5.1.jar%23117!/:1.3.5.1] {re:mixin,re:classloading} … 18 moreA detailed walkthrough of the error, its code path and all known details is as follows:—————————————————————————————
— Head —Thread: Render threadStacktrace: at potionstudios.byg.client.textures.ColorManager.onItemColorsInit(ColorManager.java:29) ~[Oh%20The%20Biomes%20You’ll%20Go-forge-1.18.1-1.3.5.1.jar%23117!/:1.3.5.1] {re:mixin,re:classloading} at net.minecraft.client.color.item.ItemColors.handler$zek000$addBYGItemColors(ItemColors.java:516) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:byg.mixins.json:client.MixinItemColors,pl:mixin:A,pl:runtimedistcleaner:A} at net.minecraft.client.color.item.ItemColors.m_92683_(ItemColors.java:89) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:byg.mixins.json:client.MixinItemColors,pl:mixin:A,pl:runtimedistcleaner:A} at net.minecraft.client.Minecraft.<init>(Minecraft.java:482) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:flywheel.mixins.json:PausedPartialTickAccessor,pl:mixin:APP:flywheel.mixins.json:ShaderCloseMixin,pl:mixin:APP:immersiveengineering.mixins.json:accessors.client.MinecraftAccess,pl:mixin:APP:physicsmod.mixins.json:MixinMinecraft,pl:mixin:APP:physicsmod.mixins.json:cloth.MixinMinecraft,pl:mixin:APP:physicsmod.mixins.json:fabricapi.MixinMinecraft,pl:mixin:APP:terrablender_forge.mixins.json:client.MixinMinecraft,pl:mixin:APP:create.mixins.json:WindowResizeMixin,pl:mixin:A,pl:runtimedistcleaner:A}— Initialization —Details: Modules: ADVAPI32.dll:Advanced Windows 32 Base API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation AppHook64_5F02C1C4-D8C7-4BE7-883F-69FA1013A55A.dll:DisplayFusion Hook:10.0.0.3:Binary Fortress Software COMCTL32.dll:User Experience Controls Library:6.10 (WinBuild.160101.0800):Microsoft Corporation CRYPT32.dll:Crypto API32:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation CRYPTBASE.dll:Base cryptographic API DLL:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation CRYPTSP.dll:Cryptographic Service Provider API:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation ColorAdapterClient.dll:Microsoft Color Adapter Client:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation CoreMessaging.dll:Microsoft CoreMessaging Dll:10.0.19041.746:Microsoft Corporation CoreUIComponents.dll:Microsoft Core UI Components Dll:10.0.19041.546:Microsoft Corporation DBGHELP.DLL:Windows Image Helper:10.0.19041.867 (WinBuild.160101.0800):Microsoft Corporation DEVOBJ.dll:Device Information Set DLL:10.0.19041.1151 (WinBuild.160101.0800):Microsoft Corporation DNSAPI.dll:DNS Client API DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation GDI32.dll:GDI Client DLL:10.0.19041.1202 (WinBuild.160101.0800):Microsoft Corporation GLU32.dll:OpenGL Utility Library DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation HID.DLL:Hid User Library:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation IMM32.DLL:Multi-User Windows IMM32 API Client DLL:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation IPHLPAPI.DLL:IP Helper API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation KERNEL32.DLL:Windows NT BASE API Client DLL:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation KERNELBASE.dll:Windows NT BASE API Client DLL:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation MMDevApi.dll:MMDevice API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation MSASN1.dll:ASN.1 Runtime APIs:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation MSCTF.dll:MSCTF Server DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation MpOav.dll:IOfficeAntiVirus Module:4.18.2111.5 (WinBuild.160101.0800):Microsoft Corporation NLAapi.dll:Network Location Awareness 2:10.0.19041.1151 (WinBuild.160101.0800):Microsoft Corporation NSI.dll:NSI User-mode interface DLL:10.0.19041.610 (WinBuild.160101.0800):Microsoft Corporation NTASN1.dll:Microsoft ASN.1 API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation Ole32.dll:Microsoft OLE for Windows:10.0.19041.1320 (WinBuild.160101.0800):Microsoft Corporation OleAut32.dll:OLEAUT32.DLL:10.0.19041.985 (WinBuild.160101.0800):Microsoft Corporation OpenAL.dll PROPSYS.dll:Microsoft Property System:7.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation PSAPI.DLL:Process Status Helper:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation Pdh.dll:Windows Performance Data Helper DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation RPCRT4.dll:Remote Procedure Call Runtime:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation SETUPAPI.DLL:Windows Setup API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation SHCORE.dll:SHCORE:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation SHELL32.dll:Windows Shell Common Dll:10.0.19041.964 (WinBuild.160101.0800):Microsoft Corporation UMPDC.dll USER32.dll:Multi-User Windows USER API Client DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation USERENV.dll:Userenv:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation VCRUNTIME140.dll:Microsoft® C Runtime Library:14.29.30133.0 built by: vcwrkspc:Microsoft Corporation VERSION.dll:Version Checking and File Installation Libraries:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation WINHTTP.dll:Windows HTTP Services:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation WINMM.dll:MCI API DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation WINSTA.dll:Winstation Library:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation WINTRUST.dll:Microsoft Trust Verification APIs:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation WS2_32.dll:Windows Socket 2.0 32-Bit DLL:10.0.19041.1081 (WinBuild.160101.0800):Microsoft Corporation WSOCK32.dll:Windows Socket 32-Bit DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation WTSAPI32.dll:Windows Remote Desktop Session Host Server SDK APIs:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation Wldp.dll:Windows Lockdown Policy:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation amsi.dll:Anti-Malware Scan Interface:10.0.19041.746 (WinBuild.160101.0800):Microsoft Corporation apphelp.dll:Application Compatibility Client Library:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation bcrypt.dll:Windows Cryptographic Primitives Library:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation bcryptPrimitives.dll:Windows Cryptographic Primitives Library:10.0.19041.1415 (WinBuild.160101.0800):Microsoft Corporation cfgmgr32.dll:Configuration Manager DLL:10.0.19041.1151 (WinBuild.160101.0800):Microsoft Corporation clbcatq.dll:COM+ Configuration Catalog:2001.12.10941.16384 (WinBuild.160101.0800):Microsoft Corporation combase.dll:Microsoft COM for Windows:10.0.19041.1320 (WinBuild.160101.0800):Microsoft Corporation cryptnet.dll:Crypto Network Related API:10.0.19041.906 (WinBuild.160101.0800):Microsoft Corporation dbgcore.DLL:Windows Core Debugging Helpers:10.0.19041.789 (WinBuild.160101.0800):Microsoft Corporation dhcpcsvc.DLL:DHCP Client Service:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation dhcpcsvc6.DLL:DHCPv6 Client:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation dinput8.dll:Microsoft DirectInput:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation drvstore.dll:Driver Store API:10.0.19041.1320 (WinBuild.160101.0800):Microsoft Corporation dwmapi.dll:Microsoft Desktop Window Manager API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation dxcore.dll:DXCore:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation fwpuclnt.dll:FWP/IPsec User-Mode API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation gdi32full.dll:GDI Client DLL:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation glfw.dll icm32.dll:Microsoft Color Management Module (CMM):10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation inputhost.dll:InputHost:10.0.19041.906 (WinBuild.160101.0800):Microsoft Corporation java.dll:OpenJDK Platform binary:17.0.1.0:Microsoft javaw.exe:OpenJDK Platform binary:17.0.1.0:Microsoft jemalloc.dll jimage.dll:OpenJDK Platform binary:17.0.1.0:Microsoft jli.dll:OpenJDK Platform binary:17.0.1.0:Microsoft jna7927139162355060508.dll:JNA native library:6.1.1:Java(TM) Native Access (JNA) jvm.dll:OpenJDK 64-Bit server VM:17.0.1.0:Microsoft kernel.appcore.dll:AppModel API Host:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation lwjgl.dll lwjgl_opengl.dll lwjgl_stb.dll management.dll:OpenJDK Platform binary:17.0.1.0:Microsoft management_ext.dll:OpenJDK Platform binary:17.0.1.0:Microsoft mscms.dll:Microsoft Color Matching System DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation msvcp140.dll:Microsoft® C Runtime Library:14.29.30133.0 built by: vcwrkspc:Microsoft Corporation msvcp_win.dll:Microsoft® C Runtime Library:10.0.19041.789 (WinBuild.160101.0800):Microsoft Corporation msvcrt.dll:Windows NT CRT DLL:7.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation mswsock.dll:Microsoft Windows Sockets 2.0 Service Provider:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation napinsp.dll:E-mail Naming Shim Provider:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation ncrypt.dll:Windows NCrypt Router:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation net.dll:OpenJDK Platform binary:17.0.1.0:Microsoft nio.dll:OpenJDK Platform binary:17.0.1.0:Microsoft ntdll.dll:NT Layer DLL:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation ntmarta.dll:Windows NT MARTA provider:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation nvoglv64.dll:NVIDIA Compatible OpenGL ICD:30.0.14.9676:NVIDIA Corporation nvspcap64.dll:NVIDIA Game Proxy:3.24.0.123:NVIDIA Corporation opengl32.dll:OpenGL Client DLL:10.0.19041.1081 (WinBuild.160101.0800):Microsoft Corporation perfos.dll:Windows System Performance Objects DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation pnrpnsp.dll:PNRP Name Space Provider:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation powrprof.dll:Power Profile Helper
DLL:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation profapi.dll:User Profile Basic API:10.0.19041.844 (WinBuild.160101.0800):Microsoft Corporation rasadhlp.dll:Remote Access AutoDial Helper:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation rsaenh.dll:Microsoft Enhanced Cryptographic Provider:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation sechost.dll:Host for SCM/SDDL/LSA Lookup APIs:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation shlwapi.dll:Shell Light-weight Utility Library:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation sunmscapi.dll:OpenJDK Platform binary:17.0.1.0:Microsoft svml.dll:OpenJDK Platform binary:17.0.1.0:Microsoft textinputframework.dll:»TextInputFramework.DYNLINK»:10.0.19041.1387 (WinBuild.160101.0800):Microsoft Corporation ucrtbase.dll:Microsoft® C Runtime Library:10.0.19041.789 (WinBuild.160101.0800):Microsoft Corporation uxtheme.dll:Microsoft UxTheme Library:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation vcruntime140_1.dll:Microsoft® C Runtime Library:14.29.30133.0 built by: vcwrkspc:Microsoft Corporation verify.dll:OpenJDK Platform binary:17.0.1.0:Microsoft win32u.dll:Win32u:10.0.19041.1466 (WinBuild.160101.0800):Microsoft Corporation windows.storage.dll:Microsoft WinRT Storage API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation winrnr.dll:LDAP RnR Provider DLL:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation wintypes.dll:Windows Base Types DLL:10.0.19041.1320 (WinBuild.160101.0800):Microsoft Corporation wshbth.dll:Windows Sockets Helper DLL:10.0.19041.546 (WinBuild.160101.0800):Microsoft Corporation xinput1_4.dll:Microsoft Common Controller API:10.0.19041.1 (WinBuild.160101.0800):Microsoft Corporation zip.dll:OpenJDK Platform binary:17.0.1.0:MicrosoftStacktrace: at net.minecraft.client.main.Main.main(Main.java:169) ~[client-1.18.1-20211210.034407-srg.jar%23144!/:?] {re:classloading,re:mixin,pl:runtimedistcleaner:A,pl:mixin:A,pl:runtimedistcleaner:A} at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] {} at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] {} at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] {} at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] {} at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:45) ~[fmlloader-1.18.1-39.0.44.jar%2323!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.1.0.jar%235!/:?] {} at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:149) [bootstraplauncher-1.0.0.jar:?] {}— System Details —Details: Minecraft Version: 1.18.1 Minecraft Version ID: 1.18.1 Operating System: Windows 10 (amd64) version 10.0 Java Version: 17.0.1, Microsoft Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft Memory: 1905640096 bytes (1817 MiB) / 3200253952 bytes (3052 MiB) up to 8589934592 bytes (8192 MiB) CPUs: 12 Processor Vendor: AuthenticAMD Processor Name: AMD Ryzen 5 1600X Six-Core Processor Identifier: AuthenticAMD Family 23 Model 1 Stepping 1 Microarchitecture: Zen Frequency (GHz): 3.59 Number of physical packages: 1 Number of physical CPUs: 6 Number of logical CPUs: 12 Graphics card #0 name: NVIDIA GeForce GTX 1070 Graphics card #0 vendor: NVIDIA (0x10de) Graphics card #0 VRAM (MB): 4095.00 Graphics card #0 deviceId: 0x1b81 Graphics card #0 versionInfo: DriverVersion=30.0.14.9676 Memory slot #0 capacity (MB): 8192.00 Memory slot #0 clockSpeed (GHz): 2.93 Memory slot #0 type: DDR4 Memory slot #1 capacity (MB): 8192.00 Memory slot #1 clockSpeed (GHz): 2.93 Memory slot #1 type: DDR4 Memory slot #2 capacity (MB): 8192.00 Memory slot #2 clockSpeed (GHz): 2.93 Memory slot #2 type: DDR4 Memory slot #3 capacity (MB): 8192.00 Memory slot #3 clockSpeed (GHz): 2.93 Memory slot #3 type: DDR4 Virtual memory max (MB): 42426.63 Virtual memory used (MB): 21730.59 Swap memory total (MB): 9728.00 Swap memory used (MB): 193.14 JVM Flags: 4 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx8192m -Xms256m Launched Version: forge-39.0.44 Backend library: LWJGL version 3.2.2 SNAPSHOT Backend API: NVIDIA GeForce GTX 1070/PCIe/SSE2 GL version 3.2.0 NVIDIA 496.76, NVIDIA Corporation Window size: <not initialized> GL Caps: Using framebuffer using OpenGL 3.2 GL debug messages: Using VBOs: Yes Is Modded: Definitely; Client brand changed to ‘forge’ Type: Client (map_client.txt) CPU: 12x AMD Ryzen 5 1600X Six-Core Processor OptiFine Version: OptiFine_1.18.1_HD_U_H4 OptiFine Build: 20211212-175054 Render Distance Chunks: 8 Mipmaps: 4 Anisotropic Filtering: 1 Antialiasing: 0 Multitexture: false Shaders: null OpenGlVersion: 3.2.0 NVIDIA 496.76 OpenGlRenderer: NVIDIA GeForce GTX 1070/PCIe/SSE2 OpenGlVendor: NVIDIA Corporation CpuCount: 12 ModLauncher: 9.1.0+9.1.0+main.6690ee51 ModLauncher launch target: forgeclient ModLauncher naming: srg ModLauncher services: mixin PLUGINSERVICE eventbus PLUGINSERVICE object_holder_definalize PLUGINSERVICE runtime_enum_extender PLUGINSERVICE capability_token_subclass PLUGINSERVICE accesstransformer PLUGINSERVICE runtimedistcleaner PLUGINSERVICE mixin TRANSFORMATIONSERVICE OptiFine TRANSFORMATIONSERVICE fml TRANSFORMATIONSERVICE FML Language Providers: [email protected] [email protected] Mod List: client-1.18.1-20211210.034407-srg.jar |Minecraft |minecraft |1.18.1 |NONE |Manifest: a1:d4:5e:04:4f:d3:d6:e0:7b:37:97:cf:77:b0:de:ad:4a:47:ce:8c:96:49:5f:0a:cf:8c:ae:b2:6d:4b:8a:3f forge-1.18.1-39.0.44-universal.jar |Forge |forge |39.0.44 |NONE |Manifest: 84:ce:76:e8:45:35:e4:0e:63:86:df:47:59:80:0f:67:6c:c1:5f:6e:5f:4d:b3:54:47:1a:9f:7f:ed:5e:f2:90
-
- To post a comment, please login.
Posts Quoted:
Reply
Clear All Quotes
Hi, i have been trying to get minecraft working on my new computer but it comes up with this error when launching the game. I have searched through the internet to solutions but they all say to change something in the .minecraft file, which has nothing in it for me as i have not loaded minecraft yet.
This is what it says:
FATAL ERROR: java.lang.ExceptionInInitializerError
at org.apache.logging.log4j.util.PropertiesUtil.<init>(PropertiesUtil.java:71)
at org.apache.logging.log4j.util.PropertiesUtil.<clinit>(PropertiesUtil.java:31)
at org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:48)
at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:44)
at net.minecraft.launcher.Launcher.<clinit>(Launcher.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at net.minecraft.bootstrap.Bootstrap.startLauncher(Bootstrap.java:240)
at net.minecraft.bootstrap.Bootstrap.execute(Bootstrap.java:124)
at net.minecraft.bootstrap.Bootstrap.main(Bootstrap.java:381)
Caused by: java.lang.NullPointerException
at org.apache.logging.log4j.util.ProviderUtil.<clinit>(ProviderUtil.java:70)
… 12 more
Please fix the error and restart.
Please Help!
Thank you in advance
Hi, i have been trying to get minecraft working on my new computer but it comes up with this error when launching the game. I have searched through the internet to solutions but they all say to change something in the .minecraft file, which has nothing in it for me as i have not loaded minecraft yet.
This is what it says:
FATAL ERROR: java.lang.ExceptionInInitializerError
at org.apache.logging.log4j.util.PropertiesUtil.<init>(PropertiesUtil.java:71)
at org.apache.logging.log4j.util.PropertiesUtil.<clinit>(PropertiesUtil.java:31)
at org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:48)
at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:44)
at net.minecraft.launcher.Launcher.<clinit>(Launcher.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at net.minecraft.bootstrap.Bootstrap.startLauncher(Bootstrap.java:240)
at net.minecraft.bootstrap.Bootstrap.execute(Bootstrap.java:124)
at net.minecraft.bootstrap.Bootstrap.main(Bootstrap.java:381)
Caused by: java.lang.NullPointerException
at org.apache.logging.log4j.util.ProviderUtil.<clinit>(ProviderUtil.java:70)
… 12 more
Please fix the error and restart.
Please Help!
Thank you in advance
Войти или зарегистрироваться
-
Этот сайт использует файлы cookie. Продолжая пользоваться данным сайтом, Вы соглашаетесь на использование нами Ваших файлов cookie. Узнать больше.
-
Вы находитесь в русском сообществе Bukkit. Мы — администраторы серверов Minecraft, разрабатываем собственные плагины и переводим на русский язык плагины наших собратьев из других стран.
Скрыть объявление
Файлы cookie
Добро пожаловать!
Тема в разделе «[Архив] Помощь», создана пользователем Sanchoce, 12 фев 2014.
- Статус темы:
-
Закрыта.
-
Sanchoce
Активный участник
Пользователь- Баллы:
- 88
- Skype:
- Sanchoce
Не запускается сервер выдает ошибку
Код:
java.lang.ExceptionInInitializerError at org.apache.logging.log4j.util.PropertiesUtil.<init>(PropertiesUtil.ja va:71) at org.apache.logging.log4j.util.PropertiesUtil.<clinit>(PropertiesUtil. java:31) at org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.ja va:48) at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:44) at net.minecraft.server.v1_7_R1.MinecraftServer.<clinit>(MinecraftServer .java:46) at org.bukkit.craftbukkit.Main.main(Main.java:152) Caused by: java.lang.NullPointerException at org.apache.logging.log4j.util.ProviderUtil.<clinit>(ProviderUtil.java :70) ... 6 more Для продолжения нажмите любую клавишу . . .
Пробовал переустановить джаву не помагло
-
The_Luuzzi
Старожил
Пользователь
The_Luuzzi,
12 фев 2014
#2
-
Sanchoce
Активный участник
Пользователь- Баллы:
- 88
- Skype:
- Sanchoce
Разобрался
Не корректно назвал папку, в которой находился сервак
Показать игнорируемое содержимое
- Статус темы:
-
Закрыта.
Поделиться этой страницей
- Ваше имя или e-mail:
- У Вас уже есть учётная запись?
-
- Нет, зарегистрироваться сейчас.
- Да, мой пароль:
-
Забыли пароль?
-
Запомнить меня
Русское сообщество Bukkit