[JBoss JIRA] (JBIDE-12053) JBoss Enterprise Application Platform 6 and JBoss AS 7
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-12053:
-----------------------------------
Summary: JBoss Enterprise Application Platform 6 and JBoss AS 7
Key: JBIDE-12053
URL: https://issues.jboss.org/browse/JBIDE-12053
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Burr Sutter
Use the phrase "JBoss Enterprise Application Platform 6 and JBoss AS 7" in the java ee 6 web archetype
This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss AS 7.1.
This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
It includes a persistence unit and some sample persistence and transaction code to help you get your feet wet with database access in enterprise Java.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-12032) JMX connection to remote AS7 not working even with -Dmanagement set up
by Martin Malina (JIRA)
Martin Malina created JBIDE-12032:
-------------------------------------
Summary: JMX connection to remote AS7 not working even with -Dmanagement set up
Key: JBIDE-12032
URL: https://issues.jboss.org/browse/JBIDE-12032
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1
JMX connection to remote AS7 server is broken again :(
It may have to do with JBIDE-11921 or JBIDE-12028.
When you start a remote AS7 server with both "Listen on all interfaces" and "Expose your management port" checked and then try to expand the server in MBean Explorer, it displays "Loading" for a while and then errors with:
{code}
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.013
!MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
!STACK 1
org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:105)
at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87)
at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:154)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
... 7 more
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.014
!MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
!STACK 0
java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:154)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:105)
at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87)
at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
(Yes, two errors - perhaps for the two intended connections?)
Also, the start poller was set to Web Poller, as the default JBoss 7 Manager Service currently doesn't work due to JBIDE-12028
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBDS-2144) JBDS 5 Beta 3 - enterprise=true breaks Forge
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2144:
---------------------------------
Summary: JBDS 5 Beta 3 - enterprise=true breaks Forge
Key: JBDS-2144
URL: https://issues.jboss.org/browse/JBDS-2144
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Version: 5.0.0.Beta3
Build id: v20120514-2058-H159-Beta3
Build date: 20120514-2058
Reporter: Burr Sutter
Priority: Blocker
steps to reproduce:
1) Click on Java EE Web Project in JBoss Central
2) Select EAP6 Beta2 as the Target Runtime - assumes you have updated the settings.xml with the correct EAP6.1 maven repo
3) Run As on Server works
4) Right-click on Project name and select Show In Forge Console
5) Type "entity" and hit return
[jboss-javaee6-webapp-eap] jboss-javaee6-webapp-eap $ entity
***ERROR*** [entity] Plugin is not usable in current scope or project
attached is the pom.xml for the project
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11850) OpenShift server: provide warning when changing deploy project
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-11850:
--------------------------------------
Summary: OpenShift server: provide warning when changing deploy project
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
>From my point of view does not make sense to allow users to switch deploy project from JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-12001) Cannot Start AS7.1.1 server with a space in path using JBoss Tools
by Darren Jones (JIRA)
Darren Jones created JBIDE-12001:
------------------------------------
Summary: Cannot Start AS7.1.1 server with a space in path using JBoss Tools
Key: JBIDE-12001
URL: https://issues.jboss.org/browse/JBIDE-12001
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: Windows 7 64-bit; Java 1.6.0u23; Eclipse 3.7.2 EE edition with JBoss Tools;
Reporter: Darren Jones
Assignee: Rob Stryker
I have a 7.1.1 server installed in "F:\My Servers\jboss-as-7.1.1.Final" (note the space in the path).
It starts just fine using the standalone.bat file within that folder. But if I try to start the server from within Eclipse using JBoss Tools (3.3.0 Beta 3), I get this error in the console:
java.lang.NoClassDefFoundError: F:/My
Caused by: java.lang.ClassNotFoundException: F:.My
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Exception in thread "main"
I've captured the command line used when I right-click on the server in Eclipse and Debug. Here it is (copied from Process Monitor's Process Tree):
"C:\Program Files\Java\jdk1.6.0_23\bin\javaw.exe" -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:63144 -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file= F:/My Servers/jboss-as-7.1.1.Final/standalone/log/boot.log Servers/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/F:/My%20Servers/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -Djboss.home.dir= F:/My Servers/jboss-as-7.1.1.Final Servers/jboss-as-7.1.1.Final -Dfile.encoding=Cp1252 -classpath "F:\My Servers\jboss-as-7.1.1.Final\jboss-modules.jar" org.jboss.modules.Main -mp "" F:/My Servers/jboss-as-7.1.1.Final/modules Servers/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11861) Deleting domain doesn't delete 'jbosstools' ssh key on OpenShift
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-11861:
--------------------------------------
Summary: Deleting domain doesn't delete 'jbosstools' ssh key on OpenShift
Key: JBIDE-11861
URL: https://issues.jboss.org/browse/JBIDE-11861
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.CR1
In order to recreate (create-delete-create) domain via JBT/JBDS the ssh key named 'jbosstools' must be deleted. Otherwise OpenShift returns
{code}
!MESSAGE Could not create domain "rhtestdomain"
!STACK 0
com.openshift.client.OpenShiftSSHKeyException: Could not add new key AAAAB3NzaC1yc2EAAAADAQABAAABAQC4gsImDDgWGzFb/h791LDbgRqGRQwv76rG0wvfXylqEDK52EkKH6Ikwbi9uYl5SxF7UO8EIx11pytQhhxkNQcSLJ8J8Zkg+s62oj5mmeojJUO6XarzAXGioELat+qDZlyDxbZJuXUM6x9AL8M8n5BfjPowq0Rqkw+gmbm1vkVfCloZWYLlivf+JI+7Kom9cgC+qJBjNqcawqNdkkdKXoEiIUHdppOzyJdY/xSTb7VFyGwEgl57Imtja2c4of9I2y8AFtd1OWK2bHrsXemCkqX24XeoV/0nBiNB4RbnDcv28U5f2zFiIhRcdtpg2x+G/zwTOd72tMU3C4aQGr5JBWg5 with the name jbosstools. There already is a key for this name, key names must be unique.
at com.openshift.internal.client.UserResource.putSSHKey(UserResource.java:182)
at org.jboss.tools.openshift.express.internal.core.console.UserDelegate.putSSHKey(UserDelegate.java:244)
at org.jboss.tools.openshift.express.internal.ui.wizard.NewDomainWizardPageModel.createDomain(NewDomainWizardPageModel.java:109)
at org.jboss.tools.openshift.express.internal.ui.wizard.NewDomainDialog$1.run(NewDomainDialog.java:46)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months