Eclipse Community Forums: TMF (Xtext) » Unable to run Xtext parser from JBoss 3.2.7

Help

Home

Home » Modeling » TMF (Xtext) » Unable to run Xtext parser from JBoss 3.2.7

Show: Today's Messages :: Show Polls :: Message Navigator

Unable to run Xtext parser from JBoss 3.2.7 [message #727982]

Thu, 22 September 2011 10:39

FJ Stöver

Messages: 25
Registered: July 2011
Location: Aachen, Germany

Junior Member

Dear colleagues,

When calling createInjectorAndDoEMFRegistration() I get exceptions - probably related to logging.

With the orignal JBoss 'log4j-boot' I got 'method not found' for 'isTraceEnabled()'; experimenting with a newer version of 'log4j-boot' I get an NPE - see the stack dump below.

Is there a way to handle this with JBoss 3.2.7? Or do I need to use a newer JBoss version? Can Xtext parsing be called through JBoss anyhow?

kind regards and thanks for your contribution

Franz-Josef
______________________
2011-09-22 11:53:09,796 ERROR [IA003] CompoundModule: IA003: null
java.lang.NullPointerException
at org.apache.log4j.Logger.isTraceEnabled(Logger.java:206)
at org.eclipse.xtext.service.MethodBasedModule.configure(MethodBasedModule.java:50)
at org.eclipse.xtext.service.CompoundModule.configure(CompoundModule.java:34)
at org.eclipse.xtext.service.AbstractGenericModule.configure(AbstractGenericModule.java:32)
at org.eclipse.xtext.service.DefaultRuntimeModule.configure(DefaultRuntimeModule.java:74)
at de.topsystem.base.AbstractBaseRuntimeModule.configure(AbstractBaseRuntimeModule.java:25)
at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
at com.google.inject.spi.Elements.getElements(Elements.java:101)
at com.google.inject.InjectorShell$Builder.build(InjectorShell.java:135)
at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:102)
at com.google.inject.Guice.createInjector(Guice.java:92)
at com.google.inject.Guice.createInjector(Guice.java:69)
at com.google.inject.Guice.createInjector(Guice.java:59)
at de.topsystem.base.BaseStandaloneSetupGenerated.createInjector(BaseStandaloneSetupGenerated.java:34)
at de.topsystem.base.BaseStandaloneSetupGenerated.createInjectorAndDoEMFRegistration(BaseStandaloneSetupGenerated.java:28)
at de.topsystem.base.BaseStandaloneSetup.doSetup(BaseStandaloneSetup.java:23)
at de.topsystem.base.BaseStandaloneSetup.Test2(BaseStandaloneSetup.java:55)
at de.topsystem.common.message_broker.interface_adapter.logical.xtext_parser.NewSitaParserInterfaceLogic.handleLogic(Unknown Source)
at de.topsystem.common.message_broker.interface_adapter.logical.AbstractBaseAdapterLogic.run(AbstractBaseAdapterLogic.java:100)
at de.topsystem.common.message_broker.jmx.MBRunnable.run(MBRunnable.java:83)
at de.topsystem.common.message_broker.LoggingThread$1.run(LoggingThread.java:41)
at java.lang.Thread.run(Unknown Source)
at de.topsystem.common.message_broker.LoggingThread.run(LoggingThread.java:51)

A lot of similar ones follow and finally a lot of these which are caused by the errors before I guess:

