[JBoss JIRA] (WFCORE-242) the deployment content is deleted if first undeploy and then deploy the same application using CLI batch
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-242?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-242:
------------------------------------------------
Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1162444|https://bugzilla.redhat.com/show_bug.cgi?id=1162444] from POST to ASSIGNED
> the deployment content is deleted if first undeploy and then deploy the same application using CLI batch
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-242
> URL: https://issues.jboss.org/browse/WFCORE-242
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Reporter: Jay Kumar SenSharma
> Assignee: Emmanuel Hugonnet
> Priority: Minor
>
> - If deploy and undeploy CLI commands executed in a batch mode then it causes missing deployment inside the "data/content" directory which leads to the following error:
> {code}
> [Host Controller] 10:33:42,387 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "example.war")]) - failure description: "WFLYDC0058: No deployment content with hash d85f1e3106bc8a49838a0dccae9e80819c25e02c is available in the deployment content repository for deployment 'example.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 configuraiton file and restart."
> [Host Controller] 10:33:42,390 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (DROOLS-655) Debug: Line after "THEN" ignored
by Marc Dzaebel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-655?page=com.atlassian.jira.plugin... ]
Marc Dzaebel updated DROOLS-655:
--------------------------------
Description:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a new line after THEN. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
was:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
> Debug: Line after "THEN" ignored
> --------------------------------
>
> Key: DROOLS-655
> URL: https://issues.jboss.org/browse/DROOLS-655
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR2
> Environment: All (Eclipse Debug)
> Reporter: Marc Dzaebel
> Assignee: Mark Proctor
> Priority: Minor
>
> If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
> {code}
> rule ""
> when
> then int i=1;
> System.out.println( i); // breakpoint set here
> end
> {code}
> Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a new line after THEN. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3974) Move 'Channel end notification received, closing channel' to DEBUG
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3974?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3974:
-----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 1153281|https://bugzilla.redhat.com/show_bug.cgi?id=1153281] from ON_QA to VERIFIED
> Move 'Channel end notification received, closing channel' to DEBUG
> ------------------------------------------------------------------
>
> Key: WFLY-3974
> URL: https://issues.jboss.org/browse/WFLY-3974
> Project: WildFly
> Issue Type: Enhancement
> Components: Naming
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 9.0.0.Beta1
>
>
> When a remote jms queue is located the following is seen:
> 2014-09-25 16:48:29,327 INFO [org.jboss.as.naming] (Remoting "jeev6dev01_200" task-1) JBAS011806: Notification de fin de canal reçue, fermeture du canal Channel ID 0cb79bd5 (inbound) of Remoting connection 53a1933a to /10.23.132.245:57733
> This is due to org.jboss.as.naming.NamingLogger where the following is used:
> @LogMessage(level=Logger.Level.INFO)
> @Message(id=11806, value="Channel end notification received, closing channel %s")
> public abstract void closingChannelOnChannelEnd(Channel paramChannel);
> Changin this to
> @LogMessage(level=Logger.Level.DEBUG)
> Would ensure that an INFO log event is not seen every time a jms message is sent to the server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-451) Filter Apache CXF
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-451?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-451:
----------------------------------------------
Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1166502|https://bugzilla.redhat.com/show_bug.cgi?id=1166502] from ON_QA to VERIFIED
> Filter Apache CXF
> -----------------
>
> Key: WFLY-451
> URL: https://issues.jboss.org/browse/WFLY-451
> Project: WildFly
> Issue Type: Task
> Components: Web Services
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 8.0.0.Alpha1
>
>
> Detect Apache CXF libraries in user deployment and *if* the webservices subsystem is actually being triggered for the deployment, either log a major warning or make the deployment fail. This would basically prevent later issues with users trying to deploy not properly packaged applications (e.g. the same war embedding CXF they were using on Tomcat) and making them aware of what they need to do.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (DROOLS-655) Debug: Line after "THEN" ignored
by Marc Dzaebel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-655?page=com.atlassian.jira.plugin... ]
Marc Dzaebel updated DROOLS-655:
--------------------------------
Description:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
was:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines.
> Debug: Line after "THEN" ignored
> --------------------------------
>
> Key: DROOLS-655
> URL: https://issues.jboss.org/browse/DROOLS-655
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR2
> Environment: All (Eclipse Debug)
> Reporter: Marc Dzaebel
> Assignee: Mark Proctor
> Priority: Minor
>
> If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
> {code}
> rule ""
> when
> then int i=1;
> System.out.println( i); // breakpoint set here
> end
> {code}
> Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (DROOLS-655) Debug: Line after "THEN" ignored
by Marc Dzaebel (JIRA)
Marc Dzaebel created DROOLS-655:
-----------------------------------
Summary: Debug: Line after "THEN" ignored
Key: DROOLS-655
URL: https://issues.jboss.org/browse/DROOLS-655
Project: Drools
Issue Type: Bug
Affects Versions: 6.2.0.CR2
Environment: All (Eclipse Debug)
Reporter: Marc Dzaebel
Assignee: Mark Proctor
Priority: Minor
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months