[JBoss JIRA] (JBIDE-18267) Errors when starting EAP 5.2 - problem with jmx agent
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18267?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18267:
--------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.CR1)
> Errors when starting EAP 5.2 - problem with jmx agent
> -----------------------------------------------------
>
> Key: JBIDE-18267
> URL: https://issues.jboss.org/browse/JBIDE-18267
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-b
> Fix For: 4.2.1.Final
>
>
> When I add EAP 5.2 using runtime detection and then start the server, I get errors in the console:
> {code}
> 15:07:25,729 INFO [JMXKernel] Legacy JMX core initialized
> javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> at sun.management.Agent.agentmain(Agent.java:95)
> 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.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> 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:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Exception thrown by the agent : javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> Exception in thread "Attach Listener" java.lang.reflect.InvocationTargetException
> 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.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.RuntimeException: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at sun.management.Agent.error(Agent.java:309)
> at sun.management.Agent.startAgent(Agent.java:153)
> at sun.management.Agent.agentmain(Agent.java:95)
> ... 6 more
> Caused by: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> 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:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Agent failed to start!
> {code}
> It's kind of strange, but it didn't happen at first. When I changed the server to compressed deployment, it started happening. So I wanted to check again in a new workspace. In the new workspace, I just added the server and start (with default - exploded wars) and it happened again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by fede pia (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
fede pia commented on JBIDE-18128:
----------------------------------
[~maxandersen] I've just seen your comment but as [~mmalina] posted in his comment I had exactly the same. If I build the project from the command line it works fine but if I build it from STS many .class files are missing. In my case, it happens for Jboss 7.1 and Wildfly 8.1.
Btw, now that Martin could reproduce the issue, do you still want me to test on a clean Eclipse 4.4 or it is no needed?
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip
>
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-18253:
----------------------------------
Labels: respin-b (was: respin-a)
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18253 at 9/8/14 11:47 AM:
-------------------------------------------------------------------
I can reproduce this:
I get an error dialog while the console shows that the server is started
!server-failed-started.png!
was (Author: adietish):
I can reproduce this:
I get an error dialog while the console shows the error started
!server-failed-started.png!
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18253:
---------------------------------------
[~adietish], I believe that's exactly the same that I'm seeing - the moment I click the start button, the error pops up, but behind it, the console is shown with the server starting.
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3113) After install, initial access of Help->About->?->About Your Installation logs error
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3113?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3113:
--------------------------------
Fix Version/s: 7.1.x
> After install, initial access of Help->About->?->About Your Installation logs error
> -----------------------------------------------------------------------------------
>
> Key: JBDS-3113
> URL: https://issues.jboss.org/browse/JBDS-3113
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 7.1.1.GA
> Environment: Version: 7.1.1.GA
> Build id: GA-v20140303-1841-B672
> Build date: 20140303-1841
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 7.1.x
>
>
> JBDS-2955 is fixed but now there are new errors:
> Still a (non-fatal) bug in beta3.respin-a:
> [ldimaggi@ldimaggi .metadata]$ more .log
> !SESSION 2014-07-18 14:41:55.380 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.eclipse.help.base 4 0 2014-07-18 14:43:03.690
> !MESSAGE An error occured while pre-processing help XHTML document "/org.eclipse.datatools.sqltools.doc.user/doc/html/asc1229700
> 427574.html" for search indexing
> !STACK 0
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; JAXP00010001: The parser has encountered more than "64000" entity
> expansions in this document; this is the limit imposed by the JDK.
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)
> at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:56)
> at org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLProcessor.java:49)
> at org.eclipse.help.internal.xhtml.DynamicXHTMLProcessor.process(DynamicXHTMLProcessor.java:76)
> at org.eclipse.help.internal.search.XHTMLSearchParticipant.preprocess(XHTMLSearchParticipant.java:106)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:297)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:52)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:231)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:628)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:602)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.help.base 4 0 2014-07-18 14:43:04.545
> !MESSAGE An error occured while pre-processing help XHTML document "/org.eclipse.jpt.doc.user/ref_details_orm.htm" for search in
> dexing
> !STACK 0
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; JAXP00010001: The parser has encountered more than "64000" entity
> expansions in this document; this is the limit imposed by the JDK.
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)
> at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:56)
> at org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLProcessor.java:49)
> at org.eclipse.help.internal.xhtml.DynamicXHTMLProcessor.process(DynamicXHTMLProcessor.java:76)
> at org.eclipse.help.internal.search.XHTMLSearchParticipant.preprocess(XHTMLSearchParticipant.java:106)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:297)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:52)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:231)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:628)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:602)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.help.base 4 4 2014-07-18 14:43:04.708
> !MESSAGE Help documentation could not be indexed completely.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2014-07-18 14:43:04.708
> !MESSAGE Help document /org.eclipse.zest.doc.isv/guide/guide.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2014-07-18 14:43:04.708
> !MESSAGE Exception occurred while adding document /org.eclipse.datatools.sqltools.doc.user/doc/html/asc1229700427574.html to ind
> ex.
> !STACK 0
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
> at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1019)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.ja
> va:510)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:298)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:52)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:231)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:628)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:602)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !SUBENTRY 1 org.eclipse.help.base 4 4 2014-07-18 14:43:04.708
> !MESSAGE Exception occurred while adding document /org.eclipse.jpt.doc.user/ref_details_orm.htm to index.
> !STACK 0
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
> at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1019)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.ja
> va:510)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:298)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:52)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:231)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:628)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:602)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18253 at 9/8/14 11:37 AM:
-------------------------------------------------------------------
I can reproduce this:
I get an error dialog while the console shows the error started
!server-failed-started.png!
was (Author: adietish):
I see this in a slightly different way:
I get an error dialog while the console shows the error started:
!server-failed-started.png!
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months