January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16380) JBOSS 6.2 EAP doesnt print jdk logging.

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16380?page=com.atlassian.jira.plugi... ] Vineela Gampa resolved JBIDE-16380. ----------------------------------- Release Notes Text: Didnt realize it is in jboss tools. Created new one in jboss application server platform. https://issues.jboss.org/browse/JBEAP-42 Resolution: Rejected > JBOSS 6.2 EAP doesnt print jdk logging. > ---------------------------------------- > > Key: JBIDE-16380 > URL: https://issues.jboss.org/browse/JBIDE-16380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Vineela Gampa > Labels: jboss > > We log request and response using com.sun.jersey.api.container.filter.LoggingFilter which uses java.util.logging.Logger . Application specific logs are getting printed with the below jboss-deployment-structure contents . > <exclusions> > <module name="org.apache.log4j" /> > <module name="org.slf4j.jcl-over-slf4j" /> > <module name="org.slf4j.impl" /> > <module name="org.slf4j" /> > <module name="org.slf4j.ext" /> > <module name="org.apache.commons.logging" /> > </exclusions> > Debugged a lot but couldnt figure out why jdk logging is going to jboss server.log rather than the appender configured in log4j.properties. > log4j.logger.com.sun.jersey.api.container.filter.LoggingFilter=INFO, RESTService > log4j.additivity.com.sun.jersey.api.container.filter.LoggingFilter=false > #requests to serve a log file > log4j.appender.RESTService=com.macys.mobile.framework.logging.log4j.v1216.AsynchronousRollingFileAppender > log4j.appender.RESTService.BufferSize=512 > log4j.appender.RESTService.Blocking=true > log4j.appender.RESTService.File=${app.log.root}/rest.log > log4j.appender.RESTService.DefaultConsoleThreshold=INFO > log4j.appender.RESTService.ConsoleThreshold=INFO > log4j.appender.RESTService.threshold=INFO > # Maximum file size and no: of back up files can be configured as per the production environment requirement > log4j.appender.RESTService.MaxFileSize=100MB > log4j.appender.RESTService.MaxBackupIndex=10 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16286: ---------------------------------------- Thanks! > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, maven > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: performance > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16380) JBOSS 6.2 EAP doesnt print jdk logging.

by Vineela Gampa (JIRA)

Vineela Gampa created JBIDE-16380: ------------------------------------- Summary: JBOSS 6.2 EAP doesnt print jdk logging. Key: JBIDE-16380 URL: https://issues.jboss.org/browse/JBIDE-16380 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Vineela Gampa We log request and response using com.sun.jersey.api.container.filter.LoggingFilter which uses java.util.logging.Logger . Application specific logs are getting printed with the below jboss-deployment-structure contents . <exclusions> <module name="org.apache.log4j" /> <module name="org.slf4j.jcl-over-slf4j" /> <module name="org.slf4j.impl" /> <module name="org.slf4j" /> <module name="org.slf4j.ext" /> <module name="org.apache.commons.logging" /> </exclusions> Debugged a lot but couldnt figure out why jdk logging is going to jboss server.log rather than the appender configured in log4j.properties. log4j.logger.com.sun.jersey.api.container.filter.LoggingFilter=INFO, RESTService log4j.additivity.com.sun.jersey.api.container.filter.LoggingFilter=false #requests to serve a log file log4j.appender.RESTService=com.macys.mobile.framework.logging.log4j.v1216.AsynchronousRollingFileAppender log4j.appender.RESTService.BufferSize=512 log4j.appender.RESTService.Blocking=true log4j.appender.RESTService.File=${app.log.root}/rest.log log4j.appender.RESTService.DefaultConsoleThreshold=INFO log4j.appender.RESTService.ConsoleThreshold=INFO log4j.appender.RESTService.threshold=INFO # Maximum file size and no: of back up files can be configured as per the production environment requirement log4j.appender.RESTService.MaxFileSize=100MB log4j.appender.RESTService.MaxBackupIndex=10 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16286: --------------------------------------- I have created JBIDE-16379 > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, maven > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: performance > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1692) Documentation plugins with context sensitive help

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1692?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-1692: -------------------------------------- We can at least do small default doc and link to JBoss Tools Documentation site > Documentation plugins with context sensitive help > ------------------------------------------------- > > Key: JBIDE-1692 > URL: https://issues.jboss.org/browse/JBIDE-1692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: help > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.3.x > > Attachments: SeamContextHelp.xml > > > Get doc into eclipse format > Have reference docs with context sensitive links -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-16379: ------------------------------------- Summary: Using symbolic links in the workspace path causes an infinite loop for m2e builder Key: JBIDE-16379 URL: https://issues.jboss.org/browse/JBIDE-16379 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.2.0.Alpha1 Reporter: Snjezana Peco Assignee: Snjezana Peco See JBIDE-16286 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-2032: -------------------------------------- We cannot, but we sure can provide simple help for such wizards without creating topics in help content. Details are [here|http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platfo...] Current buttons are not working because there is no Help context defined at all. What we need to do is: 1. Define default context with content explains that this wizard is part of JBoss Tools and has link to current JBoss Tools documentation 2. For relevant wizards like JQuery wizards called from palette we can provide more specific description with links to external resources Context (1) above should be used everywhere by default to avoid none working help buttons. For case (2) we should open JIRA for relevant wizards and work with Michelle to have good content and link to online documentation. It is not a big work and requires to add one xml file with context definintions and one line of code in java to attach context to UI element. It would not require to create new help topics in eclipse help. > Help button works not in all wizards. > ------------------------------------- > > Key: JBIDE-2032 > URL: https://issues.jboss.org/browse/JBIDE-2032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: help > Affects Versions: 2.1.0.beta1 > Reporter: Anton Klimkovich > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.x > > Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG > > > Wizards with non-working help button attached. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16286: ---------------------------------------- [~snjeza] yes, it seems that you are right. And it looks like a serious bug, doesn't it? What do you think? Using symbolic links in the workspace path should not cause an infinite loop for m2e builder. Could you please investigate this bug too? > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, maven > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: performance > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16378) Application wizard: Import/Create does not create server adapter by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16378?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16378: ------------------------------------------ This issue was introduced when fixing JBIDE-16340 > Application wizard: Import/Create does not create server adapter by default > --------------------------------------------------------------------------- > > Key: JBIDE-16378 > URL: https://issues.jboss.org/browse/JBIDE-16378 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.2.0.Alpha2 > > Attachments: create-server-adapter.png > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16378) Application wizard: Import/Create does not create server adapter by default

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16378: ---------------------------------------- Summary: Application wizard: Import/Create does not create server adapter by default Key: JBIDE-16378 URL: https://issues.jboss.org/browse/JBIDE-16378 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Alpha2 Reporter: Andre Dietisheim Fix For: 4.2.0.Alpha2 Attachments: create-server-adapter.png -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014