April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4367) Missing dependencies on app client start

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4367: ----------------------------------- Summary: Missing dependencies on app client start Key: AS7-4367 URL: https://issues.jboss.org/browse/AS7-4367 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.2.Final service jboss.jdbc-driver.registry (missing) dependents: [service jboss.jdbc-driver.h2] service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote] -- 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

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-3451) JASPI Support for Web Services

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-3451: ---------------------------------- Summary: JASPI Support for Web Services Key: AS7-3451 URL: https://issues.jboss.org/browse/AS7-3451 Project: Application Server 7 Issue Type: Feature Request Components: Security, Web Services Reporter: Anil Saldhana Assignee: Alessio Soldano Fix For: 7.1.1.Final Take care of the JASPI requirements for SOAP layer. -- 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

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-9149) Disappearing log messages

by Brian Stansberry (JIRA)

Disappearing log messages ------------------------- Key: JBAS-9149 URL: https://issues.jboss.org/browse/JBAS-9149 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Reporter: Brian Stansberry Assignee: David Lloyd Affects post-Beta1 trunk (perhaps Beta1 as well; reports are from folks using trunk) Report from Scott Stark of error messages sometimes not appearing: > On 3/25/11 11:43 AM, Scott Stark wrote: >> When starting up with a loopback address that is other than 127.0.0.1 >> (I'll get to that later), this exception happens: >> >> 14:31:16,275 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to >> start service jboss.network.default: >> org.jboss.msc.service.StartException in service jboss.network.default: >> failed to resolve interface default >> at >> org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:101) >> at >> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) >> [:1.6.0_20] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >> [:1.6.0_20] >> at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] >> >> Now I have seen this msg not be displayed at all, so under some >> circumstances it is being lost. Darran Lofthouse also reported that in some cases log messages from the start() method of one of his services would not appear, but the service would indeed be started, implying that the message is disappearing somehow. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
12
0 / 0

[JBoss JIRA] Created: (AS7-1708) Failure in CalendarUtilTestCase.testEveryMinuteEveryHourEveryDay

by Carlo de Wolf (JIRA)

Failure in CalendarUtilTestCase.testEveryMinuteEveryHourEveryDay ---------------------------------------------------------------- Key: AS7-1708 URL: https://issues.jboss.org/browse/AS7-1708 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Blocker Fix For: 7.0.2.Final I'm unable to compile AS 7. {noformat} Failed tests: testEveryMinuteEveryHourEveryDay[379](org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase): Unexpected timeout value: java.util.GregorianCalendar[time=1314918060000,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="Asia/Gaza",offset=7200000,dstSavings=3600000,useDaylight=true,transitions=144,lastRule=java.util.SimpleTimeZone[id=Asia/Gaza,offset=7200000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=7,startTime=60000,startTimeMode=0,endMode=3,endMonth=8,endDay=1,endDayOfWeek=6,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2011,MONTH=8,WEEK_OF_YEAR=36,WEEK_OF_MONTH=1,DAY_OF_MONTH=2,DAY_OF_YEAR=245,DAY_OF_WEEK=6,DAY_OF_WEEK_IN_MONTH=1,AM_PM=0,HOUR=1,HOUR_OF_DAY=1,MINUTE=1,SECOND=0,MILLISECOND=0,ZONE_OFFSET=7200000,DST_OFFSET=0] expected:<60000> but was:<3660000> {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
10
0 / 0

[JBoss JIRA] (AS7-2115) Security Audit for EJB3 Applications

by Anil Saldhana (Created) (JIRA)

Security Audit for EJB3 Applications ------------------------------------ Key: AS7-2115 URL: https://issues.jboss.org/browse/AS7-2115 Project: Application Server 7 Issue Type: Sub-task Components: EJB Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 7.1.0.CR1 EJB3 authentication/authorization events should go to the security audit framework. http://community.jboss.org/wiki/JBossAS7SecurityAuditing -- 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

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-4384) No way to query valid property values for objects of type PROPERTY via cli

by Simeon Pinder (JIRA)

