[JBoss JIRA] (JASSIST-268) Gettig Java.lang.VerifyError with Latest Javassist, Powermock 1.7 and Java 1.8
by Pedro Cerejo (JIRA)
[ https://issues.jboss.org/browse/JASSIST-268?page=com.atlassian.jira.plugi... ]
Pedro Cerejo commented on JASSIST-268:
--------------------------------------
I'm also encountering the same error. In my case the error appears when i use the appendBefore method, with a for that has a continue, like a simple for:
{code:java}
for(int i = 0; i < beforeMethods.length; i++) {
continue;
}
{code}
for methods with more than one argument.
I'm assuming that has something to do with labels but i know nothing about bytecode so don't quote me on that.
> Gettig Java.lang.VerifyError with Latest Javassist, Powermock 1.7 and Java 1.8
> ------------------------------------------------------------------------------
>
> Key: JASSIST-268
> URL: https://issues.jboss.org/browse/JASSIST-268
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.20.0-GA
> Environment: All
> Reporter: Rajesh Eagambaram
> Assignee: Shigeru Chiba
>
> Hi Team,
> We have our current JUnit development completed using Java 1.6 using Powermock1.7 and Javaassist 3.20.0-GA and it is working fine. When we upgrade the JDK to 1.8 we are getting the error "Java.lang.VerifyError: Expecting a stackmap frame at branch target 64".
> Please help to fix the issue
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JGRP-2264) JGRP000012 with SAP Hybris default config
by Diana Haase (JIRA)
Diana Haase created JGRP-2264:
---------------------------------
Summary: JGRP000012 with SAP Hybris default config
Key: JGRP-2264
URL: https://issues.jboss.org/browse/JGRP-2264
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.11
Reporter: Diana Haase
Assignee: Bela Ban
A lot of discarted messages in console.log of Hybris Clusters
[UDP] | JGRP000012: discarded message from different cluster ...
[UDP] | JGRP000012: discarded message from different cluster dev-hybris-broadcast (our cluster is con-hybris-broadcast). Sender was xxxxx (received 724 identical messages from xxxx in the last 60347 ms)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (WFLY-10293) IllegalStateException when instantiating CDI bean that is injected into a MDB
by Rich DiCroce (JIRA)
Rich DiCroce created WFLY-10293:
-----------------------------------
Summary: IllegalStateException when instantiating CDI bean that is injected into a MDB
Key: WFLY-10293
URL: https://issues.jboss.org/browse/WFLY-10293
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 12.0.0.Final
Reporter: Rich DiCroce
I have a MDB that injects an ApplicationScoped CDI bean and calls a method on it. The CDI bean injects UserTransaction, which is used in a second method that is never invoked by the MDB.
If it happens that the MDB is the first thing to call the CDI bean, Weld tries to instantiate the bean and fails with WFLYEJB0137. IMO this should succeed since it works as long as something else is the first thing to use the CDI bean.
{code}
2018-04-24 08:17:38,429 ERROR [com.sgi.song.gp.service.SONGv1.event.EventQueueHelper$Proxy$_$$_WeldSubclass] (Thread-9 (ActiveMQ-client-global-threads)) Error processing event publish. Event data is
EventQueueData [event=EventPublish{id=1524572231949-1446, type=Client-Connected, data=null, level=1, timestamp=2018-04-24T12:17:38.415Z, properties={group=CCA, name=ACE2D30CC916, class=CA, macAddress=ACE2D30CC916, site=46673101, jurisdiction=MD, remoteIP=10.230.56.210, remotePort=51032, known=true, rejected=false, NMS_showInCMC=false}}, requestId=null, source=GP.GP_QTS_2.GP.0050569A2F9E.QTS.MD, rsvp=false]: java.lang.IllegalArgumentException: WFLYWELD0049: Error injecting resource into CDI managed bean. Can't find a resource named java:comp/UserTransaction defined on private javax.transaction.UserTransaction com.sgi.song.gp.service.SONGv1.event.SONGEventDAO.tx
at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:239)
at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices$1.createResource(WeldResourceInjectionServices.java:183)
at org.jboss.weld.injection.AbstractResourceInjection.getResourceReference(AbstractResourceInjection.java:49) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.injection.AbstractResourceInjection.injectResourceReference(AbstractResourceInjection.java:63) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.util.Beans.injectEEFields(Beans.java:308) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.injection.producer.ResourceInjector$1.proceed(ResourceInjector.java:68) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:71) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:117) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:159) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:102) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:105) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at com.sgi.song.gp.service.SONGv1.event.SONGEventDAO$Proxy$_$$_WeldClientProxy.findEvent(Unknown Source) [classes:]
at com.sgi.song.gp.service.SONGv1.event.EventQueueHelper.processEvent(EventQueueHelper.java:172) [classes:]
at com.sgi.song.gp.service.SONGv1.event.EventQueueHelper.processEvent(EventQueueHelper.java:128) [classes:]
at com.sgi.song.gp.service.SONGv1.event.EventQueueHelper$Proxy$_$$_WeldSubclass.processEvent$$super(Unknown Source) [classes:]
at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) [:1.8.0_144]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:132) [narayana-jts-idlj-5.5.31.Final.jar:5.5.31.Final (revision: 78792)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.doIntercept(TransactionalInterceptorMandatory.java:59) [narayana-jts-idlj-5.5.31.Final.jar:5.5.31.Final (revision: 78792)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:79) [narayana-jts-idlj-5.5.31.Final.jar:5.5.31.Final (revision: 78792)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:51) [narayana-jts-idlj-5.5.31.Final.jar:5.5.31.Final (revision: 78792)]
at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) [:1.8.0_144]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at com.sgi.song.gp.service.SONGv1.event.EventQueueHelper$Proxy$_$$_WeldSubclass.processEvent(Unknown Source) [classes:]
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) [:1.8.0_144]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final]
at com.sgi.song.gp.service.SONGv1.event.EventQueueHelper$Proxy$_$$_WeldClientProxy.processEvent(Unknown Source) [classes:]
at com.sgi.song.gp.service.SONGv1.event.EventQueueProcessor.onMessage(EventQueueProcessor.java:35) [classes:]
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) [:1.8.0_144]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)
at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:253) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:332) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.0.3.Final.jar:3.0.3.Final]
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:243) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
at com.sgi.song.gp.service.SONGv1.event.EventQueueProcessor$$$view2.onMessage(Unknown Source) [classes:]
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) [:1.8.0_144]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at com.sgi.song.gp.service.SONGv1.event.EventQueueProcessor$$$endpoint1.onMessage(Unknown Source) [classes:]
at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:303)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124)
at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_144]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_144]
Caused by: javax.naming.NameNotFoundException: UserTransaction [Root exception is java.lang.IllegalStateException: WFLYEJB0137: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:239) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
at javax.naming.InitialContext.lookup(Unknown Source) [rt.jar:1.8.0_144]
at javax.naming.InitialContext.lookup(Unknown Source) [rt.jar:1.8.0_144]
at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:237)
... 119 more
Caused by: java.lang.IllegalStateException: WFLYEJB0137: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction
at org.jboss.as.ejb3.component.allowedmethods.AllowedMethodsInformation.realCheckPermission(AllowedMethodsInformation.java:138) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.ejb3.component.allowedmethods.AllowedMethodsInformation.checkAllowed(AllowedMethodsInformation.java:112) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.ejb3.subsystem.EJB3UserTransactionAccessControlService$1.authorizeAccess(EJB3UserTransactionAccessControlService.java:53) [wildfly-ejb3-12.0.0.Final.jar:12.0.0.Final]
at org.jboss.as.txn.service.UserTransactionAccessControlService.authorizeAccess(UserTransactionAccessControlService.java:83)
at org.jboss.as.txn.service.UserTransactionBindingService$1.getReference(UserTransactionBindingService.java:71)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143) [wildfly-naming-12.0.0.Final.jar:12.0.0.Final]
... 128 more
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (SWSQE-179) Repair B21 Openshift Cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-179?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-179:
-----------------------------------------------
PLEG was corrected; We need to upgrade B21 to Openshift 3.9
> Repair B21 Openshift Cluster
> ----------------------------
>
> Key: SWSQE-179
> URL: https://issues.jboss.org/browse/SWSQE-179
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Guilherme Baufaker Rêgo
> Priority: Blocker
>
> NAME STATUS AGE VERSION
> b06.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b16.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b18.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b21.jonqe.lab.eng.bos.redhat.com NotReady 85d v1.7.6+a08f5eeb62
> {panel:title=b21}
> oc describe node b21.jonqe.lab.eng.bos.redhat.com 1 ↵ 10571 09:40:42
> Name: b21.jonqe.lab.eng.bos.redhat.com
> Role:
> Labels: beta.kubernetes.io/arch=amd64
> beta.kubernetes.io/os=linux
> kubernetes.io/hostname=b21.jonqe.lab.eng.bos.redhat.com
> openshift-infra=apiserver
> region=infra
> zone=default
> Annotations: volumes.kubernetes.io/controller-managed-attach-detach=true
> Taints: <none>
> CreationTimestamp: Sun, 28 Jan 2018 09:01:00 -0200
> Conditions:
> Type Status LastHeartbeatTime LastTransitionTime Reason Message
> ---- ------ ----------------- ------------------ ------ -------
> OutOfDisk False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientDisk kubelet has sufficient disk space available
> MemoryPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientMemory kubelet has sufficient memory available
> DiskPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasNoDiskPressure kubelet has no disk pressure
> Ready False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 22 Apr 2018 18:28:43 -0300 KubeletNotReady PLEG is not healthy: pleg was last seen active 15h17m29.5748908s ago; threshold is 3m0s
> Addresses:
> InternalIP: 10.16.23.44
> Hostname: b21.jonqe.lab.eng.bos.redhat.com
> Capacity:
> cpu: 24
> memory: 65757652Ki
> pods: 240
> Allocatable:
> cpu: 24
> memory: 65655252Ki
> pods: 240
> System Info:
> Machine ID: b1d9d75ab38b42d095ccf0e9ebe3a2d7
> System UUID: 4C4C4544-0050-4D10-8059-C8C04F4C3032
> Boot ID: cff20a97-dbf1-4bfa-b9b2-0face47d2646
> Kernel Version: 3.10.0-693.17.1.el7.x86_64
> OS Image: Red Hat Enterprise Linux Server 7.4 (Maipo)
> Operating System: linux
> Architecture: amd64
> Container Runtime Version: docker://1.12.6
> Kubelet Version: v1.7.6+a08f5eeb62
> Kube-Proxy Version: v1.7.6+a08f5eeb62
> ExternalID: b21.jonqe.lab.eng.bos.redhat.com
> Non-terminated Pods: (24 in total)
> Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
> --------- ---- ------------ ---------- --------------- -------------
> hayk-test mongodb-1-gflrd 0 (0%) 0 (0%) 512Mi (0%) 512Mi (0%)
> kiali-test-box kiali-test-service-b-qs5tv 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-box kiali-test-service-e-jw56k 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-a-hmh8t 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-c-svxgs 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-e-6fchg 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breath kiali-test-service-c-czxr5 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breath kiali-test-service-e-cr88j 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle-callback kiali-test-service-b-zljtr 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle-callback kiali-test-service-e-8f6rt 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle kiali-test-service-c-28d5h 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle kiali-traffic-generator-lglth 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-test-service-b-xq8ff 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-test-service-e-nnnxw 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-traffic-generator-fd786 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth kiali-test-service-c-nch7m 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth kiali-traffic-generator-vqmg9 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-hourglass kiali-test-service-b-j89jp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-hourglass kiali-test-service-e-6r77d 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kube-service-catalog apiserver-566mp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kube-service-catalog controller-manager-sqmlh 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> openshift-infra hawkular-metrics-xp9hl 0 (0%) 0 (0%) 1500M (2%) 2500M (3%)
> openshift-template-service-broker apiserver-rntz8 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> react-test-demo git-explorer-4-8bdzh 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> {panel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (SWSQE-179) Repair B21 Openshift Cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-179?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo resolved SWSQE-179.
-------------------------------------------
Resolution: Done
> Repair B21 Openshift Cluster
> ----------------------------
>
> Key: SWSQE-179
> URL: https://issues.jboss.org/browse/SWSQE-179
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Guilherme Baufaker Rêgo
> Priority: Blocker
>
> NAME STATUS AGE VERSION
> b06.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b16.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b18.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62
> b21.jonqe.lab.eng.bos.redhat.com NotReady 85d v1.7.6+a08f5eeb62
> {panel:title=b21}
> oc describe node b21.jonqe.lab.eng.bos.redhat.com 1 ↵ 10571 09:40:42
> Name: b21.jonqe.lab.eng.bos.redhat.com
> Role:
> Labels: beta.kubernetes.io/arch=amd64
> beta.kubernetes.io/os=linux
> kubernetes.io/hostname=b21.jonqe.lab.eng.bos.redhat.com
> openshift-infra=apiserver
> region=infra
> zone=default
> Annotations: volumes.kubernetes.io/controller-managed-attach-detach=true
> Taints: <none>
> CreationTimestamp: Sun, 28 Jan 2018 09:01:00 -0200
> Conditions:
> Type Status LastHeartbeatTime LastTransitionTime Reason Message
> ---- ------ ----------------- ------------------ ------ -------
> OutOfDisk False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientDisk kubelet has sufficient disk space available
> MemoryPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientMemory kubelet has sufficient memory available
> DiskPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasNoDiskPressure kubelet has no disk pressure
> Ready False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 22 Apr 2018 18:28:43 -0300 KubeletNotReady PLEG is not healthy: pleg was last seen active 15h17m29.5748908s ago; threshold is 3m0s
> Addresses:
> InternalIP: 10.16.23.44
> Hostname: b21.jonqe.lab.eng.bos.redhat.com
> Capacity:
> cpu: 24
> memory: 65757652Ki
> pods: 240
> Allocatable:
> cpu: 24
> memory: 65655252Ki
> pods: 240
> System Info:
> Machine ID: b1d9d75ab38b42d095ccf0e9ebe3a2d7
> System UUID: 4C4C4544-0050-4D10-8059-C8C04F4C3032
> Boot ID: cff20a97-dbf1-4bfa-b9b2-0face47d2646
> Kernel Version: 3.10.0-693.17.1.el7.x86_64
> OS Image: Red Hat Enterprise Linux Server 7.4 (Maipo)
> Operating System: linux
> Architecture: amd64
> Container Runtime Version: docker://1.12.6
> Kubelet Version: v1.7.6+a08f5eeb62
> Kube-Proxy Version: v1.7.6+a08f5eeb62
> ExternalID: b21.jonqe.lab.eng.bos.redhat.com
> Non-terminated Pods: (24 in total)
> Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
> --------- ---- ------------ ---------- --------------- -------------
> hayk-test mongodb-1-gflrd 0 (0%) 0 (0%) 512Mi (0%) 512Mi (0%)
> kiali-test-box kiali-test-service-b-qs5tv 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-box kiali-test-service-e-jw56k 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-a-hmh8t 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-c-svxgs 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breadth-sink kiali-test-service-e-6fchg 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breath kiali-test-service-c-czxr5 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-breath kiali-test-service-e-cr88j 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle-callback kiali-test-service-b-zljtr 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle-callback kiali-test-service-e-8f6rt 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle kiali-test-service-c-28d5h 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-circle kiali-traffic-generator-lglth 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-test-service-b-xq8ff 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-test-service-e-nnnxw 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth-sink kiali-traffic-generator-fd786 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth kiali-test-service-c-nch7m 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-depth kiali-traffic-generator-vqmg9 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-hourglass kiali-test-service-b-j89jp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kiali-test-hourglass kiali-test-service-e-6r77d 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kube-service-catalog apiserver-566mp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> kube-service-catalog controller-manager-sqmlh 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> openshift-infra hawkular-metrics-xp9hl 0 (0%) 0 (0%) 1500M (2%) 2500M (3%)
> openshift-template-service-broker apiserver-rntz8 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> react-test-demo git-explorer-4-8bdzh 0 (0%) 0 (0%) 0 (0%) 0 (0%)
> {panel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (WFLY-10292) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10292?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-10292:
------------------------------------
Fix Version/s: 13.0.0.Beta1
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10292
> URL: https://issues.jboss.org/browse/WFLY-10292
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 12.0.0.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
> Fix For: 13.0.0.Beta1
>
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (WFLY-10292) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10292?page=com.atlassian.jira.plugin... ]
Darran Lofthouse moved WFCORE-3728 to WFLY-10292:
-------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-10292 (was: WFCORE-3728)
Affects Version/s: 12.0.0.Final
(was: 3.0.10.Final)
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10292
> URL: https://issues.jboss.org/browse/WFLY-10292
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 12.0.0.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (WFLY-10292) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10292?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-10292:
------------------------------------
Component/s: JMS
Security
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-10292
> URL: https://issues.jboss.org/browse/WFLY-10292
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 12.0.0.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (WFLY-10290) jboss.iiop-openjdk.poa-service.namingpoa service reload issues after server migration
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10290?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10290:
----------------------------------
Description:
*jboss.iiop-openjdk.poa-service.namingpoa* service throws java.net.BindException: Address already in use upon server reload after manual migration from older EAP release.
https://access.qa.redhat.com/documentation/en-us/red_hat_jboss_enterprise...
The issue can be reproduced with EAP 7.1.0 as TARGET_HOME as well.
*steps to reproduce* with the current (720397b26d) wildfly master:
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full-ha.xml
unzip -q jboss-eap-6.4.19.zip
cp -r wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
# Enable console logging
/subsystem=logging/pattern-formatter=COLOR-PATTERN:add(pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n")
/subsystem=logging/console-handler=CONSOLE:add(level=INFO, named-formatter=COLOR-PATTERN)
/subsystem=logging/root-logger=ROOT:add-handler(name=CONSOLE)
# reload the server twice to get the exception
reload
reload
{noformat}
*server log errors*
{noformat}
12:01:52,041 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.iiop-openjdk.poa-service.rootpoa" => "WFLYIIOP0098: Failed to resolve initial reference RootPOA
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
Caused by: java.net.BindException: Address already in use"},
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.iiop-openjdk.poa-service.irpoa",
"jboss.iiop-openjdk.poa-service.namingpoa"
],
"Services that may be the cause:" => ["jboss.iiop-openjdk.poa-service.namingpoa"]
}
}
{noformat}
*Exception stack trace*
{noformat}
12:01:51,881 SEVERE [javax.enterprise.resource.corba._DEFAULT_.rpc.transport] (MSC service thread 1-6) "IOP00410216: (COMM_FAILURE) Unable to create listener thread on the specified port: 3529": org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2632)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2651)
at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:164)
at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:218)
at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:236)
at com.sun.corba.se.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:122)
at com.sun.corba.se.impl.oa.poa.POAImpl.initialize(POAImpl.java:404)
at com.sun.corba.se.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:272)
at com.sun.corba.se.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:205)
at com.sun.corba.se.impl.orbutil.closure.Future.evaluate(Future.java:46)
at com.sun.corba.se.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:40)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:45)
at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1169)
at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:156)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at org.wildfly.iiop.openjdk.security.SocketFactoryBase.createServerSocket(SocketFactoryBase.java:59)
at org.wildfly.iiop.openjdk.security.NoSSLSocketFactory.createServerSocket(NoSSLSocketFactory.java:50)
at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:161)
... 19 more
{noformat}
was:
*jboss.iiop-openjdk.poa-service.namingpoa* service throws java.net.BindException: Address already in use upon server reload after manual migration from older EAP release.
The issue can be reproduced with EAP 7.1.0 as TARGET_HOME as well.
*steps to reproduce* with the current (720397b26d) wildfly master:
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full-ha.xml
unzip -q jboss-eap-6.4.19.zip
cp -r wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
# Enable console logging
/subsystem=logging/pattern-formatter=COLOR-PATTERN:add(pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n")
/subsystem=logging/console-handler=CONSOLE:add(level=INFO, named-formatter=COLOR-PATTERN)
/subsystem=logging/root-logger=ROOT:add-handler(name=CONSOLE)
# reload the server twice to get the exception
reload
reload
{noformat}
*server log errors*
{noformat}
12:01:52,041 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.iiop-openjdk.poa-service.rootpoa" => "WFLYIIOP0098: Failed to resolve initial reference RootPOA
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
Caused by: java.net.BindException: Address already in use"},
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.iiop-openjdk.poa-service.irpoa",
"jboss.iiop-openjdk.poa-service.namingpoa"
],
"Services that may be the cause:" => ["jboss.iiop-openjdk.poa-service.namingpoa"]
}
}
{noformat}
*Exception stack trace*
{noformat}
12:01:51,881 SEVERE [javax.enterprise.resource.corba._DEFAULT_.rpc.transport] (MSC service thread 1-6) "IOP00410216: (COMM_FAILURE) Unable to create listener thread on the specified port: 3529": org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2632)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2651)
at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:164)
at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:218)
at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:236)
at com.sun.corba.se.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:122)
at com.sun.corba.se.impl.oa.poa.POAImpl.initialize(POAImpl.java:404)
at com.sun.corba.se.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:272)
at com.sun.corba.se.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:205)
at com.sun.corba.se.impl.orbutil.closure.Future.evaluate(Future.java:46)
at com.sun.corba.se.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:40)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:45)
at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1169)
at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:156)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at org.wildfly.iiop.openjdk.security.SocketFactoryBase.createServerSocket(SocketFactoryBase.java:59)
at org.wildfly.iiop.openjdk.security.NoSSLSocketFactory.createServerSocket(NoSSLSocketFactory.java:50)
at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:161)
... 19 more
{noformat}
> jboss.iiop-openjdk.poa-service.namingpoa service reload issues after server migration
> -------------------------------------------------------------------------------------
>
> Key: WFLY-10290
> URL: https://issues.jboss.org/browse/WFLY-10290
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Migration
> Reporter: Petr Kremensky
> Assignee: Tomasz Adamski
> Priority: Critical
>
> *jboss.iiop-openjdk.poa-service.namingpoa* service throws java.net.BindException: Address already in use upon server reload after manual migration from older EAP release.
> https://access.qa.redhat.com/documentation/en-us/red_hat_jboss_enterprise...
> The issue can be reproduced with EAP 7.1.0 as TARGET_HOME as well.
>
> *steps to reproduce* with the current (720397b26d) wildfly master:
> {noformat}
> WORKSPACE=`pwd`
> CONFIG=standalone-full-ha.xml
> unzip -q jboss-eap-6.4.19.zip
> cp -r wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT wildfly
> SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
> TARGET_HOME=${WORKSPACE}/wildfly
> cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
> ${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
> ${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
> # Migrate
> /subsystem=jacorb:migrate
> /subsystem=messaging:migrate
> /subsystem=web:migrate
> /subsystem=cmp:remove
> /extension=org.jboss.as.cmp:remove
> /subsystem=jaxr:remove
> /extension=org.jboss.as.jaxr:remove
> /subsystem=threads:remove
> /extension=org.jboss.as.threads:remove
> # Enable console logging
> /subsystem=logging/pattern-formatter=COLOR-PATTERN:add(pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n")
> /subsystem=logging/console-handler=CONSOLE:add(level=INFO, named-formatter=COLOR-PATTERN)
> /subsystem=logging/root-logger=ROOT:add-handler(name=CONSOLE)
> # reload the server twice to get the exception
> reload
> reload
> {noformat}
>
> *server log errors*
> {noformat}
> 12:01:52,041 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.iiop-openjdk.poa-service.rootpoa" => "WFLYIIOP0098: Failed to resolve initial reference RootPOA
> Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
> Caused by: java.net.BindException: Address already in use"},
> "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.iiop-openjdk.poa-service.irpoa",
> "jboss.iiop-openjdk.poa-service.namingpoa"
> ],
> "Services that may be the cause:" => ["jboss.iiop-openjdk.poa-service.namingpoa"]
> }
> }
> {noformat}
>
> *Exception stack trace*
> {noformat}
> 12:01:51,881 SEVERE [javax.enterprise.resource.corba._DEFAULT_.rpc.transport] (MSC service thread 1-6) "IOP00410216: (COMM_FAILURE) Unable to create listener thread on the specified port: 3529": org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2632)
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2651)
> at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:164)
> at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:218)
> at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:236)
> at com.sun.corba.se.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:122)
> at com.sun.corba.se.impl.oa.poa.POAImpl.initialize(POAImpl.java:404)
> at com.sun.corba.se.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:272)
> at com.sun.corba.se.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:205)
> at com.sun.corba.se.impl.orbutil.closure.Future.evaluate(Future.java:46)
> at com.sun.corba.se.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:40)
> at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:45)
> at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1169)
> at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:156)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
> at org.wildfly.iiop.openjdk.security.SocketFactoryBase.createServerSocket(SocketFactoryBase.java:59)
> at org.wildfly.iiop.openjdk.security.NoSSLSocketFactory.createServerSocket(NoSSLSocketFactory.java:50)
> at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:161)
> ... 19 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months