Error stack traces are turned on

Практика показала, что хардкорные расшифровки с наших докладов хорошо заходят, так что мы решили продолжать. Сегодня у нас в меню смесь из подходов к поиску и анализу ошибок и крэшей, приправленная щепоткой полезных инструментов, подготовленная на основе доклада Андрея Паньгина aka apangin из Одноклассников на одном из JUG’ов (это была допиленная версия его доклада с JPoint 2016). В без семи минут двухчасовом докладе Андрей подробно рассказывает о стек-трейсах и хип-дампах.

Пост получился просто огромный, так что мы разбили его на две части. Сейчас вы читаете первую часть, вторая часть лежит здесь.

Сегодня я буду рассказывать про стек-трейсы и хип-дампы — тему, с одной стороны, известную каждому, с другой — позволяющую постоянно открывать что-то новое (я даже багу нашел в JVM, пока готовил эту тему).

Когда я делал тренировочный прогон этого доклада у нас в офисе, один из коллег спросил: «Все это очень интересно, но на практике это кому-нибудь вообще полезно?» После этого разговора первым слайдом в свою презентацию я добавил страницу с вопросами по теме на StackOverflow. Так что это актуально.

Сам я работаю ведущим программистом в Одноклассниках. И так сложилось, что зачастую мне приходится работать с внутренностями Java — тюнить ее, искать баги, дергать что-то через системные классы (порой не совсем легальными способами). Оттуда я и почерпнул большую часть информации, которую сегодня хотел вам представить. Конечно, в этом мне очень помог мой предыдущий опыт: я 6 лет работал в Sun Microsystems, занимался непосредственно разработкой виртуальной Java-машины. Так что теперь я знаю эту тему как изнутри JVM, так и со стороны пользователя-разработчика.

Стек-трейсы

Стек-трейсы exception

Когда начинающий разработчик пишет свой «Hello world!», у него выскакивает эксепшн и ему демонстрируется стек-трейс, где произошла эта ошибка. Так что какие-то представления о стек-трейсах есть у большинства.

Перейдем сразу к примерам.

Я написал небольшую программку, которая в цикле 100 миллионов раз производит такой эксперимент: создает массив из 10 случайных элементов типа long и проверяет, сортированный он получился или нет.

package demo1;

import java.util.concurrent.ThreadLocalRandom;

public class ProbabilityExperiment {

    private static boolean isSorted(long[] array) {
        for (int i = 0; i < array.length; i++) {
            if (array[i] > array[i + 1]) {
                return false;
            }
        }
        return true;
    }

    public void run(int experiments, int length) {
        int sorted = 0;

        for (int i = 0; i < experiments; i++) {
            try {
                long[] array = ThreadLocalRandom.current().longs(length).toArray();
                if (isSorted(array)) {
                    sorted++;
                }
            } catch (Exception e) {
                e.printStackTrace();
            }
        }

        System.out.printf("%d of %d arrays are sortedn", sorted, experiments);
    }

    public static void main(String[] args) {
        new ProbabilityExperiment().run(100_000_000, 10);
    }
}

По сути он считает вероятность получения сортированного массива, которая приблизительно равна 1/n!. Как это часто бывает, в программке ошиблись на единичку:

for (int i = 0; i < array.length; i++)

Что произойдет? Эксепшн, выход за пределы массива.
Давайте разбираться, в чем дело. У нас в консоль выводится:

java.lang.ArrayIndexOutOfBoundsException

но стек-трейсов никаких нет. Куда делись?

В HotSpot JVM есть такая оптимизация: у эксепшенов, которые кидает сама JVM из горячего кода, а в данном случае код у нас горячий — 100 миллионов раз дергается, стек-трейсы не генерируются.
Это можно исправить с помощью специального ключика:

-XX:-OmitStackTraceInFastThrow

Теперь попробуем запустить пример. Получаем все то же самое, только все стек-трейсы на месте.

Подобная оптимизация работает для всех неявных эксепшенов, которые бросает JVM: выход за границы массива, разыменование нулевого указателя и т.д.

Раз оптимизацию придумали, значит она зачем-то нужна? Понятно, что программисту удобнее, когда стек-трейсы есть.

Давайте измерим, сколько «стоит» у нас создание эксепшена (сравним с каким-нибудь простым Java-объектом, вроде Date).

@Benchmark
public Object date() {
    return new Date();
}

@Benchmark
public Object exception() {
    return new Exception();
}

С помощью JMH напишем простенькую бенчмарку и измерим, сколько наносекунд занимают обе операции.

Оказывается, создать эксепшн в 150 раз дороже, чем обычный объект.
И тут не все так просто. Для виртуальной машины эксепшн не отличается от любого другого объекта, но разгадка кроется в том, что практически все конструкторы эксепшн так или иначе сводятся к вызову метода fillInStackTrace, который заполняет стек-трейс этого эксепшена. Именно заполнение стек-трейса отнимает время.

Этот метод в свою очередь нативный, падает в VM рантайм и там гуляет по стеку, собирает все фреймы.

Метод fillInStackTrace публичный, не final. Давайте его просто переопределим:

@Benchmark
public Object exceptionNoStackTrace() {
    return new Exception() {
        @Override
        public Throwable fillInStackTrace() {
            return this;
        }
    };
}

Теперь создание обычного объекта и эксепшена без стек-трейса отнимают одинаковое время.

Есть и другой способ создать эксепшн без стек-трейса. Начиная с Java 7, у Throwable и у Exception есть protected-конструктор с дополнительным параметром writableStackTrace:

protected Exception(String message, Throwable cause,
                    boolean enableSuppression,
                    boolean writableStackTrace);

Если туда передать false, то стек-трейс генерироваться не будет, и создание эксепшена будет очень быстрым.

Зачем нужны эксепшены без стек-трейсов? К примеру, если эксепшн используется в коде в качестве способа быстро выбраться из цикла. Конечно, лучше так не делать, но бывают случаи, когда это действительно дает прирост производительности.

А сколько стоит бросить эксепшн?

Рассмотрим разные случаи: когда он бросается и ловится в одном методе, а также ситуации с разной глубиной стека.

@Param("1", "2", "10", "100", "1000"})
int depth;

@Benchmark
public Object throwCatch() {
    try {
        return recursive(depth);
    } catch (Exception e) {
        return e;
    }
}

Вот, что дают измерения:

Т.е. если у нас глубина небольшая (эксепшн ловится в том же фрейме или фреймом выше — глубина 0 или 1), эксепшн ничего не стоит. Но как только глубина стека становится большой, затраты совсем другого порядка. При этом наблюдается четкая линейная зависимость: «стоимость» исключения почти линейно зависит от глубины стека.

Дорого стоит не только получение стек-трейса, но и дальнейшие манипуляции — распечатка, отправка по сети, запись, — все, для чего используется метод getStackTrace, который переводит сохраненный стек-трейс в объекты Java.

@Benchmark
public Object fillInStackTrace() {
    return new Exception();
}

@Benchmark
public Object getStackTrace() {
    return new Exception().getStackTrace();
}

Видно, что преобразование стек-трейса в 10 раз «дороже» его получения:

Почему это происходит?

Вот метод getStackTrace в исходниках JDK:

Сначала через вызов нативного метода мы узнаем глубину стека, потом в цикле до этой глубины вызываем нативный метод, чтобы получить очередной фрейм и сконвертировать его в объект StackTraceElement (это нормальный объект Java с кучей полей). Мало того, что это долго, процедура отнимает много памяти.

Более того, в Java 9 этот объект дополнен новыми полями (в связи с известным проектом модуляризации) — теперь каждому фрейму приписывается отметка о том, из какого он модуля.

Привет тем, кто парсит эксепшены с помощью регулярных выражений. Готовьтесь к сюрпризам в Java 9 — появятся еще и модули.

Давайте подведем итоги

• создание самого объекта эксепшн — дешевое;
• занимает время получение его стек-трейса;
• еще дороже — преобразование этого внутреннего стек-трейса в Java-объект в StackTraceElement. Сложность этого дела прямо пропорциональна глубине стека.
• бросание эксепшн — быстрое, оно почти ничего не стоит (почти как безусловный переход),
• но только если эксепшн ловится в том же фрейме. Тут надо дополнить еще, что JIT у нас умеет инлайнить методы, поэтому один скомпилированный фрейм может в себя включать несколько Java-методов, заинлайниных друг в друга. Но если эксепшн ловится где-то глубже по стеку, его дороговизна пропорциональна глубине стека.

Пара советов:

• отключайте на продакшене оптимизацию, возможно, это сэкономит много времени на отладке:

  -XX:-OmitStackTraceInFastThrow

• не используйте эксепшены для управления потоком программы; это считается не очень хорошей практикой;
• но если вы все-таки прибегаете к этому способу, позаботьтесь о том, чтобы эксепшены были быстрыми и лишний раз не создавали стек-трейсы.

Стек-трейсы в тред дампах

Чтобы узнать, что же делает программа, проще всего взять тред дамп, например, утилитой jstack.

Фрагменты вывода этой утилиты:

Что здесь видно? Какие есть потоки, в каком они состоянии и их текущий стек.

Более того, если потоки захватили какие-то локи, ожидают входа в synchronized-секцию или взятия ReentrantLock, это также будет отражено в стек-трейсе.

Порой полезным оказывается малоизвестный идентификатор:

Он напрямую связан с ID потока в операционной системе. Например, если вы смотрите программой top в Linux, какие треды у вас больше всего едят CPU, pid потока — это и есть тот самый nid, который демонстрируется в тред дампе. Можно тут же найти, какому Java-потоку он соответствует.

В случае с мониторами (с synchronized-объектами) прямо в тред дампе будет написано, какой тред и какие мониторы держит, кто пытается их захватить.

В случае с ReentrantLock это, к сожалению, не так. Здесь видно, как Thread 1 пытается захватить некий ReentrantLock, но при этом не видно, кто этот лок держит. На этот случай в VM есть опция:

-XX:+PrintConcurrentLocks

Если мы запустим то же самое с PrintConcurrentLocks, в тред дампе увидим и ReentrantLock.

Здесь указан тот самый id лока. Видно, что его захватил Thread 2.

Если опция такая хорошая, почему бы ее не сделать «по умолчанию»?

Она тоже чего-то стоит. Чтобы напечатать информацию о том, какой поток какие ReentrantLock’и держит, JVM пробегает весь Java heap, ищет там все ReentrantLock’и, сопоставляет их с тредами и только потом выводит эту информацию (у треда нет информации о том, какие локи он захватил; информация есть только в обратную сторону — какой лок связан с каким тредом).

В указанном примере по названиям потоков (Thread 1 / Thread 2) непонятно, к чему они относятся. Мой совет из практики: если у вас происходит какая-то длинная операция, например, сервер обрабатывает клиентские запросы или, наоборот, клиент ходит к нескольким серверам, выставляйте треду понятное имя (как в случае ниже — прямо IP того сервера, к которому клиент сейчас идет). И тогда в дампе потока сразу будет видно, ответа от какого сервера он сейчас ждет.

Хватит теории. Давайте опять к практике. Этот пример я уже не раз приводил.

package demo2;

import java.util.stream.IntStream;

public class ParallelSum {
    static int SUM = IntStream.range(0, 100).parallel().reduce(0, (x, y) -> x + y);

    public static void main(String[] args) {
        System.out.println(SUM);
    }
}

Запускаем программку 3 раза подряд. 2 раза она выводит сумму чисел от 0 до 100 (не включая 100), третий — не хочет. Давайте смотреть тред дампы:

Первый поток оказывается RUNNABLE, выполняет наш reduce. Но смотрите, какой интересный момент: Thread.State вроде как RUNNABLE, но при этом написано, что поток in Object.wait().

Мне тоже это было не понятно. Я даже хотел сообщить о баге, но оказывается, такая бага заведена много лет назад и закрыта с формулировкой: «not an issue, will not fix».
В этой программке действительно есть дедлок. Его причина — инициализация классов.

Выражение выполняется в статическом инициализаторе класса ParallelSum:

static int SUM = IntStream.range(0, 100).parallel().reduce(0, (x, y) -> x + y);

Но поскольку стрим параллельный, исполнение происходит в отдельных потоках ForkJoinPool, из которых вызывается тело лямбды:

(x, y) -> x + y

Код лямбды записан Java-компилятором прямо в классе ParallelSum в виде приватного метода. Получается, что из ForkJoinPool мы пытаемся обратиться к классу ParallelSum, который в данный момент находится на этапе инициализации. Поэтому потоки начинают ждать, когда же закончится инициализация класса, а она не может закончиться, поскольку ожидает вычисления этой самой свертки. Дедлок.

Почему вначале сумма считалась? Просто повезло. У нас небольшое количество элементов суммируется, и иногда все исполняется в одном потоке (другой поток просто не успевает).

Но почему же тогда поток в стек-трейсе RUNNABLE? Если почитать документацию к Thread.State, станет понятно, что никакого другого состояния здесь быть не может. Не может быть состояния BLOCKED, поскольку поток не заблокирован на Java-мониторе, нет никакой synchronized-секции, и не может быть состояния WAITING, потому что здесь нет никаких вызовов Object.wait(). Синхронизация происходит на внутреннем объекте виртуальной машины, который, вообще говоря, даже не обязан быть Java-объектом.

Стек-трейс при логировании

Представьте себе ситуацию: в куче мест в нашем приложении что-то логируется. Было бы полезно узнать, из какого места появилась та или иная строчка.

В Java нет препроцессора, поэтому нет возможности использовать макросы __FILE__, __LINE__, как в С (эти макросы еще на этапе компиляции преобразуются в текущее имя файла и строку). Поэтому других способов дополнить вывод именем файла и номером строки кода, откуда это было напечатано, кроме как через стек-трейсы, нет.

public static String getLocation() {
    StackTraceElement s = new Exception().getStackTrace()[2];
	return s.getFileName() + ':' + s.getLineNumber();
}

Генерим эксепшн, у него получаем стек-трейс, берем в данном случае второй фрейм (нулевой — это метод getLocation, а первый — вызывает метод warning).

Как мы знаем, получение стек-трейса и, тем более, преобразование его в стек-трейс элементы очень дорого. А нам нужен один фрейм. Можно ли как-то проще сделать (без эксепшн)?

Помимо getStackTrace у исключения есть метод getStackTrace объекта Thread.

Thread.current().getStackTrace()

Будет ли так быстрее?

Нет. JVM никакой магии не делает, здесь все будет работать через тот же эксепшн с точно таким же стек-трейсом.

Но хитрый способ все-таки есть:

public static String getLocation() {
    StackTraceElement s = sun.misc.SharedSecrets.getJavaLangAccess()
            .getStackTraceElement(new Exception(), 2);

    return s.getFileName() + ':' + s.getLineNumber();
}

Я люблю всякие приватные штуки: Unsafe, SharedSecrets и т.д.

Есть аксессор, который позволяет получить StackTraceElement конкретного фрейма (без необходимости преобразовывать весь стек-трейс в Java-объекты). Это будет работать быстрее. Но есть плохая новость: в Java 9 это работать не будет. Там проделана большая работа по рефакторингу всего, что связано со стек-трейсами, и таких методов там теперь просто нет.

Конструкция, позволяющая получить какой-то один фрейм, может быть полезна в так называемых Caller-sensitive методах — методах, чей результат может зависеть от того, кто их вызывает. В прикладных программах с такими методами приходится сталкиваться нечасто, но в самой JDK подобных примеров немало:

В зависимости от того, кто вызывает Class.forName, поиск класса будет осуществляться в соответствующем класс-лоадере (того класса, который вызвал этот метод); аналогично — с получением ResourceBundle и загрузкой библиотеки System.loadLibrary. Также информация о том, кто вызывает, полезна при использовании различных методов, которые проверяют пермиссии (а имеет ли данный код право вызывать этот метод). На этот случай в «секретном» API предусмотрен метод getCallerClass, который на самом деле является JVM-интринсиком и вообще почти ничего не стоит.

sun.reflect.Reflection.getCallerClass

Как уже много раз говорилось, приватный API — это зло, использовать которое крайне не рекомендуется (сами рискуете нарваться на проблемы, подобные тем, что ранее вызвал Unsafe). Поэтому разработчики JDK задумались над тем, что раз этим пользуются, нужна легальная альтернатива — новый API для обхода потоков. Основные требования к этому API:

• чтобы можно было обойти только часть фреймов (если нам нужно буквально несколько верхних фреймов);
• возможность фильтровать фреймы (не показывать ненужные фреймы, относящиеся к фреймворку или системным классам);
• чтобы эти фреймы конструировались ленивым образом (lazy) — если нам не нужно получать информацию о том, с каким файлом он связан, эта информация преждевременно не извлекается;
• как в случае с getCallerClass — нам нужно не имя класса, а сам инстанс java.lang.Class.

Известно, что в публичном релизе Java 9 будет java.lang.StackWalker.
Получить его экземпляр очень просто — методом getInstance. У него есть несколько вариантов — дефолтный StackWalker или незначительно конфигурируемый опциями:

• опция RETAIN_CLASS_REFERENCE означает, что вам нужны не имена классов, а именно инстансы;
• прочие опции позволяют показать в стек-трейсе фреймы, относящиеся к системным классам и классам рефлекшн (по умолчанию они не будут показаны в стек-трейсе).

Также для оптимизации можно задавать примерную глубину, которая необходима (чтобы JVM могла оптимизировать получение стек-фреймов в batch).

Простейший пример, как этим пользоваться:

StackWalker sw = StackWalker.getInstance();
sw.forEach(System.out::println);

Берем StackWalker и вызываем метод forEach, чтобы он обошел все фреймы. В результате получим такой простой стек-трейс:

То же самое с опцией SHOW_REFLECT_FRAMES:

StackWalker sw = StackWalker.getInstance(StackWalker.Option.SHOW_REFLECT_FRAMES);
sw.forEach(System.out::println);

В этом случае добавятся методы, относящиеся к вызову через рефлекшн:

