[JBoss JIRA] (WFLY-3931) Custom formatter property changes not written to, but overriden by logging.properties
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-3931?page=com.atlassian.jira.plugin.... ]
Vsevolod Golovanov edited comment on WFLY-3931 at 11/29/14 4:14 PM:
--------------------------------------------------------------------
[~ander.parra], [^standalone.xml] - it's just a fresh standalone.xml with the following added:
{code}
<formatter name="ZZZZ">
<custom-formatter class="org.jboss.logmanager.formatters.PatternFormatter" module="org.jboss.logmanager">
<properties>
<property name="pattern" value="1" />
</properties>
</custom-formatter>
</formatter>
{code}
No more configuration or code needed to reproduce.
was (Author: vsevolodgolovanov):
[~ander.parra], here, it's just a fresh standalone.xml with the following added:
{code}
<formatter name="ZZZZ">
<custom-formatter class="org.jboss.logmanager.formatters.PatternFormatter" module="org.jboss.logmanager">
<properties>
<property name="pattern" value="1" />
</properties>
</custom-formatter>
</formatter>
{code}
No more configuration or code needed to reproduce.
> Custom formatter property changes not written to, but overriden by logging.properties
> -------------------------------------------------------------------------------------
>
> Key: WFLY-3931
> URL: https://issues.jboss.org/browse/WFLY-3931
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 8.1.0.Final
> Environment: Wildfly 8.1.0.Final
> Reporter: Vsevolod Golovanov
> Assignee: James Perkins
> Attachments: standalone.xml
>
>
> When you first add custom formatter with properties to standalone.xml, on server start property values get correctly resolved and written to logging.properties.
> If you change property values in standalone.xml of an existing custom formatter, that was flushed to logging.properties before, then on the next server start new values don't get written to logging.properties and formatter instance gets the old values from logging.properties.
> For properties with static values that are defined in standalone.xml there is a workaround: change the custom formatter name each time you change a property value.
> But with more dynamic properties, e.g. that rely on system properties, it's not so simple...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFLY-3931) Custom formatter property changes not written to, but overriden by logging.properties
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-3931?page=com.atlassian.jira.plugin.... ]
Vsevolod Golovanov updated WFLY-3931:
-------------------------------------
Attachment: standalone.xml
[~ander.parra], here, it's just a fresh standalone.xml with the following added:
{code}
<formatter name="ZZZZ">
<custom-formatter class="org.jboss.logmanager.formatters.PatternFormatter" module="org.jboss.logmanager">
<properties>
<property name="pattern" value="1" />
</properties>
</custom-formatter>
</formatter>
{code}
No more configuration or code needed to reproduce.
> Custom formatter property changes not written to, but overriden by logging.properties
> -------------------------------------------------------------------------------------
>
> Key: WFLY-3931
> URL: https://issues.jboss.org/browse/WFLY-3931
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 8.1.0.Final
> Environment: Wildfly 8.1.0.Final
> Reporter: Vsevolod Golovanov
> Assignee: James Perkins
> Attachments: standalone.xml
>
>
> When you first add custom formatter with properties to standalone.xml, on server start property values get correctly resolved and written to logging.properties.
> If you change property values in standalone.xml of an existing custom formatter, that was flushed to logging.properties before, then on the next server start new values don't get written to logging.properties and formatter instance gets the old values from logging.properties.
> For properties with static values that are defined in standalone.xml there is a workaround: change the custom formatter name each time you change a property value.
> But with more dynamic properties, e.g. that rely on system properties, it's not so simple...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFLY-4136) sql parameter log issue spy
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4136?page=com.atlassian.jira.plugin.... ]
James Perkins closed WFLY-4136.
-------------------------------
Resolution: Rejected
After looking into there is no issue here. The way the spy logs the information is correct.
> sql parameter log issue spy
> ---------------------------
>
> Key: WFLY-4136
> URL: https://issues.jboss.org/browse/WFLY-4136
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 8.2.0.Final
> Environment: NA
> Reporter: Gulam Samdani
> Assignee: Jesper Pedersen
> Priority: Critical
>
> problem description is here .
> https://developer.jboss.org/thread/250027
> most of time several people not interested on jboss because this missing feature . it is important for development . but it is not impossible . so ,
> please add this feature next version . already all server tomcat , glassfish support this , why can not jboss offer this feature .
>
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFLY-2376) DataSource properties are not persisting via CLI
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2376?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2376:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1023064|https://bugzilla.redhat.com/show_bug.cgi?id=1023064] from POST to MODIFIED
> DataSource properties are not persisting via CLI
> ------------------------------------------------
>
> Key: WFLY-2376
> URL: https://issues.jboss.org/browse/WFLY-2376
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Jay Kumar SenSharma
> Assignee: Stefano Maestri
> Fix For: 9.0.0.Beta1
>
>
> - The CLI command show that there are some valid configuration properties available like following while configuring DataSources, However those properties never get persisted in the DataSource configuration:
> {quote}
> ./jboss-cli.sh --user=admin --password=admin@123 -c --controller=remote://localhost:9999 command="/subsystem=datasources/data-source=testpool:read-resource-description(recursive=true)"
> "stale-connection-checker-properties" => {
> "type" => OBJECT,
> "description" => "The stale connection checker properties",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "reauth-plugin-properties" => {
> "type" => OBJECT,
> "description" => "The properties for the reauthentication plugin",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "exception-sorter-properties" => {
> "type" => OBJECT,
> "description" => "The exception sorter properties",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> {quote}
> - Following command never complains about any issue and the following command executed without any issue but the above properties are not persisted in the DataSource.
> ./jboss-cli.sh --user=admin --password=admin@123 -c --controller=remote://localhost:9999 command="/subsystem=datasources/data-source=testpool:add(jndi-name=\"java:jboss/TestDS\",driver-name=\"ojdbc6.jar\",connection-url=\"jdbc:oracle:thin:@DBHostName:1521:DBName\",user-name=\"user\",password=\"pass\",new-connection-sql=\"select 1 from dual\", check-valid-connection-sql=\"select 2 from dual\",valid-connection-checker-class-name=\"org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker\",exception-sorter-properties={\"prop1\"=>\"value1\"},reauth-plugin-properties={\"reauthProp1\"=>\"reauthValue1\"},exception-sorter-properties={\"exceptionSorterProp1\"=>\"exceptionSorterValue1\"})"
> - The Generated DataSource looks like following:
> ${quote}
> <datasource jndi-name="java:jboss/TestDS" pool-name="testpool" enabled="true">
> <connection-url>jdbc:oracle:thin:@DBHostName:1521:DBName</connection-url>
> <driver>ojdbc6.jar</driver>
> <new-connection-sql>select 1 from dual</new-connection-sql>
> <security>
> <user-name>user</user-name>
> <password>pass</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker"/>
> <check-valid-connection-sql>select 2 from dual</check-valid-connection-sql>
> </validation>
> </datasource>
> ${quote}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFLY-4136) sql parameter log issue spy
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4136?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-4136:
--------------------------------
Security Sensitive Issue: (was: Check in case of security relevant issue)
Fix Version/s: (was: 9.0.0.Beta1)
Priority: Minor (was: Critical)
Labels: (was: jboss)
Assignee: Jesper Pedersen (was: James Perkins)
Component/s: JCA
(was: Logging)
This is not a logging issue. This should likely just be closed, but I'm not sure familiar with how the "spy" attribute works. Assigning to JCA to see if they have anything to add.
> sql parameter log issue spy
> ---------------------------
>
> Key: WFLY-4136
> URL: https://issues.jboss.org/browse/WFLY-4136
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 8.2.0.Final
> Environment: NA
> Reporter: Gulam Samdani
> Assignee: Jesper Pedersen
> Priority: Minor
>
> problem description is here .
> https://developer.jboss.org/thread/250027
> most of time several people not interested on jboss because this missing feature . it is important for development . but it is not impossible . so ,
> please add this feature next version . already all server tomcat , glassfish support this , why can not jboss offer this feature .
>
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months