[jboss-jira] [JBoss JIRA] (WFLY-10143) Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar

Jeff Mesnil (JIRA) issues at jboss.org
Fri Mar 30 09:06:00 EDT 2018


    [ https://issues.jboss.org/browse/WFLY-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554450#comment-13554450 ] 

Jeff Mesnil commented on WFLY-10143:
------------------------------------

How do you reproduce the issue?

Are you experiencing this with WildFly 12.0.0.Final or the master branch?
There were recent changes to the client shade after the 12.0.0.Final tag in https://issues.jboss.org/browse/WFLY-10063

> Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar 
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10143
>                 URL: https://issues.jboss.org/browse/WFLY-10143
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 12.0.0.Final
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> If standalone JMS client is using only jboss-client.jar on classpath then during look up of connection factory fails with:
> {code}
> Exception in thread "Thread-0" java.lang.NoClassDefFoundError: javax/json/JsonValue
> 	at org.apache.activemq.artemis.uri.schema.connector.TCPTransportConfigurationSchema.getTransportConfigurations(TCPTransportConfigurationSchema.java:68)
> 	at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:44)
> 	at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:33)
> 	at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:86)
> 	at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:30)
> 	at org.apache.activemq.artemis.utils.uri.URIFactory.newObject(URIFactory.java:59)
> 	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.newLocator(ServerLocatorImpl.java:411)
> 	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:209)
> 	at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:202)
> 	at org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory.<init>(ActiveMQJMSConnectionFactory.java:34)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> 	at org.jboss.marshalling.reflect.SerializableClass.invokeConstructor(SerializableClass.java:340)
> 	at org.jboss.marshalling.reflect.SerializableClass.callNoArgConstructor(SerializableClass.java:292)
> 	at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1408)
> 	at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> 	at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> 	at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> 	at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> 	at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> 	at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> 	at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> 	at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> 	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> 	at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> 	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> 	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> 	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> 	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:417)
> 	at org.jboss.jms.client.ProducerTransAck.run(ProducerTransAck.java:78)
> Caused by: java.lang.ClassNotFoundException: javax.json.JsonValue
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 	... 33 more
> {code}
> This is because javax.json-api jar is missing. 
> Wildfly 12 jms-client-bom does not suffer by this issue. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list