Если добавить опцию SHOW_HIDDEN_FRAMES (она, кстати, включает в себя SHOW_REFLECT_FRAMES, т.е. рефлекшн-фреймы тоже будут показаны):

StackWalker sw = StackWalker.getInstance(StackWalker.Option.SHOW_HIDDEN_FRAMES);
sw.forEach(System.out::println);

В стек-трейсе появятся методы динамически-сгенерированных классов лямбд:

А теперь самый главный метод, который есть в StackWalker API — метод walk с такой хитрой непонятной сигнатурой с кучей дженериков:

public <T> T walk(Function<? super Stream<StackFrame>, ? extends T> function)

Метод walk принимает функцию от стек-фрейма.

Его работу проще показать на примере.

Несмотря на то, что все это выглядит страшно, как этим пользоваться — очевидно. В функцию передается стрим, а уже над стримом можно проводить все привычные операции. К примеру, вот так выглядел бы метод getCallerFrame, который достает только второй фрейм: пропускаются первые 2, потом вызывается findFirst:

public static StackFrame getCallerFrame() {
    return StackWalker.getInstance()
            .walk(stream -> stream.skip(2).findFirst())
            .orElseThrow(NoSuchElementException::new);
}

Метод walk возвращает тот результат, который возвращает эта функция стрима. Все просто.
Для данного конкретного случая (когда нужно получить просто Caller класс) есть специальный shortcut метод:

return StackWalker.getInstance(RETAIN_CLASS_REFERENCE).getCallerClass();

Еще один пример посложнее.

Обходим все фреймы, оставляем только те, которые относятся к пакету org.apache, и выводим первые 10 в список.

StackWalker sw = StackWalker.getInstance();

List<StackFrame> frames = sw.walk(stream ->
        stream.filter(sf -> sf.getClassName().startsWith("org.apache."))
              .limit(10)
              .collect(Collectors.toList()));

Интересный вопрос: зачем такая длинная сигнатура с кучей дженериков? Почему бы просто не сделать у StackWalker метод, который возвращает стрим?

public Stream<StackFrame> stream();

Если дать API, который возвращает стрим, у JDK теряется контроль над тем, что дальше над этим стримом делают. Можно дальше этот стрим положить куда-то, отдать в другой поток, попробовать его использовать через 2 часа после получения (тот стек, который мы пытались обойти, давно потерян, а тред может быть давно убит). Таким образом будет невозможно обеспечить «ленивость» Stack Walker API.

Основной поинт Stack Walker API: пока вы находитесь внутри walk, у вас зафиксировано состояние стека, поэтому все операции на этом стеке можно делать lazy.

На десерт еще немного интересного.

Как всегда, разработчики JDK прячут от нас кучу сокровищ. И помимо обычных стек-фреймов они для каких-то своих нужд сделали живые стек-фреймы, которые отличаются от обычных тем, что имеют дополнительные методы, позволяющие не только получить информацию о методе и классе, но еще и о локальных переменных, захваченных мониторах и значениях экспрешн-стека данного стек-фрейма.

/* package-private */
interface LiveStackFrame extends StackFrame {

    public Object[] getMonitors();
    public Object[] getLocals();
    public Object[] getStack();
    public static StackWalker getStackWalker();
}

Защита здесь не ахти какая: класс просто сделали непубличным. Но кто же нам мешает взять рефлекшн и попробовать его? (Примечание: в актуальных сборках JDK 9 доступ к непубличному API через рефлекшн запрещён. Чтобы его разрешить, необходимо добавить опцию JVM --add-opens=java.base/java.lang=ALL-UNNAMED)

Пробуем на таком примере. Есть программа, которая рекурсивным методом ищет выход из лабиринта. У нас есть квадратное поле size x size. Есть метод visit с текущими координатами. Мы пытаемся из текущей клетки пойти влево / вправо / вверх / вниз (если они не заняты). Если дошли из правой-нижней клетки в левую-верхнюю, считаем, что нашли выход и распечатываем стек.

package demo3;

import java.util.Random;

public class Labyrinth {
    static final byte FREE = 0;
    static final byte OCCUPIED = 1;
    static final byte VISITED = 2;

    private final byte[][] field;

    public Labyrinth(int size) {
        Random random = new Random(0);
        field = new byte[size][size];

        for (int x = 0; x < size; x++) {
            for (int y = 0; y < size; y++) {
                if (random.nextInt(10) > 7) {
                    field[x][y] = OCCUPIED;
                }
            }
        }

        field[0][0] = field[size - 1][size - 1] = FREE;
    }

    public int size() {
        return field.length;
    }

    public boolean visit(int x, int y) {
        if (x == 0 && y == 0) {
            StackTrace.dump();
            return true;
        }

        if (x < 0 || x >= size() || y < 0 || y >= size() || field[x][y] != FREE) {
            return false;
        }

        field[x][y] = VISITED;
        return visit(x - 1, y) || visit(x, y - 1) || visit(x + 1, y) || visit(x, y + 1);
    }

    public String toString() {
        return "Labyrinth";
    }

    public static void main(String[] args) {
        Labyrinth lab = new Labyrinth(10);
        boolean exitFound = lab.visit(9, 9);
        System.out.println(exitFound);
    }
}

Запускаем:

Если я делаю обычный dumpStack, который был еще в Java 8, получаем обычный стек-трейс, из которого ничего не понятно. Очевидно — рекурсивный метод сам себя вызывает, но интересно, на каком шаге (и с какими значениями координат) вызывается каждый метод.

Заменим стандартный dumpStack на наш StackTrace.dump, который через рефлекшн использует live стек-фреймы:

package demo3;

import java.lang.reflect.Method;
import java.util.Arrays;

public class StackTrace {

    private static Object invoke(String methodName, Object instance) {
        try {
            Class<?> liveStackFrame = Class.forName("java.lang.LiveStackFrame");
            Method m = liveStackFrame.getMethod(methodName);
            m.setAccessible(true);
            return m.invoke(instance);
        } catch (ReflectiveOperationException e) {
            throw new AssertionError("Should not happen", e);
        }
    }

    public static void dump() {
        StackWalker sw = (StackWalker) invoke("getStackWalker", null);
        sw.forEach(frame -> {
            Object[] locals = (Object[]) invoke("getLocals", frame);
            System.out.println(" at " + frame + "  " + Arrays.toString(locals));
        });
    }
}

В первую очередь надо получить соответствующий StackWalker, вызвав метод getStackWalker. Все фреймы, которые будут передаваться в getStackWalker, на самом деле будут экземплярами лайв стек-фрейма, у которого есть дополнительные методы, в частности, getLocals для получения локальных переменных.

Запускаем. Получаем то же самое, но у нас отображается весь путь из лабиринта в виде значений локальных переменных:

На этом мы заканчиваем первую часть поста. Вторая часть здесь.

Почему я получаю ошибку «401 Unauthorized» в Maven?

Вот ошибка, которую я получаю при вызове mvn deploy (полные журналы внизу):

[INFO] BUILD FAILURE
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project xbnjava: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

В соответствии с этой страницей поддержки соната:

«Если вы получаете 401, это потому, что maven отправляет неверные учетные данные или вообще не имеет учетных данных».

Ниже приведены шаги, которые я сделал ниже, это мои полные файлы settings.xml и pom.xml, а ниже — полные журналы из mvn deploy и mvn deploy -e.

Любые идеи будут оценены. Я просто ударяю о стену после стены с Maven.

Я получил контрольный список соната при получении ошибки 401:

Элемент контрольного списка 1. Убедитесь, что ваше имя пользователя/пароль верны, войдя в пользовательский интерфейс Nexus. Если на вашем компьютере установлен curl, вы можете попробовать установить артефакт с помощью…

• Я успешно выполнил вход на сайт sonatype.org и вышел из него, используя user/pass в settings.xml.
• Я попытался использовать curl для ручного развертывания артефакта с помощью команды

[C:]curl -u MY_SONATYPE_DOT_COM_USERNAME:MY_SONATYPE_DOT_COM_PASSWORD https://oss.sonatype.org/content/repositories/snapshots/com/github/aliteralmind/xbnjava/0.1.2-SNAPSHOT/xbnjava-0.1.2-20140716.224928-1.pom --request PUT --data @pom.xml

но получил эту ошибку:

Warning: Couldn't read data from file "pom.xml", this makes an empty POST.
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl verification of the certificate, use
 the -k (or --insecure) option.

Я снова запустил его с опцией -k, и на этот раз получил только это:

Couldn't read data from file "pom.xml", this makes an empty POST.

Я никогда раньше не использовал завиток, поэтому я не понимаю, что делать с этой информацией.

Контрольный элемент 2. Если выход ошибки отсутствует, убедитесь, что ваши права пользователя правильно настроены на сервере. Обязательно отпустите созданное вами репо.

Я не знаю, что означает «падение». Я считаю, что мои права установлены правильно, так как я получил это сообщение от соната:

• Конфигурация подготовлена, теперь вы можете:
• Развернуть артефакты моментальных снимков в репозитории https://oss.sonatype.org/content/repositories/snapshots
• Развертывание артефактов выпуска в промежуточном репозитории https://oss.sonatype.org/service/local/staging/deploy/maven2
• Содействовать поэтапным артефактам в репозитории «Релизы»
• Загрузить снимок и выпустить артефакты из группы https://oss.sonatype.org/content/groups/public
• Загрузить моментальный снимок, выпуск и поэтапные артефакты из промежуточной группы https://oss.sonatype.org/content/groups/staging

и я успешно разместил эти элементы на сервере через mvn deploy за последние пару дней.

Настройки проекта:

Элемент контрольного списка 3. Убедитесь, что вы настроили сервер в settings.xml и что идентификатор сервера идентичен идентификатору репозитория дистрибутива в pom.xml.

• В settings.xml параметры/серверы/сервер/идентификатор равны ossrh
• В pom.xml, distributionManagement/snapshotRepository/id равно ossrh

(полные файлы внизу)

Элемент контрольного списка 4. Убедитесь, что ваш файл settings.xml находится в правильном месте (обычно его _ ~/.m2/settings.xml). Вы можете проверить это, выполнив mvn help: effective-settings.

Согласно ссылке Maven настроек, settings.xml должен находиться в одном из двух мест:

• Установка Maven: $M2_HOME/conf/settings.xml
• Пользователи устанавливают: ${user.home}/.m2/settings.xml

Здесь моя настройка:

• settings.xml: C:applicationsprogrammingapache-maven-3.2.2confsettings.xml
• M2_HOME C:applicationsprogrammingapache-maven-3.2.2

Выход для mvn help:effective-settings:

[C:applicationsutilitiescurl]
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-help-plugin:2.2:effective-settings (default-cli) @ standalone-pom ---
[INFO]
Effective user-specific configuration settings:

<?xml version="1.0" encoding="UTF-8"?>
<!-- ====================================================================== -->
<!--                                                                        -->
<!-- Generated by Maven Help Plugin on 2014-07-18T12:48:19                  -->
<!-- See: http://maven.apache.org/plugins/maven-help-plugin/                -->
<!--                                                                        -->
<!-- ====================================================================== -->

<!-- ====================================================================== -->
<!--                                                                        -->
<!-- Effective Settings for 'jeffy' on 'kermit-the-frog'                    -->
<!--                                                                        -->
<!-- ====================================================================== -->

<settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sc
hemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd">
  <localRepository xmlns="http://maven.apache.org/SETTINGS/1.1.0">C:Usersjeffy.m2repository</localRepository
>
  <servers xmlns="http://maven.apache.org/SETTINGS/1.1.0">
    <server>
      <username>MY_SONATYPE_DOT_COM_USERNAME</username>
      <password>***</password>
      <id>ossrh</id>
    </server>
  </servers>
  <pluginGroups xmlns="http://maven.apache.org/SETTINGS/1.1.0">
    <pluginGroup>org.apache.maven.plugins</pluginGroup>
    <pluginGroup>org.codehaus.mojo</pluginGroup>
  </pluginGroups>
</settings>

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.310 s
[INFO] Finished at: 2014-07-18T12:48:19-04:00
[INFO] Final Memory: 7M/17M
[INFO] ------------------------------------------------------------------------

Контрольный элемент 5. Если сервер использует https, но URL-адрес вашего POM — http, вы также можете получить 401.

Я не понимаю, к какому URL это относится.

Контрольный пункт 6. Используйте последнюю версию Maven, так как существует известная проблема в отношении 401: MNG-4469

Я использую последнюю версию:

[C:]mvn -version
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
Maven home: C:applicationsprogrammingapache-maven-3.2.2
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:applicationsprogrammingjdk_7_51jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"

——————

Полные settings.xml и pom.xml файлы

(Полный журнал для mvn deploy и mvn deploy -e ниже)

settings.xml:

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
   <servers>
     <server>
       <id>ossrh</id>
       <username>MY_SONATYPE_DOT_COM_USERNAME</username>
       <password>MY_SONATYPE_DOT_COM_PASSWORD</password>
     </server>
   </servers>

   <pluginGroups></pluginGroups>
   <proxies></proxies>
   <mirrors></mirrors>
   <profiles></profiles>
</settings>

pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.github.aliteralmind</groupId>
   <artifactId>xbnjava</artifactId>
   <packaging>pom</packaging>
   <version>0.1.2</version>
   <name>XBN-Java</name>
   <url>https://github.com/aliteralmind/xbnjava</url>
   <inceptionYear>2014</inceptionYear>
   <organization>
      <name>Jeff Epstein</name>
   </organization>
   <description>XBN-Java is a collection of generically-useful backend (server side, non-GUI) programming utilities, featuring RegexReplacer and FilteredLineIterator. XBN-Java is the foundation of Codelet (http://codelet.aliteralmind.com).</description>

   <parent>
      <groupId>org.sonatype.oss</groupId>
      <artifactId>oss-parent</artifactId>
      <version>7</version>
   </parent>

   <licenses>
      <license>
         <name>Lesser General Public License (LGPL) version 3.0</name>
         <url>https://www.gnu.org/licenses/lgpl-3.0.txt</url>
      </license>
      <license>
         <name>Apache Software License (ASL) version 2.0</name>
         <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      </license>
   </licenses>

   <developers>
      <developer>
         <name>Jeff Epstein</name>
         <email>[email protected]</email>
         <roles>
            <role>Lead Developer</role>
         </roles>
      </developer>
   </developers>

   <issueManagement>
      <system>GitHub Issue Tracker</system>
      <url>https://github.com/aliteralmind/xbnjava/issues</url>
   </issueManagement>

   <distributionManagement>
      <snapshotRepository>
         <id>ossrh</id>
         <url>https://oss.sonatype.org/content/repositories/snapshots</url>
      </snapshotRepository>
   </distributionManagement>

   <scm>
      <connection>scm:git:[email protected]:aliteralmind/xbnjava.git</connection>
      <url>scm:git:[email protected]:aliteralmind/xbnjava.git</url>
      <developerConnection>scm:git:[email protected]:aliteralmind/xbnjava.git</developerConnection>
   </scm>

   <properties>
      <java.version>1.7</java.version>
      <jarprefix>R:jeffyprogrammingbuild/${project.artifactId}-${project.version}/download/${project.artifactId}-${project.version}</jarprefix>
   </properties>
<!--
  <profiles>
    <profile>
      <id>default-tools.jar</id>
      <activation>
        <property>
          <name>java.vendor</name>
          <value>Sun Microsystems Inc.</value>
        </property>
      </activation>
      <dependencies>
        <dependency>
          <groupId>com.sun</groupId>
          <artifactId>tools</artifactId>
          <version>1.4.2</version>
          <scope>system</scope>
          <systemPath>${java.home}/../lib/tools.jar</systemPath>
        </dependency>
      </dependencies>
    </profile>
  </profiles>
 -->
   <build>
      <plugins>
         <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>build-helper-maven-plugin</artifactId>
            <version>1.8</version>
            <executions>
               <execution>
                  <id>attach-artifacts</id>
                  <phase>package</phase>
                  <goals>
                     <goal>attach-artifact</goal>
                  </goals>
                  <configuration>
                     <artifacts>
                        <artifact>
                           <file>${jarprefix}-all.jar</file>
                           <type>jar</type>
                        </artifact>
                     </artifacts>
                  </configuration>
               </execution>
            </executions>
         </plugin>
      </plugins>
   </build>

   <profiles>
      <!--
      This profile will sign the JAR file, sources file, and javadocs file using the GPG key on the local machine.
      See: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
      -->
      <profile>
         <id>release-sign-artifacts</id>
         <activation>
            <property>
               <name>release</name>
               <value>true</value>
            </property>
         </activation>
      </profile>
   </profiles>
</project>

——————

Полный журнал для mvn deploy и mvn deploy -e

mvn deploy вывод:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building XBN-Java 0.1.2
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ xbnjava ---
[INFO] --- build-helper-maven-plugin:1.8:attach-artifact (attach-artifacts) @ xbnjava ---
[INFO] --- maven-install-plugin:2.4:install (default-install) @ xbnjava ---
[INFO] Installing R:jeffyprogrammingsandboxz__for_git_commit_onlyxbnjavapom.xml to C:Usersjeffy.m2repositorycomgithubaliteralmindxbnjava.1.2xbnjava-0.1.2.pom
[INFO] Installing R:jeffyprogrammingbuildxbnjava-0.1.2downloadxbnjava-0.1.2-all.jar to C:Usersjeffy.m2repositorycomgithubaliteralmindxbnjava.1.2xbnjava-0.1.2.jar
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ xbnjava ---
Uploading: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom
2/6 KB
4/6 KB
6/6 KB

(раздел «Неисправность»:)

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.204 s
[INFO] Finished at: 2014-07-18T11:25:17-04:00
[INFO] Final Memory: 7M/17M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project xbnjava: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

mvn deploy -e вывод:

[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building XBN-Java 0.1.2
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ xbnjava ---
[INFO] --- build-helper-maven-plugin:1.8:attach-artifact (attach-artifacts) @ xbnjava ---
[INFO] --- maven-install-plugin:2.4:install (default-install) @ xbnjava ---
[INFO] Installing R:jeffyprogrammingsandboxz__for_git_commit_onlyxbnjavapom.xml to C:Usersjeffy.m2repositorycomgithubaliteralmindxbnjava.1.2xbnjava-0.1.2.pom
[INFO] Installing R:jeffyprogrammingbuildxbnjava-0.1.2downloadxbnjava-0.1.2-all.jar to C:Usersjeffy.m2repositorycomgithubaliteralmindxbnjava.1.2xbnjava-0.1.2.jar
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ xbnjava ---
Uploading: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom
2/6 KB
4/6 KB
6/6 KB

(раздел «Неисправность»:)

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.492 s
[INFO] Finished at: 2014-07-18T11:25:37-04:00
[INFO] Final Memory: 7M/17M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project xbnjava: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project xbnjava: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
   at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
   at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
   at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
   at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
   at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
   at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
   at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:193)
   at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
   ... 19 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:143)
   at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167)
   at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149)
   ... 21 more
