[JBoss JIRA] (JBIDE-13443) Update version of Birt in Kepler target platform
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13443:
-----------------------------------
Assignee: Mickael Istria (was: Snjezana Peco)
> Update version of Birt in Kepler target platform
> ------------------------------------------------
>
> Key: JBIDE-13443
> URL: https://issues.jboss.org/browse/JBIDE-13443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> The version of Birt we build against does not match with version for Kepler and conflicts on ICU4j
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> says:
> {quote}
> Could not install from: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> Software currently installed: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> Only one of the following can be installed at once:
> International Components for Unicode for Java (ICU4J) 4.4.2.v20110823 (com.ibm.icu 4.4.2.v20110823)
> International Components for Unicode for Java (ICU4J) 50.1.0.v20121116-2 (com.ibm.icu 50.1.0.v20121116-2)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> To: org.eclipse.epp.package.jee.feature.feature.group [2.0.0.20121218-0936]
> Cannot satisfy dependency:
> From: BIRT Chart Framework 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR (org.eclipse.birt.chart.feature.group 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR)
> To: org.eclipse.birt.core [4.2.1.v201209121203]
> Cannot satisfy dependency:
> From: BIRT Core Package 4.2.1.v201209121203 (org.eclipse.birt.core 4.2.1.v201209121203)
> To: package com.ibm.icu.lang [3.4.4,5.0.0)
> Cannot satisfy dependency:
> From: Eclipse e4 Rich Client Platform 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 (org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4)
> To: com.ibm.icu [50.1.0.v20121116-2]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 2.0.0.20121218-0936 (org.eclipse.epp.package.jee.feature.feature.group 2.0.0.20121218-0936)
> To: org.eclipse.platform.feature.group [4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP (org.eclipse.platform.feature.group 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP)
> To: org.eclipse.rcp.feature.group [4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP]
> Cannot satisfy dependency:
> From: Eclipse RCP 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP (org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP)
> To: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4]
> Cannot satisfy dependency:
> From: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> To: org.eclipse.birt.chart.feature.group 2.5.0
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-12913) Startup/Shutdown Pollers fails with EAP511
by Jesper Skov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi... ]
Jesper Skov commented on JBIDE-12913:
-------------------------------------
We're running 2.4.0.Final-v20121205-2029-B41 of the JBoss AS plugin (according to Eclipse's About dialog's plugin registry).
Maybe that's something else than the 4.0.0GA?!
Because we see the dialog. And as noted in the original description, netstat agrees with me; nothing is running on port 8080.
I don't have any JBoss processes running in the background - switching the startup Poller+save on the server config makes it all magically work.
And I'd be surprised if that action alone would kill anything happening to be (silently, invisibly) locking port 8080.
Anyway, I'll just document the workaround and be done with it. Thanks.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-12913) Startup/Shutdown Pollers fails with EAP511
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-12913.
---------------------------------
Resolution: Done
This was fixed back in beta2 and is not replicatable in GA.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-12913) Startup/Shutdown Pollers fails with EAP511
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-12913:
-------------------------------------
Ok, the screenshot is a little small, but I know that screenshot.
That screenshot is not a failure. That screenshot means you have a jboss process already running in the background on teh ports you are attempting to run the new version on.
You should check your running process list and terminate the already-running jboss or tomcat instance (anything using port 8080).
This is not a bug. This is an intended feature.
How you ended up with such a process, I cannot know. I do know that I've just started the app server 5 or 6 times with various changes to configuration, and I have experienced no errors.
JMX is still a valid poller. So is web port poller. Both are still valid pollers and I've not experienced any evidence that either are failing.
I'm going to re-close this as resolved.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-12913) Startup/Shutdown Pollers fails with EAP511
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-12913:
-------------------------------------
I am not able to replicate this on win7 jbds6.0.0.GA and EAP 5.1.1, whether we are bound to localhost or 0.0.0.0.
Neither way can I replicate this.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-10777) Use Sonar for Code Quality Analysis
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10777?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-10777:
----------------------------------------
Hey [~ldimaggio] (and others), I found a workaround for Eclipse bug 397996 which I did set up in parent pom (removing sourceDirectory tag which is useless to set in the Tycho world).
So you can see a running job here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... , you'll notice it's the same as any job except it doesn't do any publishing, and adds an invocation of Sonar plugin. See in the configuration of the Sonar plugin the setting of maven.repo.local and sonar.jacoco.reportPath.
Then you can see code analysis reports + coverage reports here: http://sonar.mw.lab.eng.bos.redhat.com/sonar/dashboard/index/org.jboss.to...
It now seems to me that there is no technical issue preventing us from using Sonar. We now need to decide of how we'll use it.
Adding [~vpakan] to recipients for this issue since he was interested in Sonar.
> Use Sonar for Code Quality Analysis
> -----------------------------------
>
> Key: JBIDE-10777
> URL: https://issues.jboss.org/browse/JBIDE-10777
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Affects Versions: 3.1.2
> Environment: any
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: LATER
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Sonar provides a very powerful tool to get report about tests, code coverage, and static analysis in a project (errors, duplications...). It is easy to use, there is a nice integration with Maven and Hudson/Jenkins. It provides reporting tools for everything existing in the Java world, and more.
> Adding Sonar to Hudson really helps to make code better.
> http://www.sonarsource.org/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months