[JBoss JIRA] (WFLY-9839) Incorrect lock management in infinispan
by Oleg K (JIRA)
Oleg K created WFLY-9839:
----------------------------
Summary: Incorrect lock management in infinispan
Key: WFLY-9839
URL: https://issues.jboss.org/browse/WFLY-9839
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate, Transactions
Affects Versions: 11.0.0.Final, 10.1.0.Final
Environment: Reproduced on Debian 8 GNU/Linux,
Java - openjdk version "1.8.0_131"
Reporter: Oleg K
Assignee: Scott Marlow
If we update one JPA entity with one id (primary key) in several transactions and refresh (via EntityManager.refresh call) loaded entity between them - infinispan does not release lock for the entity - so one can fail on timeout waiting for that lock to be released.
The root exception is:
org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 15 seconds for key 10 and requestor GlobalTransaction:<null>:6:local. Lock is held by GlobalTransaction:<null>:4:local
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAndRecord(AbstractLockingInterceptor.java:193)
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockKey(AbstractTxLockingInterceptor.java:193)
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockOrRegisterBackupLock(AbstractTxLockingInterceptor.java:116)
at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitDataWriteCommand(PessimisticLockingInterceptor.java:134)
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.visitPutKeyValueCommand(AbstractTxLockingInterceptor.java:65)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:367)
at org.infinispan.interceptors.TxInterceptor.visitPutKeyValueCommand(TxInterceptor.java:221)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:114)
at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:83)
at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:43)
at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:335)
at org.infinispan.cache.impl.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1672)
at org.infinispan.cache.impl.CacheImpl.putInternal(CacheImpl.java:1121)
at org.infinispan.cache.impl.CacheImpl.put(CacheImpl.java:1111)
at org.infinispan.cache.impl.DecoratedCache.put(DecoratedCache.java:453)
at org.infinispan.cache.impl.AbstractDelegatingCache.put(AbstractDelegatingCache.java:291)
at org.hibernate.cache.infinispan.access.TxInvalidationCacheAccessDelegate.update(TxInvalidationCacheAccessDelegate.java:67)
at org.hibernate.cache.infinispan.entity.ReadWriteAccess.update(ReadWriteAccess.java:29)
at org.hibernate.action.internal.EntityUpdateAction.cacheUpdate(EntityUpdateAction.java:222)
at org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:196)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:582)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:456)
at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:337)
at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39)
at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1282)
at org.hibernate.jpa.spi.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:1300)
at org.jboss.as.jpa.container.AbstractEntityManager.flush(AbstractEntityManager.java:459)
at wildfly.infinispan.test.MyEntityManagerEJB.updateMyEntity(MyEntityManagerEJB.java:36)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9837) Cannot register web service, fails with NullPointerException in DelegateClassLoader
by Antonio Chirizzi (JIRA)
[ https://issues.jboss.org/browse/WFLY-9837?page=com.atlassian.jira.plugin.... ]
Antonio Chirizzi updated WFLY-9837:
-----------------------------------
Description:
While deploying a EAR application, which contains a WAR which is trying to register a web service, I get the follwing exception:
{code}
13:53:34,624 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/standalone/data/wsdl/dms-new-ear-services-0.0.8.1.ear/dms-new-war-0.0.7.1.war/BusinessWebServiceService.wsdl
13:53:34,658 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client-5.1.9.Final.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-services-ws-discovery-api-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,773 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "dms-new-war-0.0.7.1.war" of deployment "dms-new-ear-services-0.0.8.1.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory could not be instantiated: java.lang.NullPointerException
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:204)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:152)
at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:232)
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:120)
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2180)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:85)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:217)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:160)
at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:129)
at org.jboss.wsf.stack.cxf.client.ProviderImpl$JBossWSServiceImpl.<init>(ProviderImpl.java:574)
at org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:258)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.tullettprebon.dms.tmmalternativeaddress.ws.TMMMarkitWireService.<init>(TMMMarkitWireService.java:60)
at com.tullettprebon.dms.webservices.ReferenceWebService.<init>(ReferenceWebService.java:232)
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:423)
at java.lang.Class.newInstance(Class.java:442)
at org.jboss.wsf.stack.cxf.configuration.BusHolder.newInstance(BusHolder.java:322)
at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:212)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
... 33 more
{code}
I wasted 3 days trying to find a solution thinking that the problem was in my dependencies with xerces or any other xml resolver.
Then I decided to checkout the code near the root cause:
{code}
Caused by: java.lang.NullPointerException
at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
... 33 more
{code}
and I think I have fixed a bug in {{jbossws-common-3.1.5}}.
I have downloaded the latest version of {{jbossws-common-master}} from github (with which the problem was still showing).
Then I fixed the class {{org/jboss/ws/common/utils/DelegateClassLoader.java}} changing this:
{code}
/** {@inheritDoc} */
@Override
public InputStream getResourceAsStream(final String name)
{
InputStream is = parent.getResourceAsStream(name);
return (is == null) ? delegate.getResourceAsStream(name) : is;
}
{code}
to this:
{code}
/** {@inheritDoc} */
@Override
public InputStream getResourceAsStream(final String name)
{
InputStream is = null;
if (parent != null)
{
is = parent.getResourceAsStream(name);
}
return (is == null) ? delegate.getResourceAsStream(name) : is;
}
{code}
and then built again the jbossws-common jar and replaced the (suspected) faulty one under the WildFly modules. With the new jar the webservice can be registered.
was:
While deploying a EAR application, which contains a WAR which is trying to register a web service, I get the follwing exception:
{code}
13:53:34,624 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/standalone/data/wsdl/dms-new-ear-services-0.0.8.1.ear/dms-new-war-0.0.7.1.war/BusinessWebServiceService.wsdl
13:53:34,658 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client-5.1.9.Final.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-services-ws-discovery-api-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
13:53:34,773 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "dms-new-war-0.0.7.1.war" of deployment "dms-new-ear-services-0.0.8.1.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory could not be instantiated: java.lang.NullPointerException
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:204)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:152)
at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:232)
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:120)
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2180)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:85)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:217)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:160)
at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:129)
at org.jboss.wsf.stack.cxf.client.ProviderImpl$JBossWSServiceImpl.<init>(ProviderImpl.java:574)
at org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:258)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.tullettprebon.dms.tmmalternativeaddress.ws.TMMMarkitWireService.<init>(TMMMarkitWireService.java:60)
at com.tullettprebon.dms.webservices.ReferenceWebService.<init>(ReferenceWebService.java:232)
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:423)
at java.lang.Class.newInstance(Class.java:442)
at org.jboss.wsf.stack.cxf.configuration.BusHolder.newInstance(BusHolder.java:322)
at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:212)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
... 33 more
{code}
I wasted 3 days trying to find a solution thinking that the problem was in my dependencies with xerces or any other xml resolver.
Then I decided to checkout the code near the root cause:
{code}
Caused by: java.lang.NullPointerException
at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
... 33 more
{code}
and I think I have fixed a bug in {{jbossws-common-3.1.5}}.
I have downloaded the latest version of {{jbossws-common-master}} from github (with which the problem was still showing).
Then I fixed the class {{org/jboss/ws/common/utils/DelegateClassLoader.java}} changing this:
{code}
/** {@inheritDoc} */
@Override
public InputStream getResourceAsStream(final String name)
{
InputStream is = parent.getResourceAsStream(name);
return (is == null) ? delegate.getResourceAsStream(name) : is;
}
{code}
to this:
{code}
/** {@inheritDoc} */
@Override
public InputStream getResourceAsStream(final String name)
{
InputStream is = null;
if (parent != null)
{
is = parent.getResourceAsStream(name);
}
return (is == null) ? delegate.getResourceAsStream(name) : is;
}
{code}
> Cannot register web service, fails with NullPointerException in DelegateClassLoader
> -----------------------------------------------------------------------------------
>
> Key: WFLY-9837
> URL: https://issues.jboss.org/browse/WFLY-9837
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 11.0.0.Final
> Reporter: Antonio Chirizzi
> Assignee: Alessio Soldano
>
> While deploying a EAR application, which contains a WAR which is trying to register a web service, I get the follwing exception:
> {code}
> 13:53:34,624 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/standalone/data/wsdl/dms-new-ear-services-0.0.8.1.ear/dms-new-war-0.0.7.1.war/BusinessWebServiceService.wsdl
> 13:53:34,658 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client-5.1.9.Final.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> 13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> 13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-services-ws-discovery-api-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar.
> 13:53:34,773 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "dms-new-war-0.0.7.1.war" of deployment "dms-new-ear-services-0.0.8.1.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory could not be instantiated: java.lang.NullPointerException
> at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:204)
> at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:152)
> at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:232)
> at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:120)
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2180)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
> at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
> at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
> at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:85)
> at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:217)
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:160)
> at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:129)
> at org.jboss.wsf.stack.cxf.client.ProviderImpl$JBossWSServiceImpl.<init>(ProviderImpl.java:574)
> at org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:258)
> at javax.xml.ws.Service.<init>(Service.java:57)
> at com.tullettprebon.dms.tmmalternativeaddress.ws.TMMMarkitWireService.<init>(TMMMarkitWireService.java:60)
> at com.tullettprebon.dms.webservices.ReferenceWebService.<init>(ReferenceWebService.java:232)
> 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:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.jboss.wsf.stack.cxf.configuration.BusHolder.newInstance(BusHolder.java:322)
> at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:212)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
> at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
> at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
> at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
> at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
> at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
> ... 33 more
> {code}
> I wasted 3 days trying to find a solution thinking that the problem was in my dependencies with xerces or any other xml resolver.
> Then I decided to checkout the code near the root cause:
> {code}
> Caused by: java.lang.NullPointerException
> at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132)
> at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147)
> at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102)
> at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98)
> at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103)
> at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192)
> ... 33 more
> {code}
> and I think I have fixed a bug in {{jbossws-common-3.1.5}}.
> I have downloaded the latest version of {{jbossws-common-master}} from github (with which the problem was still showing).
> Then I fixed the class {{org/jboss/ws/common/utils/DelegateClassLoader.java}} changing this:
> {code}
> /** {@inheritDoc} */
> @Override
> public InputStream getResourceAsStream(final String name)
> {
> InputStream is = parent.getResourceAsStream(name);
> return (is == null) ? delegate.getResourceAsStream(name) : is;
> }
> {code}
> to this:
> {code}
> /** {@inheritDoc} */
> @Override
> public InputStream getResourceAsStream(final String name)
> {
> InputStream is = null;
> if (parent != null)
> {
> is = parent.getResourceAsStream(name);
> }
> return (is == null) ? delegate.getResourceAsStream(name) : is;
> }
> {code}
> and then built again the jbossws-common jar and replaced the (suspected) faulty one under the WildFly modules. With the new jar the webservice can be registered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-16) Set Up Confluence Board
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-16:
---------------------------------
Summary: Set Up Confluence Board
Key: SWSQE-16
URL: https://issues.jboss.org/browse/SWSQE-16
Project: Swift Sunshine QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Prachi Yadav
Priority: Minor
* We could have meeting notes, sprint retrospective notes, we could reference JIRAs (QE and Dev board), create pages for tasks documentation even test plans could be created on Confluence
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9804) AuthenticationForwardingSFSFTestCase fails on JDK9
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9804?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-9804:
------------------------------
Labels: jdk9 (was: )
> AuthenticationForwardingSFSFTestCase fails on JDK9
> ---------------------------------------------------
>
> Key: WFLY-9804
> URL: https://issues.jboss.org/browse/WFLY-9804
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Darran Lofthouse
> Labels: jdk9
>
> AuthenticationForwardingSFSFTestCase test fails on JDK9 with
> {noformat}
> javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "/entry-ejb/EntryBeanSFSB!org.wildfly.test.manual.elytron.seccontext.Entry?stateful" [Root exception is org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available]
> at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:160)
> at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:84)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
> at org.wildfly.test.manual.elytron.seccontext.SeccontextUtil.lookup(SeccontextUtil.java:177)
> at org.wildfly.test.manual.elytron.seccontext.AbstractSecurityContextPropagationTestBase.lambda$getDoubleWhoAmICallable$0(AbstractSecurityContextPropagationTestBase.java:435)
> at org.wildfly.common.context.Contextual.runCallable(Contextual.java:127)
> at org.wildfly.test.manual.elytron.seccontext.AbstractAuthenticationForwardingTestCase.testClientOauthbearerInsufficientRolesFails(AbstractAuthenticationForwardingTestCase.java:154)
> .....
> Caused by: org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available
> at org.jboss.ejb.client.NamingEJBClientInterceptor.handleSessionCreation(NamingEJBClientInterceptor.java:100)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.TransactionInterceptor.handleSessionCreation(TransactionInterceptor.java:100)
> at org.jboss.ejb.client.EJBSessionCreationInvocationContext.proceed(EJBSessionCreationInvocationContext.java:70)
> at org.jboss.ejb.client.EJBClientContext.createSession(EJBClientContext.java:835)
> at org.jboss.ejb.client.EJBClient.createSessionProxy(EJBClient.java:198)
> at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:158)
> ... 137 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9824) Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
by shubhashish dash (JIRA)
[ https://issues.jboss.org/browse/WFLY-9824?page=com.atlassian.jira.plugin.... ]
shubhashish dash updated WFLY-9824:
-----------------------------------
Component/s: EJB
> Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9824
> URL: https://issues.jboss.org/browse/WFLY-9824
> Project: WildFly
> Issue Type: Bug
> Components: EE, EJB
> Affects Versions: 11.0.0.Beta1, 11.0.0.Final
> Reporter: shubhashish dash
> Priority: Critical
> Attachments: EAR.ear, server.log
>
>
> I have deployed a EAR in wildfly 11.0.0 Final. The EAR has two sub deplyoment one is a .rar and another is a .war . The both the deployment contains below code
> ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> final InitialContext initialContext = new InitialContext();
> final ManagementHome mejb = (ManagementHome) initialContext.lookup("ejb/mgmt/MEJB");
> final ObjectName searchpattern = new ObjectName("*:j2eeType=J2EEServer,*");
> final Management management = mejb.create();
> final Set<ObjectName> set = management.queryNames(searchpattern, null);
> if (set != null && set.size() != 0) {
> final String s = management.getAttribute(set.iterator().next(), "serverVendor").toString();
> System.out.println(s);
> }
> ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> But while running the application I am getting "javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB"" error. This error only comes in case of rar and not in the war.
> I have attached the sample app with this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro edited comment on WFLY-9746 at 2/15/18 9:52 AM:
-------------------------------------------------------------
You've specified configuration from the 2.0 schema, but are using the 3.0 schema. Remember that version 3.0 of the schema specified by this PR is different from the 3.0 schema included with the Artemis upgrade PR. If you use the configuration corresponding to the 2.0 schema as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
was (Author: pferraro):
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. Remember that version 3.0 of the schema specified by this PR is different from the 3.0 schema included with the Artemis upgrade PR. If you use the configuration corresponding to the 2.0 schema as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9824) Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
by shubhashish dash (JIRA)
[ https://issues.jboss.org/browse/WFLY-9824?page=com.atlassian.jira.plugin.... ]
shubhashish dash edited comment on WFLY-9824 at 2/15/18 9:52 AM:
-----------------------------------------------------------------
Hi David,
Could you please tell me why this is not a bug ? The same application running fine in version 11.0.0.Alpha1 and not in 11.0.0.Beta1 & 11.0.0 Final .
Thanks,
Shubhashish
was (Author: subhadash):
Hi David,
Could you please tell me why this is not a bug ? The same application running fine in version 11.0.0.Alpha1 and not in 11.0.0.Beta1 & 11.0.0 Final .
Thanks,
Shubhashish
> Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9824
> URL: https://issues.jboss.org/browse/WFLY-9824
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 11.0.0.Beta1, 11.0.0.Final
> Reporter: shubhashish dash
> Priority: Critical
> Attachments: EAR.ear, server.log
>
>
> I have deployed a EAR in wildfly 11.0.0 Final. The EAR has two sub deplyoment one is a .rar and another is a .war . The both the deployment contains below code
> ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> final InitialContext initialContext = new InitialContext();
> final ManagementHome mejb = (ManagementHome) initialContext.lookup("ejb/mgmt/MEJB");
> final ObjectName searchpattern = new ObjectName("*:j2eeType=J2EEServer,*");
> final Management management = mejb.create();
> final Set<ObjectName> set = management.queryNames(searchpattern, null);
> if (set != null && set.size() != 0) {
> final String s = management.getAttribute(set.iterator().next(), "serverVendor").toString();
> System.out.println(s);
> }
> ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> But while running the application I am getting "javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB"" error. This error only comes in case of rar and not in the war.
> I have attached the sample app with this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro edited comment on WFLY-9746 at 2/15/18 9:51 AM:
-------------------------------------------------------------
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. Remember that version 3.0 of the schema specified by this PR is different from the 3.0 schema included with the Artemis upgrade PR. If you use the configuration corresponding to the 2.0 schema as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
was (Author: pferraro):
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. Remember that the schema specified by this PR is different from the 3.0 schema included with the Artemis upgrade PR. If you use the configuration corresponding to the 2.0 schema as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro edited comment on WFLY-9746 at 2/15/18 9:50 AM:
-------------------------------------------------------------
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. Remember that the schema specified by this PR is different from the 3.0 schema included with the Artemis upgrade PR. If you use the configuration corresponding to the 2.0 schema as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
was (Author: pferraro):
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. If you used the configuration as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro edited comment on WFLY-9746 at 2/15/18 9:48 AM:
-------------------------------------------------------------
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. If you used the configuration as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
was (Author: pferraro):
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. If you used the configuration as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months