Caused by: org.eclipse.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:337)
   at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:268)
   at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:413)
   at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:139)
   ... 23 more
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact com.github.aliteralmind:xbnjava:pom:0.1.2 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1016)
   at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004)
   at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:895)
   at org.eclipse.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:522)
   at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:331)
   ... 26 more
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Return code is: 401, ReasonPhrase: Unauthorized.
   at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:573)
   at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:493)
   at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:474)
   at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:454)
   at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:871)
   ... 28 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I recently got an email from Nosheen Javed asking about an exception he was getting on his Maven build. The exception was:

[FATAL] Non-resolvable parent POM: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0

…which, when listed in full, comes out as:

Apache Maven 3.0.4 (r1232337; 2012-01-17 13:44:56+0500)
Maven home: C:UsersNosheenworkspacesimple-fingers-sampleEMBEDDED
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: C:Program Files (x86)Javajre7
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from EMBEDDEDconfsettings.xml
[DEBUG] Reading user settings from C:UsersNosheen.m2settings.xml
[DEBUG] Using local repository at C:UsersNosheen.m2repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for C:UsersNosheen.m2repository
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]

org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 inhttp://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 4, column 10
 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363)
 at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
 at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[ERROR]  
[ERROR]   The project com.mycompany.samples:simple-fingers-sample:4.2.0.0 (C:UsersNosheenworkspacesimple-fingers-samplepom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 inhttp://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
org.apache.maven.model.resolution.UnresolvableModelException: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
 at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:159)
 at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:813)
 at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:664)
 at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:310)
 at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:410)
 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:379)
 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:343)
 at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
 at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
 at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)
 at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:155)
 ... 22 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
 at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
 at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204)
 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427)
 ... 26 more
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

I thought it worth noting as it’s something I’ve seen several times. It generally crops up when you’re setting up a project giving you a bewildering amount of information. This is telling me that slf4j has not been set up, that the build is using Java version 1.7.0_07 from Oracle, and that the Maven home is C:UsersNosheenworkspacesimple-fingers-sampleEMBEDDED; however, if you dissect the whole lot, you can refine the problem down to the following:

[FATAL] Non-resolvable parent POM: Failure to find com.mycompany.samples:biometrics-samples:pom:4.2.0.0 inhttp://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM

This means that the project the Nosheen is trying to get to compile has a parent project called «com.mycompany.samples:biometrics-samples:pom» and Maven can’t find it.In this case, I’m assuming that the parent project «com.mycompany.samples:biometrics-samples:pom» is a MyCompany internal project that will not be stored in an external Maven repository like Maven Central.The irritating thing about this exception is that there are a few reasons for it to be thrown which means that there are a number of things that you have to check in order to fix it.Firstly, is the parent project in your local repository? If not there are a couple of options, like do you need to check it out and build it yourself? If you have checked it out can your project see it or do you need to add a relative path element to your project’s POM file? Something like this:

<parent>
  <groupId>com.mycompany.samples</groupId>
  <artifactId>biometrics-samples</artifactId>
  <version>1.0-SNAPSHOT</version>
  <relativePath>{path to}/mycompany-samples/pom.xml</relativePath>
 </parent>

If your company has an internal repository on some company server somewhere, then do you need to add a reference to it in either of your local or global settings.xml or pom.xml files? Something like this JBoss public repository definition:

<repositories>
  <repository> 
      <id>jboss-public-repository-group</id> 
      <url>https://repository.jboss.org/nexus/content/groups/public-jboss</url> 
   <releases> 
    <enabled>true</enabled> 
   </releases> 
   <snapshots> 
     <enabled>true</enabled> 
   </snapshots> 
  </repository>
 </repositories>

If your Maven build is being accessed via Eclipse, then are your Eclipse preferences set up correctly? You may have installed a separate copy/version of Maven to the internal one supplied by Eclipse; are you using that by mistake? Check this here in your preferences:

Using the wrong one may mean that you’re using the wrong version of the global settings.xml.The fortunate thing is that you can confirm that your Eclipse settings are okay by taking a look at the exception message above. At the top of the message you’ll see:

DEBUG] Reading global settings from EMBEDDEDconfsettings.xml
[DEBUG] Reading user settings from C:UsersNosheen.m2settings.xml
[DEBUG] Using local repository at C:UsersNosheen.m2repository

From this, you can see that Nosheen is using the embedded Eclipse instance, taking the global settings.xml from EMBEDDEDconfsettings.xml and the user settings.xml from C:UsersNosheen.m2settings.xml. The local repository is at C:UsersNosheen.m2repository.If you still have problems, then check out the advice given in the links at the bottom of the exception:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Finally, there are the obvious things to check, like, have you spelled the name of the parent project correctly?

At home yes, but I was in a bit of a rush at work and forgot to do that
lol. I also just realized this machine was updated to maven3 at work.
Ok So I ran the clean install then re-ran the same command and received the
same error I received at home, on the work machine.

org.apache.maven.plugins:maven-archetype-plugin:
.2:generate (default-cli) on project spring-mvc-quickstart:
org.apache.maven.ar
hetype.exception.InvalidPackaging: Unable to add module to the current
project
s it is not of packaging type 'pom' -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal
rg.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli)
on pr
ject spring-mvc-quickstart:
org.apache.maven.archetype.exception.InvalidPackagi
g: Unable to add module to the current project as it is not of packaging
type '
om'
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto
.java:213)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto
.java:153)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto
.java:145)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj
ct(LifecycleModuleBuilder.java:84)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj
ct(LifecycleModuleBuilder.java:59)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedB
ild(LifecycleStarter.java:183)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecyc
eStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl
java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Lau
cher.java:290)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.ja
a:230)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(L
uncher.java:409)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java
352)
Caused by: org.apache.maven.plugin.MojoFailureException:
org.apache.maven.arche
ype.exception.InvalidPackaging: Unable to add module to the current project
as
t is not of packaging type 'pom'
        at
org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.exec
te(CreateProjectFromArchetypeMojo.java:211)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Defaul
BuildPluginManager.java:101)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto
.java:209)
        ... 19 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please re
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureEx
eption
C:devtestspring-mvc-quickstart-archetype-master>mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
05:51
28-0800)
Maven home: C:apache-maven-3.0.5
Java version: 1.7.0_10, vendor: Oracle Corporation
Java home: C:Program FilesJavajdk1.7.0_10jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
C:devtestspring-mvc-quickstart-archetype-master>

On Tue, Mar 18, 2014 at 4:06 PM, Rafal Borowiec notifications@github.comwrote:

> So, when you downloaded the code, did you run: mvn clean install to
> install the archetype in your local repository?
> 
> ## 
> 
> Reply to this email directly or view it on GitHubhttps://github.com/kolorobot/spring-mvc-quickstart-archetype/issues/50#issuecomment-38000145
> .
> 
> ```
> ```

Stack trace API

All internal errors thrown in V8 capture a stack trace when they are created. This stack trace can be accessed from JavaScript through the non-standard error.stack property. V8 also has various hooks for controlling how stack traces are collected and formatted, and for allowing custom errors to also collect stack traces. This document outlines V8’s JavaScript stack trace API.

Basic stack traces #

By default, almost all errors thrown by V8 have a stack property that holds the topmost 10 stack frames, formatted as a string. Here’s an example of a fully formatted stack trace:

The stack trace is collected when the error is created and is the same regardless of where or how many times the error is thrown. We collect 10 frames because it is usually enough to be useful but not so many that it has a noticeable negative performance impact. You can control how many stack frames are collected by setting the variable

Setting it to 0 disables stack trace collection. Any finite integer value can be used as the maximum number of frames to collect. Setting it to Infinity means that all frames get collected. This variable only affects the current context; it has to be set explicitly for each context that needs a different value. (Note that what is known as a “context” in V8 terminology corresponds to a page or in Google Chrome). To set a different default value that affects all contexts use the following V8 command-line flag:

To pass this flag to V8 when running Google Chrome, use:

Async stack traces #

The —async-stack-traces flag (turned on by default since V8 v7.3) enables the new zero-cost async stack traces, which enriches the stack property of Error instances with async stack frames, i.e. await locations in the code. These async frames are marked with async in the stack string:

At the time of this writing, this functionality is limited to await locations, Promise.all() and Promise.any() , since for those cases the engine can reconstruct the necessary information without any additional overhead (that’s why it’s zero-cost).

Stack trace collection for custom exceptions #

The stack trace mechanism used for built-in errors is implemented using a general stack trace collection API that is also available to user scripts. The function

adds a stack property to the given error object that yields the stack trace at the time captureStackTrace was called. Stack traces collected through Error.captureStackTrace are immediately collected, formatted, and attached to the given error object.

The optional constructorOpt parameter allows you to pass in a function value. When collecting the stack trace all frames above the topmost call to this function, including that call, are left out of the stack trace. This can be useful to hide implementation details that won’t be useful to the user. The usual way of defining a custom error that captures a stack trace would be:

Passing in MyError as a second argument means that the constructor call to MyError won’t show up in the stack trace.

Customizing stack traces #

Unlike Java where the stack trace of an exception is a structured value that allows inspection of the stack state, the stack property in V8 just holds a flat string containing the formatted stack trace. This is for no other reason than compatibility with other browsers. However, this is not hardcoded but only the default behavior and can be overridden by user scripts.

For efficiency stack traces are not formatted when they are captured but on demand, the first time the stack property is accessed. A stack trace is formatted by calling

and using whatever this call returns as the value of the stack property. If you assign a different function value to Error.prepareStackTrace that function is used to format stack traces. It gets passed the error object that it is preparing a stack trace for, as well as a structured representation of the stack. User stack trace formatters are free to format the stack trace however they want and even return non-string values. It is safe to retain references to the structured stack trace object after a call to prepareStackTrace completes so that it is also a valid return value. Note that the custom prepareStackTrace function is only called once the stack property of Error object is accessed.

The structured stack trace is an array of CallSite objects, each of which represents a stack frame. A CallSite object defines the following methods

• getThis : returns the value of this
• getTypeName : returns the type of this as a string. This is the name of the function stored in the constructor field of this , if available, otherwise the object’s [[Class]] internal property.
• getFunction : returns the current function
• getFunctionName : returns the name of the current function, typically its name property. If a name property is not available an attempt is made to infer a name from the function’s context.
• getMethodName : returns the name of the property of this or one of its prototypes that holds the current function
• getFileName : if this function was defined in a script returns the name of the script
• getLineNumber : if this function was defined in a script returns the current line number
• getColumnNumber : if this function was defined in a script returns the current column number
• getEvalOrigin : if this function was created using a call to eval returns a string representing the location where eval was called
• isToplevel : is this a top-level invocation, that is, is this the global object?
• isEval : does this call take place in code defined by a call to eval ?
• isNative : is this call in native V8 code?
• isConstructor : is this a constructor call?
• isAsync : is this an async call (i.e. await , Promise.all() , or Promise.any() )?
• isPromiseAll : is this an async call to Promise.all() ?
• isPromiseAny : is this an async call to Promise.any() ?
• getPromiseIndex : returns the index of the promise element that was followed in Promise.all() or Promise.any() for async stack traces, or null if the CallSite is not an async Promise.all() or Promise.any() call.

The default stack trace is created using the CallSite API so any information that is available there is also available through this API.

To maintain restrictions imposed on strict mode functions, frames that have a strict mode function and all frames below (its caller etc.) are not allow to access their receiver and function objects. For those frames, getFunction() and getThis() returns undefined .

Compatibility #

The API described here is specific to V8 and is not supported by any other JavaScript implementations. Most implementations do provide an error.stack property but the format of the stack trace is likely to be different from the format described here. The recommended use of this API is:

• Only rely on the layout of the formatted stack trace if you know your code is running in v8.
• It is safe to set Error.stackTraceLimit and Error.prepareStackTrace regardless of which implementation is running your code but be aware that it only has an effect if your code is running in V8.

Appendix: Stack trace format #

The default stack trace format used by V8 can for each stack frame give the following information:

• Whether the call is a construct call.
• The type of the this value ( Type ).
• The name of the function called ( functionName ).
• The name of the property of this or one of its prototypes that holds the function ( methodName ).
• The current location within the source ( location )

Any of these may be unavailable and different formats for stack frames are used depending on how much of this information is available. If all the above information is available a formatted stack frame looks like this:

Or, in the case of a construct call:

Or, in case of an async call:

If only one of functionName and methodName is available, or if they are both available but the same, the format is:

If neither is available is used as the name.

The Type value is the name of the function stored in the constructor field of this . In V8, all constructor calls set this property to the constructor function so unless this field has been actively changed after the object was created it, it holds the name of the function it was created by. If it is unavailable the [[Class]] property of the object is used.

One special case is the global object where the Type is not shown. In that case the stack frame is formatted as:

The location itself has several possible formats. Most common is the file name, line and column number within the script that defined the current function:

If the current function was created using eval the format is:

…where position is the full position where the call to eval occurred. Note that this means that positions can be nested if there are nested calls to eval , for instance:

If a stack frame is within V8’s libraries the location is:

…and if is unavailable, it’s:

Except as otherwise noted, any code samples from the V8 project are licensed under V8’s BSD-style license. Other content on this page is licensed under the Creative Commons Attribution 3.0 License. For details, see our site policies.

Источник

ztrue/tracerr

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Golang Errors with Stack Trace and Source Fragments

Tired of uninformative error output? Probably this will be more convenient:

Find more executable examples in examples dir.

Create New Error

Add Stack Trace to Existing Error

If err is nil then it still be nil with no stack trace added.

Print Error and Stack Trace

Stack trace will be printed only if err is of type tracerr.Error , otherwise just error text will be shown.

This will print error message and stack trace if any:

This will add source code:

It’s able to set up number of lines of code to display for each frame, which is 6 by default:

Or to set up number of lines before and after traced line:

The same, but with color, which is much more useful:

Save Output to Variable

It’s also able to save output to variable instead of printing it, which works the same way:

Get Stack Trace

Stack trace will be empty if err is not an instance of tracerr.Error .

Or if err is of type tracerr.Error :

Get Original Error

Unwrapped error will be nil if err is nil and will be the same error if err is not an instance of tracerr.Error .

Or if err is of type tracerr.Error :

Stack trace causes a performance overhead, depending on a stack trace depth. This can be insignificant in a number of situations (such as HTTP request handling), however, avoid of adding a stack trace for really hot spots where a high number of errors created frequently, this can be inefficient.

Benchmarks done on a MacBook Pro 2015 with go 1.11.

Benchmarks for creating a new error with a stack trace of different depth:

Источник

Node.js v19.4.0 documentation

Errors #

Applications running in Node.js will generally experience four categories of errors:

• Standard JavaScript errors such as , , , , , and .
• System errors triggered by underlying operating system constraints such as attempting to open a file that does not exist or attempting to send data over a closed socket.
• User-specified errors triggered by application code.
• AssertionError s are a special class of error that can be triggered when Node.js detects an exceptional logic violation that should never occur. These are raised typically by the node:assert module.

All JavaScript and system errors raised by Node.js inherit from, or are instances of, the standard JavaScript class and are guaranteed to provide at least the properties available on that class.

Error propagation and interception #

Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API that is called.

All JavaScript errors are handled as exceptions that immediately generate and throw an error using the standard JavaScript throw mechanism. These are handled using the try…catch construct provided by the JavaScript language.

Any use of the JavaScript throw mechanism will raise an exception that must be handled using try…catch or the Node.js process will exit immediately.

With few exceptions, Synchronous APIs (any blocking method that does not accept a callback function, such as fs.readFileSync ), will use throw to report errors.

Errors that occur within Asynchronous APIs may be reported in multiple ways:

Most asynchronous methods that accept a callback function will accept an Error object passed as the first argument to that function. If that first argument is not null and is an instance of Error , then an error occurred that should be handled.

When an asynchronous method is called on an object that is an EventEmitter , errors can be routed to that object’s ‘error’ event.

A handful of typically asynchronous methods in the Node.js API may still use the throw mechanism to raise exceptions that must be handled using try…catch . There is no comprehensive list of such methods; please refer to the documentation of each method to determine the appropriate error handling mechanism required.

The use of the ‘error’ event mechanism is most common for stream-based and event emitter-based APIs, which themselves represent a series of asynchronous operations over time (as opposed to a single operation that may pass or fail).

For all EventEmitter objects, if an ‘error’ event handler is not provided, the error will be thrown, causing the Node.js process to report an uncaught exception and crash unless either: The domain module is used appropriately or a handler has been registered for the ‘uncaughtException’ event.

Errors generated in this way cannot be intercepted using try…catch as they are thrown after the calling code has already exited.

Developers must refer to the documentation for each method to determine exactly how errors raised by those methods are propagated.

Error-first callbacks #

Most asynchronous methods exposed by the Node.js core API follow an idiomatic pattern referred to as an error-first callback. With this pattern, a callback function is passed to the method as an argument. When the operation either completes or an error is raised, the callback function is called with the Error object (if any) passed as the first argument. If no error was raised, the first argument will be passed as null .

