[JBoss JIRA] (WFCORE-384) Server does wrongly reference a list of socket binding groups
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-384?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-384:
------------------------------------
Fix Version/s: 3.0.0.Beta1
(was: 2.0.0.CR1)
> Server does wrongly reference a list of socket binding groups
> -------------------------------------------------------------
>
> Key: WFCORE-384
> URL: https://issues.jboss.org/browse/WFCORE-384
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Ken Wills
> Fix For: 3.0.0.Beta1
>
>
> hbraun: i see that a server (host=foo/server=bar) can have a list of socket-binding-groups
> [10:59am] hbraun: shouldn't that be a a single socket binding instead?
> [11:00am] emuckenhuber: oh... yeah
> [11:00am] hbraun: maybe it's just the description that's wrong
> [11:00am] emuckenhuber: that sounds similar to the jvm thing we had
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-396) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-396?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-396:
------------------------------------
Fix Version/s: 3.0.0.Beta1
(was: 2.0.0.CR1)
> Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-396
> URL: https://issues.jboss.org/browse/WFCORE-396
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
> Fix For: 3.0.0.Beta1
>
>
> Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.)
> But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-60) Capabilities and requirements in a managed process
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-60?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFCORE-60:
----------------------------------------
I'll resolve it when the misc side issues I want fixed are done.
Admittedly, I'm far too lazy to link those to this one. ;)
> Capabilities and requirements in a managed process
> --------------------------------------------------
>
> Key: WFCORE-60
> URL: https://issues.jboss.org/browse/WFCORE-60
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.0.0.CR1
>
>
> Implement the aspects discussed under the "Runtime" section of https://community.jboss.org/docs/DOC-52712
> Add an API to the OperationContext for handlers to publish capabilities and for other handlers to register a requirement for those capabilities and to access the API object associated with the capability.
> The registry of capabilities and requirements should be maintained with a semantic equivalent to the resource tree. The registry is copied-on-write, making the copy invisible to concurrently executing operations, and then the copy is published on commit of the operation that modified it. If the operation does not commit, the copy is discarded, so handlers have no need to revert changes they make to the registry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFLY-5199) On MariaDB 5.3+ and MySQL 5.6.4+, EJB timers in a JDBC storage don't work correctly due to timestamp rounding
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/WFLY-5199?page=com.atlassian.jira.plugin.... ]
Jan Martiska reopened WFLY-5199:
--------------------------------
[~swd847] PR #7998 won't fix it, that one is meant for WFLY-5207 and Microsoft SQL Server. This issue is for MySQL + MariaDB.
For this issue I wanted to discuss with you which of my suggested options (in the description) you find the best.
My suggestion is 3), I included a link to a possible implementation.
If you agree with it, I can send a PR.
> On MariaDB 5.3+ and MySQL 5.6.4+, EJB timers in a JDBC storage don't work correctly due to timestamp rounding
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5199
> URL: https://issues.jboss.org/browse/WFLY-5199
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Beta2
> Environment: MariaDB 5.3+, Mysql 5.6.4+
> Reporter: Jan Martiska
> Assignee: Stuart Douglas
> Fix For: 10.0.0.CR1
>
>
> EJB timers don't execute, because the DatabaseTimerPersistence.shouldRun method returns false for them, because it is unable to SELECT them from the database using a java.sql.Timestamp.
> On MariaDB 5.3+ and MySQL 5.6.4+, the behavior of the DATETIME type has changed compared to MySQL 5.5 and older.
> In previous versions, it was possible to insert into DATETIME columns with JDBC using a java.sql.Timestamp which contained fractional seconds, the fraction was truncated/rounded and a subsequent SELECT statement with the same java.sql.Timestamp returned such rows, because the fraction was truncated/rounded from the queried Timestamp too.
> On MySQL 5.6.4+ and MariaDB 5.3+, when a java.sql.Timestamp including a fractional second is inserted into a DATETIME, attempting to SELECT with the same Timestamp doesn't return the row, because the DATETIME type now defaults to DATETIME(0) which truncates/rounds to whole seconds, and the queried Timestamp no longer gets truncated/rounded during the query execution. It would only work if the column was declared as DATETIME(6), which ensures that inserted values don't get truncated/rounded. Documentation: https://dev.mysql.com/doc/refman/5.7/en/fractional-seconds.html
> MySQL rounds the timestamp, MariaDB truncates it (always rounds down).
> However, declaring DATETIME(6) is not possible in older versions of MySQL or MariaDB, so to support both new and old versions, we have probably these options:
> 1. introduce a new DDL file(s) for MySQL 5.6.4+ and MariaDB 5.3+ and use it depending on the detected version - this DDL would use DATETIME(6) instead of DATETIME
> 2. change the DatabaseTimerPersistence implementation so that it will not insert fractional seconds into the database at all (EJB timers don't support timing with higher precision than whole seconds anyway)
> 3. same as option 2, but only for MariaDB/MySQL dialects
> 4. any other idea?
> I personally like number 3 the best, it is the least risky and introduces only minimal changes.. but it's still somewhat ugly.
> This seems to resolve it for me (implementation suggestion of option 3): https://github.com/jmartisk/wildfly/commits/mysql-mariadb-timer-suggestion
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (DROOLS-795) Timers are reset during the serialization process
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-795?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-795:
------------------------------------------------
Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1248429|https://bugzilla.redhat.com/show_bug.cgi?id=1248429] from ON_QA to VERIFIED
> Timers are reset during the serialization process
> -------------------------------------------------
>
> Key: DROOLS-795
> URL: https://issues.jboss.org/browse/DROOLS-795
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.3.0.CR1
>
>
> When the marshall serializes a timer it doesn't take count of how much time it is already passed, so when the timer is deserialized it restart from it start time. The following failing test case reproduces the problem.
> {code}
> @Test
> public void testMarshallWithTimedRule() {
> String drl = "rule \"Rule A Timeout\"\n" +
> "when\n" +
> " String( this == \"ATrigger\" )\n" +
> "then\n" +
> " insert (new String( \"A-Timer\") );\n" +
> "System.out.println(\"+++++++Got ATrigger, started A-Timer with 5s timeout\");\n" +
> "end\n" +
> "\n" +
> "rule \"Timer For rule A Timeout\"\n" +
> " timer ( int: 5s )\n" +
> "when\n" +
> " String( this == \"A-Timer\")\n" +
> "then\n" +
> " delete ( \"A-Timer\" );\n" +
> " delete ( \"ATrigger\" );\n" +
> "System.out.println(\"******* reset rule A based on timer\");\n" +
> "end\n";
> KieBase kbase = new KieHelper().addContent( drl, ResourceType.DRL )
> .build( EqualityBehaviorOption.EQUALITY,
> DeclarativeAgendaOption.ENABLED,
> EventProcessingOption.STREAM );
> KieSessionConfiguration sessionConfig = KnowledgeBaseFactory.newKnowledgeSessionConfiguration();
> sessionConfig.setOption( ClockTypeOption.get( "pseudo" ) );
> KieSession ksession = kbase.newKieSession(sessionConfig, null);
> ksession.insert( new String( "ATrigger" ) );
> assertEquals( 1, ksession.getFactCount() );
> ksession.fireAllRules();
> assertEquals( 2, ksession.getFactCount() );
> SessionPseudoClock clock = ksession.getSessionClock();
> clock.advanceTime( 4, TimeUnit.SECONDS );
> assertEquals( 2, ksession.getFactCount() );
> ksession.fireAllRules();
> assertEquals( 2, ksession.getFactCount() );
> ksession = marshallAndUnmarshall( kbase, ksession, sessionConfig);
> clock = ksession.getSessionClock();
> clock.advanceTime( 4, TimeUnit.SECONDS );
> assertEquals( 2, ksession.getFactCount() );
> ksession.fireAllRules();
> assertEquals( 0, ksession.getFactCount() );
> }
> public static KieSession marshallAndUnmarshall(KieBase kbase, KieSession ksession, KieSessionConfiguration sessionConfig) {
> // Serialize and Deserialize
> try {
> Marshaller marshaller = KieServices.Factory.get().getMarshallers().newMarshaller(kbase);
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> marshaller.marshall(baos, ksession);
> marshaller = MarshallerFactory.newMarshaller( kbase );
> ByteArrayInputStream bais = new ByteArrayInputStream(baos.toByteArray());
> baos.close();
> ksession = marshaller.unmarshall(bais, sessionConfig, null);
> bais.close();
> } catch (Exception e) {
> e.printStackTrace();
> fail("unexpected exception :" + e.getMessage());
> }
> return ksession;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-940) CLI gets fooled by early connection
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-940?page=com.atlassian.jira.plugin... ]
Petr Kremensky moved JBEAP-953 to WFCORE-940:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-940 (was: JBEAP-953)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> CLI gets fooled by early connection
> -----------------------------------
>
> Key: WFCORE-940
> URL: https://issues.jboss.org/browse/WFCORE-940
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> CLI in confused by early connection to domain which is booting. CLI acts as I was connected to the standalone instance, some high level commands are not executable.
> {noformat}
> [pkremens@dhcp-10-40-5-149 bin]$ ./domain.sh
> ...
> # run while domain is booting
> [pkremens@dhcp-10-40-5-149 bin]$ ./jboss-cli.sh -c
> [standalone@localhost:9999 /]
> # domain has fully booted
> [standalone@localhost:9999 /] ls -l
> ATTRIBUTE VALUE TYPE
> launch-type DOMAIN STRING
> ...
> [standalone@localhost:9999 /] shutdown --host=master
> --host is not allowed in the standalone mode.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFLY-3971) Jar Services in META-INF/services are not loaded from static modules
by Lucas K (JIRA)
[ https://issues.jboss.org/browse/WFLY-3971?page=com.atlassian.jira.plugin.... ]
Lucas K commented on WFLY-3971:
-------------------------------
Got the same problem with atmospheres [AnnotationScanningServletContainerInitializer|http://atmosphere.github.io/atmosphere/apidocs/org/atmosphere/cpr/AnnotationScanningServletContainerInitializer.html]. It's not called, if atmosphere is a static module.
But i got a workaround for the moment:
I added export="true" to the atmosphere-module and added a new JAR to the WEB-INF/lib folder. The JAR only contains the META-INF folder of atmosphere.jar. Inside it there is the services folder with the "javax.servlet.ServletContainerInitializer" file.
The atmosphere-module gets loaded and exported. So if the new JAR is deployed the ServletContainerInitializer is read and the AnnotationScanningServletContainerInitializer of atmosphere gets called.
I hope it helps someone who has the same problem and is also waiting for the bugfix.
> Jar Services in META-INF/services are not loaded from static modules
> --------------------------------------------------------------------
>
> Key: WFLY-3971
> URL: https://issues.jboss.org/browse/WFLY-3971
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 9.0.0.Final, 10.0.0.Alpha6
> Reporter: Tomas Repel
> Assignee: Stuart Douglas
>
> If the web application (war) uses jar file from static module, the content of META-INF/services has no effect. If the jar is located inside WEB-INF/lib, services are loaded successfully.
> Neither adding `Dependencies: my.module.name.com services` into MANIFEST.MF nor adding `services="import"` to jboss-deployment-structure.xml works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-939) Embedded host controller should set lunch type attribute to EMBEDDED
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-939?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFCORE-939:
----------------------------------
Environment: (was: *DomainRootDefinition.java* always set launch type to {noformat}new LaunchTypeHandler(ServerEnvironment.LaunchType.DOMAIN){noformat} even if the host controller process is embedded.
Looking into the LaunchType class, I believe that EMBEDDED value should be used.
{noformat}
/** The manner in which a server can be launched */
public static enum LaunchType {
/** Launched by a Host Controller in a managed domain */
DOMAIN(ProcessType.DOMAIN_SERVER),
/** Launched from the command line */
STANDALONE(ProcessType.STANDALONE_SERVER),
/** Launched by another process in which the server is embedded */
EMBEDDED(ProcessType.EMBEDDED_SERVER),
...
{noformat}
\\
*Additional info:*
{noformat}./standalone.sh
launch-type STANDALONE
{noformat}
{noformat}./domain.sh
launch-type DOMAIN
{noformat}
{noformat}[disconnected /] embed-server
launch-type EMBEDDED
{noformat}
{noformat}[disconnected /] embed-host-controller
launch-type DOMAIN
{noformat})
> Embedded host controller should set lunch type attribute to EMBEDDED
> --------------------------------------------------------------------
>
> Key: WFCORE-939
> URL: https://issues.jboss.org/browse/WFCORE-939
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-939) Embedded host controller should set lunch type attribute to EMBEDDED
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-939?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFCORE-939:
----------------------------------
Description:
*DomainRootDefinition.java* always set launch type to {noformat}new LaunchTypeHandler(ServerEnvironment.LaunchType.DOMAIN){noformat} even if the host controller process is embedded.
Looking into the LaunchType class, I believe that EMBEDDED value should be used.
{noformat}
/** The manner in which a server can be launched */
public static enum LaunchType {
/** Launched by a Host Controller in a managed domain */
DOMAIN(ProcessType.DOMAIN_SERVER),
/** Launched from the command line */
STANDALONE(ProcessType.STANDALONE_SERVER),
/** Launched by another process in which the server is embedded */
EMBEDDED(ProcessType.EMBEDDED_SERVER),
...
{noformat}
\\
*Additional info:*
{noformat}./standalone.sh
launch-type STANDALONE
{noformat}
{noformat}./domain.sh
launch-type DOMAIN
{noformat}
{noformat}[disconnected /] embed-server
launch-type EMBEDDED
{noformat}
{noformat}[disconnected /] embed-host-controller
launch-type DOMAIN
{noformat}
> Embedded host controller should set lunch type attribute to EMBEDDED
> --------------------------------------------------------------------
>
> Key: WFCORE-939
> URL: https://issues.jboss.org/browse/WFCORE-939
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
> *DomainRootDefinition.java* always set launch type to {noformat}new LaunchTypeHandler(ServerEnvironment.LaunchType.DOMAIN){noformat} even if the host controller process is embedded.
> Looking into the LaunchType class, I believe that EMBEDDED value should be used.
> {noformat}
> /** The manner in which a server can be launched */
> public static enum LaunchType {
> /** Launched by a Host Controller in a managed domain */
> DOMAIN(ProcessType.DOMAIN_SERVER),
> /** Launched from the command line */
> STANDALONE(ProcessType.STANDALONE_SERVER),
> /** Launched by another process in which the server is embedded */
> EMBEDDED(ProcessType.EMBEDDED_SERVER),
> ...
> {noformat}
> \\
> *Additional info:*
> {noformat}./standalone.sh
> launch-type STANDALONE
> {noformat}
> {noformat}./domain.sh
> launch-type DOMAIN
> {noformat}
> {noformat}[disconnected /] embed-server
> launch-type EMBEDDED
> {noformat}
> {noformat}[disconnected /] embed-host-controller
> launch-type DOMAIN
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (WFCORE-939) Embedded host controller should set lunch type attribute to EMBEDDED
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-939?page=com.atlassian.jira.plugin... ]
Petr Kremensky moved JBEAP-951 to WFCORE-939:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-939 (was: JBEAP-951)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> Embedded host controller should set lunch type attribute to EMBEDDED
> --------------------------------------------------------------------
>
> Key: WFCORE-939
> URL: https://issues.jboss.org/browse/WFCORE-939
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Environment: *DomainRootDefinition.java* always set launch type to {noformat}new LaunchTypeHandler(ServerEnvironment.LaunchType.DOMAIN){noformat} even if the host controller process is embedded.
> Looking into the LaunchType class, I believe that EMBEDDED value should be used.
> {noformat}
> /** The manner in which a server can be launched */
> public static enum LaunchType {
> /** Launched by a Host Controller in a managed domain */
> DOMAIN(ProcessType.DOMAIN_SERVER),
> /** Launched from the command line */
> STANDALONE(ProcessType.STANDALONE_SERVER),
> /** Launched by another process in which the server is embedded */
> EMBEDDED(ProcessType.EMBEDDED_SERVER),
> ...
> {noformat}
> \\
> *Additional info:*
> {noformat}./standalone.sh
> launch-type STANDALONE
> {noformat}
> {noformat}./domain.sh
> launch-type DOMAIN
> {noformat}
> {noformat}[disconnected /] embed-server
> launch-type EMBEDDED
> {noformat}
> {noformat}[disconnected /] embed-host-controller
> launch-type DOMAIN
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months