April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4204) TS clustering: test with both repl and dist caches

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4204: ----------------------------------- Summary: TS clustering: test with both repl and dist caches Key: AS7-4204 URL: https://issues.jboss.org/browse/AS7-4204 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Test Suite Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.2.Final Just like we did in AS7-3954, but with different cache types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-2985) TS: Multiple Surefire executions - FAILURE in one supresses successive.

by Ondrej Zizka (Created) (JIRA)

TS: Multiple Surefire executions - FAILURE in one supresses successive. ----------------------------------------------------------------------- Key: AS7-2985 URL: https://issues.jboss.org/browse/AS7-2985 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
5
0 / 0

[JBoss JIRA] (AS7-3861) Document how to configure firewall when using different JGroups stacks

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3861: ----------------------------------- Summary: Document how to configure firewall when using different JGroups stacks Key: AS7-3861 URL: https://issues.jboss.org/browse/AS7-3861 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Documentation Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.1.Final Document how to configure firewall for using different clustering stacks https://docs.jboss.org/author/display/AS71/High+Availability+Guide Needed by OpenShift team (especially TCP stacks). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3825) Update the HA documentation

by Heiko Braun (JIRA)

Heiko Braun created AS7-3825: -------------------------------- Summary: Update the HA documentation Key: AS7-3825 URL: https://issues.jboss.org/browse/AS7-3825 Project: Application Server 7 Issue Type: Feature Request Components: Documentation Reporter: Heiko Braun Fix For: 7.1.1.Final We need to update the HA docs. Besides modcluster it's pretty much empty: https://docs.jboss.org/author/display/AS71/High+Availability+Guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-4155) TS: Make Surefure test ordering configurable.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4155: --------------------------------- Summary: TS: Make Surefure test ordering configurable. Key: AS7-4155 URL: https://issues.jboss.org/browse/AS7-4155 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3726) TS: Pass the path to docs/examples to the tests.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3726: --------------------------------- Summary: TS: Pass the path to docs/examples to the tests. Key: AS7-3726 URL: https://issues.jboss.org/browse/AS7-3726 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1663) An extended persistence context should not be propagated if there is no JTA transaction

by Scott Marlow (JIRA)

An extended persistence context should not be propagated if there is no JTA transaction --------------------------------------------------------------------------------------- Key: AS7-1663 URL: https://issues.jboss.org/browse/AS7-1663 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Affects Versions: 7.0.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.2.Final JPA 2.0 specification section 7.6.3.1 Requirements for Persistence Context Propagation: " Persistence contexts are propagated by the container across component invocations as follows. If a component is called and there is no JTA transaction or the JTA transaction is not propagated, the persistence context is not propagated. " For the case of a SFSB (with an extended persistence context XPC) method that is not in a JTA transaction, invoking a SLSB (with a transactional entity manager PC) method that requires a transaction. The SLSB method should not use the extended persistence context but should instead start a new persistence context instead for the duration of the SLSB transaction (will end at the method end). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] (AS7-4277) Performance regression introduced in AS7-4205

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4277: ----------------------------------- Summary: Performance regression introduced in AS7-4205 Key: AS7-4277 URL: https://issues.jboss.org/browse/AS7-4277 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: No Release Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.2.Final After https://github.com/jbossas/jboss-as/pull/1869 we are seeing read time-outs on the clients and TimeoutException on the server. {noformat} [JBossINF] 12:46:55,011 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-5717,null) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [15 seconds] on key [OKaB26plMWYsWpHQS+UmsJ7R] for requestor [GlobalTransaction:<perf21/web>:3592818:remote]! Lock held by [GlobalTransaction:<perf21/web>:3591864:remote] [JBossINF] at org.infinispan.util.concurrent.locks.LockManagerImpl.lock(LockManagerImpl.java:204) [JBossINF] at org.infinispan.util.concurrent.locks.LockManagerImpl.acquireLock(LockManagerImpl.java:178) [JBossINF] at org.infinispan.util.concurrent.locks.LockManagerImpl.acquireLock(LockManagerImpl.java:168) [JBossINF] at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:209) [JBossINF] at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAndRegisterBackupLock(AbstractTxLockingInterceptor.java:136) [JBossINF] at org.infinispan.interceptors.locking.OptimisticLockingInterceptor$LockAcquisitionVisitor.visitPutKeyValueCommand(OptimisticLockingInterceptor.java:202) [JBossINF] at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:76) [JBossINF] at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.acquireLocksVisitingCommands(OptimisticLockingInterceptor.java:262) [JBossINF] at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:92) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.NotificationInterceptor.visitPrepareCommand(NotificationInterceptor.java:58) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:130) [JBossINF] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.TxInterceptor.visitPrepareCommand(TxInterceptor.java:106) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.StateTransferLockInterceptor.handleWithRetries(StateTransferLockInterceptor.java:208) [JBossINF] at org.infinispan.interceptors.StateTransferLockInterceptor.visitPrepareCommand(StateTransferLockInterceptor.java:85) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:130) [JBossINF] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:130) [JBossINF] at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:89) [JBossINF] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:130) [JBossINF] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [JBossINF] at org.infinispan.interceptors.BatchingInterceptor.handleDefault(BatchingInterceptor.java:70) [JBossINF] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [JBossINF] at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:345) [JBossINF] at org.infinispan.commands.tx.PrepareCommand.perform(PrepareCommand.java:127) [JBossINF] at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:127) [JBossINF] at org.infinispan.remoting.InboundInvocationHandlerImpl.handleWithWaitForBlocks(InboundInvocationHandlerImpl.java:136) [JBossINF] at org.infinispan.remoting.InboundInvocationHandlerImpl.handleWithRetry(InboundInvocationHandlerImpl.java:162) [JBossINF] at org.infinispan.remoting.InboundInvocationHandlerImpl.handle(InboundInvocationHandlerImpl.java:114) [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommand(CommandAwareRpcDispatcher.java:221) [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:201) [JBossINF] at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:456) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:363) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:238) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:543) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.JChannel.up(JChannel.java:716) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.RSVP.up(RSVP.java:181) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:882) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:759) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:365) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:595) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.BARRIER.up(BARRIER.java:102) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.FD.up(FD.java:273) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:282) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.stack.Protocol.up(Protocol.java:358) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.TP.passMessageUp(TP.java:1174) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1722) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1704) [jgroups-3.0.8.Final.jar:3.0.8.Final] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
6
0 / 0

[JBoss JIRA] (AS7-3658) NPE when starting a hornetQ backup server

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-3658: ---------------------------------------- Summary: NPE when starting a hornetQ backup server Key: AS7-3658 URL: https://issues.jboss.org/browse/AS7-3658 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Emanuel Muckenhuber Assignee: Andy Taylor Fix For: 7.1.1.Final When configuring a <hornetq-server /> with <backup>true</backup> - the service fails to start: {code} 17:45:00,446 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.messaging.backup-server.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging.backup-server.jms.manager: java.lang.NullPointerException at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:80) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: java.lang.NullPointerException at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:74) ... 5 more {code} This affects e.g. docs/examples/configs/standalone-hornetq-colocated.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
7
0 / 0

[JBoss JIRA] (JBRULES-3315) Remove drools-grip from spring

by Mark Proctor (Created) (JIRA)

Remove drools-grip from spring ------------------------------ Key: JBRULES-3315 URL: https://issues.jboss.org/browse/JBRULES-3315 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor As the grid work is only partially working and causes complexity in the release process for drools-spring, we have decided to remove drools-grip from spring for now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
22
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012