March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-58) Delegation configuration does not always show the right controls

by Koen Aers (JIRA)

Delegation configuration does not always show the right controls ---------------------------------------------------------------- Key: GPD-58 URL: http://jira.jboss.com/jira/browse/GPD-58 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-21) Add support for the process-state

by Koen Aers (JIRA)

Add support for the process-state --------------------------------- Key: GPD-21 URL: http://jira.jboss.com/jira/browse/GPD-21 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 Basic support is already provided. What still needs to be added is a way to configure. -- 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

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-42) Add script configuration on fork

by Koen Aers (JIRA)

Add script configuration on fork -------------------------------- Key: GPD-42 URL: http://jira.jboss.com/jira/browse/GPD-42 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 -- 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

19 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-494) Add smoke test using ConnectionFactory

by Tim Fox (JIRA)

Add smoke test using ConnectionFactory -------------------------------------- Key: JBMESSAGING-494 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-494 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.CR4 Need to add a smoke test that uses /ConnectionFactory as opposed to /JmsXA. This is because there was a classloader bug that only manifests when sending a message from an ejb to a topic using /Connectionfactory. Really, the smoke tests should be refactored to have a more appropriate use of connection factories. -- 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

19 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-789) Non causality when using Remoting socket transport and one way invocations

by Tim Fox (JIRA)

Non causality when using Remoting socket transport and one way invocations -------------------------------------------------------------------------- Key: JBMESSAGING-789 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-789 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Priority: Critical Fix For: 1.2.0.CR1 The remoting socket transport uses an underlying pool of tcp connections, and subsequent invocations get a connection from the pool, use it and return it from the pool. This means that subsequent invocations can use a different underlying TCP connection, and later invocations can overtake earlier ones depending on how the OS schedules the read threads listening on the connections. Temporary work around is to use a pool size of 1, or completely serialize all invocations per VM by encloing in the synchronized block. This gives us effectively one TCP connection per VM. A better approach would be for the remoting Client object to be pinned to the actual TCP connection one to one. I.e. we don't want or need the pool. It is just a big PITA for us. -- 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

19 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBRULES-718) Drools 3.1.0-M1 rules build 3.0.4 compatibility problems with eval statements

by Thomas Gonzalez (JIRA)