1) No implementation for org.eclipse.xtext.IGrammarAccess was bound.
while locating org.eclipse.xtext.IGrammarAccess
for parameter 0 at org.eclipse.xtext.parsetree.reconstr.impl.DefaultHiddenTokenHelper.setGrammar(DefaultHiddenTokenHelper.java:20)
at org.eclipse.xtext.parsetree.reconstr.impl.DefaultHiddenTokenHelper.setGrammar(DefaultHiddenTokenHelper.java:20)
while locating org.eclipse.xtext.parsetree.reconstr.IHiddenTokenHelper
for field at org.eclipse.xtext.parsetree.reconstr.impl.TokenUtil.hiddenTokenHelper(TokenUtil.java:33)
while locating org.eclipse.xtext.parsetree.reconstr.impl.TokenUtil
for field at org.eclipse.xtext.serializer.tokens.CrossReferenceSerializer.tokenUtil(CrossReferenceSerializer.java:38)
while locating org.eclipse.xtext.serializer.tokens.ICrossReferenceSerializer
for field at org.eclipse.xtext.serializer.acceptor.SequenceFeeder$Provider.crossRefSerializer(SequenceFeeder.java:42)
while locating org.eclipse.xtext.serializer.acceptor.SequenceFeeder$Provider
for field at org.eclipse.xtext.serializer.sequencer.AbstractSemanticSequencer.feederProvider(AbstractSemanticSequencer.java:22)
at org.eclipse.xtext.service.DefaultRuntimeModule.configureGenericSemanticSequencer(DefaultRuntimeModule.java:219)

Report message to a moderator

Re: Unable to run Xtext parser from JBoss 3.2.7 [message #728266 is a reply to message #727982]

Thu, 22 September 2011 20:13

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

Hi Franz-Josef,

please make sure to use org.apache.log4j 1.2.15.

Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

On 22.09.11 12:39, Franz-Josef t wrote:
> Dear colleagues,
>
> When calling createInjectorAndDoEMFRegistration() I get exceptions -
> probably related to logging.
>
> With the orignal JBoss 'log4j-boot' I got 'method not found' for
> 'isTraceEnabled()'; experimenting with a newer version of 'log4j-boot' I
> get an NPE - see the stack dump below.
>
> Is there a way to handle this with JBoss 3.2.7? Or do I need to use a
> newer JBoss version? Can Xtext parsing be called through JBoss anyhow?
> kind regards and thanks for your contribution
>
> Franz-Josef
> ______________________
> 2011-09-22 11:53:09,796 ERROR [IA003] CompoundModule: IA003: null
> java.lang.NullPointerException
> at org.apache.log4j.Logger.isTraceEnabled(Logger.java:206)
> at
> org.eclipse.xtext.service.MethodBasedModule.configure(MethodBasedModule.java:50)
>
> at
> org.eclipse.xtext.service.CompoundModule.configure(CompoundModule.java:34)
> at
> org.eclipse.xtext.service.AbstractGenericModule.configure(AbstractGenericModule.java:32)
>
> at
> org.eclipse.xtext.service.DefaultRuntimeModule.configure(DefaultRuntimeModule.java:74)
>
> at
> de.topsystem.base.AbstractBaseRuntimeModule.configure(AbstractBaseRuntimeModule.java:25)
>
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at com.google.inject.InjectorShell$Builder.build(InjectorShell.java:135)
> at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:102)
> at com.google.inject.Guice.createInjector(Guice.java:92)
> at com.google.inject.Guice.createInjector(Guice.java:69)
> at com.google.inject.Guice.createInjector(Guice.java:59)
> at
> de.topsystem.base.BaseStandaloneSetupGenerated.createInjector(BaseStandaloneSetupGenerated.java:34)
>
> at
> de.topsystem.base.BaseStandaloneSetupGenerated.createInjectorAndDoEMFRegistration(BaseStandaloneSetupGenerated.java:28)
>
> at
> de.topsystem.base.BaseStandaloneSetup.doSetup(BaseStandaloneSetup.java:23)
> at de.topsystem.base.BaseStandaloneSetup.Test2(BaseStandaloneSetup.java:55)
> at
> de.topsystem.common.message_broker.interface_adapter.logical.xtext_parser.NewSitaParserInterfaceLogic.handleLogic(Unknown
> Source)
> at
> de.topsystem.common.message_broker.interface_adapter.logical.AbstractBaseAdapterLogic.run(AbstractBaseAdapterLogic.java:100)
>
> at
> de.topsystem.common.message_broker.jmx.MBRunnable.run(MBRunnable.java:83)
> at
> de.topsystem.common.message_broker.LoggingThread$1.run(LoggingThread.java:41)
>
> at java.lang.Thread.run(Unknown Source)
> at
> de.topsystem.common.message_broker.LoggingThread.run(LoggingThread.java:51)
>
> A lot of similar ones follow and finally a lot of these which are caused
> by the errors before I guess:
> 1) No implementation for org.eclipse.xtext.IGrammarAccess was bound.
> while locating org.eclipse.xtext.IGrammarAccess
> for parameter 0 at
> org.eclipse.xtext.parsetree.reconstr.impl.DefaultHiddenTokenHelper.setGrammar(DefaultHiddenTokenHelper.java:20)
>
> at
> org.eclipse.xtext.parsetree.reconstr.impl.DefaultHiddenTokenHelper.setGrammar(DefaultHiddenTokenHelper.java:20)
>
> while locating org.eclipse.xtext.parsetree.reconstr.IHiddenTokenHelper
> for field at
> org.eclipse.xtext.parsetree.reconstr.impl.TokenUtil.hiddenTokenHelper(TokenUtil.java:33)
>
> while locating org.eclipse.xtext.parsetree.reconstr.impl.TokenUtil
> for field at
> org.eclipse.xtext.serializer.tokens.CrossReferenceSerializer.tokenUtil(CrossReferenceSerializer.java:38)
>
> while locating
> org.eclipse.xtext.serializer.tokens.ICrossReferenceSerializer
> for field at
> org.eclipse.xtext.serializer.acceptor.SequenceFeeder$Provider.crossRefSerializer(SequenceFeeder.java:42)
>
> while locating
> org.eclipse.xtext.serializer.acceptor.SequenceFeeder$Provider
> for field at
> org.eclipse.xtext.serializer.sequencer.AbstractSemanticSequencer.feederProvider(AbstractSemanticSequencer.java:22)
>
> at
> org.eclipse.xtext.service.DefaultRuntimeModule.configureGenericSemanticSequencer(DefaultRuntimeModule.java:219)
>

