[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-25923.
---------------------------------
Since this doesn't seem to be happening anymore, I'm closing this issue. Feel free to reopen or file a new JIRA if you see this problem again.
> Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25923
> URL: https://issues.jboss.org/browse/JBIDE-25923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.6.0.AM1
>
> Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif
>
>
> When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
> {code}
> 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
> 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1229?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1229:
-----------------------------------
All set.
On Thu, Jun 7, 2018 at 8:05 AM, Andrej Podhradsky (JIRA) <issues(a)jboss.org>
> Cannot install Teiid Designer into Devstudio 12.0.0
> ---------------------------------------------------
>
> Key: JBTIS-1229
> URL: https://issues.jboss.org/browse/JBTIS-1229
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Affects Versions: 4.6.0.CR1
> Environment: Red Hat Developer Studio
> Version: 12.0.0.AM3
> Build id: AM3-v20180605-1618-B2654
> OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from
> https://devstudio.redhat.com/12/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1229?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1229:
---------------------------------
Assignee: Paul Leacu
> Cannot install Teiid Designer into Devstudio 12.0.0
> ---------------------------------------------------
>
> Key: JBTIS-1229
> URL: https://issues.jboss.org/browse/JBTIS-1229
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Affects Versions: 4.6.0.CR1
> Environment: Red Hat Developer Studio
> Version: 12.0.0.AM3
> Build id: AM3-v20180605-1618-B2654
> OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from
> https://devstudio.redhat.com/12/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1229?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1229:
------------------------------------------
Workaround is very simple - just add the photon update site
http://download.eclipse.org/releases/photon/
> Cannot install Teiid Designer into Devstudio 12.0.0
> ---------------------------------------------------
>
> Key: JBTIS-1229
> URL: https://issues.jboss.org/browse/JBTIS-1229
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Affects Versions: 4.6.0.CR1
> Environment: Red Hat Developer Studio
> Version: 12.0.0.AM3
> Build id: AM3-v20180605-1618-B2654
> OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31
> Reporter: Andrej Podhradsky
> Priority: Blocker
>
> Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from
> https://devstudio.redhat.com/12/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1229:
----------------------------------------
Summary: Cannot install Teiid Designer into Devstudio 12.0.0
Key: JBTIS-1229
URL: https://issues.jboss.org/browse/JBTIS-1229
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: teiid
Affects Versions: 4.6.0.CR1
Environment: Red Hat Developer Studio
Version: 12.0.0.AM3
Build id: AM3-v20180605-1618-B2654
OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31
Reporter: Andrej Podhradsky
Priority: Blocker
Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from
https://devstudio.redhat.com/12/staging/updates/integration-stack/
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found
Cannot satisfy dependency:
From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740]
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26086) SSP server does not send error codes for bad requests
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26086?page=com.atlassian.jira.plugi... ]
Jan Richter reassigned JBIDE-26086:
-----------------------------------
Assignee: Rob Stryker
> SSP server does not send error codes for bad requests
> -----------------------------------------------------
>
> Key: JBIDE-26086
> URL: https://issues.jboss.org/browse/JBIDE-26086
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM3
> Reporter: Jan Richter
> Assignee: Rob Stryker
>
> Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated.
> For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting.
> {noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1
> Sec-WebSocket-Version: 13
> Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ==
> Connection: Upgrade
> Upgrade: websocket
> Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
> Host: localhost:27511
> "
> at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89)
> at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748){noformat}
> This is most likely a 'feature' of lsp4j, thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26086) SSP server does not send error codes for bad requests
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26086?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-26086:
--------------------------------
Description:
Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated.
For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting.
{noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ==
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Host: localhost:27511
"
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748){noformat}
This is most likely a 'feature' of lsp4j, thoughts?
was:
Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated.
For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting.
{noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ==
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Host: localhost:27511
"
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748){noformat}
> SSP server does not send error codes for bad requests
> -----------------------------------------------------
>
> Key: JBIDE-26086
> URL: https://issues.jboss.org/browse/JBIDE-26086
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM3
> Reporter: Jan Richter
>
> Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated.
> For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting.
> {noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1
> Sec-WebSocket-Version: 13
> Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ==
> Connection: Upgrade
> Upgrade: websocket
> Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
> Host: localhost:27511
> "
> at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89)
> at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748){noformat}
> This is most likely a 'feature' of lsp4j, thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months