[JBoss JIRA] (JBIDE-26303) ZipException below FileSet.checkType (thrown in ZipFile.read)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26303?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26303:
-------------------------------
Fix Version/s: 4.9.0.Final
> ZipException below FileSet.checkType (thrown in ZipFile.read)
> -------------------------------------------------------------
>
> Key: JBIDE-26303
> URL: https://issues.jboss.org/browse/JBIDE-26303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Reporter: Automated Error Reporting Bot
> Fix For: 4.9.0.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: invalid LOC header (bad signature)
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsByteArray(Util.java:525)
> at org.eclipse.jdt.internal.compiler.util.Util.getZipEntryByteContent(Util.java:691)
> at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:359)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284)
> at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259)
> at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.checkType(FileSet.java:80)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.add(FileSet.java:50)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.buildJars(JSF2ProjectBuilder.java:228)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:138)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.buildExtensionModels(KbBuilder.java:212)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:133)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.10.0.v20180427-1454 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.13.0.v20180512-1138 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.14.0.v20180417-0825 |
> | org.eclipse.debug.core | 3.11.0.v20170605-1534 | 3.11.0.v20170605-1534 |
> | org.eclipse.debug.ui | 3.12.50.v20170920-1329 | 3.12.50.v20170920-1329 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.14.0.v20180611-0500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.14.0.v20180528-0519 |
> | org.eclipse.jdt.ui | 3.12.2.v20160929-0804 | 3.12.2.v20160929-0804 |
> | org.eclipse.jst.common.project.facet.core | 1.4.500.v201508121553 | 1.5.0.v201710021614 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.8.3.20180227-2137 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.8.2.20171007-0217 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.701.v201707142105 |
> | org.fusesource.ide.camel.model.service.core | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180406-2149 |
> | org.fusesource.ide.projecttemplates | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180409-0833 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.300.v20180614-0303 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.9.0.v20180614-0303 |
> Operating Systems:
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5729a808e4b0a5...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26303) ZipException below FileSet.checkType (thrown in ZipFile.read)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26303?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26303:
----------------------------------
Assignee: Jeff MAURY
> ZipException below FileSet.checkType (thrown in ZipFile.read)
> -------------------------------------------------------------
>
> Key: JBIDE-26303
> URL: https://issues.jboss.org/browse/JBIDE-26303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: 4.9.0.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: invalid LOC header (bad signature)
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsByteArray(Util.java:525)
> at org.eclipse.jdt.internal.compiler.util.Util.getZipEntryByteContent(Util.java:691)
> at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:359)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284)
> at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259)
> at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.checkType(FileSet.java:80)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.add(FileSet.java:50)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.buildJars(JSF2ProjectBuilder.java:228)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:138)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.buildExtensionModels(KbBuilder.java:212)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:133)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.10.0.v20180427-1454 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.13.0.v20180512-1138 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.14.0.v20180417-0825 |
> | org.eclipse.debug.core | 3.11.0.v20170605-1534 | 3.11.0.v20170605-1534 |
> | org.eclipse.debug.ui | 3.12.50.v20170920-1329 | 3.12.50.v20170920-1329 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.14.0.v20180611-0500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.14.0.v20180528-0519 |
> | org.eclipse.jdt.ui | 3.12.2.v20160929-0804 | 3.12.2.v20160929-0804 |
> | org.eclipse.jst.common.project.facet.core | 1.4.500.v201508121553 | 1.5.0.v201710021614 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.8.3.20180227-2137 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.8.2.20171007-0217 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.701.v201707142105 |
> | org.fusesource.ide.camel.model.service.core | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180406-2149 |
> | org.fusesource.ide.projecttemplates | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180409-0833 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.300.v20180614-0303 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.9.0.v20180614-0303 |
> Operating Systems:
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5729a808e4b0a5...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26147:
-------------------------------
Sprint: devex #153 August 2018, devex #154 September 2018 (was: devex #153 August 2018)
> Incremental publish not working with WF13, WF12 and WF11
> --------------------------------------------------------
>
> Key: JBIDE-26147
> URL: https://issues.jboss.org/browse/JBIDE-26147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.6.0.AM3
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Fix For: 4.9.x
>
> Attachments: helloworld-rs.zip
>
>
> Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context.
> This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0.
> Then this code is commented out, the application is incrementally published but the error persists
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22138:
-------------------------------
Sprint: devex #150 June 2018, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #150 June 2018, devex #152 July 2018, devex #153 August 2018)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.x
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25000:
-------------------------------
Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.x
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months