The JavaScript try…catch mechanism cannot be used to intercept errors generated by asynchronous APIs. A common mistake for beginners is to try to use throw inside an error-first callback:

This will not work because the callback function passed to fs.readFile() is called asynchronously. By the time the callback has been called, the surrounding code, including the try…catch block, will have already exited. Throwing an error inside the callback can crash the Node.js process in most cases. If domains are enabled, or a handler has been registered with process.on(‘uncaughtException’) , such errors can be intercepted.

Class: Error #

A generic JavaScript object that does not denote any specific circumstance of why the error occurred. Error objects capture a «stack trace» detailing the point in the code at which the Error was instantiated, and may provide a text description of the error.

All errors generated by Node.js, including all system and JavaScript errors, will either be instances of, or inherit from, the Error class.

new Error(message[, options]) #

Creates a new Error object and sets the error.message property to the provided text message. If an object is passed as message , the text message is generated by calling String(message) . If the cause option is provided, it is assigned to the error.cause property. The error.stack property will represent the point in the code at which new Error() was called. Stack traces are dependent on V8’s stack trace API. Stack traces extend only to either (a) the beginning of synchronous code execution, or (b) the number of frames given by the property Error.stackTraceLimit , whichever is smaller.

Error.captureStackTrace(targetObject[, constructorOpt]) #

Creates a .stack property on targetObject , which when accessed returns a string representing the location in the code at which Error.captureStackTrace() was called.

The first line of the trace will be prefixed with $: $ .

The optional constructorOpt argument accepts a function. If given, all frames above constructorOpt , including constructorOpt , will be omitted from the generated stack trace.

The constructorOpt argument is useful for hiding implementation details of error generation from the user. For instance:

Error.stackTraceLimit #

The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj) ).

The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed.

If set to a non-number value, or set to a negative number, stack traces will not capture any frames.

error.cause #

If present, the error.cause property is the underlying cause of the Error . It is used when catching an error and throwing a new one with a different message or code in order to still have access to the original error.

The error.cause property is typically set by calling new Error(message, < cause >) . It is not set by the constructor if the cause option is not provided.

This property allows errors to be chained. When serializing Error objects, util.inspect() recursively serializes error.cause if it is set.

error.code #

The error.code property is a string label that identifies the kind of error. error.code is the most stable way to identify an error. It will only change between major versions of Node.js. In contrast, error.message strings may change between any versions of Node.js. See Node.js error codes for details about specific codes.

error.message #

The error.message property is the string description of the error as set by calling new Error(message) . The message passed to the constructor will also appear in the first line of the stack trace of the Error , however changing this property after the Error object is created may not change the first line of the stack trace (for example, when error.stack is read before this property is changed).

error.stack #

The error.stack property is a string describing the point in the code at which the Error was instantiated.

The first line is formatted as : , and is followed by a series of stack frames (each line beginning with «at «). Each frame describes a call site within the code that lead to the error being generated. V8 attempts to display a name for each function (by variable name, function name, or object method name), but occasionally it will not be able to find a suitable name. If V8 cannot determine a name for the function, only location information will be displayed for that frame. Otherwise, the determined function name will be displayed with location information appended in parentheses.

Frames are only generated for JavaScript functions. If, for example, execution synchronously passes through a C++ addon function called cheetahify which itself calls a JavaScript function, the frame representing the cheetahify call will not be present in the stack traces:

The location information will be one of:

• native , if the frame represents a call internal to V8 (as in [].forEach ).
• plain-filename.js:line:column , if the frame represents a call internal to Node.js.
• /absolute/path/to/file.js:line:column , if the frame represents a call in a user program (using CommonJS module system), or its dependencies.
• :///url/to/module/file.mjs:line:column , if the frame represents a call in a user program (using ES module system), or its dependencies.

The string representing the stack trace is lazily generated when the error.stack property is accessed.

The number of frames captured by the stack trace is bounded by the smaller of Error.stackTraceLimit or the number of available frames on the current event loop tick.

Class: AssertionError #

Indicates the failure of an assertion. For details, see Class: assert.AssertionError .

Class: RangeError #

Indicates that a provided argument was not within the set or range of acceptable values for a function; whether that is a numeric range, or outside the set of options for a given function parameter.

Node.js will generate and throw RangeError instances immediately as a form of argument validation.

Class: ReferenceError #

Indicates that an attempt is being made to access a variable that is not defined. Such errors commonly indicate typos in code, or an otherwise broken program.

While client code may generate and propagate these errors, in practice, only V8 will do so.

Unless an application is dynamically generating and running code, ReferenceError instances indicate a bug in the code or its dependencies.

Class: SyntaxError #

Indicates that a program is not valid JavaScript. These errors may only be generated and propagated as a result of code evaluation. Code evaluation may happen as a result of eval , Function , require , or vm. These errors are almost always indicative of a broken program.

SyntaxError instances are unrecoverable in the context that created them – they may only be caught by other contexts.

Class: SystemError #

Node.js generates system errors when exceptions occur within its runtime environment. These usually occur when an application violates an operating system constraint. For example, a system error will occur if an application attempts to read a file that does not exist.

• address If present, the address to which a network connection failed
• code The string error code
• dest If present, the file path destination when reporting a file system error
• errno The system-provided error number
• info If present, extra details about the error condition
• message A system-provided human-readable description of the error
• path If present, the file path when reporting a file system error
• port If present, the network connection port that is not available
• syscall The name of the system call that triggered the error

error.address #

If present, error.address is a string describing the address to which a network connection failed.

error.code #

The error.code property is a string representing the error code.

error.dest #

If present, error.dest is the file path destination when reporting a file system error.

error.errno #

The error.errno property is a negative number which corresponds to the error code defined in libuv Error handling .

On Windows the error number provided by the system will be normalized by libuv.

To get the string representation of the error code, use util.getSystemErrorName(error.errno) .

error.info #

If present, error.info is an object with details about the error condition.

error.message #

error.message is a system-provided human-readable description of the error.

error.path #

If present, error.path is a string containing a relevant invalid pathname.

error.port #

If present, error.port is the network connection port that is not available.

error.syscall #

The error.syscall property is a string describing the syscall that failed.

Common system errors #

This is a list of system errors commonly-encountered when writing a Node.js program. For a comprehensive list, see the errno (3) man page.

EACCES (Permission denied): An attempt was made to access a file in a way forbidden by its file access permissions.

EADDRINUSE (Address already in use): An attempt to bind a server ( net , http , or https ) to a local address failed due to another server on the local system already occupying that address.

ECONNREFUSED (Connection refused): No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.

ECONNRESET (Connection reset by peer): A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or reboot. Commonly encountered via the http and net modules.

EEXIST (File exists): An existing file was the target of an operation that required that the target not exist.

EISDIR (Is a directory): An operation expected a file, but the given pathname was a directory.

EMFILE (Too many open files in system): Maximum number of file descriptors allowable on the system has been reached, and requests for another descriptor cannot be fulfilled until at least one has been closed. This is encountered when opening many files at once in parallel, especially on systems (in particular, macOS) where there is a low file descriptor limit for processes. To remedy a low limit, run ulimit -n 2048 in the same shell that will run the Node.js process.

ENOENT (No such file or directory): Commonly raised by fs operations to indicate that a component of the specified pathname does not exist. No entity (file or directory) could be found by the given path.

ENOTDIR (Not a directory): A component of the given pathname existed, but was not a directory as expected. Commonly raised by fs.readdir .

ENOTEMPTY (Directory not empty): A directory with entries was the target of an operation that requires an empty directory, usually fs.unlink .

ENOTFOUND (DNS lookup failed): Indicates a DNS failure of either EAI_NODATA or EAI_NONAME . This is not a standard POSIX error.

EPERM (Operation not permitted): An attempt was made to perform an operation that requires elevated privileges.

EPIPE (Broken pipe): A write on a pipe, socket, or FIFO for which there is no process to read the data. Commonly encountered at the net and http layers, indicative that the remote side of the stream being written to has been closed.

ETIMEDOUT (Operation timed out): A connect or send request failed because the connected party did not properly respond after a period of time. Usually encountered by http or net . Often a sign that a socket.end() was not properly called.

Class: TypeError #

Indicates that a provided argument is not an allowable type. For example, passing a function to a parameter which expects a string would be a TypeError .

Node.js will generate and throw TypeError instances immediately as a form of argument validation.

Exceptions vs. errors #

A JavaScript exception is a value that is thrown as a result of an invalid operation or as the target of a throw statement. While it is not required that these values are instances of Error or classes which inherit from Error , all exceptions thrown by Node.js or the JavaScript runtime will be instances of Error .

Some exceptions are unrecoverable at the JavaScript layer. Such exceptions will always cause the Node.js process to crash. Examples include assert() checks or abort() calls in the C++ layer.

OpenSSL errors #

Errors originating in crypto or tls are of class Error , and in addition to the standard .code and .message properties, may have some additional OpenSSL-specific properties.

error.opensslErrorStack #

An array of errors that can give context to where in the OpenSSL library an error originates from.

error.function #

The OpenSSL function the error originates in.

error.library #

The OpenSSL library the error originates in.

error.reason #

A human-readable string describing the reason for the error.

Node.js error codes #

ABORT_ERR #

Used when an operation has been aborted (typically using an AbortController ).

APIs not using AbortSignal s typically do not raise an error with this code.

This code does not use the regular ERR_* convention Node.js errors use in order to be compatible with the web platform’s AbortError .

ERR_AMBIGUOUS_ARGUMENT #

A function argument is being used in a way that suggests that the function signature may be misunderstood. This is thrown by the node:assert module when the message parameter in assert.throws(block, message) matches the error message thrown by block because that usage suggests that the user believes message is the expected message rather than the message the AssertionError will display if block does not throw.

ERR_ARG_NOT_ITERABLE #

An iterable argument (i.e. a value that works with for. of loops) was required, but not provided to a Node.js API.

ERR_ASSERTION #

A special type of error that can be triggered whenever Node.js detects an exceptional logic violation that should never occur. These are raised typically by the node:assert module.

ERR_ASSERT_SNAPSHOT_NOT_SUPPORTED #

An attempt was made to use assert.snapshot() in an environment that does not support snapshots, such as the REPL, or when using node —eval .

ERR_ASYNC_CALLBACK #

An attempt was made to register something that is not a function as an AsyncHooks callback.

ERR_ASYNC_TYPE #

The type of an asynchronous resource was invalid. Users are also able to define their own types if using the public embedder API.

ERR_BROTLI_COMPRESSION_FAILED #

Data passed to a Brotli stream was not successfully compressed.

ERR_BROTLI_INVALID_PARAM #

An invalid parameter key was passed during construction of a Brotli stream.

ERR_BUFFER_CONTEXT_NOT_AVAILABLE #

An attempt was made to create a Node.js Buffer instance from addon or embedder code, while in a JS engine Context that is not associated with a Node.js instance. The data passed to the Buffer method will have been released by the time the method returns.

When encountering this error, a possible alternative to creating a Buffer instance is to create a normal Uint8Array , which only differs in the prototype of the resulting object. Uint8Array s are generally accepted in all Node.js core APIs where Buffer s are; they are available in all Contexts.

ERR_BUFFER_OUT_OF_BOUNDS #

An operation outside the bounds of a Buffer was attempted.

ERR_BUFFER_TOO_LARGE #

An attempt has been made to create a Buffer larger than the maximum allowed size.

ERR_CANNOT_WATCH_SIGINT #

Node.js was unable to watch for the SIGINT signal.

ERR_CHILD_CLOSED_BEFORE_REPLY #

A child process was closed before the parent received a reply.

ERR_CHILD_PROCESS_IPC_REQUIRED #

Used when a child process is being forked without specifying an IPC channel.

ERR_CHILD_PROCESS_STDIO_MAXBUFFER #

Used when the main process is trying to read data from the child process’s STDERR/STDOUT, and the data’s length is longer than the maxBuffer option.

ERR_CLOSED_MESSAGE_PORT #

There was an attempt to use a MessagePort instance in a closed state, usually after .close() has been called.

ERR_CONSOLE_WRITABLE_STREAM #

Console was instantiated without stdout stream, or Console has a non-writable stdout or stderr stream.

ERR_CONSTRUCT_CALL_INVALID #

A class constructor was called that is not callable.

ERR_CONSTRUCT_CALL_REQUIRED #

A constructor for a class was called without new .

ERR_CONTEXT_NOT_INITIALIZED #

The vm context passed into the API is not yet initialized. This could happen when an error occurs (and is caught) during the creation of the context, for example, when the allocation fails or the maximum call stack size is reached when the context is created.

ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED #

A client certificate engine was requested that is not supported by the version of OpenSSL being used.

ERR_CRYPTO_ECDH_INVALID_FORMAT #

An invalid value for the format argument was passed to the crypto.ECDH() class getPublicKey() method.

ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY #

An invalid value for the key argument has been passed to the crypto.ECDH() class computeSecret() method. It means that the public key lies outside of the elliptic curve.

ERR_CRYPTO_ENGINE_UNKNOWN #

An invalid crypto engine identifier was passed to require(‘node:crypto’).setEngine() .

ERR_CRYPTO_FIPS_FORCED #

The —force-fips command-line argument was used but there was an attempt to enable or disable FIPS mode in the node:crypto module.

ERR_CRYPTO_FIPS_UNAVAILABLE #

An attempt was made to enable or disable FIPS mode, but FIPS mode was not available.

ERR_CRYPTO_HASH_FINALIZED #

hash.digest() was called multiple times. The hash.digest() method must be called no more than one time per instance of a Hash object.

ERR_CRYPTO_HASH_UPDATE_FAILED #

hash.update() failed for any reason. This should rarely, if ever, happen.

ERR_CRYPTO_INCOMPATIBLE_KEY #

The given crypto keys are incompatible with the attempted operation.

ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS #

The selected public or private key encoding is incompatible with other options.

ERR_CRYPTO_INITIALIZATION_FAILED #

Initialization of the crypto subsystem failed.

ERR_CRYPTO_INVALID_AUTH_TAG #

An invalid authentication tag was provided.

ERR_CRYPTO_INVALID_COUNTER #

An invalid counter was provided for a counter-mode cipher.

ERR_CRYPTO_INVALID_CURVE #

An invalid elliptic-curve was provided.

ERR_CRYPTO_INVALID_DIGEST #

An invalid crypto digest algorithm was specified.

ERR_CRYPTO_INVALID_IV #

An invalid initialization vector was provided.

ERR_CRYPTO_INVALID_JWK #

An invalid JSON Web Key was provided.

ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE #

The given crypto key object’s type is invalid for the attempted operation.

ERR_CRYPTO_INVALID_KEYLEN #

An invalid key length was provided.

ERR_CRYPTO_INVALID_KEYPAIR #

An invalid key pair was provided.

ERR_CRYPTO_INVALID_KEYTYPE #

An invalid key type was provided.

ERR_CRYPTO_INVALID_MESSAGELEN #

An invalid message length was provided.

ERR_CRYPTO_INVALID_SCRYPT_PARAMS #

Invalid scrypt algorithm parameters were provided.

ERR_CRYPTO_INVALID_STATE #

A crypto method was used on an object that was in an invalid state. For instance, calling cipher.getAuthTag() before calling cipher.final() .

ERR_CRYPTO_INVALID_TAG_LENGTH #

An invalid authentication tag length was provided.

ERR_CRYPTO_JOB_INIT_FAILED #

Initialization of an asynchronous crypto operation failed.

ERR_CRYPTO_JWK_UNSUPPORTED_CURVE #

Key’s Elliptic Curve is not registered for use in the JSON Web Key Elliptic Curve Registry.

ERR_CRYPTO_JWK_UNSUPPORTED_KEY_TYPE #

Key’s Asymmetric Key Type is not registered for use in the JSON Web Key Types Registry.

ERR_CRYPTO_OPERATION_FAILED #

A crypto operation failed for an otherwise unspecified reason.

ERR_CRYPTO_PBKDF2_ERROR #

The PBKDF2 algorithm failed for unspecified reasons. OpenSSL does not provide more details and therefore neither does Node.js.

ERR_CRYPTO_SCRYPT_INVALID_PARAMETER #

One or more crypto.scrypt() or crypto.scryptSync() parameters are outside their legal range.

ERR_CRYPTO_SCRYPT_NOT_SUPPORTED #

Node.js was compiled without scrypt support. Not possible with the official release binaries but can happen with custom builds, including distro builds.

ERR_CRYPTO_SIGN_KEY_REQUIRED #

A signing key was not provided to the sign.sign() method.

ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH #

crypto.timingSafeEqual() was called with Buffer , TypedArray , or DataView arguments of different lengths.

ERR_CRYPTO_UNKNOWN_CIPHER #

An unknown cipher was specified.

ERR_CRYPTO_UNKNOWN_DH_GROUP #

An unknown Diffie-Hellman group name was given. See crypto.getDiffieHellman() for a list of valid group names.

ERR_CRYPTO_UNSUPPORTED_OPERATION #

An attempt to invoke an unsupported crypto operation was made.

ERR_DEBUGGER_ERROR #

An error occurred with the debugger.

ERR_DEBUGGER_STARTUP_ERROR #

The debugger timed out waiting for the required host/port to be free.

ERR_DLOPEN_DISABLED #

Loading native addons has been disabled using —no-addons .

ERR_DLOPEN_FAILED #

A call to process.dlopen() failed.

ERR_DIR_CLOSED #

The fs.Dir was previously closed.

ERR_DIR_CONCURRENT_OPERATION #

A synchronous read or close call was attempted on an fs.Dir which has ongoing asynchronous operations.

ERR_DNS_SET_SERVERS_FAILED #

c-ares failed to set the DNS server.

ERR_DOMAIN_CALLBACK_NOT_AVAILABLE #

