November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBASMP-14) Update server-manager dependency

by Andrew Lee Rubinger (JIRA)

Update server-manager dependency -------------------------------- Key: JBASMP-14 URL: https://jira.jboss.org/jira/browse/JBASMP-14 Project: JBoss AS Maven Plugins Issue Type: Task Components: ejb3-testrunner Affects Versions: 0.1.0 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger The POM is referencing an outdated jboss-as-server-manager, should be jboss-server-manager -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBASMP-18) Allow JBOSS_HOME to be a relative path

by Andrew Lee Rubinger (JIRA)

Allow JBOSS_HOME to be a relative path -------------------------------------- Key: JBASMP-18 URL: https://jira.jboss.org/jira/browse/JBASMP-18 Project: JBoss AS Maven Plugins Issue Type: Feature Request Components: common Affects Versions: control-plugin-0.1.1 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: common-0.1.1 If specified JBOSS_HOME is a relative path, expand it to be absolute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBASMP-13) Configure Surefire in POM

by Andrew Lee Rubinger (JIRA)

Configure Surefire in POM ------------------------- Key: JBASMP-13 URL: https://jira.jboss.org/jira/browse/JBASMP-13 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-example Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Set jbossalll-client via additionalClasspathElements, configure redirectToFile and showSummary -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBASMP-15) Resolve dependencies in preparation for 0.1.0 Release

by Andrew Lee Rubinger (JIRA)

Resolve dependencies in preparation for 0.1.0 Release ----------------------------------------------------- Key: JBASMP-15 URL: https://jira.jboss.org/jira/browse/JBASMP-15 Project: JBoss AS Maven Plugins Issue Type: Task Components: build, common, deploy, example, plugin-control, plugin-ejb3-testrunner Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 Align dependency versions in order to release all modules, starting at 0.1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBASMP-10) Remove EJB3 TestRunner Plugin from Aggregator

by Andrew Lee Rubinger (JIRA)

Remove EJB3 TestRunner Plugin from Aggregator --------------------------------------------- Key: JBASMP-10 URL: https://jira.jboss.org/jira/browse/JBASMP-10 Project: JBoss AS Maven Plugins Issue Type: Task Affects Versions: 0.1.0 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger The EJB3 TestRunner Plugin is now deprecated in favor of moving the EJB3 TestSuite to either AS or Core/Embedded Unit tests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBASMP-6) Align current versions to all start at 0.1.0-SNAPSHOT

by Andrew Lee Rubinger (JIRA)

Align current versions to all start at 0.1.0-SNAPSHOT ----------------------------------------------------- Key: JBASMP-6 URL: http://jira.jboss.com/jira/browse/JBASMP-6 Project: JBoss AS Maven Plugins Issue Type: Task Components: build, common, control-example, control-plugin Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 0.1.0 POMs should be set to same version, 0.1.0-SNAPSHOT, including the Aggregator POM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8134) Common mechanism for all secure socket definitions

by Brian Stansberry (JIRA)

Common mechanism for all secure socket definitions -------------------------------------------------- Key: JBAS-8134 URL: https://jira.jboss.org/browse/JBAS-8134 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> The JAASSecurityDomain in my opinion should >> handle all secure socket definitions. Mod-cluster currently does >> not support JAASSecurityDomains. I won't comment either way on whether JAASSecurityDomain is how we'll do this, but I definitely agree that a common mechanism should be used for all secure socket definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
12
0 / 0

[JBoss JIRA] Created: (JGRP-1165) Out-of-sync views in the cluster causes NAKACK issues and invalid node list at application layer

by vivek v (JIRA)

Out-of-sync views in the cluster causes NAKACK issues and invalid node list at application layer ------------------------------------------------------------------------------------------------- Key: JGRP-1165 URL: https://jira.jboss.org/jira/browse/JGRP-1165 Project: JGroups Issue Type: Bug Affects Versions: 2.9, 2.8 Reporter: vivek v Assignee: Bela Ban There is a logic in GMS (in the installView(..) method) where it checks whether the node itself is in the view or not, if not then just discard the view, if(checkSelfInclusion(mbrs) == false) { if(log.isWarnEnabled()) log.warn(local_addr + ": not member of view " + new_view + "; discarding it"); return; } Now, the problem /w this logic is that the node will remain /w the old view and when trying to send message to the members in the old view the messages would be discarded /w NAKACK as this node won't be there in their new view. So here is an example, 1) 3 nodes all with same view - V1 {n1, n2, n3} 2) n1 (coordinator) suspects (due to missing heartbeat) n2 and publishes new view - V2 {n1, n3} - n2 discards the suspect message from n1 as FD_SOCK is still connected 3) n2 receives this view, but discards it due to the logic in GMS 4) n2 still keeps the old view V1 and continue to send messages to n1 and n3. n1 and n3 will discard messages from n2 /w NAKACK as it's not in their view (V2). 5) After few minutes (could be 10-15 minutes or more) n1 will publish a merge view V3(n1, n2,n3} - joining V1 and V2. Now all nodes got the same view The problem is on n2 the application layer will never know that it can't talk to n1 and n3 - thus, the RPC calls will fail during the time the nodes had different views. I would assume if a node gets a view, which doesn't have itself in it - it should drop all the nodes that are in that new view. So, basically we will create two new subgroups. This way we won't discard messages from each other. The application layer needs to know at all times what nodes can it talk to. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
23
0 / 0

[JBoss JIRA] Created: (JBRULES-2794) Running More Than 100 Threads Results in ArrayIndexOutOfBoundsException from Drools AbstractHashTable

by Anatoly Polinsky (JIRA)

Running More Than 100 Threads Results in ArrayIndexOutOfBoundsException from Drools AbstractHashTable ----------------------------------------------------------------------------------------------------- Key: JBRULES-2794 URL: https://jira.jboss.org/browse/JBRULES-2794 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Ubuntu, Intellij / Windows XP, Eclipse Reporter: Anatoly Polinsky Assignee: Mark Proctor Unfortunately it is not a consistent behaviour, but happens quite often. This is not observed at all when running with e.g. 50 threads. java.util.concurrent.ExecutionException: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction@1102fab at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.jpmc.tss.admincenter.framework.workflow.stress.test.WorkflowStressTest.shouldRunFlow(WorkflowStressTest.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74) at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82) at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:240) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:180) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:94) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:192) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115) Caused by: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction@1102fab at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1473) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1631) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:318) at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:99) at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:38) at org.drools.persistence.session.SingleSessionCommandService.execute(SingleSessionCommandService.java:285) at org.drools.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:193) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:692) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:625) at org.custom.workflow.stress.test.WorkflowRunner.call(WorkflowRunner.java:18) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at org.drools.core.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:317) at org.drools.reteoo.EntryPointNode.updateSink(EntryPointNode.java:323) at org.drools.reteoo.ObjectTypeNode.attach(ObjectTypeNode.java:303) at org.drools.reteoo.builder.PatternBuilder.attachObjectTypeNode(PatternBuilder.java:257) at org.drools.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:92) at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:68) at org.drools.reteoo.Rete.assertObject(Rete.java:111) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:280) at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute(ReteooWorkingMemory.java:360) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1471) ... 24 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-7832) VFSDirContext issues

by Remy Maucherat (JIRA)

VFSDirContext issues -------------------- Key: JBAS-7832 URL: https://jira.jboss.org/jira/browse/JBAS-7832 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M3 Reporter: Remy Maucherat Assignee: Remy Maucherat Following the update to VFS 3, VFSDirContext exhibits weird behavior, although it is partially working. Workaround using a regular FileDirContext. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010