[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 11:07 AM:
------------------------------------------------------------------
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
was (Author: emag):
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe commented on WFLY-1721:
----------------------------------------
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (WFLY-1969) PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1969?page=com.atlassian.jira.plugin.... ]
Alessio Soldano reassigned WFLY-1969:
-------------------------------------
Assignee: Alessio Soldano (was: Derek Horton)
> PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
> --------------------------------------------------------------------------------------
>
> Key: WFLY-1969
> URL: https://issues.jboss.org/browse/WFLY-1969
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Alpha4
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 8.0.0.Beta1
>
>
> A linkage error javax.xml.crypto.dsig.XMLSignContext is thrown when a XMLSignatureFactory is first resolved by PicketLink (instead of the WS subsystem) on WFLY.
> This should be fixed by tuning the module dependencies in org.picketlink module, either by modifying the relative order of org.apache.santuario.xmlsec and javax.api modules, or -better by setting an exclude block as follows:
> {noformat}
> ...
> <module name="org.apache.santuario.xmlsec">
> <imports>
> <exclude path="javax/*"/>
> </imports>
> </module>
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-1721:
-----------------------------------
Found the issue, directory variable is not properly expanded.
if you look into $WILDFLY_HOME/bin/
you will see ${jboss.server.log.dir} directory with log in it.
i will send fix to address this.
for now you can just specify directory without variable.
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ]
Dimitris Andreadis commented on WFLY-1547:
------------------------------------------
This JIRA just came to my attention. Have you guys considered what happens in the Windows case, as well? Because in older releases (3/4.x) we always had to clean-up the tmp directory upon start-up *anyway* due to the windows/classloader file locking problem.
> deploy directories not cleaned up
> ---------------------------------
>
> Key: WFLY-1547
> URL: https://issues.jboss.org/browse/WFLY-1547
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Reporter: Shaun Appleton
> Assignee: Bartosz Baranowski
> Attachments: deployment_with_hack_no_hook.txt
>
>
> JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories.
> The following reproduces this -
> i) ensure run.conf has the -Xrs set
> ii) ensure deployments has a deployable .ear in it
> iii) ./run standalone.sh and allow the deployments to deploy
> iv) stop the EAP process ie kill <process_id>
> v) observe content tmp/vfs
> (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP)
> This will eventually cause problems with lack of disk space.
> Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems.
> It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 10:46 AM:
------------------------------------------------------------------
{quote}
even if you request some page, does access log file gets created then?
{quote}
No.
{code}
$ wget localhost:8080
// wait a little while...
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6.
was (Author: emag):
{quote}
even if you request some page, does access log file gets created then?
{quote}
No.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6.
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (HIBERNATE-142) @JoinColumn annotation doesn't fully support column names requiring double-quotes
by Paul Spinelli (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-142?page=com.atlassian.jira.plu... ]
Paul Spinelli commented on HIBERNATE-142:
-----------------------------------------
My bad. Since I have a workaround, I'm in no rush. If you can move it when you do have time, I'd be happy with that. Thanks!
> @JoinColumn annotation doesn't fully support column names requiring double-quotes
> ---------------------------------------------------------------------------------
>
> Key: HIBERNATE-142
> URL: https://issues.jboss.org/browse/HIBERNATE-142
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Hibernate 4.2.4-Final
> Eclipse Juno
> J2EE 3.0 Web app
> Reporter: Paul Spinelli
> Assignee: Steve Ebersole
> Priority: Minor
>
> Due to the way an existing database schema has been configured, my JPA annotations (using Hibernate as my provider) all required that table names/column names be double-quoted:
> (e.g. String ID_COLUMN_NAME = "\"Id\"";)
> This does not pose a problem EXCEPT when using the @JoinColumn annotation (specifically, the 'referencedColumnName' attribute). This DOES NOT work (I get an error that the logical column name cannot be found):
> @JoinColumn(name=ID_COLUMN_NAME, referencedColumnName=ID_COLUMN_NAME)
> However, this DOES work:
> @JoinColumn(name=ID_COLUMN_NAME, referencedColumnName="`Id`")
> It seems that the 'name' attribute supports double-quotes while the 'referencedColumnName' attribute does not. Is there a reason it should not?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months