The node:domain module was not usable since it could not establish the required error handling hooks, because process.setUncaughtExceptionCaptureCallback() had been called at an earlier point in time.

ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE #

process.setUncaughtExceptionCaptureCallback() could not be called because the node:domain module has been loaded at an earlier point in time.

The stack trace is extended to include the point in time at which the node:domain module had been loaded.

ERR_DUPLICATE_STARTUP_SNAPSHOT_MAIN_FUNCTION #

v8.startupSnapshot.setDeserializeMainFunction() could not be called because it had already been called before.

ERR_ENCODING_INVALID_ENCODED_DATA #

Data provided to TextDecoder() API was invalid according to the encoding provided.

ERR_ENCODING_NOT_SUPPORTED #

Encoding provided to TextDecoder() API was not one of the WHATWG Supported Encodings.

ERR_EVAL_ESM_CANNOT_PRINT #

—print cannot be used with ESM input.

ERR_EVENT_RECURSION #

Thrown when an attempt is made to recursively dispatch an event on EventTarget .

ERR_EXECUTION_ENVIRONMENT_NOT_AVAILABLE #

The JS execution context is not associated with a Node.js environment. This may occur when Node.js is used as an embedded library and some hooks for the JS engine are not set up properly.

ERR_FALSY_VALUE_REJECTION #

A Promise that was callbackified via util.callbackify() was rejected with a falsy value.

ERR_FEATURE_UNAVAILABLE_ON_PLATFORM #

Used when a feature that is not available to the current platform which is running Node.js is used.

ERR_FS_CP_DIR_TO_NON_DIR #

An attempt was made to copy a directory to a non-directory (file, symlink, etc.) using fs.cp() .

ERR_FS_CP_EEXIST #

An attempt was made to copy over a file that already existed with fs.cp() , with the force and errorOnExist set to true .

ERR_FS_CP_EINVAL #

When using fs.cp() , src or dest pointed to an invalid path.

ERR_HTTP_CONTENT_LENGTH_MISMATCH #

Response body size doesn’t match with the specified content-length header value.

ERR_FS_CP_FIFO_PIPE #

An attempt was made to copy a named pipe with fs.cp() .

ERR_FS_CP_NON_DIR_TO_DIR #

An attempt was made to copy a non-directory (file, symlink, etc.) to a directory using fs.cp() .

ERR_FS_CP_SOCKET #

An attempt was made to copy to a socket with fs.cp() .

ERR_FS_CP_SYMLINK_TO_SUBDIRECTORY #

When using fs.cp() , a symlink in dest pointed to a subdirectory of src .

ERR_FS_CP_UNKNOWN #

An attempt was made to copy to an unknown file type with fs.cp() .

ERR_FS_EISDIR #

Path is a directory.

ERR_FS_FILE_TOO_LARGE #

An attempt has been made to read a file whose size is larger than the maximum allowed size for a Buffer .

ERR_FS_INVALID_SYMLINK_TYPE #

An invalid symlink type was passed to the fs.symlink() or fs.symlinkSync() methods.

ERR_HTTP_HEADERS_SENT #

An attempt was made to add more headers after the headers had already been sent.

ERR_HTTP_INVALID_HEADER_VALUE #

An invalid HTTP header value was specified.

ERR_HTTP_INVALID_STATUS_CODE #

Status code was outside the regular status code range (100-999).

ERR_HTTP_REQUEST_TIMEOUT #

The client has not sent the entire request within the allowed time.

ERR_HTTP_SOCKET_ENCODING #

Changing the socket encoding is not allowed per RFC 7230 Section 3.

ERR_HTTP_TRAILER_INVALID #

The Trailer header was set even though the transfer encoding does not support that.

ERR_HTTP2_ALTSVC_INVALID_ORIGIN #

HTTP/2 ALTSVC frames require a valid origin.

ERR_HTTP2_ALTSVC_LENGTH #

HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes.

ERR_HTTP2_CONNECT_AUTHORITY #

For HTTP/2 requests using the CONNECT method, the :authority pseudo-header is required.

ERR_HTTP2_CONNECT_PATH #

For HTTP/2 requests using the CONNECT method, the :path pseudo-header is forbidden.

ERR_HTTP2_CONNECT_SCHEME #

For HTTP/2 requests using the CONNECT method, the :scheme pseudo-header is forbidden.

ERR_HTTP2_ERROR #

A non-specific HTTP/2 error has occurred.

ERR_HTTP2_GOAWAY_SESSION #

New HTTP/2 Streams may not be opened after the Http2Session has received a GOAWAY frame from the connected peer.

ERR_HTTP2_HEADER_SINGLE_VALUE #

Multiple values were provided for an HTTP/2 header field that was required to have only a single value.

ERR_HTTP2_HEADERS_AFTER_RESPOND #

An additional headers was specified after an HTTP/2 response was initiated.

ERR_HTTP2_HEADERS_SENT #

An attempt was made to send multiple response headers.

ERR_HTTP2_INFO_STATUS_NOT_ALLOWED #

Informational HTTP status codes ( 1xx ) may not be set as the response status code on HTTP/2 responses.

ERR_HTTP2_INVALID_CONNECTION_HEADERS #

HTTP/1 connection specific headers are forbidden to be used in HTTP/2 requests and responses.

ERR_HTTP2_INVALID_HEADER_VALUE #

An invalid HTTP/2 header value was specified.

ERR_HTTP2_INVALID_INFO_STATUS #

An invalid HTTP informational status code has been specified. Informational status codes must be an integer between 100 and 199 (inclusive).

ERR_HTTP2_INVALID_ORIGIN #

HTTP/2 ORIGIN frames require a valid origin.

ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH #

Input Buffer and Uint8Array instances passed to the http2.getUnpackedSettings() API must have a length that is a multiple of six.

ERR_HTTP2_INVALID_PSEUDOHEADER #

Only valid HTTP/2 pseudoheaders ( :status , :path , :authority , :scheme , and :method ) may be used.

ERR_HTTP2_INVALID_SESSION #

An action was performed on an Http2Session object that had already been destroyed.

ERR_HTTP2_INVALID_SETTING_VALUE #

An invalid value has been specified for an HTTP/2 setting.

ERR_HTTP2_INVALID_STREAM #

An operation was performed on a stream that had already been destroyed.

ERR_HTTP2_MAX_PENDING_SETTINGS_ACK #

Whenever an HTTP/2 SETTINGS frame is sent to a connected peer, the peer is required to send an acknowledgment that it has received and applied the new SETTINGS . By default, a maximum number of unacknowledged SETTINGS frames may be sent at any given time. This error code is used when that limit has been reached.

ERR_HTTP2_NESTED_PUSH #

An attempt was made to initiate a new push stream from within a push stream. Nested push streams are not permitted.

ERR_HTTP2_NO_MEM #

Out of memory when using the http2session.setLocalWindowSize(windowSize) API.

ERR_HTTP2_NO_SOCKET_MANIPULATION #

An attempt was made to directly manipulate (read, write, pause, resume, etc.) a socket attached to an Http2Session .

ERR_HTTP2_ORIGIN_LENGTH #

HTTP/2 ORIGIN frames are limited to a length of 16382 bytes.

ERR_HTTP2_OUT_OF_STREAMS #

The number of streams created on a single HTTP/2 session reached the maximum limit.

ERR_HTTP2_PAYLOAD_FORBIDDEN #

A message payload was specified for an HTTP response code for which a payload is forbidden.

ERR_HTTP2_PING_CANCEL #

An HTTP/2 ping was canceled.

ERR_HTTP2_PING_LENGTH #

HTTP/2 ping payloads must be exactly 8 bytes in length.

ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED #

An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header key names that begin with the : prefix.

ERR_HTTP2_PUSH_DISABLED #

An attempt was made to create a push stream, which had been disabled by the client.

ERR_HTTP2_SEND_FILE #

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send a directory.

ERR_HTTP2_SEND_FILE_NOSEEK #

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send something other than a regular file, but offset or length options were provided.

ERR_HTTP2_SESSION_ERROR #

The Http2Session closed with a non-zero error code.

ERR_HTTP2_SETTINGS_CANCEL #

The Http2Session settings canceled.

ERR_HTTP2_SOCKET_BOUND #

An attempt was made to connect a Http2Session object to a net.Socket or tls.TLSSocket that had already been bound to another Http2Session object.

ERR_HTTP2_SOCKET_UNBOUND #

An attempt was made to use the socket property of an Http2Session that has already been closed.

ERR_HTTP2_STATUS_101 #

Use of the 101 Informational status code is forbidden in HTTP/2.

ERR_HTTP2_STATUS_INVALID #

An invalid HTTP status code has been specified. Status codes must be an integer between 100 and 599 (inclusive).

ERR_HTTP2_STREAM_CANCEL #

An Http2Stream was destroyed before any data was transmitted to the connected peer.

ERR_HTTP2_STREAM_ERROR #

A non-zero error code was been specified in an RST_STREAM frame.

ERR_HTTP2_STREAM_SELF_DEPENDENCY #

When setting the priority for an HTTP/2 stream, the stream may be marked as a dependency for a parent stream. This error code is used when an attempt is made to mark a stream and dependent of itself.

ERR_HTTP2_TOO_MANY_INVALID_FRAMES #

The limit of acceptable invalid HTTP/2 protocol frames sent by the peer, as specified through the maxSessionInvalidFrames option, has been exceeded.

ERR_HTTP2_TRAILERS_ALREADY_SENT #

Trailing headers have already been sent on the Http2Stream .

ERR_HTTP2_TRAILERS_NOT_READY #

The http2stream.sendTrailers() method cannot be called until after the ‘wantTrailers’ event is emitted on an Http2Stream object. The ‘wantTrailers’ event will only be emitted if the waitForTrailers option is set for the Http2Stream .

ERR_HTTP2_UNSUPPORTED_PROTOCOL #

http2.connect() was passed a URL that uses any protocol other than http: or https: .

ERR_ILLEGAL_CONSTRUCTOR #

An attempt was made to construct an object using a non-public constructor.

ERR_IMPORT_ASSERTION_TYPE_FAILED #

An import assertion has failed, preventing the specified module to be imported.

ERR_IMPORT_ASSERTION_TYPE_MISSING #

An import assertion is missing, preventing the specified module to be imported.

ERR_IMPORT_ASSERTION_TYPE_UNSUPPORTED #

An import assertion is not supported by this version of Node.js.

ERR_INCOMPATIBLE_OPTION_PAIR #

An option pair is incompatible with each other and cannot be used at the same time.

ERR_INPUT_TYPE_NOT_ALLOWED #

The —input-type flag was used to attempt to execute a file. This flag can only be used with input via —eval , —print , or STDIN .

ERR_INSPECTOR_ALREADY_ACTIVATED #

While using the node:inspector module, an attempt was made to activate the inspector when it already started to listen on a port. Use inspector.close() before activating it on a different address.

ERR_INSPECTOR_ALREADY_CONNECTED #

While using the node:inspector module, an attempt was made to connect when the inspector was already connected.

ERR_INSPECTOR_CLOSED #

While using the node:inspector module, an attempt was made to use the inspector after the session had already closed.

ERR_INSPECTOR_COMMAND #

An error occurred while issuing a command via the node:inspector module.

ERR_INSPECTOR_NOT_ACTIVE #

The inspector is not active when inspector.waitForDebugger() is called.

ERR_INSPECTOR_NOT_AVAILABLE #

The node:inspector module is not available for use.

ERR_INSPECTOR_NOT_CONNECTED #

While using the node:inspector module, an attempt was made to use the inspector before it was connected.

ERR_INSPECTOR_NOT_WORKER #

An API was called on the main thread that can only be used from the worker thread.

ERR_INTERNAL_ASSERTION #

There was a bug in Node.js or incorrect usage of Node.js internals. To fix the error, open an issue at https://github.com/nodejs/node/issues.

ERR_INVALID_ADDRESS_FAMILY #

The provided address family is not understood by the Node.js API.

ERR_INVALID_ARG_TYPE #

An argument of the wrong type was passed to a Node.js API.

ERR_INVALID_ARG_VALUE #

An invalid or unsupported value was passed for a given argument.

ERR_INVALID_ASYNC_ID #

An invalid asyncId or triggerAsyncId was passed using AsyncHooks . An id less than -1 should never happen.

ERR_INVALID_BUFFER_SIZE #

A swap was performed on a Buffer but its size was not compatible with the operation.

ERR_INVALID_CHAR #

Invalid characters were detected in headers.

ERR_INVALID_CURSOR_POS #

A cursor on a given stream cannot be moved to a specified row without a specified column.

ERR_INVALID_FD #

A file descriptor (‘fd’) was not valid (e.g. it was a negative value).

ERR_INVALID_FD_TYPE #

A file descriptor (‘fd’) type was not valid.

ERR_INVALID_FILE_URL_HOST #

A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible host. This situation can only occur on Unix-like systems where only localhost or an empty host is supported.

ERR_INVALID_FILE_URL_PATH #

A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible path. The exact semantics for determining whether a path can be used is platform-dependent.

ERR_INVALID_HANDLE_TYPE #

An attempt was made to send an unsupported «handle» over an IPC communication channel to a child process. See subprocess.send() and process.send() for more information.

ERR_INVALID_HTTP_TOKEN #

An invalid HTTP token was supplied.

ERR_INVALID_IP_ADDRESS #

An IP address is not valid.

ERR_INVALID_MIME_SYNTAX #

The syntax of a MIME is not valid.

ERR_INVALID_MODULE #

An attempt was made to load a module that does not exist or was otherwise not valid.

ERR_INVALID_MODULE_SPECIFIER #

The imported module string is an invalid URL, package name, or package subpath specifier.

ERR_INVALID_OBJECT_DEFINE_PROPERTY #

An error occurred while setting an invalid attribute on the property of an object.

ERR_INVALID_PACKAGE_CONFIG #

An invalid package.json file failed parsing.

ERR_INVALID_PACKAGE_TARGET #

The package.json «exports» field contains an invalid target mapping value for the attempted module resolution.

ERR_INVALID_PERFORMANCE_MARK #

While using the Performance Timing API ( perf_hooks ), a performance mark is invalid.

ERR_INVALID_PROTOCOL #

An invalid options.protocol was passed to http.request() .

ERR_INVALID_REPL_EVAL_CONFIG #

Both breakEvalOnSigint and eval options were set in the REPL config, which is not supported.

ERR_INVALID_REPL_INPUT #

The input may not be used in the REPL . The conditions under which this error is used are described in the REPL documentation.

ERR_INVALID_RETURN_PROPERTY #

Thrown in case a function option does not provide a valid value for one of its returned object properties on execution.

ERR_INVALID_RETURN_PROPERTY_VALUE #

Thrown in case a function option does not provide an expected value type for one of its returned object properties on execution.

ERR_INVALID_RETURN_VALUE #

Thrown in case a function option does not return an expected value type on execution, such as when a function is expected to return a promise.

ERR_INVALID_STATE #

Indicates that an operation cannot be completed due to an invalid state. For instance, an object may have already been destroyed, or may be performing another operation.

ERR_INVALID_SYNC_FORK_INPUT #

A Buffer , TypedArray , DataView , or string was provided as stdio input to an asynchronous fork. See the documentation for the child_process module for more information.

ERR_INVALID_THIS #

A Node.js API function was called with an incompatible this value.

ERR_INVALID_TRANSFER_OBJECT #

An invalid transfer object was passed to postMessage() .

ERR_INVALID_TUPLE #

An element in the iterable provided to the WHATWG URLSearchParams constructor did not represent a [name, value] tuple – that is, if an element is not iterable, or does not consist of exactly two elements.

ERR_INVALID_URI #

An invalid URI was passed.

ERR_INVALID_URL #

An invalid URL was passed to the WHATWG URL constructor or the legacy url.parse() to be parsed. The thrown error object typically has an additional property ‘input’ that contains the URL that failed to parse.

ERR_INVALID_URL_SCHEME #

An attempt was made to use a URL of an incompatible scheme (protocol) for a specific purpose. It is only used in the WHATWG URL API support in the fs module (which only accepts URLs with ‘file’ scheme), but may be used in other Node.js APIs as well in the future.

ERR_IPC_CHANNEL_CLOSED #

An attempt was made to use an IPC communication channel that was already closed.

ERR_IPC_DISCONNECTED #

An attempt was made to disconnect an IPC communication channel that was already disconnected. See the documentation for the child_process module for more information.

ERR_IPC_ONE_PIPE #

An attempt was made to create a child Node.js process using more than one IPC communication channel. See the documentation for the child_process module for more information.

ERR_IPC_SYNC_FORK #

An attempt was made to open an IPC communication channel with a synchronously forked Node.js process. See the documentation for the child_process module for more information.

ERR_LOADER_CHAIN_INCOMPLETE #

An ESM loader hook returned without calling next() and without explicitly signaling a short circuit.

ERR_MANIFEST_ASSERT_INTEGRITY #

An attempt was made to load a resource, but the resource did not match the integrity defined by the policy manifest. See the documentation for policy manifests for more information.

ERR_MANIFEST_DEPENDENCY_MISSING #

An attempt was made to load a resource, but the resource was not listed as a dependency from the location that attempted to load it. See the documentation for policy manifests for more information.

ERR_MANIFEST_INTEGRITY_MISMATCH #

An attempt was made to load a policy manifest, but the manifest had multiple entries for a resource which did not match each other. Update the manifest entries to match in order to resolve this error. See the documentation for policy manifests for more information.

ERR_MANIFEST_INVALID_RESOURCE_FIELD #

A policy manifest resource had an invalid value for one of its fields. Update the manifest entry to match in order to resolve this error. See the documentation for policy manifests for more information.

ERR_MANIFEST_INVALID_SPECIFIER #

A policy manifest resource had an invalid value for one of its dependency mappings. Update the manifest entry to match to resolve this error. See the documentation for policy manifests for more information.

ERR_MANIFEST_PARSE_POLICY #

An attempt was made to load a policy manifest, but the manifest was unable to be parsed. See the documentation for policy manifests for more information.

