[JBoss JIRA] (JBIDE-13160) Error connecting to jmx for EAP 5.1.2
by Martin Malina (JIRA)
Martin Malina created JBIDE-13160:
-------------------------------------
Summary: Error connecting to jmx for EAP 5.1.2
Key: JBIDE-13160
URL: https://issues.jboss.org/browse/JBIDE-13160
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.CR1
Environment: JBDS 6.0.0.CR1a B133
OS X 10.8.2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
I am unable to connect to JMX with EAP 5.1.2
The error:
{code}
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-11-27 16:32:24.946
!MESSAGE Error connecting to remote JMX. Please ensure your server is properly configured for JMX access.
!STACK 0
java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:416)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:248)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy105.getDomains(Unknown Source)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.createConnection(JBossServerConnection.java:171)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:233)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:225)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
Note that this is a local server and the password was set accordingly in the server editor (admin=admin) and the admin definition was enabled in jboss-as/server/default/conf/props/jmx-console-users.properties and I confirmed it worked through the web interface.
--
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, 4 months
[JBoss JIRA] (JBIDE-13135) Remote System Deployment doesn't work for EAP 5.1 from Windows to Linux
by Martin Malina (JIRA)
Martin Malina created JBIDE-13135:
-------------------------------------
Summary: Remote System Deployment doesn't work for EAP 5.1 from Windows to Linux
Key: JBIDE-13135
URL: https://issues.jboss.org/browse/JBIDE-13135
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.CR1
Environment: Windows XP 32 bit
JBoss EAP 5.1.1
JBDS 6.0.0.CR1 B111
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
While verifying JBIDE-11681 I also tried to set up a remote EAP 5.1 from Windows to Linux. Server start fails.
The problem is that '\' is used in many places of the start command.
This is what ps displays:
{code}
16628 pts/1 Sl 0:00 \_ java -Dprogram.name=JBossTools: jboss-eap-5.1.1 Runtime -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=\home\rasp\jbossqa\runtimes\jboss-eap-5.1.1\jboss-as\lib\endorsed -Djava.library.path=\home\rasp\jbossqa\runtimes\jboss-eap-5.1.1\jboss-as\bin\native -classpath /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/bin/run.jar org.jboss.Main --configuration=default -b MARVIN.BRQ.REDHAT.COM -Djboss.server.base.url=file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver
{code}
When I tried to run this command manually, this is what I got:
{code}
15:22:05,089 INFO [ServerImpl] Starting JBoss (Microcontainer)...
15:22:05,090 INFO [ServerImpl] Release ID: JBoss [EAP] 5.1.1 (build: SVNTag=JBPAPP_5_1_1 date=201105171607)
15:22:05,091 INFO [ServerImpl] Bootstrap URL: null
15:22:05,091 INFO [ServerImpl] Home Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as
15:22:05,091 INFO [ServerImpl] Home URL: file:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/
15:22:05,091 INFO [ServerImpl] Library URL: file:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/lib/
15:22:05,092 INFO [ServerImpl] Patch URL: null
15:22:05,092 INFO [ServerImpl] Common Base URL: file:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/common/
15:22:05,102 INFO [ServerImpl] Common Library URL: file:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/common/lib/
15:22:05,102 INFO [ServerImpl] Server Name: default
15:22:05,102 INFO [ServerImpl] Server Base Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server
15:22:05,103 INFO [ServerImpl] Server Base URL: file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/
15:22:05,103 INFO [ServerImpl] Server Config URL: file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/conf/
15:22:05,103 INFO [ServerImpl] Server Home Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default
15:22:05,103 INFO [ServerImpl] Server Home URL: file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/
15:22:05,103 INFO [ServerImpl] Server Data Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default/data
15:22:05,103 INFO [ServerImpl] Server Library URL: file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/lib/
15:22:05,103 INFO [ServerImpl] Server Log Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default/log
15:22:05,104 INFO [ServerImpl] Server Native Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default/tmp/native
15:22:05,104 INFO [ServerImpl] Server Temp Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default/tmp
15:22:05,104 INFO [ServerImpl] Server Temp Deploy Dir: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.1/jboss-as/server/default/tmp/deploy
15:22:08,410 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/conf/bootstrap.xml
Failed to boot JBoss:
java.lang.RuntimeException: Error unmarshalling file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/conf/bootstrap.xml
at org.jboss.bootstrap.xml.BootstrapParser.parse(BootstrapParser.java:60)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:123)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:679)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: file:homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/conf/bootstrap.xml
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:119)
at org.jboss.bootstrap.xml.BootstrapParser.parse(BootstrapParser.java:53)
... 5 more
Caused by: java.io.FileNotFoundException: homeraspjbossqaruntimesjboss-eap-5.1.1jboss-asserver/default/conf/bootstrap.xml
at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:105)
at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:112)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173)
... 7 more
15:22:09,540 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
15:22:09,619 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
{code}
As you can see the backslashes get removed and so the paths are wrong.
--
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, 4 months
[JBoss JIRA] (JBIDE-13154) Disable Maven conversion via the M2 Facet for Seam 2.3 projects
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-13154:
-----------------------------------
Summary: Disable Maven conversion via the M2 Facet for Seam 2.3 projects
Key: JBIDE-13154
URL: https://issues.jboss.org/browse/JBIDE-13154
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Beta2
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.0.0.CR1
Mavenification of Seam 2.x projects via the M2 Facet contains lots of hardcoded stuff for dependencies / layout / everything.
We decided Seam 2.3 conversion support was out of scope of such conversion mechanism, as it would have required significant refactoring of the existing code for little to no benefit.
As a consequence, the Seam part of the M2 conversion will be restricted to Seam [2.0, 2.3).
The preferred way of converting Maven projects is to right-click on project > Configure > Convert to Maven.
--
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, 4 months
[JBoss JIRA] (JBIDE-13164) test failure in org.jboss.tools.seam.core.test.SeamEARTest.testEarProject (from org.jboss.tools.seam.core.test.SeamCoreAllTests) : War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13164:
----------------------------------
Summary: test failure in org.jboss.tools.seam.core.test.SeamEARTest.testEarProject (from org.jboss.tools.seam.core.test.SeamCoreAllTests) : War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project
Key: JBIDE-13164
URL: https://issues.jboss.org/browse/JBIDE-13164
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.0.0.CR1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 4.0.0.CR1
Test failure / regression.
Build #50 was blue:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/50/testReport/org.jboss.tools.seam.core.test/SeamEARTest/testEarProject/}
Passed
org.jboss.tools.seam.core.test.SeamEARTest.testEarProject (from org.jboss.tools.seam.core.test.SeamCoreAllTests)
{code}
Now, build #53 is red:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/53/testReport/org.jboss.tools.seam.core.test/SeamEARTest/testEarProject/}
Failed
org.jboss.tools.seam.core.test.SeamEARTest.testEarProject (from org.jboss.tools.seam.core.test.SeamCoreAllTests)
Failing for the past 2 builds (Since Failed#52 )
Took 6.1 sec.
add description
Error Message
War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project
Stacktrace
junit.framework.AssertionFailedError: War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.SeamEARTest.testEarProject(SeamEARTest.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
{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, 4 months
[JBoss JIRA] (JBIDE-13136) Deployment tab of server editor is always disabled
by Martin Malina (JIRA)
Martin Malina created JBIDE-13136:
-------------------------------------
Summary: Deployment tab of server editor is always disabled
Key: JBIDE-13136
URL: https://issues.jboss.org/browse/JBIDE-13136
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.CR1
Environment: JBDS 6.0.0.CR1 B111
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
The Deployment tab of server editor is disabled even if it shouldn't be.
Just add a AS 7.1.1 server and you'll see it (no projects needed).
This may be a regression from JBIDE-13033
I saw this in two different instances of JBDS so hopefully you will be able to replicate this.
--
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, 4 months