Simeon Pinder created AS7-4384: ---------------------------------- Summary: No way to query valid property values for objects of type PROPERTY via cli Key: AS7-4384 URL: https://issues.jboss.org/browse/AS7-4384 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.1.Final Environment: CLI browsing AS 7.1.1.Final model with modcluster enabled via *ha profile. Reporter: Simeon Pinder Assignee: Alexey Loubyansky If you run the following to browse the resource-description subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description(operations=true,inherited=false,recursive=false,proxies=false) You'll encounter Object type = PROPERTY "property" => { "description" => "Properties for the metric.", "type" => PROPERTY, "required" => false } Which has an acceptable list of property values as described here. http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#LoadMetric There is no way to query the acceptable and currently supported list of property values via cli. You must hard code and risk going out of synch with as7/modclusters supported values. -- 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

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2298) Can't use functions when MVEL dialect is set at package level

by Michael Neale (JIRA)

Can't use functions when MVEL dialect is set at package level ------------------------------------------------------------- Key: JBRULES-2298 URL: https://jira.jboss.org/jira/browse/JBRULES-2298 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Reporter: Michael Neale Assignee: Edson Tirelli Priority: Critical package jboss.cloud dialect "mvel" #trying to get functions working... rule "something" when s: SimpleFact(id == 42, name == "michael") then System.out.println("hello"); end function String doSomething() { return "hey"; } And I get: java.lang.NullPointerException at org.drools.rule.builder.dialect.mvel.MVELDialect.compile(MVELDialect.java:510) at org.drools.rule.builder.dialect.mvel.MVELDialect.addFunction(MVELDialect.java:338) at org.drools.compiler.PackageBuilder.addFunction(PackageBuilder.java:1104) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:626) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:290) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:488) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25) -- 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, 9 months

6
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2797) HashTableIterator of AbstractHashTable is not Thread Safe

by Anatoly Polinsky (JIRA)

HashTableIterator of AbstractHashTable is not Thread Safe ---------------------------------------------------------- Key: JBRULES-2797 URL: https://jira.jboss.org/browse/JBRULES-2797 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-core (flow) Affects Versions: 5.1.1.FINAL, FUTURE Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor public static class HashTableIterator has a shared state that gets inconsistent when multiple threads work on the getting the next entity: public Object next() { if ( this.entry != null ) { PART 1 >> this.entry = this.entry.getNext(); } // if no entry keep skipping rows until we come to the end, or find one that is populated while ( this.entry == null && ++this.row < this.length ){ PART II >> this.entry = this.table[this.row]; } return this.entry; } In "PART 1", the race condition causes "this.entry" be NULL in "this.entry.getNext()", and throws the exception below. In "PART 2", the race condition causes inconsistent state of "this.row", and throws multiple exceptions, but mostly the one that is described in: https://jira.jboss.org/browse/JBRULES-2794 java.util.concurrent.ExecutionException: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction@1ff323 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.custom.workflow.stress.test.WorkflowStressTest.shouldRunFlow(WorkflowStressTest.java:49) 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@1ff323 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:38) 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.NullPointerException at org.drools.core.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:312) 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, 9 months

2
5
0 / 0

[JBoss JIRA] (AS7-4382) Enter the same password in add-user cause an NP

by Flemming Harms (JIRA)

Flemming Harms created AS7-4382: ----------------------------------- Summary: Enter the same password in add-user cause an NP Key: AS7-4382 URL: https://issues.jboss.org/browse/AS7-4382 Project: Application Server 7 Issue Type: Bug Components: Domain Management Environment: all environments Reporter: Flemming Harms Assignee: Brian Stansberry if you type in the same password for a user when using the add-user CLI it throws a NP exception Exception in thread "main" java.lang.NullPointerException at org.jboss.as.domain.management.security.state.ErrorState.execute(ErrorState.java:58) at org.jboss.as.domain.management.security.AddPropertiesUser.run(AddPropertiesUser.java:117) at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:159) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:260) at org.jboss.modules.Main.main(Main.java:291) This is due to the console object was not passed correctly down to the ErrorState from the WeakCheckState -- 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

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] (LOGMGR-39) Serious performance degradation when using FileHandler

by Carlo de Wolf (JIRA)

Carlo de Wolf created LOGMGR-39: ----------------------------------- Summary: Serious performance degradation when using FileHandler Key: LOGMGR-39 URL: https://issues.jboss.org/browse/LOGMGR-39 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.2.GA Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.3.0.Beta1 FileHandler shows serious performance issues when publish a large amount of records. -- 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

12 years, 9 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012