ERR_MANIFEST_TDZ #

An attempt was made to read from a policy manifest, but the manifest initialization has not yet taken place. This is likely a bug in Node.js.

ERR_MANIFEST_UNKNOWN_ONERROR #

A policy manifest was loaded, but had an unknown value for its «onerror» behavior. See the documentation for policy manifests for more information.

ERR_MEMORY_ALLOCATION_FAILED #

An attempt was made to allocate memory (usually in the C++ layer) but it failed.

ERR_MESSAGE_TARGET_CONTEXT_UNAVAILABLE #

A message posted to a MessagePort could not be deserialized in the target vm Context . Not all Node.js objects can be successfully instantiated in any context at this time, and attempting to transfer them using postMessage() can fail on the receiving side in that case.

ERR_METHOD_NOT_IMPLEMENTED #

A method is required but not implemented.

ERR_MISSING_ARGS #

A required argument of a Node.js API was not passed. This is only used for strict compliance with the API specification (which in some cases may accept func(undefined) but not func() ). In most native Node.js APIs, func(undefined) and func() are treated identically, and the ERR_INVALID_ARG_TYPE error code may be used instead.

ERR_MISSING_OPTION #

For APIs that accept options objects, some options might be mandatory. This code is thrown if a required option is missing.

ERR_MISSING_PASSPHRASE #

An attempt was made to read an encrypted key without specifying a passphrase.

ERR_MISSING_PLATFORM_FOR_WORKER #

The V8 platform used by this instance of Node.js does not support creating Workers. This is caused by lack of embedder support for Workers. In particular, this error will not occur with standard builds of Node.js.

ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LIST #

An object that needs to be explicitly listed in the transferList argument is in the object passed to a postMessage() call, but is not provided in the transferList for that call. Usually, this is a MessagePort .

In Node.js versions prior to v15.0.0, the error code being used here was ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST . However, the set of transferable object types has been expanded to cover more types than MessagePort .

ERR_MODULE_NOT_FOUND #

A module file could not be resolved by the ECMAScript modules loader while attempting an import operation or when loading the program entry point.

ERR_MULTIPLE_CALLBACK #

A callback was called more than once.

A callback is almost always meant to only be called once as the query can either be fulfilled or rejected but not both at the same time. The latter would be possible by calling a callback more than once.

ERR_NAPI_CONS_FUNCTION #

While using Node-API , a constructor passed was not a function.

ERR_NAPI_INVALID_DATAVIEW_ARGS #

While calling napi_create_dataview() , a given offset was outside the bounds of the dataview or offset + length was larger than a length of given buffer .

ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT #

While calling napi_create_typedarray() , the provided offset was not a multiple of the element size.

ERR_NAPI_INVALID_TYPEDARRAY_LENGTH #

While calling napi_create_typedarray() , (length * size_of_element) + byte_offset was larger than the length of given buffer .

ERR_NAPI_TSFN_CALL_JS #

An error occurred while invoking the JavaScript portion of the thread-safe function.

ERR_NAPI_TSFN_GET_UNDEFINED #

An error occurred while attempting to retrieve the JavaScript undefined value.

ERR_NAPI_TSFN_START_IDLE_LOOP #

On the main thread, values are removed from the queue associated with the thread-safe function in an idle loop. This error indicates that an error has occurred when attempting to start the loop.

ERR_NAPI_TSFN_STOP_IDLE_LOOP #

Once no more items are left in the queue, the idle loop must be suspended. This error indicates that the idle loop has failed to stop.

ERR_NOT_BUILDING_SNAPSHOT #

An attempt was made to use operations that can only be used when building V8 startup snapshot even though Node.js isn’t building one.

ERR_NO_CRYPTO #

An attempt was made to use crypto features while Node.js was not compiled with OpenSSL crypto support.

ERR_NO_ICU #

An attempt was made to use features that require ICU, but Node.js was not compiled with ICU support.

ERR_NON_CONTEXT_AWARE_DISABLED #

A non-context-aware native addon was loaded in a process that disallows them.

ERR_OUT_OF_RANGE #

A given value is out of the accepted range.

ERR_PACKAGE_IMPORT_NOT_DEFINED #

The package.json «imports» field does not define the given internal package specifier mapping.

ERR_PACKAGE_PATH_NOT_EXPORTED #

The package.json «exports» field does not export the requested subpath. Because exports are encapsulated, private internal modules that are not exported cannot be imported through the package resolution, unless using an absolute URL.

ERR_PARSE_ARGS_INVALID_OPTION_VALUE #

When strict set to true , thrown by util.parseArgs() if a value is provided for an option of type , or if a value is provided for an option of type .

ERR_PARSE_ARGS_UNEXPECTED_POSITIONAL #

Thrown by util.parseArgs() , when a positional argument is provided and allowPositionals is set to false .

ERR_PARSE_ARGS_UNKNOWN_OPTION #

When strict set to true , thrown by util.parseArgs() if an argument is not configured in options .

ERR_PERFORMANCE_INVALID_TIMESTAMP #

An invalid timestamp value was provided for a performance mark or measure.

ERR_PERFORMANCE_MEASURE_INVALID_OPTIONS #

Invalid options were provided for a performance measure.

ERR_PROTO_ACCESS #

Accessing Object.prototype.__proto__ has been forbidden using —disable-proto=throw . Object.getPrototypeOf and Object.setPrototypeOf should be used to get and set the prototype of an object.

ERR_REQUIRE_ESM #

An attempt was made to require() an ES Module.

ERR_SCRIPT_EXECUTION_INTERRUPTED #

Script execution was interrupted by SIGINT (For example, Ctrl + C was pressed.)

ERR_SCRIPT_EXECUTION_TIMEOUT #

Script execution timed out, possibly due to bugs in the script being executed.

ERR_SERVER_ALREADY_LISTEN #

The server.listen() method was called while a net.Server was already listening. This applies to all instances of net.Server , including HTTP, HTTPS, and HTTP/2 Server instances.

ERR_SERVER_NOT_RUNNING #

The server.close() method was called when a net.Server was not running. This applies to all instances of net.Server , including HTTP, HTTPS, and HTTP/2 Server instances.

ERR_SOCKET_ALREADY_BOUND #

An attempt was made to bind a socket that has already been bound.

ERR_SOCKET_BAD_BUFFER_SIZE #

An invalid (negative) size was passed for either the recvBufferSize or sendBufferSize options in dgram.createSocket() .

ERR_SOCKET_BAD_PORT #

An API function expecting a port >= 0 and ERR_SOCKET_BAD_TYPE #

An API function expecting a socket type ( udp4 or udp6 ) received an invalid value.

ERR_SOCKET_BUFFER_SIZE #

While using dgram.createSocket() , the size of the receive or send Buffer could not be determined.

ERR_SOCKET_CLOSED #

An attempt was made to operate on an already closed socket.

ERR_SOCKET_CLOSED_BEFORE_CONNECTION #

When calling net.Socket.write() on a connecting socket and the socket was closed before the connection was established.

ERR_SOCKET_DGRAM_IS_CONNECTED #

A dgram.connect() call was made on an already connected socket.

ERR_SOCKET_DGRAM_NOT_CONNECTED #

A dgram.disconnect() or dgram.remoteAddress() call was made on a disconnected socket.

ERR_SOCKET_DGRAM_NOT_RUNNING #

A call was made and the UDP subsystem was not running.

ERR_SRI_PARSE #

A string was provided for a Subresource Integrity check, but was unable to be parsed. Check the format of integrity attributes by looking at the Subresource Integrity specification.

ERR_STREAM_ALREADY_FINISHED #

A stream method was called that cannot complete because the stream was finished.

ERR_STREAM_CANNOT_PIPE #

An attempt was made to call stream.pipe() on a Writable stream.

ERR_STREAM_DESTROYED #

A stream method was called that cannot complete because the stream was destroyed using stream.destroy() .

ERR_STREAM_NULL_VALUES #

An attempt was made to call stream.write() with a null chunk.

ERR_STREAM_PREMATURE_CLOSE #

An error returned by stream.finished() and stream.pipeline() , when a stream or a pipeline ends non gracefully with no explicit error.

ERR_STREAM_PUSH_AFTER_EOF #

An attempt was made to call stream.push() after a null (EOF) had been pushed to the stream.

ERR_STREAM_UNSHIFT_AFTER_END_EVENT #

An attempt was made to call stream.unshift() after the ‘end’ event was emitted.

ERR_STREAM_WRAP #

Prevents an abort if a string decoder was set on the Socket or if the decoder is in objectMode .

ERR_STREAM_WRITE_AFTER_END #

An attempt was made to call stream.write() after stream.end() has been called.

ERR_STRING_TOO_LONG #

An attempt has been made to create a string longer than the maximum allowed length.

ERR_SYNTHETIC #

An artificial error object used to capture the call stack for diagnostic reports.

ERR_SYSTEM_ERROR #

An unspecified or non-specific system error has occurred within the Node.js process. The error object will have an err.info object property with additional details.

ERR_TAP_LEXER_ERROR #

An error representing a failing lexer state.

ERR_TAP_PARSER_ERROR #

An error representing a failing parser state. Additional information about the token causing the error is available via the cause property.

ERR_TAP_VALIDATION_ERROR #

This error represents a failed TAP validation.

ERR_TEST_FAILURE #

This error represents a failed test. Additional information about the failure is available via the cause property. The failureType property specifies what the test was doing when the failure occurred.

ERR_TLS_CERT_ALTNAME_FORMAT #

This error is thrown by checkServerIdentity if a user-supplied subjectaltname property violates encoding rules. Certificate objects produced by Node.js itself always comply with encoding rules and will never cause this error.

ERR_TLS_CERT_ALTNAME_INVALID #

While using TLS, the host name/IP of the peer did not match any of the subjectAltNames in its certificate.

ERR_TLS_DH_PARAM_SIZE #

While using TLS, the parameter offered for the Diffie-Hellman ( DH ) key-agreement protocol is too small. By default, the key length must be greater than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly recommended to use 2048 bits or larger for stronger security.

ERR_TLS_HANDSHAKE_TIMEOUT #

A TLS/SSL handshake timed out. In this case, the server must also abort the connection.

ERR_TLS_INVALID_CONTEXT #

The context must be a SecureContext .

ERR_TLS_INVALID_PROTOCOL_METHOD #

The specified secureProtocol method is invalid. It is either unknown, or disabled because it is insecure.

ERR_TLS_INVALID_PROTOCOL_VERSION #

Valid TLS protocol versions are ‘TLSv1’ , ‘TLSv1.1’ , or ‘TLSv1.2’ .

ERR_TLS_INVALID_STATE #

The TLS socket must be connected and securely established. Ensure the ‘secure’ event is emitted before continuing.

ERR_TLS_PROTOCOL_VERSION_CONFLICT #

Attempting to set a TLS protocol minVersion or maxVersion conflicts with an attempt to set the secureProtocol explicitly. Use one mechanism or the other.

ERR_TLS_PSK_SET_IDENTIY_HINT_FAILED #

Failed to set PSK identity hint. Hint may be too long.

ERR_TLS_RENEGOTIATION_DISABLED #

An attempt was made to renegotiate TLS on a socket instance with TLS disabled.

ERR_TLS_REQUIRED_SERVER_NAME #

While using TLS, the server.addContext() method was called without providing a host name in the first parameter.

ERR_TLS_SESSION_ATTACK #

An excessive amount of TLS renegotiations is detected, which is a potential vector for denial-of-service attacks.

ERR_TLS_SNI_FROM_SERVER #

An attempt was made to issue Server Name Indication from a TLS server-side socket, which is only valid from a client.

ERR_TRACE_EVENTS_CATEGORY_REQUIRED #

The trace_events.createTracing() method requires at least one trace event category.

ERR_TRACE_EVENTS_UNAVAILABLE #

The node:trace_events module could not be loaded because Node.js was compiled with the —without-v8-platform flag.

ERR_TRANSFORM_ALREADY_TRANSFORMING #

A Transform stream finished while it was still transforming.

ERR_TRANSFORM_WITH_LENGTH_0 #

A Transform stream finished with data still in the write buffer.

ERR_TTY_INIT_FAILED #

The initialization of a TTY failed due to a system error.

ERR_UNAVAILABLE_DURING_EXIT #

Function was called within a process.on(‘exit’) handler that shouldn’t be called within process.on(‘exit’) handler.

ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET #

process.setUncaughtExceptionCaptureCallback() was called twice, without first resetting the callback to null .

This error is designed to prevent accidentally overwriting a callback registered from another module.

ERR_UNESCAPED_CHARACTERS #

A string that contained unescaped characters was received.

ERR_UNHANDLED_ERROR #

An unhandled error occurred (for instance, when an ‘error’ event is emitted by an EventEmitter but an ‘error’ handler is not registered).

ERR_UNKNOWN_BUILTIN_MODULE #

Used to identify a specific kind of internal Node.js error that should not typically be triggered by user code. Instances of this error point to an internal bug within the Node.js binary itself.

ERR_UNKNOWN_CREDENTIAL #

A Unix group or user identifier that does not exist was passed.

ERR_UNKNOWN_ENCODING #

An invalid or unknown encoding option was passed to an API.

ERR_UNKNOWN_FILE_EXTENSION #

An attempt was made to load a module with an unknown or unsupported file extension.

ERR_UNKNOWN_MODULE_FORMAT #

An attempt was made to load a module with an unknown or unsupported format.

ERR_UNKNOWN_SIGNAL #

An invalid or unknown process signal was passed to an API expecting a valid signal (such as subprocess.kill() ).

ERR_UNSUPPORTED_DIR_IMPORT #

import a directory URL is unsupported. Instead, self-reference a package using its name and define a custom subpath in the «exports» field of the package.json file.

ERR_UNSUPPORTED_ESM_URL_SCHEME #

import with URL schemes other than file and data is unsupported.

ERR_USE_AFTER_CLOSE #

An attempt was made to use something that was already closed.

ERR_VALID_PERFORMANCE_ENTRY_TYPE #

While using the Performance Timing API ( perf_hooks ), no valid performance entry types are found.

ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING #

A dynamic import callback was not specified.

ERR_VM_MODULE_ALREADY_LINKED #

The module attempted to be linked is not eligible for linking, because of one of the following reasons:

• It has already been linked ( linkingStatus is ‘linked’ )
• It is being linked ( linkingStatus is ‘linking’ )
• Linking has failed for this module ( linkingStatus is ‘errored’ )

ERR_VM_MODULE_CACHED_DATA_REJECTED #

The cachedData option passed to a module constructor is invalid.

ERR_VM_MODULE_CANNOT_CREATE_CACHED_DATA #

Cached data cannot be created for modules which have already been evaluated.

ERR_VM_MODULE_DIFFERENT_CONTEXT #

The module being returned from the linker function is from a different context than the parent module. Linked modules must share the same context.

ERR_VM_MODULE_LINK_FAILURE #

The module was unable to be linked due to a failure.

ERR_VM_MODULE_NOT_MODULE #

The fulfilled value of a linking promise is not a vm.Module object.

ERR_VM_MODULE_STATUS #

The current module’s status does not allow for this operation. The specific meaning of the error depends on the specific function.

ERR_WASI_ALREADY_STARTED #

The WASI instance has already started.

ERR_WASI_NOT_STARTED #

The WASI instance has not been started.

ERR_WEBASSEMBLY_RESPONSE #

The Response that has been passed to WebAssembly.compileStreaming or to WebAssembly.instantiateStreaming is not a valid WebAssembly response.

ERR_WORKER_INIT_FAILED #

The Worker initialization failed.

ERR_WORKER_INVALID_EXEC_ARGV #

The execArgv option passed to the Worker constructor contains invalid flags.

ERR_WORKER_NOT_RUNNING #

An operation failed because the Worker instance is not currently running.

ERR_WORKER_OUT_OF_MEMORY #

The Worker instance terminated because it reached its memory limit.

ERR_WORKER_PATH #

The path for the main script of a worker is neither an absolute path nor a relative path starting with ./ or ../ .

ERR_WORKER_UNSERIALIZABLE_ERROR #

All attempts at serializing an uncaught exception from a worker thread failed.

ERR_WORKER_UNSUPPORTED_OPERATION #

The requested functionality is not supported in worker threads.

ERR_ZLIB_INITIALIZATION_FAILED #

Creation of a zlib object failed due to incorrect configuration.

HPE_HEADER_OVERFLOW #

History

Max header size in http_parser was set to 8 KiB.

Too much HTTP header data was received. In order to protect against malicious or malconfigured clients, if more than 8 KiB of HTTP header data is received then HTTP parsing will abort without a request or response object being created, and an Error with this code will be emitted.

HPE_UNEXPECTED_CONTENT_LENGTH #

Server is sending both a Content-Length header and Transfer-Encoding: chunked .

Transfer-Encoding: chunked allows the server to maintain an HTTP persistent connection for dynamically generated content. In this case, the Content-Length HTTP header cannot be used.

Use Content-Length or Transfer-Encoding: chunked .

MODULE_NOT_FOUND #

History

Added requireStack property.

A module file could not be resolved by the CommonJS modules loader while attempting a require() operation or when loading the program entry point.

Legacy Node.js error codes #

ERR_CANNOT_TRANSFER_OBJECT #

The value passed to postMessage() contained an object that is not supported for transferring.

ERR_CRYPTO_HASH_DIGEST_NO_UTF16 #

The UTF-16 encoding was used with hash.digest() . While the hash.digest() method does allow an encoding argument to be passed in, causing the method to return a string rather than a Buffer , the UTF-16 encoding (e.g. ucs or utf16le ) is not supported.

ERR_HTTP2_FRAME_ERROR #

Used when a failure occurs sending an individual frame on the HTTP/2 session.

ERR_HTTP2_HEADERS_OBJECT #

Used when an HTTP/2 Headers Object is expected.

ERR_HTTP2_HEADER_REQUIRED #

Used when a required header is missing in an HTTP/2 message.

ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND #

