March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBBUILD-716) Add scm revision and build timestamp to all jar manifests

by Paul Gier (JIRA)

Paul Gier created JBBUILD-716: --------------------------------- Summary: Add scm revision and build timestamp to all jar manifests Key: JBBUILD-716 URL: https://issues.jboss.org/browse/JBBUILD-716 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Reporter: Paul Gier Assignee: Paul Gier Fix For: JBoss Parent POM - 9 Add the scm revision (git ID) and human readable build timestamp to all jar manifests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
5
0 / 0

[JBoss JIRA] (AS7-4177) Add handler for /host=xxx/server=yyy/interface=zzz tries to install a runtime service

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4177: ------------------------------------- Summary: Add handler for /host=xxx/server=yyy/interface=zzz tries to install a runtime service Key: AS7-4177 URL: https://issues.jboss.org/browse/AS7-4177 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.2.Final The /host=xxx/server=yyy/interface=zzz resource is a configuration-only resource inside the Host Controller, but when the add handlers for it run, they are attempting to install runtime services. The runtime services should only be installed in the server process. This leads to boot failures if different server configs declare an interface with the same name (which would be the norm if an server-level interface config is declared at all): [Host Controller] 13:55:33,400 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("server-config" => "server-two"), [Host Controller] ("interface" => "public") [Host Controller] ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.network.public is already registered [Host Controller] at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [Host Controller] at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:955) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] [Host Controller] at org.jboss.as.server.services.net.SpecifiedInterfaceAddHandler.performRuntime(SpecifiedInterfaceAddHandler.java:56) [Host Controller] at org.jboss.as.controller.operations.common.InterfaceAddHandler.performRuntime(InterfaceAddHandler.java:110) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4176) JDR fails to collect large logfiles on Windows

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-4176: ---------------------------------- Summary: JDR fails to collect large logfiles on Windows Key: AS7-4176 URL: https://issues.jboss.org/browse/AS7-4176 Project: Application Server 7 Issue Type: Bug Components: JDR Environment: This failure happens on any Windows environment Reporter: Jesse Jaggars Assignee: Jesse Jaggars Fix For: 7.1.2.Final Large log files are tailed via shelling out to `tail`. Upstream sosreport has implemented a cross-platform way to perform this operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4174) Remote client failover does not work properly

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-4174: ------------------------------------- Summary: Remote client failover does not work properly Key: AS7-4174 URL: https://issues.jboss.org/browse/AS7-4174 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai It seems that remote client failover does not work properly. I have two servers connected in cluster where a stateful bean is deployed. My steps are following: 1) Start both servers 2) Run client. Client connects to server1 and lookups the stateful bean there. Client still runs and possess proxy of bean. 3) Kill server1 4) Let client invoke a method on bean remotely. I would suppose that client should be routed to server2 and it should get a response. But client fails with timeout with {code} Exception in thread "main" java.lang.IllegalStateException: No EJB receiver contexts available in cluster ejb {code} You can check my client: https://github.com/ochaloup/testing/blob/master/myejbclient/src/client/Cl... and the stateful bean: https://github.com/ochaloup/testing/blob/master/myejb/ejbModule/ochaloup/... https://github.com/ochaloup/testing/blob/master/myejbclient/src/jboss-ejb... I run servers like: bin/standalone.sh -c=standalone-ha.xml -Djboss.node.name=clust1 bin/standalone.sh -c=standalone-ha.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=clust2 client is run by command: java -cp myejbclient.jar:$JBOSS_HOME/build/target/jboss1/bin/client/jboss-client.jar client.ClientStateful (the jar files will be attached) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-4114) datasource min/max pool size details not available via json/cli

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-4114?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber reassigned AS7-4114: ---------------------------------------- Assignee: Stefano Maestri (was: Fernando Nasser) "undefined" means it's not configured, not sure if there is a default value which should be exposed instead. There is a "statistics" exposing additional metrics. > datasource min/max pool size details not available via json/cli > --------------------------------------------------------------- > > Key: AS7-4114 > URL: https://issues.jboss.org/browse/AS7-4114 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.Final > Environment: DR13, cli/json interface. > Reporter: Simeon Pinder > Assignee: Stefano Maestri > Labels: rhq > > Use cli to browse data with recursive/runtime both true but fields are undefined. The max/min pool sizes are available via localhost:9990/console/App.hmtl. > /subsystem=datasources/data-source=H2DS/ > max-pool-size => undefined > min-pool-size => undefined -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4114) datasource min/max pool size details not available via json/cli

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-4114?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber commented on AS7-4114: ------------------------------------------ Assigning to Stefano, since i am not sure if this is a bug. > datasource min/max pool size details not available via json/cli > --------------------------------------------------------------- > > Key: AS7-4114 > URL: https://issues.jboss.org/browse/AS7-4114 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.Final > Environment: DR13, cli/json interface. > Reporter: Simeon Pinder > Assignee: Stefano Maestri > Labels: rhq > > Use cli to browse data with recursive/runtime both true but fields are undefined. The max/min pool sizes are available via localhost:9990/console/App.hmtl. > /subsystem=datasources/data-source=H2DS/ > max-pool-size => undefined > min-pool-size => undefined -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4175) Deployment content is not always removed from data/content

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4175: ------------------------------------- Summary: Deployment content is not always removed from data/content Key: AS7-4175 URL: https://issues.jboss.org/browse/AS7-4175 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final, 7.1.0.Final Reporter: Brian Stansberry Assignee: Kabir Khan Priority: Critical Fix For: 7.1.2.Final Attachments: test-ds.xml The AS7-341 fix doesn't seem to be working in some use cases. I'll attach a test-ds.xml that can be used to manual reproduce this. Using a -ds.xml is useful since it's trivial to modify the deployment file to create a new hash. >From the CLI, this works (i.e. when both steps are done there are zero additional subdirectories in data/content, i.e. zero total directories on a fresh install): [standalone@localhost:9999 /] deploy /home/me/test-ds.xml [standalone@localhost:9999 /] undeploy test-ds.xml However, this does not work (i.e. when both steps are done there is one additional subdirectories in data/content, i.e. one total directory on a fresh install): [standalone@localhost:9999 /] deploy /home/me/test-ds.xml manually modify /home/me/test-ds.xml [standalone@localhost:9999 /] deploy --force /home/me/test-ds.xml There may be other permutations of the of deploy/redeploy/undeploy that also leave file behind. In particular, the forum thread references using the jboss maven plugin, so whatever ops it is invoking should be checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-4115) Jboss Web Connector resources max-threads data not available in ui or cli/json data

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-4115?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber reassigned AS7-4115: ---------------------------------------- Assignee: Jean-Frederic Clere (was: Fernando Nasser) I think the attribute you are looking for is max-connections. There is no max-threads anymore. Assigning to jean-frederic to validate. > Jboss Web Connector resources max-threads data not available in ui or cli/json data > ------------------------------------------------------------------------------------ > > Key: AS7-4115 > URL: https://issues.jboss.org/browse/AS7-4115 > Project: Application Server 7 > Issue Type: Bug > Environment: Using JBEAP-6.0.0.ER1. > Reporter: Simeon Pinder > Assignee: Jean-Frederic Clere > Labels: rhq > > Looks like max-threads is not currently exposed for JBoss Web Connectors. > "connector" => {"http" => { > "bytesReceived" => "0", > "bytesSent" => "0", > "enable-lookups" => false, > "enabled" => true, > "errorCount" => "0", > "max-post-size" => 2097152, > "max-save-post-size" => 4096, > "maxTime" => "0", > "processingTime" => "0", > "protocol" => "HTTP/1.1", > "redirect-port" => 8443, > "requestCount" => "0", > "scheme" => "http", > "secure" => false, > "socket-binding" => "http", > "ssl" => undefined, > "virtual-server" => undefined > }} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4173) Upgrade Infinispan to 5.1.3.Final

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4173: ----------------------------------- Summary: Upgrade Infinispan to 5.1.3.Final Key: AS7-4173 URL: https://issues.jboss.org/browse/AS7-4173 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.2.Final Tracking Jira to pull Infinispan fixes to AS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4116) removal of unrequested json snippet '"server-groups" => undefined' postpended to operation responses via cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4116?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-4116: ------------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > removal of unrequested json snippet '"server-groups" => undefined' postpended to operation responses via cli > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-4116 > URL: https://issues.jboss.org/browse/AS7-4116 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Reporter: Simeon Pinder > Assignee: Emanuel Muckenhuber > Priority: Minor > Labels: rhq > Fix For: 7.1.2.Final > > > When submitting operations to as7 via CLI sometimes and extra ["server-groups" => undefined] string is post-pended to the response. The result is still valid JSON it appears, but the results are potentially confusing to external json integrators. > To reproduce: > - run AS7 via domain.sh to run HostController. > - login > - submit the following operation: > /host=master/core-service=platform-mbean/type=threading/:read-resource(recursive=true,proxies=false,include-runtime=true,include-defaults=true) > - Look at the result returned: > { > "outcome" => "success", > "result" => { > "all-thread-ids" => [ > 2173L, > 2172L, > 2171L, > 51L, > 50L, > 49L, > 48L, > 45L, > 44L, > 43L, > 42L, > 41L, > 40L, > 39L, > 38L, > 37L, > 36L, > 35L, > 34L, > 33L, > 32L, > 31L, > 30L, > 29L, > 28L, > 27L, > 26L, > 25L, > 24L, > 23L, > 22L, > 21L, > 19L, > 18L, > 17L, > 16L, > 15L, > 14L, > 13L, > 12L, > 11L, > 8L, > 4L, > 3L, > 2L, > 1L > ], > "thread-contention-monitoring-supported" => true, > "thread-cpu-time-supported" => true, > "current-thread-cpu-time-supported" => true, > "object-monitor-usage-supported" => true, > "synchronizer-usage-supported" => true, > "thread-contention-monitoring-enabled" => false, > "thread-cpu-time-enabled" => true, > "thread-count" => 46, > "peak-thread-count" => 49, > "total-started-thread-count" => 2168L, > "daemon-thread-count" => 6, > "current-thread-cpu-time" => 0L, > "current-thread-user-time" => 0L > }, > "server-groups" => undefined > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

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 March 2012