Drools 3.1.0-M1 rules build 3.0.4 compatibility problems with eval statements ----------------------------------------------------------------------------- Key: JBRULES-718 URL: http://jira.jboss.com/jira/browse/JBRULES-718 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.1-m1 Environment: windows 2k Reporter: Thomas Gonzalez Assigned To: Mark Proctor Priority: Blocker Hi Tom - its great you are trying this out - once again - could you attach enough to reproduce this to a JIRA? It will get added to the integration tests. There is no fundamental reason why you can't cast like that at all, its certainly not a design constraint, just - SHOCK - a bug ! Say it isn't so ! On 3/2/07, Tom Gonzalez <tomgon(a)nortel.com> wrote: We are in the process of converting from 3.0.4 to 3.1.0-M1 and having problems building rules that have eval statements in them that buil d in 3.0.4 with no problems. We are getting rules build errors as follows: [java] Feb 28, 2007 5:55:29 PM com.nortel.connect.rbuilder.RulePackager build [java] INFO: ============== Start build RulePackage: [engrules.mss] ========= [java] Feb 28, 2007 5:55:29 PM com.nortel.connect.rbuilder.RulePackage addRulesFromDrlFile [java] INFO: adding Rules from: MG15000Rules.drl (with associated DSL) [java] Feb 28, 2007 5:55:29 PM com.nortel.connect.rbuilder.RulePackage addRulesFromDrlFile [java] INFO: parsed rules using dsl [java] org.drools.RuntimeDroolsException: unable to find the function ',' [java] at org.drools.semantics.java.StaticMethodFunctionResolver.resolveFunction(StaticMethodFunctionResolver.java:9) [java] at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:132) [java] at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:103) [java] at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:66) [java] at org.drools.semantics.java.builder.EvalBuilder.build(EvalBuilder.java:78) [java] at org.drools.semantics.java.builder.GroupElementBuilder.build(GroupElementBuilder.java:63) [java] at org.drools.semantics.java.builder.GroupElementBuilder.build(GroupElementBuilder.java:63) [java] at org.drools.semantics.java.RuleBuilder.build(RuleBuilder.java:178) [java] at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:381) [java] at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:219) [java] at com.nortel.connect.rbuilder.RulePackage.addRulesFromDrlFile(RulePackage.java:229) [java] at com.nortel.connect.rbuilder.RulePackager.build(RulePackager.java:206) [java] at com.nortel.connect.rbuilder.RulePackager.buildAll(RulePackager.java:142) [java] at com.nortel.connect.rbuilder.RulePackager.main(RulePackager.java:92) [java] Feb 28, 2007 5:55:30 PM com.nortel.connect.rbuilder.RulePackage addRulesFromDrlFile We have a number of rules with eval's in them such as: eval( !(checkVspToInstanceRatio( (Integer)$vsp3ocount, (Integer)$vsp4ecount, (Integer)$vsp3count, (Integer)$nstacount)) ); eval ( !(strInStr((String)$shelfsn,(String)$netwksn)) eval( !(checkDlepNumber( (Integer)$dlepkey, (Integer)$nstakey)) || !(isEvenInteger((Integer)$nstakey)) The parser has issue with the cast syntax in the eval removing the cast (like (Integer) ) cleans up the paser issue however this is not a feasible solution. Casting is required in some cases with out adding a good bit of extra work. Can you restore the support we previously had for casting with in an eval and retain the flexibility of using casts when needed? Thanks, Regards, Tom G -- 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

19 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (BPEL-246) Create org.jbpm.bpel.integration.server.JAXWSHandler implementation with the same functionality as org.jbpm.bpel.integration.server.SoapHandler

by Konstantin Pavlov (JIRA)

Create org.jbpm.bpel.integration.server.JAXWSHandler implementation with the same functionality as org.jbpm.bpel.integration.server.SoapHandler ----------------------------------------------------------------------------------------------------------------------------------------------- Key: BPEL-246 URL: http://jira.jboss.com/jira/browse/BPEL-246 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Environment: JBoss 4.0.5.GA + JBossWS 1.2.0.SP1 + jBPL BPEL 1.1-beta-3 Reporter: Konstantin Pavlov Assigned To: Alejandro Guizar Priority: Critical When using JBossWS 1.2.0 with JAXWS I get an exception because SOAPHandler instance is returned instead of javax.xml.ws.handler.Handler expected. 20:21:44,646 ERROR [SOAPFaultHelperJAXWS] SOAP request exception java.lang.ClassCastException: org.jbpm.bpel.integration.server.SoapHandler at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.initHandlerChain(HandlerResolverImpl.java:161) -- 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

19 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1179) Create a special undeletable user for the administrator

by Thomas Heute (JIRA)

Create a special undeletable user for the administrator ------------------------------------------------------- Key: JBPORTAL-1179 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1179 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Reporter: Thomas Heute Fix For: 2.6.Beta1 The user with username "admin" is now mandatory at least for the CMS service (see JCRCMS.java). We should not be able to delete the admin user. Ultimately we should be able to give him any username. -- 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

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3865) Recursive loop on shutdown

by Scott M Stark (JIRA)

Recursive loop on shutdown -------------------------- Key: JBAS-3865 URL: http://jira.jboss.com/jira/browse/JBAS-3865 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta2 When shutting down the server mid startup after an error I have seen the server get into a state where it loops on this type of error: 09:29:21,803 ERROR [AbstractKernelController] INTERNAL ERROR: context not found in previous state Installed context=name=EJB3EntityCacheConfig state=Installedjava.lang.Exception: STACKTRACE at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:638) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:325) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.stop(ServiceController.java:481) at org.jboss.system.deployers.ServiceDeployer.stop(ServiceDeployer.java:131) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:111) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:44) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.undeploy(AbstractSimpleRealDeployer.java:60) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.prepareUndeploy(AbstractSimpleDeployer.java:42) at org.jboss.deployers.plugins.deployer.DeployerWrapper.prepareUndeploy(DeployerWrapper.java:105) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:419) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:428) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:357) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.shutdown(MainDeployerImpl.java:482) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:739) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:721) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.run(ServerImpl.java:706) 09:29:21,906 ERROR [AbstractKernelController] INTERNAL ERROR: context not found in previous state Installed context=name=EJB3EntityCacheConfig state=Installedjava.lang.Exception: STACKTRACE at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:638) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:325) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.stop(ServiceController.java:481) at org.jboss.system.deployers.ServiceDeployer.stop(ServiceDeployer.java:131) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:111) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:44) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.undeploy(AbstractSimpleRealDeployer.java:60) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.prepareUndeploy(AbstractSimpleDeployer.java:42) at org.jboss.deployers.plugins.deployer.DeployerWrapper.prepareUndeploy(DeployerWrapper.java:105) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:419) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:428) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:357) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.shutdown(MainDeployerImpl.java:482) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:739) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:721) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.run(ServerImpl.java:706) 09:29:21,906 ERROR [AbstractKernelController] INTERNAL ERROR: context not found in previous state Installed context=name=EJB3EntityCacheConfig state=Installedjava.lang.Exception: STACKTRACE at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:638) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613) at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:664) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:325) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.stop(ServiceController.java:481) at org.jboss.system.deployers.ServiceDeployer.stop(ServiceDeployer.java:131) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:111) at org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:44) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.undeploy(AbstractSimpleRealDeployer.java:60) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.prepareUndeploy(AbstractSimpleDeployer.java:42) at org.jboss.deployers.plugins.deployer.DeployerWrapper.prepareUndeploy(DeployerWrapper.java:105) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:419) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:428) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:357) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.shutdown(MainDeployerImpl.java:482) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:739) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:721) at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.run(ServerImpl.java:706) A kill -9 is required to stop it after this. -- 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

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-627) null pointer with number comparison..

by Sachin Holla (JIRA)

null pointer with number comparison.. ------------------------------------- Key: JBRULES-627 URL: http://jira.jboss.com/jira/browse/JBRULES-627 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Environment: Windows XP or Solaris Sun JDK 1.4.2 Drools 3.0.4 distribution Reporter: Sachin Holla Assigned To: Mark Proctor getting a null pointer while asserting fact: Caused by: java.lang.NullPointerException at org.drools.base.evaluators.IntegerFactory$IntegerGreaterEvaluator.evaluate(Unknown Source) at org.drools.rule.BoundVariableConstraint.isAllowed(Unknown Source) at org.drools.common.BetaNodeBinder.isAllowed(Unknown Source) at org.drools.reteoo.TupleSource.attemptJoin(Unknown Source) at org.drools.reteoo.JoinNode.assertTuple(Unknown Source) at org.drools.reteoo.LeftInputAdapterNode.createAndAssertTuple(Unknown Source) at org.drools.reteoo.LeftInputAdapterNode.assertObject(Unknown Source) at org.drools.reteoo.ObjectSource.propagateAssertObject(Unknown Source) at org.drools.reteoo.ObjectTypeNode.assertObject(Unknown Source) at org.drools.reteoo.Rete.assertObject(Unknown Source) at org.drools.reteoo.ReteooRuleBase.assertObject(Unknown Source) at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(Unknown Source) at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source) at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source) Rule is something like this: rule "Greater Than with NULL number!!" when MyFact ( integerAttribute > 10 ) then ..... end the *intergerAttribute* is of type java.lang.Integer and value is *null*. no such problem if expression changed to *integerAttribute == 10* or != -- 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

19 years, 2 months

5
6
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 March 2007