May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-751) Always log a WARN for invalid resource adapters

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-751?page=com.atlassian.jira.plugin.... ] Jesper Pedersen resolved JBJCA-751. ----------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.CR1) Resolution: Done > Always log a WARN for invalid resource adapters > ----------------------------------------------- > > Key: JBJCA-751 > URL: https://issues.jboss.org/browse/JBJCA-751 > Project: IronJacamar > Issue Type: Task > Components: Deployer > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > IronJacamar 1.0 has been out and thereby given people a chance to fix their resource adapters. > Even if archive validation is turned off; if there is an error/warn log a WARN about the resource adapter -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-179?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-179: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] https://bugzilla.redhat.com/show_bug.cgi?id=959545 is for the composite operation issue. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: WFLY-179 > URL: https://issues.jboss.org/browse/WFLY-179 > Project: WildFly > Issue Type: Bug > Components: CLI, Clustering > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-179?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-179: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] @Alex, looking into this, this "Operation 'composite' does not expect any property issue" has nothing to do with the mod_cluster subsystem. The things Rado has pointed out may influence what results you would see when trying to isolate this issue, but it's a general problem with manually entered composite operations. I'll file a separate issue. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: WFLY-179 > URL: https://issues.jboss.org/browse/WFLY-179 > Project: WildFly > Issue Type: Bug > Components: CLI, Clustering > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-179?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-179: ---------------------------------------------- Radoslav Husar <rhusar(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] @Alex, I see your problem now. You seem to be using the stock profile to test this, however: You are specifying the "ajp" connector as a connector for mod_cluster. Note that AJP connector has been *removed* from the default profile in EAP 6.1.0, whereas it was present in EAP 6.0.1. The default profile now only specifies "http" connector. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: WFLY-179 > URL: https://issues.jboss.org/browse/WFLY-179 > Project: WildFly > Issue Type: Bug > Components: CLI, Clustering > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-23) Quoted script parameters are not properly parsed in the bash script

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-23?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-23: --------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 918030|https://bugzilla.redhat.com/show_bug.cgi?id=918030] OK, just reminder - if you won't find solution for Solaris 10, please limit readlink invocation only to Solaris 11 and Linux. > Quoted script parameters are not properly parsed in the bash script > ------------------------------------------------------------------- > > Key: WFLY-23 > URL: https://issues.jboss.org/browse/WFLY-23 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Quotes are added to parameters passed via the command line. When checking the parameters for the {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} properties quoted parameters are not found. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-179?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-179: ---------------------------------------------- Radoslav Husar <rhusar(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] I cannot reproduce this issue. I have created 2 servers using default configuration, where I removed mod_cluster subsystem. I let the servers autostart. I start the domain. I run the following batch: > [domain@localhost:9999 /] batch > [domain@localhost:9999 / #] /profile=default/subsystem=modcluster:add > #1 /profile=default/subsystem=modcluster:add > [domain@localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration:add(advertise=false, proxy-list="localhost:6666", connector=http) > #2 /profile=default/subsystem=modcluster/mod-cluster-config=configuration:add(advertise=false, proxy-list="localhost:6666", connector=http) > [domain@localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration:add > #3 /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration:add > [domain@localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration/load-metric=busyness:add(type=busyness) > #4 /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration/load-metric=busyness:add(type=busyness) > [domain@localhost:9999 / #] run-batch > The batch executed successfully I get correct logging (from server1) which I am expecting: > 19:29:48,306 DEBUG [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 1) Entered VERIFY stage; waiting for service container to settle > 19:29:48,306 DEBUG [org.jboss.as.modcluster] (ServerService Thread Pool -- 48) Starting Mod_cluster Extension > 19:29:48,327 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000001: Initializing mod_cluster ${project.version} > 19:29:48,331 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000003: Received server start event > 19:29:48,334 ERROR [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000043: Failed to send INFO to localhost/127.0.0.1:6666: java.net.ConnectException: Connection refused @Alex, what should I do differently to hit an issue? > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: WFLY-179 > URL: https://issues.jboss.org/browse/WFLY-179 > Project: WildFly > Issue Type: Bug > Components: CLI, Clustering > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-23) Quoted script parameters are not properly parsed in the bash script

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-23?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-23: --------------------------------------------- James Perkins <jperkins(a)redhat.com> made a comment on [bug 918030|https://bugzilla.redhat.com/show_bug.cgi?id=918030] I tried that it doesn't work either. It doesn't like the ${p#*=} bit. I'm trying to figure out how to handle that on Solaris 10 then we could test on Solaris 11. > Quoted script parameters are not properly parsed in the bash script > ------------------------------------------------------------------- > > Key: WFLY-23 > URL: https://issues.jboss.org/browse/WFLY-23 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Quotes are added to parameters passed via the command line. When checking the parameters for the {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} properties quoted parameters are not found. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-23) Quoted script parameters are not properly parsed in the bash script

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-23?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-23: --------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 918030|https://bugzilla.redhat.com/show_bug.cgi?id=918030] Uname for Solaris 10: --------------------- [hudson@dev20-01 ~]$ uname -a SunOS dev20-01.mw.lab.eng.bos.redhat.com 5.10 Generic_142910-17 i86pc i386 i86pc [hudson@dev20-01 ~]$ uname -v Generic_142910-17 [hudson@dev20-01 ~]$ uname -r 5.10 Uname for Solaris 11: --------------------- [hudson@dev21-01 ~]$ uname -a SunOS dev21-01 5.11 11.0 i86pc i386 i86pc [hudson@dev21-01 ~]$ uname -v 11.0 [hudson@dev21-01 ~]$ uname -r 5.11 Maybe code for darwin could be used for Solaris 10. > Quoted script parameters are not properly parsed in the bash script > ------------------------------------------------------------------- > > Key: WFLY-23 > URL: https://issues.jboss.org/browse/WFLY-23 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Quotes are added to parameters passed via the command line. When checking the parameters for the {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} properties quoted parameters are not found. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application

by Florian Beckmann (JIRA)

[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ] Florian Beckmann commented on AS7-5744: --------------------------------------- Just for completeness: I filed a bug report on sourceforge for sphinx4. https://sourceforge.net/p/cmusphinx/bugs/309/ > JRE logging.properties file in a jar fails the deployment of an application > --------------------------------------------------------------------------- > > Key: AS7-5744 > URL: https://issues.jboss.org/browse/AS7-5744 > Project: Application Server 7 > Issue Type: Bug > Components: EE, Logging > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows 7 pro > JBoss 7.1.3 > Reporter: Francois MESSIAEN > Assignee: James Perkins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > Attachments: logging.properties > > > If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown: > {noformat} > 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties' > at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final] > ... 5 more > Caused by: java.lang.IllegalArgumentException: className is null > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final] > at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122) > ... 6 more > 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service > JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear" > {noformat} > The content of the fullear.ear I use for this test is: > * lib > ** myejbClient.jar > * META-INF > ** application.xml > ** jboss-app.xml > ** jboss-deployment-structure.xml > ** jboss-ejb-client.xml > ** management-trackfolder-hornetq-jms.xml > ** MANIFEST.MF > * myejb.jar > * web.war > I put the logging.properties files in myejbclient.jar file. The content of that jar file is : > * org > ** mapp > *** ejb > **** logging.properties > **** Greeter.class > * META-INF > ** MANIFEST.MF > The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-23) Quoted script parameters are not properly parsed in the bash script

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-23?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-23: --------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 918030|https://bugzilla.redhat.com/show_bug.cgi?id=918030] Solaris 11 contains readlink command. [hudson@dev21-01 ~]$ which readlink /usr/bin/readlink Solaris 10 does NOT contain readlink command. Workaround is to use GNU coreutils - command greadlink, but we can't rely on tha fact it's installed on every Solaris 10 system. [hudson@dev20-01 ~]$ which greadlink /opt/csw/bin/greadlink code from https://github.com/sstephenson/ruby-build/pull/9/files resolve_link() { $(type -p greadlink readlink | head -1) $1 } ... path="$(resolve_link "$name" || true)" Suggestion: For Solaris we should limit readlink invocation only to Solaris 11 and maybe document workaround for Solaris 10 - define JBOSS_LOG_DIR variable. This was needed for all Solaris and Windows platforms in EAP 6.0.0 and EAP 6.0.1. > Quoted script parameters are not properly parsed in the bash script > ------------------------------------------------------------------- > > Key: WFLY-23 > URL: https://issues.jboss.org/browse/WFLY-23 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Quotes are added to parameters passed via the command line. When checking the parameters for the {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} properties quoted parameters are not found. -- 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

13 years, 2 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

jboss-jira May 2013