HTTP/2 informational headers must only be sent prior to calling the Http2Stream.prototype.respond() method.

ERR_HTTP2_STREAM_CLOSED #

Used when an action has been performed on an HTTP/2 Stream that has already been closed.

ERR_HTTP_INVALID_CHAR #

Used when an invalid character is found in an HTTP response status message (reason phrase).

ERR_INDEX_OUT_OF_RANGE #

A given index was out of the accepted range (e.g. negative offsets).

ERR_INVALID_OPT_VALUE #

An invalid or unexpected value was passed in an options object.

ERR_INVALID_OPT_VALUE_ENCODING #

An invalid or unknown file encoding was passed.

ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST #

This error code was replaced by ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LIST in Node.js v15.0.0, because it is no longer accurate as other types of transferable objects also exist now.

ERR_NAPI_CONS_PROTOTYPE_OBJECT #

Used by the Node-API when Constructor.prototype is not an object.

ERR_NETWORK_IMPORT_BAD_RESPONSE #

Response was received but was invalid when importing a module over the network.

ERR_NETWORK_IMPORT_DISALLOWED #

A network module attempted to load another module that it is not allowed to load. Likely this restriction is for security reasons.

ERR_NO_LONGER_SUPPORTED #

A Node.js API was called in an unsupported manner, such as Buffer.write(string, encoding, offset[, length]) .

ERR_OPERATION_FAILED #

An operation failed. This is typically used to signal the general failure of an asynchronous operation.

ERR_OUTOFMEMORY #

Used generically to identify that an operation caused an out of memory condition.

ERR_PARSE_HISTORY_DATA #

The node:repl module was unable to parse data from the REPL history file.

ERR_SOCKET_CANNOT_SEND #

Data could not be sent on a socket.

ERR_STDERR_CLOSE #

History

Rather than emitting an error, process.stderr.end() now only closes the stream side but not the underlying resource, making this error obsolete.

Removed in: v10.12.0

An attempt was made to close the process.stderr stream. By design, Node.js does not allow stdout or stderr streams to be closed by user code.

ERR_STDOUT_CLOSE #

History

Rather than emitting an error, process.stderr.end() now only closes the stream side but not the underlying resource, making this error obsolete.

Removed in: v10.12.0

An attempt was made to close the process.stdout stream. By design, Node.js does not allow stdout or stderr streams to be closed by user code.

ERR_STREAM_READ_NOT_IMPLEMENTED #

Used when an attempt is made to use a readable stream that has not implemented readable._read() .

ERR_TLS_RENEGOTIATION_FAILED #

Used when a TLS renegotiation request has failed in a non-specific way.

ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER #

A SharedArrayBuffer whose memory is not managed by the JavaScript engine or by Node.js was encountered during serialization. Such a SharedArrayBuffer cannot be serialized.

This can only happen when native addons create SharedArrayBuffer s in «externalized» mode, or put existing SharedArrayBuffer into externalized mode.

ERR_UNKNOWN_STDIN_TYPE #

An attempt was made to launch a Node.js process with an unknown stdin file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

ERR_UNKNOWN_STREAM_TYPE #

An attempt was made to launch a Node.js process with an unknown stdout or stderr file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

ERR_V8BREAKITERATOR #

The V8 BreakIterator API was used but the full ICU data set is not installed.

ERR_VALUE_OUT_OF_RANGE #

Used when a given value is out of the accepted range.

ERR_VM_MODULE_NOT_LINKED #

The module must be successfully linked before instantiation.

ERR_VM_MODULE_LINKING_ERRORED #

The linker function returned a module for which linking has failed.

ERR_WORKER_UNSUPPORTED_EXTENSION #

The pathname used for the main script of a worker has an unknown file extension.

ERR_ZLIB_BINDING_CLOSED #

Used when an attempt is made to use a zlib object after it has already been closed.

Источник

Adblock
detector

All internal errors thrown in V8 capture a stack trace when they are created. This stack trace can be accessed from JavaScript through the non-standard error.stack property. V8 also has various hooks for controlling how stack traces are collected and formatted, and for allowing custom errors to also collect stack traces. This document outlines V8’s JavaScript stack trace API.

Basic stack traces #

By default, almost all errors thrown by V8 have a stack property that holds the topmost 10 stack frames, formatted as a string. Here’s an example of a fully formatted stack trace:

ReferenceError: FAIL is not defined
   at Constraint.execute (deltablue.js:525:2)
   at Constraint.recalculate (deltablue.js:424:21)
   at Planner.addPropagate (deltablue.js:701:6)
   at Constraint.satisfy (deltablue.js:184:15)
   at Planner.incrementalAdd (deltablue.js:591:21)
   at Constraint.addConstraint (deltablue.js:162:10)
   at Constraint.BinaryConstraint (deltablue.js:346:7)
   at Constraint.EqualityConstraint (deltablue.js:515:38)
   at chainTest (deltablue.js:807:6)
   at deltaBlue (deltablue.js:879:2)

The stack trace is collected when the error is created and is the same regardless of where or how many times the error is thrown. We collect 10 frames because it is usually enough to be useful but not so many that it has a noticeable negative performance impact. You can control how many stack frames are collected by setting the variable

Error.stackTraceLimit

Setting it to 0 disables stack trace collection. Any finite integer value can be used as the maximum number of frames to collect. Setting it to Infinity means that all frames get collected. This variable only affects the current context; it has to be set explicitly for each context that needs a different value. (Note that what is known as a “context” in V8 terminology corresponds to a page or <iframe> in Google Chrome). To set a different default value that affects all contexts use the following V8 command-line flag:

--stack-trace-limit <value>

To pass this flag to V8 when running Google Chrome, use:

--js-flags='--stack-trace-limit <value>'

Async stack traces #

The --async-stack-traces flag (turned on by default since V8 v7.3) enables the new zero-cost async stack traces, which enriches the stack property of Error instances with async stack frames, i.e. await locations in the code. These async frames are marked with async in the stack string:

ReferenceError: FAIL is not defined
    at bar (<anonymous>)
    at async foo (<anonymous>)

At the time of this writing, this functionality is limited to await locations, Promise.all() and Promise.any(), since for those cases the engine can reconstruct the necessary information without any additional overhead (that’s why it’s zero-cost).

Stack trace collection for custom exceptions #

The stack trace mechanism used for built-in errors is implemented using a general stack trace collection API that is also available to user scripts. The function

Error.captureStackTrace(error, constructorOpt)

adds a stack property to the given error object that yields the stack trace at the time captureStackTrace was called. Stack traces collected through Error.captureStackTrace are immediately collected, formatted, and attached to the given error object.

The optional constructorOpt parameter allows you to pass in a function value. When collecting the stack trace all frames above the topmost call to this function, including that call, are left out of the stack trace. This can be useful to hide implementation details that won’t be useful to the user. The usual way of defining a custom error that captures a stack trace would be:

function MyError() {
  Error.captureStackTrace(this, MyError);
  // Any other initialization goes here.
}

Passing in MyError as a second argument means that the constructor call to MyError won’t show up in the stack trace.

Customizing stack traces #

Unlike Java where the stack trace of an exception is a structured value that allows inspection of the stack state, the stack property in V8 just holds a flat string containing the formatted stack trace. This is for no other reason than compatibility with other browsers. However, this is not hardcoded but only the default behavior and can be overridden by user scripts.

For efficiency stack traces are not formatted when they are captured but on demand, the first time the stack property is accessed. A stack trace is formatted by calling

Error.prepareStackTrace(error, structuredStackTrace)

and using whatever this call returns as the value of the stack property. If you assign a different function value to Error.prepareStackTrace that function is used to format stack traces. It gets passed the error object that it is preparing a stack trace for, as well as a structured representation of the stack. User stack trace formatters are free to format the stack trace however they want and even return non-string values. It is safe to retain references to the structured stack trace object after a call to prepareStackTrace completes so that it is also a valid return value. Note that the custom prepareStackTrace function is only called once the stack property of Error object is accessed.

The structured stack trace is an array of CallSite objects, each of which represents a stack frame. A CallSite object defines the following methods

• getThis: returns the value of this
• getTypeName: returns the type of this as a string. This is the name of the function stored in the constructor field of this, if available, otherwise the object’s [[Class]] internal property.
• getFunction: returns the current function
• getFunctionName: returns the name of the current function, typically its name property. If a name property is not available an attempt is made to infer a name from the function’s context.
• getMethodName: returns the name of the property of this or one of its prototypes that holds the current function
• getFileName: if this function was defined in a script returns the name of the script
• getLineNumber: if this function was defined in a script returns the current line number
• getColumnNumber: if this function was defined in a script returns the current column number
• getEvalOrigin: if this function was created using a call to eval returns a string representing the location where eval was called
• isToplevel: is this a top-level invocation, that is, is this the global object?
• isEval: does this call take place in code defined by a call to eval?
• isNative: is this call in native V8 code?
• isConstructor: is this a constructor call?
• isAsync: is this an async call (i.e. await, Promise.all(), or Promise.any())?
• isPromiseAll: is this an async call to Promise.all()?
• isPromiseAny: is this an async call to Promise.any()?
• getPromiseIndex: returns the index of the promise element that was followed in Promise.all() or Promise.any() for async stack traces, or null if the CallSite is not an async Promise.all() or Promise.any() call.

The default stack trace is created using the CallSite API so any information that is available there is also available through this API.

To maintain restrictions imposed on strict mode functions, frames that have a strict mode function and all frames below (its caller etc.) are not allow to access their receiver and function objects. For those frames, getFunction() and getThis() returns undefined.

Compatibility #

The API described here is specific to V8 and is not supported by any other JavaScript implementations. Most implementations do provide an error.stack property but the format of the stack trace is likely to be different from the format described here. The recommended use of this API is:

• Only rely on the layout of the formatted stack trace if you know your code is running in v8.
• It is safe to set Error.stackTraceLimit and Error.prepareStackTrace regardless of which implementation is running your code but be aware that it only has an effect if your code is running in V8.

Appendix: Stack trace format #

The default stack trace format used by V8 can for each stack frame give the following information:

• Whether the call is a construct call.
• The type of the this value (Type).
• The name of the function called (functionName).
• The name of the property of this or one of its prototypes that holds the function (methodName).
• The current location within the source (location)

Any of these may be unavailable and different formats for stack frames are used depending on how much of this information is available. If all the above information is available a formatted stack frame looks like this:

at Type.functionName [as methodName] (location)

Or, in the case of a construct call:

at new functionName (location)

Or, in case of an async call:

at async functionName (location)

If only one of functionName and methodName is available, or if they are both available but the same, the format is:

at Type.name (location)

If neither is available <anonymous> is used as the name.

The Type value is the name of the function stored in the constructor field of this. In V8, all constructor calls set this property to the constructor function so unless this field has been actively changed after the object was created it, it holds the name of the function it was created by. If it is unavailable the [[Class]] property of the object is used.

One special case is the global object where the Type is not shown. In that case the stack frame is formatted as:

at functionName [as methodName] (location)

The location itself has several possible formats. Most common is the file name, line and column number within the script that defined the current function:

fileName:lineNumber:columnNumber

If the current function was created using eval the format is:

eval at position

…where position is the full position where the call to eval occurred. Note that this means that positions can be nested if there are nested calls to eval, for instance:

eval at Foo.a (eval at Bar.z (myscript.js:10:3))

If a stack frame is within V8’s libraries the location is:

native

…and if is unavailable, it’s:

unknown location

Thank you so much for the quick response. Answer to your questions.

1) I am using maven 3.3.9

2) there is no network issues. I am able to open the urls from the browser

3) All are not working

4) dump is below

C:workVRO>mvn -e -X archetype:generate -DarchetypeCatalog=https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -DrepoUrl=https://15.218.171.196:8281/vco-repo -Dmaven.repo.remote=https://15.218.171.196:8281/vco-repo -Dmave

.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30)

Maven home: C:optapache-maven-3.3.9

Java version: 1.7.0_21, vendor: Oracle Corporation

Java home: C:optJavajdk1.7.0_45jre

Default locale: en_US, platform encoding: Cp1252

OS name: «windows server 2012», version: «6.2», arch: «x86», family: «windows»

[DEBUG] Created new class realm maven.api

[DEBUG] Importing foreign packages into class realm maven.api

[DEBUG]   Imported: javax.enterprise.inject.* < plexus.core

[DEBUG]   Imported: javax.enterprise.util.* < plexus.core

[DEBUG]   Imported: javax.inject.* < plexus.core

[DEBUG]   Imported: org.apache.maven.* < plexus.core

[DEBUG]   Imported: org.apache.maven.artifact < plexus.core

[DEBUG]   Imported: org.apache.maven.classrealm < plexus.core

[DEBUG]   Imported: org.apache.maven.cli < plexus.core

[DEBUG]   Imported: org.apache.maven.configuration < plexus.core

[DEBUG]   Imported: org.apache.maven.exception < plexus.core

[DEBUG]   Imported: org.apache.maven.execution < plexus.core

[DEBUG]   Imported: org.apache.maven.execution.scope < plexus.core

[DEBUG]   Imported: org.apache.maven.lifecycle < plexus.core

[DEBUG]   Imported: org.apache.maven.model < plexus.core

[DEBUG]   Imported: org.apache.maven.monitor < plexus.core

[DEBUG]   Imported: org.apache.maven.plugin < plexus.core

[DEBUG]   Imported: org.apache.maven.profiles < plexus.core

[DEBUG]   Imported: org.apache.maven.project < plexus.core

[DEBUG]   Imported: org.apache.maven.reporting < plexus.core

[DEBUG]   Imported: org.apache.maven.repository < plexus.core

[DEBUG]   Imported: org.apache.maven.rtinfo < plexus.core

[DEBUG]   Imported: org.apache.maven.settings < plexus.core

[DEBUG]   Imported: org.apache.maven.toolchain < plexus.core

[DEBUG]   Imported: org.apache.maven.usability < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.* < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.authentication < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.authorization < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.events < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.observers < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.proxy < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.repository < plexus.core

[DEBUG]   Imported: org.apache.maven.wagon.resource < plexus.core

[DEBUG]   Imported: org.codehaus.classworlds < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.* < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.classworlds < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.component < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.configuration < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.container < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.context < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.lifecycle < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.logging < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.personality < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core

