Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

MrynalKumar
MrynalKumar
Offline

Badges

Badges
4

Accepted Solutions

Accepted Solutions
0

Likes

Likes
1

Posts

Posts
6

Discussions

Discussions
4

Questions

Questions
2

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by MrynalKumar
Customize the badges you want to showcase on your profile
I also faced similar issue. Unicode character(special cha...
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
I also faced similar issue. Unicode character(special characters) passed as a request parameter getting converted to question mark(?).Reason : Reason is the character encoding.Solution :# Solution 11. Configure 'Apache Sling Request Parameter Handling', Set the property 'Default Parameter Encoding'='iso-8859-1'2. Take care of the character encoding (to UTF-8) through codequeryString = new String(request.getParameter(initialSearchConfig.getQueryStringParamName()).getBytes("iso-8859-1"), "UTF-8");...

Views

2.2K

Likes

0

Replies

0
Re: AEM 6.5 Asset direct link downloads ,does not open as...
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
@arvindp66202646 I also faced similar issue while performing AEM upgrade from 6.3 to 6.5 SP4Reason - Reason is the response header ‘content-disposition: attachment’. Solution : There are two possible solutions -#Solution1 -Control the content-disposition using 'Apache Sling Content Disposition Filter' Configure the property 'Enable for all Resource Paths' to true. Do not set the content-disposition header explicitly.Keep the content-disposition header to its default value - 'Inline'#Solution2 - ...

Views

1.8K

Likes

0

Replies

0
, , I also faced similar issue while doing the AEM upgra...
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
@salmana68849090 , @jbrar , I also faced similar issue while doing the AEM upgrade from AEM 6.3 to 6.5 SP4. The issue got resolved.Error Log -27.03.2020 12:03:14.328 *WARN* [10.202.47.202 [1585335794320] GET /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json HTTP/1.1] com.adobe.granite.workflow.core.jcr.WorkflowModelManager Workflow model does not exist: /etc/workflow/models/XXXXXXXXX/jcr:content/model27.03.2020 12:03:14.328 *ERROR* [10.202.47.202 [1585335794320] GET /mnt/overl...

Views

4.5K

Likes

0

Replies

0
Re: Felix Bundle Start Error ( osgi.wiring.package; (osgi.wiring.package=javax.annotation)))n
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
I also faced similar error while upgrading from AEM 6.3 to 6.5 SP4. Error Log -24.03.2020 15:09:40.573 *ERROR* [qtp1041007297-2360] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unable to resolve com.XXX.XXXX.XXX [590](R 590.0): missing requirement [com.XXX.XXX.XXX [590](R 590.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.xml.namespace)(version>=0.0.0)(!(version>=1.0.0))) Unresolved requirements: [[com.XXX.XXX.XXX [590](R 590.0)] osgi...

Views

6.2K

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI depen...
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
@jineetv21622325 , I also faced similar error while upgrading from AEM 6.3 to 6.5 SP4. Error Log -24.03.2020 15:09:40.573 *ERROR* [qtp1041007297-2360] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unable to resolve com.XXX.XXXX.XXX [590](R 590.0): missing requirement [com.XXX.XXX.XXX [590](R 590.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.xml.namespace)(version>=0.0.0)(!(version>=1.0.0))) Unresolved requirements: [[com.XXX.XXX.XXX [...

Views

1.4K

Like

1

Replies

0
, I also faced similar issue. '/system/console/slinglog'...
Avatar
Give Back 5
Level 1
MrynalKumar
Level 1

Like

1 like

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
MrynalKumar
- Adobe Experience Manager
@monikam6817093 , I also faced similar issue. '/system/console/slinglog' was not getting loaded. Error Log -07.04.2020 10:12:45.297 *ERROR* [qtp1407899993-6020] org.apache.felix.http.jetty Exception while processing request to /system/console/slinglog (java.lang.NullPointerException)java.lang.NullPointerException: null at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) at org.apache.sling.commons.log.logback.internal.LogConfigManager.getLogWriter(LogConfigManager.java:223)...

Views

2.1K

Likes

0

Replies

0
Likes from