[JBoss JIRA] (WFLY-7550) Manifest Validation Error
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-7550?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-7550.
-------------------------------
Resolution: Rejected
# This is a user issue, not a server bug; such issues should start out on the forums
# The problem is that the MANIFEST.MF is not valid according to the JDK (this isn't our code rejecting it)
# It works on other app servers because they don't try to read the manifest, or else they ignore errors; nevertheless, the manifest is the problem and that's what you have to fix (or remove)
> Manifest Validation Error
> -------------------------
>
> Key: WFLY-7550
> URL: https://issues.jboss.org/browse/WFLY-7550
> Project: WildFly
> Issue Type: Bug
> Components: MSC
> Affects Versions: 10.1.0.Final
> Reporter: Rohit Lakshykar
> Assignee: David Lloyd
> Priority: Blocker
>
> Facing issue while deploying application.
> description available here
> http://stackoverflow.com/questions/40507281/jboss-wildfly-java-io-ioexcep...
> I have checked manifest file and working fine on other servers except wildfly
> 17:24:51,665 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."axiswebservice.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."axiswebservice.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "axiswebservice.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0161: Failed to get manifest for deployment "/content/axiswebservice.war/WEB-INF/lib/AxisBankEncDemov1.0.jar"
> at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:78)
> at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:65)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: java.io.IOException: invalid manifest format
> at java.util.jar.Manifest.read(Manifest.java:225)
> at java.util.jar.Manifest.<init>(Manifest.java:69)
> at org.jboss.vfs.VFSUtils.readManifest(VFSUtils.java:243)
> at org.jboss.vfs.VFSUtils.getManifest(VFSUtils.java:227)
> at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:76)
> ... 7 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2128) MERGE3: incorrect merge
by Anjith Paila (JIRA)
[ https://issues.jboss.org/browse/JGRP-2128?page=com.atlassian.jira.plugin.... ]
Anjith Paila commented on JGRP-2128:
------------------------------------
We have a 3 node Infinispan cache cluster with numOwners=2. We started the nodes one by one and the cluster got formed correctly with 3 nodes. Then we disconnected one of the node from the network and connected it back. But this started creating incorrect merges instead of forming the original 3 node cluster. I've added the logs of all 3 nodes and they have trace mode enabled.
> MERGE3: incorrect merge
> -----------------------
>
> Key: JGRP-2128
> URL: https://issues.jboss.org/browse/JGRP-2128
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.12, 4.0
>
> Attachments: BrokerPE-0.zip, SEM03VVM-201.zip, SEM03VVM-202.zip
>
>
> The following merge is incorrect, investigate what the desired behavior should be.
> Link: http://stackoverflow.com/questions/40492204/incorrect-merge-views-with-in...
> {noformat}
> (Incoming-1,BrokerPE-0-28575) ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714]
> ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714] --> one node disconnected
> ISPN000093: Received new, MERGED cluster view for channel ISPN: MergeView::[BrokerPE-0-28575|4] (2) [BrokerPE-0-28575, SEM03VVM-201-59385], 2 subgroups: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714], [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714] --> incorrect merge
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1809) JBoss CLI patch command doesn't honor custom configuration location
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1809?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky commented on WFCORE-1809:
-------------------------------------------
Could be. Let's consider a few cases though.
Suppose, I have multiple custom config directories. I launch a server using one of those custom configs. Then I apply a patch. The patching mechanism will backup the config directory.
Question: which one? The active one? All of them? The patching mechanism is not aware of all the possible custom config locations.
What if I then launch a server using another config? The server will actually be patched for that config too.
Question: what if I now rollback that last patch? Which config dir should I reset? The active one? All of them? Again, custom config locations are not known.
Suppose we have a server with some patching history. I create a custom config dir, launch the server and rollback a few patches
Question: which config dirs should be reset?
> JBoss CLI patch command doesn't honor custom configuration location
> -------------------------------------------------------------------
>
> Key: WFCORE-1809
> URL: https://issues.jboss.org/browse/WFCORE-1809
> Project: WildFly Core
> Issue Type: Bug
> Components: Patching
> Affects Versions: 3.0.0.Alpha8
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
>
> Suppose we are using custom standalone directory(example: standalone_dev) and if we try to rollback applied CP patch, with "--rest-configuration=true" option, it always restore configuration files from default location(JBOSS_HOME/standalone) not from the "standalone_dev" directory. I can see same result when I try to rollback patch through management console and through JBoss CLI in connected mode.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2128) MERGE3: incorrect merge
by Anjith Paila (JIRA)
[ https://issues.jboss.org/browse/JGRP-2128?page=com.atlassian.jira.plugin.... ]
Anjith Paila updated JGRP-2128:
-------------------------------
Attachment: SEM03VVM-202.zip
> MERGE3: incorrect merge
> -----------------------
>
> Key: JGRP-2128
> URL: https://issues.jboss.org/browse/JGRP-2128
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.12, 4.0
>
> Attachments: BrokerPE-0.zip, SEM03VVM-201.zip, SEM03VVM-202.zip
>
>
> The following merge is incorrect, investigate what the desired behavior should be.
> Link: http://stackoverflow.com/questions/40492204/incorrect-merge-views-with-in...
> {noformat}
> (Incoming-1,BrokerPE-0-28575) ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714]
> ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714] --> one node disconnected
> ISPN000093: Received new, MERGED cluster view for channel ISPN: MergeView::[BrokerPE-0-28575|4] (2) [BrokerPE-0-28575, SEM03VVM-201-59385], 2 subgroups: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714], [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714] --> incorrect merge
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2128) MERGE3: incorrect merge
by Anjith Paila (JIRA)
[ https://issues.jboss.org/browse/JGRP-2128?page=com.atlassian.jira.plugin.... ]
Anjith Paila updated JGRP-2128:
-------------------------------
Attachment: BrokerPE-0.zip
> MERGE3: incorrect merge
> -----------------------
>
> Key: JGRP-2128
> URL: https://issues.jboss.org/browse/JGRP-2128
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.12, 4.0
>
> Attachments: BrokerPE-0.zip, SEM03VVM-201.zip, SEM03VVM-202.zip
>
>
> The following merge is incorrect, investigate what the desired behavior should be.
> Link: http://stackoverflow.com/questions/40492204/incorrect-merge-views-with-in...
> {noformat}
> (Incoming-1,BrokerPE-0-28575) ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714]
> ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714] --> one node disconnected
> ISPN000093: Received new, MERGED cluster view for channel ISPN: MergeView::[BrokerPE-0-28575|4] (2) [BrokerPE-0-28575, SEM03VVM-201-59385], 2 subgroups: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714], [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714] --> incorrect merge
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2128) MERGE3: incorrect merge
by Anjith Paila (JIRA)
[ https://issues.jboss.org/browse/JGRP-2128?page=com.atlassian.jira.plugin.... ]
Anjith Paila updated JGRP-2128:
-------------------------------
Attachment: SEM03VVM-201.zip
> MERGE3: incorrect merge
> -----------------------
>
> Key: JGRP-2128
> URL: https://issues.jboss.org/browse/JGRP-2128
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.12, 4.0
>
> Attachments: BrokerPE-0.zip, SEM03VVM-201.zip, SEM03VVM-202.zip
>
>
> The following merge is incorrect, investigate what the desired behavior should be.
> Link: http://stackoverflow.com/questions/40492204/incorrect-merge-views-with-in...
> {noformat}
> (Incoming-1,BrokerPE-0-28575) ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714]
> ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714] --> one node disconnected
> ISPN000093: Received new, MERGED cluster view for channel ISPN: MergeView::[BrokerPE-0-28575|4] (2) [BrokerPE-0-28575, SEM03VVM-201-59385], 2 subgroups: [BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714], [BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714] --> incorrect merge
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months