Not able to install any package through Package Manager

Avatar

Avatar
Validate 1
Level 1
AEM_Dev_Newbie
Level 1

Like

1 like

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
AEM_Dev_Newbie
Level 1

Like

1 like

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
AEM_Dev_Newbie
Level 1

25-05-2020

I have been having this issue since last week. Tried to create a new AEM instance so I deleted the crx-quickstart folder and started AEM again. Everything went fine but when I tried to install the AEM service pack it could not be installed. The same behavior is happening for any package being installed through http://localhost:4502/crx/packmgr/index.jsp and I get the following error:

AEM_Dev_Newbie_0-1590404955539.png

Also get the following error in logs whenever the above problem occurs:

*ERROR* [qtp1913257142-71] org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage Error during install.
org.eclipse.jetty.io.RuntimeIOException: org.eclipse.jetty.io.EofException
at org.eclipse.jetty.server.ResponseWriter.isOpen(ResponseWriter.java:133) [org.apache.felix.http.jetty:4.0.8]
at org.eclipse.jetty.server.ResponseWriter.format(ResponseWriter.java:467) [org.apache.felix.http.jetty:4.0.8]
at org.eclipse.jetty.server.ResponseWriter.printf(ResponseWriter.java:439) [org.apache.felix.http.jetty:4.0.8]
at com.day.crx.packaging.impl.response.StreamedScriptResponse.writeCallback(StreamedScriptResponse.java:228) [com.adobe.granite.crx-packagemgr:1.2.74]
at com.day.crx.packaging.impl.response.StreamedScriptResponse.access$000(StreamedScriptResponse.java:44) [com.adobe.granite.crx-packagemgr:1.2.74]
at com.day.crx.packaging.impl.response.StreamedScriptResponse$1.flush(StreamedScriptResponse.java:82) [com.adobe.granite.crx-packagemgr:1.2.74]
at java.io.PrintWriter.flush(Unknown Source)...

There are more lines in error.log

 

I have tried starting AEM in a completely fresh browser such that not extensions interfere or any scripts don't get blocked. Still no luck. This problem started happening suddenly. There has been no change in the way I start new AEM instances and no change in code or my system's Java installation.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 5
Level 2
piotrr32520682
Level 2

Likes

7 likes

Total Posts

4 posts

Correct reply

2 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 5
Level 2
piotrr32520682
Level 2

Likes

7 likes

Total Posts

4 posts

Correct reply

2 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
piotrr32520682
Level 2

25-05-2020

I have noticed similar problems after updating the chrome to Version 83.0.4103.61 (Official Build) (64-bit).

It looks like new chrome close the connection too early and I am not able to upload the package with Chrome.

Try different browser and let's hope it will be fixed in next Chrome update.

Answers (14)

Answers (14)

Avatar

Avatar
Validate 1
Level 2
konradw58070066
Level 2

Likes

11 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 5
View profile

Avatar
Validate 1
Level 2
konradw58070066
Level 2

Likes

11 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
konradw58070066
Level 2

29-05-2020

Meanwhile Adobe confirmed that this is a problem with the package manager. So Chrome is not to blame here (only because they implemented a slightly more strict sandboxing model).

 

This is tracked internally at GRANITE-30226 (Package Manager) and GRANITE-30280 (CRX DE) and the following bundle contains the fix: com.adobe.granite:com.adobe.granite.crx-packagemgr:1.2.100.

 

This is supposed to be contained in an upcoming ServicePack/Hotfix.

Avatar

Avatar
Validate 1
Level 2
debasis-swain
Level 2

Likes

12 likes

Total Posts

23 posts

Correct reply

2 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
debasis-swain
Level 2

Likes

12 likes

Total Posts

23 posts

Correct reply

2 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile
debasis-swain
Level 2

01-06-2020

Hi,

 

This issues is with chrome browser latest version 83.0.4103.61 . There is a known bug reported Jira bug number : GRANITE-30226 with Adobe for fix.

 

In the meanwhile you can use other browsers for installing.

 

Thanks,

 

 

 

Avatar

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile
manising
Level 3

07-06-2020

This issue is resolved with the latest version of Chrome Version 83.0.4103.97 (Official Build) (64-bit)

 

You can also raise a support ticket to get a fix if you are not upgrading Chrome 

Avatar

Avatar
Boost 50
Employee
surabhikatiyar
Employee

Likes

68 likes

Total Posts

46 posts

Correct reply

18 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Boost 50
Employee
surabhikatiyar
Employee

Likes

68 likes

Total Posts

46 posts

Correct reply

18 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile
surabhikatiyar
Employee

04-06-2020

The issue has come up with the customers who are upgrading to the latest chrome version Version 83.0.4103.61 (Official Build). The fix will be available soon for the customers. Or you can open a daycare ticket to get the hot-fix. Workaround would be to build and deploy packages with other browsers like Firefox, Edge or IE

Avatar

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

106 likes

Total Posts

164 posts

Correct reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

106 likes

Total Posts

164 posts

Correct reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile
sunjot16
Employee

25-05-2020

It's reproducible. Seems like a Chrome issue.

 

Try to reload the browser after a few seconds. You will see the package installed.