[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core

[DEBUG]   Imported: org.eclipse.aether.* < plexus.core

[DEBUG]   Imported: org.eclipse.aether.artifact < plexus.core

[DEBUG]   Imported: org.eclipse.aether.collection < plexus.core

[DEBUG]   Imported: org.eclipse.aether.deployment < plexus.core

[DEBUG]   Imported: org.eclipse.aether.graph < plexus.core

[DEBUG]   Imported: org.eclipse.aether.impl < plexus.core

[DEBUG]   Imported: org.eclipse.aether.installation < plexus.core

[DEBUG]   Imported: org.eclipse.aether.internal.impl < plexus.core

[DEBUG]   Imported: org.eclipse.aether.metadata < plexus.core

[DEBUG]   Imported: org.eclipse.aether.repository < plexus.core

[DEBUG]   Imported: org.eclipse.aether.resolution < plexus.core

[DEBUG]   Imported: org.eclipse.aether.spi < plexus.core

[DEBUG]   Imported: org.eclipse.aether.transfer < plexus.core

[DEBUG]   Imported: org.eclipse.aether.version < plexus.core

[DEBUG]   Imported: org.slf4j.* < plexus.core

[DEBUG]   Imported: org.slf4j.helpers.* < plexus.core

[DEBUG]   Imported: org.slf4j.spi.* < plexus.core

[DEBUG] Populating class realm maven.api

[INFO] Error stacktraces are turned on.

[DEBUG] Reading global settings from C:optapache-maven-3.3.9confsettings.xml

[DEBUG] Reading user settings from C:UsersAdministrator.m2settings.xml

[DEBUG] Reading global toolchains from C:optapache-maven-3.3.9conftoolchains.xml

[DEBUG] Reading user toolchains from C:UsersAdministrator.m2toolchains.xml

[DEBUG] Using local repository at C:UsersAdministrator.m2repository

[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for C:UsersAdministrator.m2repository

[INFO] Scanning for projects…

[DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1: (none)

[DEBUG] Looking up lifecyle mappings for packaging pom from ClassRealm[plexus.core, parent: null]

[DEBUG] Resolving plugin prefix archetype from [org.apache.maven.plugins, org.codehaus.mojo]

[DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.apache.maven.plugins/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.codehaus.mojo/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Resolved plugin prefix archetype to org.apache.maven.plugins:maven-archetype-plugin from repository central

[DEBUG] Resolving plugin version for org.apache.maven.plugins:maven-archetype-plugin

[DEBUG] Could not find metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Resolved plugin version for org.apache.maven.plugins:maven-archetype-plugin to 2.4 from repository central (https://repo.maven.apache.org/maven2, default, releases)

[DEBUG] === REACTOR BUILD PLAN ================================================

[DEBUG] Project: org.apache.maven:standalone-pom:pom:1

[DEBUG] Tasks:   [archetype:generate]

[DEBUG] Style:   Aggregating

[DEBUG] =======================================================================

[INFO]

[INFO] ————————————————————————

[INFO] Building Maven Stub Project (No POM) 1

[INFO] ————————————————————————

[DEBUG] Resolving plugin prefix archetype from [org.apache.maven.plugins, org.codehaus.mojo]

[DEBUG] Could not find metadata org.apache.maven.plugins/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.apache.maven.plugins/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.codehaus.mojo/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Resolved plugin prefix archetype to org.apache.maven.plugins:maven-archetype-plugin from repository central

[DEBUG] Resolving plugin version for org.apache.maven.plugins:maven-archetype-plugin

[DEBUG] Could not find metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml in local (C:UsersAdministrator.m2repository)

[DEBUG] Skipped remote request for org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml, locally cached metadata up-to-date.

[DEBUG] Resolved plugin version for org.apache.maven.plugins:maven-archetype-plugin to 2.4 from repository central (https://repo.maven.apache.org/maven2, default, releases)

[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process

test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]

[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]

[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]

[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process

test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]

[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]

[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]

[DEBUG] === PROJECT BUILD PLAN ================================================

[DEBUG] Project:       org.apache.maven:standalone-pom:1

[DEBUG] Dependencies (collect): []

[DEBUG] Dependencies (resolve): []

[DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]

[DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]

[DEBUG] — init fork of org.apache.maven:standalone-pom:1 for org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) —

[DEBUG] Dependencies (collect): []

[DEBUG] Dependencies (resolve): []

[DEBUG] — exit fork of org.apache.maven:standalone-pom:1 for org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) —

[DEBUG] ————————————————————————

[DEBUG] Goal:          org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli)

[DEBUG] Style:         Regular

[DEBUG] Configuration: <?xml version=»1.0″ encoding=»UTF-8″?>

<configuration>

  <archetypeArtifactId>${archetypeArtifactId}</archetypeArtifactId>

  <archetypeCatalog default-value=»remote,local»>${archetypeCatalog}</archetypeCatalog>

  <archetypeGroupId>${archetypeGroupId}</archetypeGroupId>

  <archetypeRepository>${archetypeRepository}</archetypeRepository>

  <archetypeVersion>${archetypeVersion}</archetypeVersion>

  <basedir default-value=»${basedir}»/>

  <filter>${filter}</filter>

  <goals>${goals}</goals>

  <interactiveMode default-value=»${settings.interactiveMode}»>${interactiveMode}</interactiveMode>

  <localRepository default-value=»${localRepository}»/>

  <remoteArtifactRepositories default-value=»${project.remoteArtifactRepositories}»/>

  <session default-value=»${session}»/>

</configuration>

[DEBUG] =======================================================================

[INFO]

[INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > generate-sources @ standalone-pom >>>

[INFO]

[INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < generate-sources @ standalone-pom <<<

[INFO]

[INFO] — maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom —

[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=0, ConflictMarker.markTime=0, ConflictMarker.nodeCount=134, ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0, ConflictIdSorter.conflictIdCount=60, Confl

ctIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=15, ConflictResolver.conflictItemCount=125, DefaultDependencyCollector.collectTime=313, DefaultDependencyCollector.transformTime=15}

[DEBUG] org.apache.maven.plugins:maven-archetype-plugin:jar:2.4:

[DEBUG]    org.apache.maven.archetype:archetype-catalog:jar:2.4:compile

[DEBUG]    org.apache.maven.archetype:archetype-descriptor:jar:2.4:compile

[DEBUG]    org.apache.maven.archetype:archetype-registry:jar:2.4:compile

[DEBUG]    org.apache.maven.archetype:archetype-common:jar:2.4:compile

[DEBUG]       net.sourceforge.jchardet:jchardet:jar:1.0:compile

[DEBUG]       org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:compile

[DEBUG]       dom4j:dom4j:jar:1.6.1:compile

[DEBUG]          xml-apis:xml-apis:jar:1.0.b2:compile

[DEBUG]       jdom:jdom:jar:1.0:compile

[DEBUG]       org.apache.maven:maven-model:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-project:jar:2.2.1:compile

[DEBUG]          org.apache.maven:maven-plugin-registry:jar:2.2.1:compile

[DEBUG]          org.codehaus.plexus:plexus-interpolation:jar:1.11:compile

[DEBUG]       org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile

[DEBUG]          junit:junit:jar:4.11:test

[DEBUG]             org.hamcrest:hamcrest-core:jar:1.3:test

[DEBUG]       org.codehaus.plexus:plexus-velocity:jar:1.1.8:compile

[DEBUG]       org.apache.velocity:velocity:jar:1.5:compile

[DEBUG]          commons-lang:commons-lang:jar:2.1:compile

[DEBUG]          oro:oro:jar:2.0.8:compile

[DEBUG]    org.codehaus.plexus:plexus-utils:jar:3.0.21:compile

[DEBUG]    commons-io:commons-io:jar:2.2:compile

[DEBUG]    org.apache.maven:maven-plugin-api:jar:2.2.1:compile

[DEBUG]    org.apache.maven:maven-core:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-settings:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile

[DEBUG]       org.slf4j:slf4j-jdk14:jar:1.5.6:runtime

[DEBUG]          org.slf4j:slf4j-api:jar:1.5.6:runtime

[DEBUG]       org.slf4j:jcl-over-slf4j:jar:1.5.6:runtime

[DEBUG]       org.apache.maven.reporting:maven-reporting-api:jar:2.2.1:compile

[DEBUG]          org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile

[DEBUG]          org.apache.maven.doxia:doxia-logging-api:jar:1.1:compile

[DEBUG]       org.apache.maven:maven-profile:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-artifact:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-repository-metadata:jar:2.2.1:compile

[DEBUG]       org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile

[DEBUG]       commons-cli:commons-cli:jar:1.2:compile

[DEBUG]       org.apache.maven:maven-plugin-descriptor:jar:2.2.1:compile

[DEBUG]       org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-6:compile

[DEBUG]          org.codehaus.plexus:plexus-component-api:jar:1.0-alpha-16:compile

[DEBUG]             org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-7:compile

[DEBUG]       org.apache.maven:maven-artifact-manager:jar:2.2.1:compile

[DEBUG]          backport-util-concurrent:backport-util-concurrent:jar:3.1:compile

[DEBUG]       org.apache.maven:maven-monitor:jar:2.2.1:compile

[DEBUG]       classworlds:classworlds:jar:1.1:compile

[DEBUG]       org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile

[DEBUG]          org.sonatype.plexus:plexus-cipher:jar:1.4:compile

[DEBUG]    org.apache.maven.shared:maven-invoker:jar:2.1.1:compile

[DEBUG]    commons-collections:commons-collections:jar:3.2.1:compile

[DEBUG]    org.codehaus.groovy:groovy:jar:1.8.3:compile

[DEBUG]       antlr:antlr:jar:2.7.7:compile

[DEBUG]       asm:asm:jar:3.2:compile

[DEBUG]       asm:asm-commons:jar:3.2:compile

[DEBUG]       asm:asm-util:jar:3.2:compile

[DEBUG]       asm:asm-analysis:jar:3.2:compile

[DEBUG]       asm:asm-tree:jar:3.2:compile

[DEBUG]    org.beanshell:bsh:jar:2.0b4:compile

[DEBUG]    org.apache.maven.shared:maven-script-interpreter:jar:1.0:compile

[DEBUG]       org.apache.ant:ant:jar:1.8.1:compile

[DEBUG] Created new class realm plugin>org.apache.maven.plugins:maven-archetype-plugin:2.4

[DEBUG] Importing foreign packages into class realm plugin>org.apache.maven.plugins:maven-archetype-plugin:2.4

[DEBUG]   Imported:  < maven.api

[DEBUG] Populating class realm plugin>org.apache.maven.plugins:maven-archetype-plugin:2.4

[DEBUG]   Included: org.apache.maven.plugins:maven-archetype-plugin:jar:2.4

[DEBUG]   Included: org.apache.maven.archetype:archetype-catalog:jar:2.4

[DEBUG]   Included: org.apache.maven.archetype:archetype-descriptor:jar:2.4

[DEBUG]   Included: org.apache.maven.archetype:archetype-registry:jar:2.4

[DEBUG]   Included: org.apache.maven.archetype:archetype-common:jar:2.4

[DEBUG]   Included: net.sourceforge.jchardet:jchardet:jar:1.0

[DEBUG]   Included: org.codehaus.plexus:plexus-component-annotations:jar:1.5.5

[DEBUG]   Included: dom4j:dom4j:jar:1.6.1

[DEBUG]   Included: xml-apis:xml-apis:jar:1.0.b2

[DEBUG]   Included: jdom:jdom:jar:1.0

[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.11

[DEBUG]   Included: org.codehaus.plexus:plexus-velocity:jar:1.1.8

[DEBUG]   Included: org.apache.velocity:velocity:jar:1.5

[DEBUG]   Included: commons-lang:commons-lang:jar:2.1

[DEBUG]   Included: oro:oro:jar:2.0.8

[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0.21

[DEBUG]   Included: commons-io:commons-io:jar:2.2

[DEBUG]   Included: org.slf4j:slf4j-jdk14:jar:1.5.6

[DEBUG]   Included: org.slf4j:jcl-over-slf4j:jar:1.5.6

[DEBUG]   Included: org.apache.maven.reporting:maven-reporting-api:jar:2.2.1

[DEBUG]   Included: org.apache.maven.doxia:doxia-sink-api:jar:1.1

[DEBUG]   Included: org.apache.maven.doxia:doxia-logging-api:jar:1.1

[DEBUG]   Included: commons-cli:commons-cli:jar:1.2

[DEBUG]   Included: org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-6

[DEBUG]   Included: backport-util-concurrent:backport-util-concurrent:jar:3.1

[DEBUG]   Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3

[DEBUG]   Included: org.sonatype.plexus:plexus-cipher:jar:1.4

[DEBUG]   Included: org.apache.maven.shared:maven-invoker:jar:2.1.1

[DEBUG]   Included: commons-collections:commons-collections:jar:3.2.1

[DEBUG]   Included: org.codehaus.groovy:groovy:jar:1.8.3

[DEBUG]   Included: antlr:antlr:jar:2.7.7

[DEBUG]   Included: asm:asm:jar:3.2

[DEBUG]   Included: asm:asm-commons:jar:3.2

[DEBUG]   Included: asm:asm-util:jar:3.2

[DEBUG]   Included: asm:asm-analysis:jar:3.2

[DEBUG]   Included: asm:asm-tree:jar:3.2

[DEBUG]   Included: org.beanshell:bsh:jar:2.0b4

[DEBUG]   Included: org.apache.maven.shared:maven-script-interpreter:jar:1.0

[DEBUG]   Included: org.apache.ant:ant:jar:1.8.1

[DEBUG] Configuring mojo org.apache.maven.plugins:maven-archetype-plugin:2.4:generate from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-archetype-plugin:2.4, parent: sun.misc.Launcher$AppClassLoader@1365360]

[DEBUG] Setting property: classpath.resource.loader.class => ‘org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader’.

[DEBUG] Setting property: site.resource.loader.class => ‘org.codehaus.plexus.velocity.SiteResourceLoader’.

[DEBUG] Setting property: velocimacro.messages.on => ‘false’.

[DEBUG] Setting property: resource.loader => ‘classpath,site’.

[DEBUG] Setting property: runtime.log.invalid.references => ‘false’.

[DEBUG] Setting property: resource.manager.logwhenfound => ‘false’.

[DEBUG] *******************************************************************

[DEBUG] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29)

[DEBUG] RuntimeInstance initializing.

[DEBUG] Default Properties File: orgapachevelocityruntimedefaultsvelocity.properties

[DEBUG] LogSystem has been deprecated. Please use a LogChute implementation.

[DEBUG] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl)

[DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader

[DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader

[DEBUG] ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl)

[DEBUG] Default ResourceManager initialization complete.

[DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Literal

[DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Macro

[DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Parse

[DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Include

[DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach

[DEBUG] Created ’20’ parsers.

[DEBUG] Velocimacro : initialization starting.

[DEBUG] Velocimacro : allowInline = true : VMs can be defined inline in templates

[DEBUG] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions

[DEBUG] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed.

[DEBUG] Velocimacro : autoload off : VM system will not automatically reload global library macros

[DEBUG] Velocimacro : Velocimacro : initialization complete.

[DEBUG] RuntimeInstance successfully initialized.

[DEBUG] Configuring mojo ‘org.apache.maven.plugins:maven-archetype-plugin:2.4:generate’ with basic configurator —>

[DEBUG]   (f) archetypeCatalog = https://15.218.171.196:8281/vco-repo/archetype-catalog.xml

[DEBUG]   (f) basedir = C:workVRO

[DEBUG]   (f) interactiveMode = true

[DEBUG]   (f) localRepository =       id: local

      url: file:///C:/Users/Administrator/.m2/repository/

   layout: default

snapshots: [enabled => true, update => always]

releases: [enabled => true, update => always]

[DEBUG]   (f) remoteArtifactRepositories = [      id: central

      url: https://repo.maven.apache.org/maven2

   layout: default

    proxy: web-proxy.in.hpecorp.net:8088

snapshots: [enabled => false, update => daily]

releases: [enabled => true, update => daily]

]

[DEBUG]   (f) session = org.apache.maven.execution.MavenSession@100588d

[DEBUG] — end configuration —

[INFO] Generating project in Interactive mode

[DEBUG] Searching for remote catalog: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml/archetype-catalog.xml

[DEBUG] Searching for remote catalog: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml

[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)

Choose archetype:

1: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-plugin-archetype-inventory (o11nplugin-project-archetype)

2: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-package-archetype (o11nplugin-project-archetype)

3: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-archetype-inventory-annotation (o11nplugin-project-archetype)

4: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-plugin-archetype-simple (o11nplugin-project-archetype)

5: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-archetype-spring (o11nplugin-spring-archetype)

6: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-plugin-archetype-modeldriven (o11nplugin-project-archetype)

7: https://15.218.171.196:8281/vco-repo/archetype-catalog.xml -> com.vmware.o11n:o11n-client-archetype-rest (o11nplugin-project-archetype)

Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 1

[DEBUG] Not found archetype com.vmware.o11n:o11n-plugin-archetype-inventory:7.0.0 in cache

[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://15.218.171.196:8281/vco-repo

[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://15.218.171.196:8281/vco-repo via web-proxy.in.hpecorp.net:8088

Downloading: https://15.218.171.196:8281/vco-repo/com/vmware/o11n/o11n-plugin-archetype-inventory/7.0.0/o11n-plug…

[DEBUG] Writing tracking file C:UsersAdministrator.m2repositorycomvmwareo11no11n-plugin-archetype-inventory7.0.0o11n-plugin-archetype-inventory-7.0.0.jar.lastUpdated

[DEBUG] Archetype com.vmware.o11n:o11n-plugin-archetype-inventory:7.0.0 doesn’t exist

org.apache.maven.archetype.downloader.DownloadException: Error downloading com.vmware.o11n:o11n-plugin-archetype-inventory:jar:7.0.0.

        at org.apache.maven.archetype.downloader.DefaultDownloader.download(DefaultDownloader.java:74)

        at org.apache.maven.archetype.common.DefaultArchetypeArtifactManager.exists(DefaultArchetypeArtifactManager.java:278)

        at org.apache.maven.archetype.ui.generation.DefaultArchetypeGenerationConfigurator.configureArchetype(DefaultArchetypeGenerationConfigurator.java:116)

        at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:189)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:601)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Could not transfer artifact com.vmware.o11n:o11n-plugin-archetype-inventory:jar:7.0.0 from/to o11n-plugin-archetype-inventory-repo (https://15.218.171.196:

8281/vco-repo): Failed to transfer file: https://15.218.171.196:8281/vco-repo/com/vmware/o11n/o11n-plugin-archetype-inventory/7.0.0/o11n-plug…. Return code is: 503 , ReasonPhrase:Service Unavailable.

  com.vmware.o11n:o11n-plugin-archetype-inventory:jar:7.0.0

from the specified remote repositories:

  o11n-plugin-archetype-inventory-repo (https://15.218.171.196:8281/vco-repo, releases=true, snapshots=true),

  central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)

        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:225)

        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:154)

        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:555)

        at org.apache.maven.archetype.downloader.DefaultDownloader.download(DefaultDownloader.java:70)

        … 25 more

Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact com.vmware.o11n:o11n-plugin-archetype-inventory:jar:7.0.0 from/to o11n-plugin-archetype-inventory-repo (https://15.218.171.196:8281/

vco-repo): Failed to transfer file: https://15.218.171.196:8281/vco-repo/com/vmware/o11n/o11n-plugin-archetype-inventory/7.0.0/o11n-plug…. Return code is: 503 , ReasonPhrase:Service Unavailable.

        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)

        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)

        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)

        at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)

        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:215)

        … 28 more

Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact com.vmware.o11n:o11n-plugin-archetype-inventory:jar:7.0.0 from/to o11n-plugin-archetype-inventory-repo (https://15.218.171.196:8281/vco-

repo): Failed to transfer file: https://15.218.171.196:8281/vco-repo/com/vmware/o11n/o11n-plugin-archetype-inventory/7.0.0/o11n-plug…. Return code is: 503 , ReasonPhrase:Service Unavailable.

        at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)

        at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)

        at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)

        at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)

        at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)

        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)

        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)

        … 32 more

Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://15.218.171.196:8281/vco-repo/com/vmware/o11n/o11n-plugin-archetype-inventory/7.0.0/o11n-plug…. Return code

is: 503 , ReasonPhrase:Service Unavailable.

        at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1021)

        at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:960)

        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)

        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)

        at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)

        at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)

        at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)

        at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)

        at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)

        at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)

        … 37 more

[INFO] ————————————————————————

[INFO] BUILD FAILURE

[INFO] ————————————————————————

[INFO] Total time: 01:34 min

[INFO] Finished at: 2016-06-09T16:37:36+05:30

[INFO] Final Memory: 13M/31M

[INFO] ————————————————————————

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.vmware.o11n:o11n-plugin-archetype-inventory:7.0.0) -> [

Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.vmware.

o11n:o11n-plugin-archetype-inventory:7.0.0)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:601)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoFailureException: The desired archetype does not exist (com.vmware.o11n:o11n-plugin-archetype-inventory:7.0.0)

        at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:205)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        … 20 more

Caused by: org.apache.maven.archetype.exception.UnknownArchetype: The desired archetype does not exist (com.vmware.o11n:o11n-plugin-archetype-inventory:7.0.0)

        at org.apache.maven.archetype.ui.generation.DefaultArchetypeGenerationConfigurator.configureArchetype(DefaultArchetypeGenerationConfigurator.java:119)

        at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:189)

        … 22 more

[ERROR]

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Regards….