[JBoss JIRA] (WFLY-1021) Possible errrors
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1021?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-1021:
----------------------------------------
Based on another similar JIRA from the reporter I believe this is about the i18n text string in the various XXXMessages / XXXLogger files in the source code.
> Possible errrors
> ----------------
>
> Key: WFLY-1021
> URL: https://issues.jboss.org/browse/WFLY-1021
> Project: WildFly
> 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 was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-750) Clarifications needed for Message Translations II
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-750?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-750:
----------------------------------
Component/s: Domain Management
JMS
(was: Documentation)
I put Domain Management and JMS as the components on this as I recognize a few kernel messages in the description (hence Domain Management) and I'm guessing the "HTML" and "connection factory" ones relate to JMS.
> Clarifications needed for Message Translations II
> -------------------------------------------------
>
> Key: WFLY-750
> URL: https://issues.jboss.org/browse/WFLY-750
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, JMS
> Reporter: Yamamoto Mie
> Fix For: Awaiting Volunteers
>
>
> Can you please rephrase the following string?
> 1) String representation the object name of this platform managed object.
> 2) Configuration to use a list users stored within a properties file as the user repository. The entries within the properties file are username={credentials} with each user being specified on it's own line.
> ---- is this "configuration to use a list of users stored ---??" or "a list that users stored within a properties file ---"?
> Possible errors:
> 1) An '%s' element whose '%s' attribute (is) has already been found
> 2) A list of Java Virtual Machine configurations that can be applied (ot) servers on the host. TODO children
> 3) Names of direct child resources of the domain root resource requests for which this Host Controller should ignore. Only relevant on a slave Host Controller. Configuring such "ignored resources" may help allow a Host Controller from an earlier release to function as a slave to a master Host Controller running a later release, by letting the slave ignore portions of the configuration its version of the software cannot understand. This strategy can only be successful if the servers managed by the slave Host Controller do not reference any of the ignored configuration.
> (how the sentence ends such as . etc)
> 4)Te(The) address this message is sent to.
> 5)A string in HTML format as a string in HTML format.????
> 6)Removes managed (<- a) connection factory.
> 7)(T)his permission allows the user to consume a message from a queue bound to matching addresses.
> 8)Removes (and) audit configuration
> 9) Whether this (this) memory manager is valid in the Java virtual machine.
> 10) The approximate accumulated elapsed time (in milliseconds) that the thread has blocked to enter or reenter a monitor since thread contention monitoring is enabled, or -1 if thread contention monitoring is not enabled. (If the --- unfinished sentence)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-771) JBoss AS 7 documentation cannot be exported to PDF
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-771?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry resolved WFLY-771.
-----------------------------------
Resolution: Out of Date
Looking at https://docs.jboss.org/author/display/AS72/Documentation# I see Export to PDF in the Tools menu. I've seen it on other pages in the WFLYxx docs series as well, so I'm going to assume this just got corrected somewhere along the line.
> JBoss AS 7 documentation cannot be exported to PDF
> --------------------------------------------------
>
> Key: WFLY-771
> URL: https://issues.jboss.org/browse/WFLY-771
> Project: WildFly
> Issue Type: Bug
> Components: Documentation
> Reporter: Hendy Irawan
> Attachments: export_pdf.png, export_pdf1.png
>
>
> Most JBoss projects Confluence documentation, notably Arquillian, can be exported to PDF which is very handy for offline browsing and archive :
> 1. Click Tools > View in Hierarchy
> 2. Click Advanced tab
> 3. Click "Export to PDF"
> However, this feature is missing in the JBoss AS7 Confluence Space. It would be awesome if this is enabled, as JBoss AS7 is the flagship product of JBoss. This feature should also have a more prominent introduction, as people unfamiliar with Confluence unaware of this very useful feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1555) Domain Setup docs doesn't explain domain.xml vs host.xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1555?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-6605 to WFCORE-1555:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1555 (was: WFLY-6605)
Component/s: Domain Management
(was: Documentation)
(was: Domain Management)
Affects Version/s: (was: 10.0.0.Final)
> Domain Setup docs doesn't explain domain.xml vs host.xml
> --------------------------------------------------------
>
> Key: WFCORE-1555
> URL: https://issues.jboss.org/browse/WFCORE-1555
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: John Mazzitelli
>
> There looks to be some information missing from:
> https://docs.jboss.org/author/display/WFLY10/Domain+Setup
> Or at least it is confusing. Notice that some of the instructions have this:
> "(See domain/configuration/host.xml)"
> and in other parts it has this:
> "(See domain/configuration/domain.xml)"
> Other than that, there is no mention of "host.xml" versus "domain.xml". This is confusing because the names of the files seem to infer that "domain.xml" is the configuration for the domain controller and "host.xml" is the configuration for the slave host controllers, but that clearly isn't the case (as the instructions both say to edit host.xml to configure both DC and HC). Both DC and HC's config files have:
> <host xmlns="urn:jboss:domain:3.0"> ...
> as the root node, whereas domain.xml has "<domain>".
> The docs should make it clear what and when domain.xml is used versus host.xml. It still isn't clear to me when domain.xml is used/when it is parsed. I assume it is read in by the DC during initialization.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6605) Domain Setup docs doesn't explain domain.xml vs host.xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6605?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-6605:
--------------------------------------
Component/s: Domain Management
Assignee: (was: ANGELA ROBERTSON)
> Domain Setup docs doesn't explain domain.xml vs host.xml
> --------------------------------------------------------
>
> Key: WFLY-6605
> URL: https://issues.jboss.org/browse/WFLY-6605
> Project: WildFly
> Issue Type: Enhancement
> Components: Documentation, Domain Management
> Affects Versions: 10.0.0.Final
> Reporter: John Mazzitelli
>
> There looks to be some information missing from:
> https://docs.jboss.org/author/display/WFLY10/Domain+Setup
> Or at least it is confusing. Notice that some of the instructions have this:
> "(See domain/configuration/host.xml)"
> and in other parts it has this:
> "(See domain/configuration/domain.xml)"
> Other than that, there is no mention of "host.xml" versus "domain.xml". This is confusing because the names of the files seem to infer that "domain.xml" is the configuration for the domain controller and "host.xml" is the configuration for the slave host controllers, but that clearly isn't the case (as the instructions both say to edit host.xml to configure both DC and HC). Both DC and HC's config files have:
> <host xmlns="urn:jboss:domain:3.0"> ...
> as the root node, whereas domain.xml has "<domain>".
> The docs should make it clear what and when domain.xml is used versus host.xml. It still isn't clear to me when domain.xml is used/when it is parsed. I assume it is read in by the DC during initialization.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]
by Jive JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ]
Jive JIRA Integration updated WFCORE-1330:
------------------------------------------
Forum Reference: https://developer.jboss.org/message/956219#956219
> Deployment error after reboot [WFLYSRV0137]
> -------------------------------------------
>
> Key: WFCORE-1330
> URL: https://issues.jboss.org/browse/WFCORE-1330
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.2.Final
> Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65
> Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance.
> Reporter: Tobi Tobias
> Assignee: ehsavoie Hugonnet
> Priority: Critical
> Attachments: server.log, server.log
>
>
> I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE).
> After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred.
> But if I restart the server now, I get following error message:
> 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot.
> The only way to fix the configuration is to manually remove the deployments from the standalone.xml.
> But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1553) data.dir not cleaned up correctly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1553?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1553:
------------------------------------------
[~hbraun] It seems like it, yes. If the idea is the self-container container cleans everything up generically, then that's in core. If the idea is subsystems clean stuff up in the data dir that they ordinarily wouldn't because they discover they are in a self-container server, then that's better as a wildfly-dev discussion. Hopefully that's not the goal as I don't think it's practical. ;)
> data.dir not cleaned up correctly
> ---------------------------------
>
> Key: WFCORE-1553
> URL: https://issues.jboss.org/browse/WFCORE-1553
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Heiko Braun
>
> When running the examples and shutting down the server, certain files remain in the tmp.dir.
> Steps to reproduce:
> 1) cd examples; mvn install
> 2) java -Djava.io.tmpdir=servlet/servlet-cdi/target/test-tmp -jar servlet/servlet-cdi/target/example-servlet-cdi-swarm.jar
> 3) du -ch servlet/servlet-cdi/target/test-tmp
> This leaves us with:
> {noformat}
> hbraun:~/dev/prj/wfs/wildfly-swarm-examples (1.0.0.Beta8)$ du -ch servlet/servlet-cdi/target/test-tmp
> 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/kernel
> 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore/defaultStore
> 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore
> 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store
> 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d
> 4.0K servlet/servlet-cdi/target/test-tmp
> 4.0K total
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1179) Provide an isolated reproducer for DROOLS-1174
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1179?page=com.atlassian.jira.plugi... ]
Jiri Locker edited comment on DROOLS-1179 at 5/16/16 9:58 AM:
--------------------------------------------------------------
Geoffrey:
{quote}
To isolate, run DinnerPartySolveAllTurtleTest with VM option -DrunTurtleTests=true in optaplanner-examples.
It's already occurring at the first step and the 3rd move of LS, but it still has a CH, many rules and many data (which might cause it to be moved a much later move of course).
{quote}
was (Author: jlocker):
Geoffrey:
{quote}To isolate, run DinnerPartySolveAllTurtleTest with VM option -DrunTurtleTests=true in optaplanner-examples.
It's already occurring at the first step and the 3th move of LS, but it still has a CH, many rules and many data (which might cause it to be moved a much later move of course).{quote}
> Provide an isolated reproducer for DROOLS-1174
> ----------------------------------------------
>
> Key: DROOLS-1179
> URL: https://issues.jboss.org/browse/DROOLS-1179
> Project: Drools
> Issue Type: Sub-task
> Components: core engine
> Reporter: Jiri Locker
> Assignee: Jiri Locker
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months