[JBoss JIRA] (JGRP-1599) TP: JGroups internal thread pool
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1599?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1599:
---------------------------
Description:
Add an internal thread pool which is used only for JGroups-internal messages (tagges as Flag.INTERNAL). This prevents internal messages (such as credits, heartbeats etc) to be dropped when the OOB thread pool is maxed out.
If enabled, internal messages will get processed by the internal thread pool, otherwise the OOB pool will be used.
> TP: JGroups internal thread pool
> --------------------------------
>
> Key: JGRP-1599
> URL: https://issues.jboss.org/browse/JGRP-1599
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> Add an internal thread pool which is used only for JGroups-internal messages (tagges as Flag.INTERNAL). This prevents internal messages (such as credits, heartbeats etc) to be dropped when the OOB thread pool is maxed out.
> If enabled, internal messages will get processed by the internal thread pool, otherwise the OOB pool will be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4268) Add JMS bridge to Messaging subsystem
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-4268?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil commented on AS7-4268:
----------------------------------
these jars do not exist: they are only to illustrate what is required to create a module for a messaging provider. I have updated the documentation to make this clearer?
> Add JMS bridge to Messaging subsystem
> -------------------------------------
>
> Key: AS7-4268
> URL: https://issues.jboss.org/browse/AS7-4268
> Project: Application Server 7
> Issue Type: Task
> Components: JMS
> Affects Versions: 7.1.1.Final
> Reporter: Justin Bertram
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.Alpha1
>
>
> Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it.
>
> It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4268) Add JMS bridge to Messaging subsystem
by Shameer Kunjumohamed (JIRA)
[ https://issues.jboss.org/browse/AS7-4268?page=com.atlassian.jira.plugin.s... ]
Shameer Kunjumohamed commented on AS7-4268:
-------------------------------------------
Hi, I was trying to configure the JMSBridge based on the doc of AS72, but couldn't figure out where would I download the dependency jar from (acmemq-1.2.3.jar and mylogapi-0.0.1.jar) ? A google search didnt help actually.
Could anyone help on this ?
> Add JMS bridge to Messaging subsystem
> -------------------------------------
>
> Key: AS7-4268
> URL: https://issues.jboss.org/browse/AS7-4268
> Project: Application Server 7
> Issue Type: Task
> Components: JMS
> Affects Versions: 7.1.1.Final
> Reporter: Justin Bertram
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.Alpha1
>
>
> Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it.
>
> It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4268) Add JMS bridge to Messaging subsystem
by Shameer Kunjumohamed (JIRA)
[ https://issues.jboss.org/browse/AS7-4268?page=com.atlassian.jira.plugin.s... ]
Shameer Kunjumohamed edited comment on AS7-4268 at 2/25/13 3:41 AM:
--------------------------------------------------------------------
Hi, I was trying to configure the JMSBridge based on the doc of AS72, but couldn't figure out where would I download the dependency jars from (acmemq-1.2.3.jar and mylogapi-0.0.1.jar) ? A google search didnt help actually.
Could anyone help on this ?
was (Author: skunjumohamed):
Hi, I was trying to configure the JMSBridge based on the doc of AS72, but couldn't figure out where would I download the dependency jar from (acmemq-1.2.3.jar and mylogapi-0.0.1.jar) ? A google search didnt help actually.
Could anyone help on this ?
> Add JMS bridge to Messaging subsystem
> -------------------------------------
>
> Key: AS7-4268
> URL: https://issues.jboss.org/browse/AS7-4268
> Project: Application Server 7
> Issue Type: Task
> Components: JMS
> Affects Versions: 7.1.1.Final
> Reporter: Justin Bertram
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.Alpha1
>
>
> Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it.
>
> It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6511) Investigate OSGi test failures after MSC upgrade to 1.1.1.Final
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/AS7-6511?page=com.atlassian.jira.plugin.s... ]
Richard Opalka commented on AS7-6511:
-------------------------------------
The MSC 1.1.1.Final is in AS8 upstream now (and this issue sometimes appear in some PRs)
> Investigate OSGi test failures after MSC upgrade to 1.1.1.Final
> ---------------------------------------------------------------
>
> Key: AS7-6511
> URL: https://issues.jboss.org/browse/AS7-6511
> Project: Application Server 7
> Issue Type: Task
> Components: OSGi
> Environment: Tested on (not able to reproduce)
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>java -version
> java version "1.6.0_38"
> Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /home/opalka/java/maven/3.0.4
> Java version: 1.6.0_38, vendor: Sun Microsystems Inc.
> Java home: /home/opalka/java/jdk/orcl/jdk1.6.0_38/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.7.6-201.fc18.x86_64", arch: "amd64", family: "unix"
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>uname -a
> Linux blackhole 3.7.6-201.fc18.x86_64 #1 SMP Mon Feb 4 15:54:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Richard Opalka
> Assignee: Thomas Diesler
> Fix For: 7.3.0.Alpha1
>
>
> I did my best to reproduce this issue but I'm not able to reproduce it locally:( It doesn't matter if I run whole test suite or just this test, the
> test is always passing for me. Since OSGi is not my domain, I'm assigning
> this issue to OSGi team. This bug is related to this PR:
> https://github.com/jbossas/jboss-as/pull/4052
> I'm temporarily disabling the failing test (the purpose of this JIRA).
> Failing test is:
> [INFO] Surefire report directory: /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/osgi/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> ...
> Results :
> Failed tests: testFailStartLevel(org.jboss.as.test.integration.osgi.deployment.DeferredResolveTestCase): Bundle ACTIVE expected:<32> but was:<4>
> Tests run: 120, Failures: 1, Errors: 0, Skipped: 6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6341) EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6341?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-6341:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=915169
> EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
> -------------------------------------------------------------------------------------------------------
>
> Key: AS7-6341
> URL: https://issues.jboss.org/browse/AS7-6341
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> If an entity is removed and new created within the same transaction the 'afterCompletition' procedure try to sync it twice.
> It looks like that the entity is registered twice in this case.
> The Exception is shown in the server.log, nevertheless the transactions and method execution will be succeed.
> The following Exception can be safely ignored.
> 08:17:10,005 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014138: Exception releasing entity: java.lang.IllegalStateException: JBAS014172: Instance [org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@31b489ae] not found in cache
> at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:86) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.releaseInstance(EntityBeanSynchronizationInterceptor.java:154) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.access$200(EntityBeanSynchronizationInterceptor.java:56) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization.afterCompletion(EntityBeanSynchronizationInterceptor.java:219) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:321) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6341) EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6341?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6341:
----------------------------------------------
Osamu Nagano <onagano(a)redhat.com> made a comment on [bug 915169|https://bugzilla.redhat.com/show_bug.cgi?id=915169]
This is a backport of AS7-6341, included in the upstream already, but not in EAP_6.1.0.DR1 yet.
Description of problem:
If an entity is removed and new created within the same transaction the 'afterCompletition' procedure try to sync it twice.
It looks like that the entity is registered twice in this case.
The Exception is shown in the server.log, nevertheless the transactions and method execution will be succeed.
The following Exception can be safely ignored.
08:17:10,005 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014138: Exception releasing entity: java.lang.IllegalStateException: JBAS014172: Instance [org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@31b489ae] not found in cache
at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:86) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.releaseInstance(EntityBeanSynchronizationInterceptor.java:154) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.access$200(EntityBeanSynchronizationInterceptor.java:56) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization.afterCompletion(EntityBeanSynchronizationInterceptor.java:219) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:321) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
> -------------------------------------------------------------------------------------------------------
>
> Key: AS7-6341
> URL: https://issues.jboss.org/browse/AS7-6341
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> If an entity is removed and new created within the same transaction the 'afterCompletition' procedure try to sync it twice.
> It looks like that the entity is registered twice in this case.
> The Exception is shown in the server.log, nevertheless the transactions and method execution will be succeed.
> The following Exception can be safely ignored.
> 08:17:10,005 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014138: Exception releasing entity: java.lang.IllegalStateException: JBAS014172: Instance [org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@31b489ae] not found in cache
> at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:86) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.releaseInstance(EntityBeanSynchronizationInterceptor.java:154) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.access$200(EntityBeanSynchronizationInterceptor.java:56) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization.afterCompletion(EntityBeanSynchronizationInterceptor.java:219) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:321) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ]
jaikiran pai reassigned AS7-6616:
---------------------------------
Assignee: jaikiran pai
> AS 8: Testsuite fails on Solaris SPARC 10
> -----------------------------------------
>
> Key: AS7-6616
> URL: https://issues.jboss.org/browse/AS7-6616
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41
> Reporter: Frank Langelage
> Assignee: jaikiran pai
> Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml
>
>
> Compiling the current sources from github fails for me on this environment.
> On Windows everything is fine.
> Compiling 7.2.0.Final works in this environment.
> But regarding this test, nothing seems to have changed in between.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec
> Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
> Running org.jboss.as.naming.InitialContextTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE!
> Running org.jboss.as.naming.InitialContextFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
> Running org.jboss.as.naming.NamingEventCoordinatorTestCase
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
> Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec
> Running org.jboss.as.naming.InMemoryNamingStoreTestCase
> Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
> Running org.jboss.as.naming.ObjectFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
> Running org.jboss.as.naming.NamingContextTestCase
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
> Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
> Results :
> Tests in error:
> testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null
> Tests run: 70, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s]
> [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s]
> [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s]
> [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s]
> [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s]
> [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSF ..................... SKIPPED
> [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED
> [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: System JMX Module ....... SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Build Modular ........... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED
> [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:36.380s
> [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013
> [INFO] Final Memory: 122M/348M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures.
> [ERROR]
> [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-naming
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on AS7-6616:
-----------------------------------
Frank, I've sent a PR containing a fix for this. Can you give it a try against Solaris and see if that fixes this issue?
> AS 8: Testsuite fails on Solaris SPARC 10
> -----------------------------------------
>
> Key: AS7-6616
> URL: https://issues.jboss.org/browse/AS7-6616
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41
> Reporter: Frank Langelage
> Assignee: jaikiran pai
> Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml
>
>
> Compiling the current sources from github fails for me on this environment.
> On Windows everything is fine.
> Compiling 7.2.0.Final works in this environment.
> But regarding this test, nothing seems to have changed in between.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec
> Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
> Running org.jboss.as.naming.InitialContextTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE!
> Running org.jboss.as.naming.InitialContextFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
> Running org.jboss.as.naming.NamingEventCoordinatorTestCase
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
> Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec
> Running org.jboss.as.naming.InMemoryNamingStoreTestCase
> Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
> Running org.jboss.as.naming.ObjectFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
> Running org.jboss.as.naming.NamingContextTestCase
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
> Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
> Results :
> Tests in error:
> testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null
> Tests run: 70, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s]
> [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s]
> [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s]
> [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s]
> [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s]
> [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSF ..................... SKIPPED
> [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED
> [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: System JMX Module ....... SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Build Modular ........... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED
> [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:36.380s
> [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013
> [INFO] Final Memory: 122M/348M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures.
> [ERROR]
> [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-naming
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months