Or, you can either go back to a previous version of Chrome, or use some other browser.

 

Hope it helps !!

 

 

Avatar

Avatar
Validate 1
Level 1
ankushd75501011
Level 1

Likes

2 likes

Total Posts

15 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile

Avatar
Validate 1
Level 1
ankushd75501011
Level 1

Likes

2 likes

Total Posts

15 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile
ankushd75501011
Level 1

14-06-2020

This issue has been resolved in the latest AEM service pack 6.5.5.

Avatar

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile
manising
Level 3

07-06-2020

 

This issue is resolved with the latest version of Chrome Version 83.0.4103.97 (Official Build) (64-bit)

 

You can also raise a support ticket to get a fix if you are not upgrading Chrome 

Avatar

Avatar
Boost 1
Level 1
vibhuranjan
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
vibhuranjan
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
vibhuranjan
Level 1

01-06-2020

I was also facing the same issue since yesterday and after checking this post i tried internet explorer to upload the package. I was able to do so. So it seems issue is with latest version of Chrome.

 

Following error i was getting:

 

org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage Error during install. org.eclipse.jetty.io.RuntimeIOException: org.eclipse.jetty.io.EofException

Avatar

Avatar
Boost 1
Level 1
Yogas24
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
Yogas24
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Yogas24
Level 1

01-06-2020

It's Chrome Browser issue, works with Mozilla . 

 

Thanks.

Avatar

Avatar
Ignite 1
Employee
aemmarc
Employee

Likes

184 likes

Total Posts

243 posts

Correct reply

92 solutions
Top badges earned
Ignite 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Ignite 1
Employee
aemmarc
Employee

Likes

184 likes

Total Posts

243 posts

Correct reply

92 solutions
Top badges earned
Ignite 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
aemmarc
Employee

26-05-2020

This issue has been observed by quite a few people and organizations.

Specific to build 83.0.4103.61 of Google Chrome.

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

648 likes

Total Posts

608 posts

Correct reply

240 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

648 likes

Total Posts

608 posts

Correct reply

240 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

25-05-2020

@AEM_Dev_Newbie,

I took the time to spin up a new AEM 6.4/6.5 instance to test our this problem. After installing Chrome, Version 83.0.4103.61 (Official Build) (64-bit), I had similar problems with the package manager;  I had the exact same problem as you.

  • I cannot install a content package.
  • I cannot build a content package.
  • I cannot create a new content package with content filters.

I solved this problem by using another browser, like Firefox or Safari.

While using Chrome, these are the errors that I am catching:

 

// error
25.05.2020 15:24:18.519 *WARN* [qtp1034376894-1722] org.eclipse.jetty.server.HttpChannel //localhost:4502/crx/packmgr/service/script.html/etc/packages/my_packages/test.zip
java.lang.IllegalStateException: Committed
	at org.eclipse.jetty.server.HttpChannel.resetBuffer(HttpChannel.java:808) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.HttpOutput.resetBuffer(HttpOutput.java:887) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.Response.resetBuffer(Response.java:1246) [org.apache.felix.http.jetty:3.4.7.B012]
	at javax.servlet.ServletResponseWrapper.resetBuffer(ServletResponseWrapper.java:195) [org.apache.felix.http.servlet-api:1.1.2]
	at org.apache.felix.http.base.internal.dispatch.ServletResponseWrapper.sendError(ServletResponseWrapper.java:67) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.apache.felix.http.base.internal.dispatch.ServletResponseWrapper.sendError(ServletResponseWrapper.java:61) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.apache.felix.http.base.internal.dispatch.Dispatcher$1.doFilter(Dispatcher.java:156) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager.invokePreprocessors(WhiteboardManager.java:1000) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:91) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49) [org.apache.felix.http.jetty:3.4.7.B012]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) [org.apache.felix.http.servlet-api:1.1.2]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:224) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.Server.handle(Server.java:534) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [org.apache.felix.http.jetty:3.4.7.B012]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [org.apache.felix.http.jetty:3.4.7.B012]
	at java.lang.Thread.run(Thread.java:748)

 

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

25-05-2020

@AEM_Dev_Newbie Since @piotrr32520682  had similar issue, may be you can try it in a different browser and check if it is working. 

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

390 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

390 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

25-05-2020

Adding to what Veena mentioned. You need to make sure that if you extract the archive you get the jcr_root as one of the folders. AEM need to find jcr_root as the first folder otherwise it will not install. 

other than that, please make sure you are trying in a private window and logged in as admin

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

25-05-2020

@AEM_Dev_Newbie Are you sure you are installing an AEM package ? Not all zip files can be installed in AEM. If you read the documentation on packages , it is clearly mentioned what all constitutes and AEM package. 

 

A package also contains vault meta information, including the filter definitions and import configuration information. Additional content properties (that are not used for package extraction) can be included in the package, such as a description, a visual image, or an icon; these properties are for the content package consumer and for informational purposes only.

 

If you extract/open the zip file you are trying to install, you should be able to find the below structure 

 

packages.JPGThere should be a jcr_root folder and a META_INF folder. If you don't find those, then the zip file you are trying to install is not an AEM package.