Report message to a moderator

Re: Unable to run Xtext parser from JBoss 3.2.7 [message #728449 is a reply to message #728266]

Fri, 23 September 2011 09:53

FJ Stöver

Messages: 25
Registered: July 2011
Location: Aachen, Germany

Junior Member

Good morning Sebastian,

Thank you for your contribution.

It seems the problem cannot be solved that easy.

I've experimented a bit and changed the log4j jar in the JBoss server lib, and printed loggers jar file path:

1) Using org.apache.log4j_1.2.15.v201012070815.jar:
> Logger was loaded from here: 'D:\Programme\java\jboss-3.2.7\lib\log4j-boot.jar'
Please note the 'boot'in the file name! (When JBoss starts it brings it's own log4j with it - namely the one contained in 'log4j-boot'. That's actually a 'normal' log4J with additional functions)

2) Renamed org.apache.log4j_1.2.15.v201012070815.jar to log4j.jar
> Logger was loaded from here: 'D:\Programme\java\jboss-3.2.7\server\xxxxxx\lib\log4j.jar'.
It took the correct (and renamed) one (1.2.15) I think.

Hewever when our program is started by JBoss it is able to write to that logger - but when it calls parser.parse() from Xtext environment the mentioned NPE is raised.

Any idea?

kind regards Franz-Josef

Report message to a moderator

Re: Unable to run Xtext parser from JBoss 3.2.7 [message #730804 is a reply to message #728449]

Thu, 29 September 2011 08:09

FJ Stöver

Messages: 25
Registered: July 2011
Location: Aachen, Germany

Junior Member

Dear colleagues,

meanwhile we are able to run Xtext (2.1) in jBoss 3.2.7.

* We had to replace log4j-boot.jar with one from jBoss 4.2.2
* There was a problem with a proprietary component that mimicked log4j

We had no problems to run Xtext under jBoss 7.0

kind regards Franz-Josef

Report message to a moderator

Previous Topic:	Re: Referencing models defined in files outside of eclipse
Next Topic:	XText & Validation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Sep 19 02:45:53 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter