[JBoss JIRA] (JBRULES-3334) AbstractTabuAcceptor doesn't add the starting solution as tabu
by Patrik Dufresne (Created) (JIRA)
AbstractTabuAcceptor doesn't add the starting solution as tabu
--------------------------------------------------------------
Key: JBRULES-3334
URL: https://issues.jboss.org/browse/JBRULES-3334
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.3.1.Final
Reporter: Patrik Dufresne
Assignee: Mark Proctor
When setting a complete solution tabu, the starting solution is not considered a Tabu making it possible to visit the same solution again.
Consider a situation where there is construction phase followed by a local search phase. The construction phase will create a solution that will not be added to the tabu list of the local search phased.
To fix it, I suggest to override the function phaseStarted(...) in SolutionTabuAcceptor to add solution to the Tabu map.
--
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
13 years, 6 months
[JBoss JIRA] Created: (AS7-1459) Add a commandline flag to the startup script to enable debugging
by Dan Allen (JIRA)
Add a commandline flag to the startup script to enable debugging
----------------------------------------------------------------
Key: AS7-1459
URL: https://issues.jboss.org/browse/AS7-1459
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.0.0.Final
Reporter: Dan Allen
Assignee: Alexey Loubyansky
The startup script (standalone.sh & standalone.bat) should honor a commandline option that can be used to start the server with debugging enabled. Currently, the developer has to uncomment the JAVA_OPTS line in the standalone.conf file manually.
Proposal for starting the server with debugging enabled:
./bin/standalone.sh --debug
If necessary, the optional flag could accept the port as an optional argument.
./bin/standalone.sh --debug 8787
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-4237) Possible errrors
by Yamamoto Mie (JIRA)
Yamamoto Mie created AS7-4237:
---------------------------------
Summary: Possible errrors
Key: AS7-4237
URL: https://issues.jboss.org/browse/AS7-4237
Project: Application Server 7
Issue Type: Enhancement
Components: Documentation
Reporter: Yamamoto Mie
Priority: Minor
I have a few questions about AS7 and also found possible errors in the doc.
Questions:
- Null owned session update
can you explain when is this message shown?
- to multiple create* methods with different return types on home %s
when is this message shown?
to create* multiple methods?? or multiple create() methods?
- EJB component for address %s is in
Is this EJB component for address %s is in (state %s)?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Possible errors
- Class %s has more *that* one constructor annotated with @Inject
-> more than?
- Boolean to determine whether to create create the tables
- Boolean to determine whether to create drop the tables
- Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds.
- Filed to lookup: %s
- Specifies whether the ejb3 container need only (to?) provide the "LITE" profile of the specification. This value should only be false when using the "everything" distro.
- Removes a specific (a) bean instance pool which has a strict upper limit for bean instances
-No timed object invoke(d) for %s
--
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
13 years, 6 months
[JBoss JIRA] Created: (JBAS-8824) Cardinality constraints on children are not enforced after parsing
by Brian Stansberry (JIRA)
Cardinality constraints on children are not enforced after parsing
------------------------------------------------------------------
Key: JBAS-8824
URL: https://issues.jboss.org/browse/JBAS-8824
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 7.0.0.Alpha1
Reporter: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.Beta1
The parsers enforce cardinality constraints on child elements in the model, but they aren't enforced thereafter. So, for example, a second "profile" or "socket-binding-group" could be added to a standalone server via a management operation.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months