[JBoss JIRA] (JBIDE-13897) Remote EAP 6.1 cannot stop (maintenance)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13897?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13897:
---------------------------------------
Unfortunately this didn't seem to make it into 4.0.x :(
> Remote EAP 6.1 cannot stop (maintenance)
> ----------------------------------------
>
> Key: JBIDE-13897
> URL: https://issues.jboss.org/browse/JBIDE-13897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.1.Final
> Environment: JBDS 7.0.0.Alpha1a B10
> EAP 6.1.0.DR4.1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.0.2.Final
>
>
> After JBIDE-13585 added support for EAP 6.1 I tried to use it as a remote server. Server start and deploy worked fine, but when I tried to stop the server it won't do it.
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2013-02-20 11:06:05.662
> !MESSAGE Server JBoss EAP 6.1 Runtime Server marvin failed to stop.
> {code}
> !remote-server-stop.png!
--
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
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2505:
-------------------------------------
[~nickboldt] I don't get it. The plugin was upversioned because it changed, no? And since it changed, the feature should upversion, too, no? Had the contents (= included plugins) of the feature not changed, the plugin would still have the same version, no? I must be missing something here.
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
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
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2505:
----------------------------------
Having a plugin increment and a feature NOT is SOP* for Eclipse.org. Since the contents of the feature have not changed, there's no need to upversion it. That said, to ensure the new plugin can be installed on top of an old one the hash suffix on the feature version is incremented so that it will be seen as new.
Thus you might have org.foo.feature_4.2.1.datestamp-hashabc and a month later, when org.foo plugin 4.2.2 is released, the feature will be rebuilt as org.foo.feature_4.2.1.datestamp-hashabf, using the same datestamp but a newer hash (abc < abf).
* - SOP = Standard Operating Procedures
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
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
[JBoss JIRA] (JBIDE-13896) EAP6.1 client jar incompatibility
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-13896:
-----------------------------------
Summary: EAP6.1 client jar incompatibility
Key: JBIDE-13896
URL: https://issues.jboss.org/browse/JBIDE-13896
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha2
Work as follows:
1) Clean up unit tests to use only API
2) make service interface throw Runtime Exceptions
3) minor cleanup to service interface
4) Ensure tests properly load all bundles
5) Move some no-dep classes from as71 mgmt bundle to management.core
6) Either:
a) Create a new bundle with additional jars in case of incompatibility, or
b) Update jars in as71 mgmt bundle to jars that work for all adapters
--
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
[JBoss JIRA] (JBIDE-11264) When project is inside eclipse workspace Maven import gets the application name wrong
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11264?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-11264.
----------------------------------
Closing - won't fix.
> When project is inside eclipse workspace Maven import gets the application name wrong
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-11264
> URL: https://issues.jboss.org/browse/JBIDE-11264
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, UpStream
> Affects Versions: 3.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Fred Bricon
> Fix For: 3.3.x, 4.0.x
>
> Attachments: import.ogv, untitled.mp4
>
>
> When I have an existing OpenShift application with name different that the artifact id in pom file and I want to import it into Eclipse workspace, I get different Eclipse project names depending on the chosen location of the newly created workspace file.
> # when selected default value (/home/xxx/git) the project's name is the one from pom file
> # when selected the workspace location the project's name is the OpenShift application name
--
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
[JBoss JIRA] (JBIDE-12784) IllegalArgumentException after importing HTML5 project from JBoss Central
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12784?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-12784.
----------------------------------
Closing. Tracker issue for 4.1.0: JBIDE-13731
> IllegalArgumentException after importing HTML5 project from JBoss Central
> -------------------------------------------------------------------------
>
> Key: JBIDE-12784
> URL: https://issues.jboss.org/browse/JBIDE-12784
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, UpStream
> Affects Versions: 4.0.0.Alpha2
> Reporter: Stefan Bunciak
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.0.x
>
>
> {code}duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)){code}
> Stack trace:
> {code}
> java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5))
> at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95)
> at org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource.addResourceModelListener(JpaXmlResource.java:264)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:579)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:552)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1683)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:254)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1668)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1860)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1852)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1835)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1646)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1638)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:684)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:670)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
[JBoss JIRA] (JBIDE-13895) Push "Stacks" into 'runtime' component in base
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-13895:
-----------------------------------
Summary: Push "Stacks" into 'runtime' component in base
Key: JBIDE-13895
URL: https://issues.jboss.org/browse/JBIDE-13895
Project: Tools (JBoss Tools)
Issue Type: Task
Components: central, runtime-detection
Affects Versions: 4.1.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
Stacks support duplicates what is available in runtimes. The models should be unified, which would involve pushing stacks down into base / runtimes.
Subtasks to be created.
--
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
[JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13894:
--------------------------------------
Summary: 'Tail files...' dialog ignores -n parameter value
Key: JBIDE-13894
URL: https://issues.jboss.org/browse/JBIDE-13894
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.x
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.1.0.Beta1
Attachments: tail1.png
I set -n parameter to 3:
!tail1.png|thumbnail!
but the console output contains much more lines right away:
{code}
Loading....
==> jbosseap-6.0/logs/server.log <==
2013/04/02 07:57:42,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war
2013/04/02 07:57:44,331 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context:
2013/04/02 07:57:48,743 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai
2013/04/02 07:57:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war"
2013/04/02 07:57:48,934 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war"
2013/04/02 07:57:49,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management
2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990
2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand)
2013/04/02 08:03:58,941 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager
2013/04/02 08:03:59,130 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy
==> jbosseap-6.0/logs/boot.log <==
user.name = 515ac573e0b8cd1da6000005
user.timezone = America/New_York
07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties
07:56:56,854 WARN [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted.
07:56:56,853 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
07:56:57,037 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
07:56:57,038 WARN [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted.
07:56:56,959 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
07:56:57,148 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
07:56:57,938 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
{code}
I would expect the same behaviour like on linux system - to output just the specified 3 lines...
--
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
[JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13894?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13894:
-----------------------------------
Attachment: tail1.png
> 'Tail files...' dialog ignores -n parameter value
> -------------------------------------------------
>
> Key: JBIDE-13894
> URL: https://issues.jboss.org/browse/JBIDE-13894
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.x
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: tail1.png
>
>
> I set -n parameter to 3:
> !tail1.png|thumbnail!
> but the console output contains much more lines right away:
> {code}
> Loading....
> ==> jbosseap-6.0/logs/server.log <==
> 2013/04/02 07:57:42,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war
> 2013/04/02 07:57:44,331 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context:
> 2013/04/02 07:57:48,743 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai
> 2013/04/02 07:57:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war"
> 2013/04/02 07:57:48,934 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war"
> 2013/04/02 07:57:49,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management
> 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990
> 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand)
> 2013/04/02 08:03:58,941 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager
> 2013/04/02 08:03:59,130 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy
> ==> jbosseap-6.0/logs/boot.log <==
> user.name = 515ac573e0b8cd1da6000005
> user.timezone = America/New_York
> 07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties
> 07:56:56,854 WARN [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted.
> 07:56:56,853 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
> 07:56:57,037 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 07:56:57,038 WARN [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted.
> 07:56:56,959 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
> 07:56:57,148 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
> 07:56:57,938 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> {code}
> I would expect the same behaviour like on linux system - to output just the specified 3 lines...
--
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
[JBoss JIRA] (JBIDE-13893) NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
by Martin Malina (JIRA)
Martin Malina created JBIDE-13893:
-------------------------------------
Summary: NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
Key: JBIDE-13893
URL: https://issues.jboss.org/browse/JBIDE-13893
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.1.Final
Environment: JBDS 6.0.1.CR1b B361
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.2.Final, 4.1.0.Alpha2
After installing JBDS and starting it afresh, I get this warning in the error view:
{code}
NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
An exception stack trace is not available.
{code}
I'm not sure if it happens in 4.1.x as well, but odds are it does - it seems to be related to the recently added support for EAP 6.1.
--
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