Hi I'm following the Getting Started with AEM Sites - WKND Tutorial but I'm getting an error when running the comand mvn -PautoInstallPackage -Padobe-public clean
install
[INFO] --- content-package-maven-plugin:1.0.2:install (install-package) @ aem-guides-wknd.ui.apps ---
[INFO] Installing aem-guides-wknd.ui.apps (D:\AEM\workspace_wknd_site\aem-guides-wknd\ui.apps\target\aem-guides-wknd.ui.apps-0.0.1-SNAPSHOT.zip) to http://127.0.0.1:4502/crx/packmgr/service.jsp
INFO] I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: socket write error
INFO] Retrying request
[ERROR] Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:1.0.2:install (install-package) on project aem-guides-wknd.ui.apps: Software caused connection abort: recv failed -> [Help1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:1.0.2:install (install-package) on project aem-guides-wknd.ui.apps: Software caused connection abort: recv failed
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
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: Software caused connection abort: recv failed
at com.day.jcr.vault.maven.mgr.AbstractPackageManagerMojo.postRequest (AbstractPackageManagerMojo.java:265)
at com.day.jcr.vault.maven.mgr.PackageInstallMojo.uploadPackage (PackageInstallMojo.java:312)
at com.day.jcr.vault.maven.mgr.PackageInstallMojo.execute (PackageInstallMojo.java:221)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
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: java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0 (Native Method)
at java.net.SocketInputStream.socketRead (SocketInputStream.java:116)
at java.net.SocketInputStream.read (SocketInputStream.java:171)
at java.net.SocketInputStream.read (SocketInputStream.java:141)
at java.io.BufferedInputStream.fill (BufferedInputStream.java:246)
at java.io.BufferedInputStream.read (BufferedInputStream.java:265)
at org.apache.commons.httpclient.HttpParser.readRawLine (HttpParser.java:78)
at org.apache.commons.httpclient.HttpParser.readLine (HttpParser.java:106)
at org.apache.commons.httpclient.HttpConnection.readLine (HttpConnection.java:1116)
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine (HttpMethodBase.java:1973)
at org.apache.commons.httpclient.HttpMethodBase.readResponse (HttpMethodBase.java:1735)
at org.apache.commons.httpclient.HttpMethodBase.execute (HttpMethodBase.java:1098)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry (HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod (HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java:323)
at com.day.jcr.vault.maven.mgr.AbstractPackageManagerMojo.postRequest (AbstractPackageManagerMojo.java:232)
at com.day.jcr.vault.maven.mgr.PackageInstallMojo.uploadPackage (PackageInstallMojo.java:312)
at com.day.jcr.vault.maven.mgr.PackageInstallMojo.execute (PackageInstallMojo.java:221)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
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)
[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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :aem-guides-wknd.ui.apps
I'm running with Maven 3.6.0 :
D:\AEM\workspace_wknd_site\aem-guides-wknd>mvn -v
Apache Maven 3.6.0
Maven home: C:\Maven\apache-maven-3.6.0\bin\..
Java version: 1.8.0_121, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_121\jre
I have running the AEM instance correctly and I'm able to reach either : http://127.0.0.1:4502/crx/packmgr/service.jsp or http://localhost:4502/crx/packmgr/service.jsp
My pom.xml file is set to useProxy as false and settings.xml is placed in .m2 folder.
I'm running out of options, any help is much appreciated.
Solved! Go to Solution.
Views
Replies
Total Likes
Could you try to reproduce the same on a different machine/network?
My guess is that either firewall/antivirus policies/network restrictions could potentially be the root cause for this behavior that's blocking "upload/installation" of files on your m/c.
Views
Replies
Total Likes
set java home to jdk rather than jre
check if
Views
Replies
Total Likes
Hello!
My java is set to jdk, the info is displaying the runtime it seems. regarding the points you mention, there is no use of https, the proxy is not set in the settings.xml file and I can install the package with the admin user, some how maven is not able to connect with the localhost url, neither eclipse.
Views
Replies
Total Likes
Can you use command line and Maven to deploy to AEM. This will tell us if your Java and Maven are properly setup. See if you ca follow this article - Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13
Views
Replies
Total Likes
Could you try to reproduce the same on a different machine/network?
My guess is that either firewall/antivirus policies/network restrictions could potentially be the root cause for this behavior that's blocking "upload/installation" of files on your m/c.
Views
Replies
Total Likes
Yes, it seems that´s the issue, since I can run the command to our development server and I was able to perform the localhost build in another clean installation.
I'll have to validate what is blocking the connection.
Thanks a lot!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies