January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3184) Subdeployments not shown in JBoss console

by Richard Opalka (Created) (JIRA)

Subdeployments not shown in JBoss console ----------------------------------------- Key: AS7-3184 URL: https://issues.jboss.org/browse/AS7-3184 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1 Reporter: Richard Opalka Assignee: Heiko Braun Priority: Critical Fix For: 7.1.0.Final When there are subdeployments in ear these are not shown in JBoss administation console. For example there's missing web subdeployment with webservice endpoints listing. -- 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

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-2859) Management: unable to add connector listening on created interface

by Dominik Pospisil (Created) (JIRA)

Management: unable to add connector listening on created interface ------------------------------------------------------------------ Key: AS7-2859 URL: https://issues.jboss.org/browse/AS7-2859 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Creating connector listening on newly created inteface fails with: MSC00001: Failed to start service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface Steps to reproduce: 1) create new interface /interface=test-interface:add(nic="tun0") 2) add socket binding which uses created interface /socket-binding-group=standard-sockets/socket-binding=test-binding:add(interface="test-interface", port=9091) 3) add web connector /subsystem=web/connector=test:add(socket-binding="test-binding", protocol="HTTP/1.1", scheme="http") Step 3 fails with: 16:27:56,388 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:95) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23] at java.lang.Thread.run(Thread.java:679) [:1.6.0_23] 16:27:56,592 INFO [org.jboss.as.controller] (Remoting "simkin:MANAGEMENT" task-2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface -- 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

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-2073) Add Connector Operation returns success even if connector fails to start

by Dominik Pospisil (Created) (JIRA)

Add Connector Operation returns success even if connector fails to start ------------------------------------------------------------------------ Key: AS7-2073 URL: https://issues.jboss.org/browse/AS7-2073 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Affects Versions: 7.1.0.Alpha1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Steps to reproduce: 1) start standalone server 2) issue: /socket-binding-group=standard-sockets/socket-binding=https:add(port=8443) /subsystem=web/connector=test-connectr:add(socket-binding=https, scheme=https, protocol="HTTP/1.1", enabled=true) What happens is that created connector fails to start due to misssing keystore file. However the configuration model is updated and the operation returns success. I think that the model should be rolled back and the operation should return failure. -- 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

12 years, 8 months

7
11
0 / 0

[JBoss JIRA] (AS7-2403) Host Controller should log joining/leaving domain (INFO) level

by Kevin Barfield (Created) (JIRA)

Host Controller should log joining/leaving domain (INFO) level -------------------------------------------------------------- Key: AS7-2403 URL: https://issues.jboss.org/browse/AS7-2403 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kevin Barfield Assignee: Brian Stansberry Priority: Minor When a host joins/leaves a domain, there is a INFO log message showing the slave join on the domain controller console. There should be the same INFO log message on the host controller console. -- 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

12 years, 8 months

6
5
0 / 0

[JBoss JIRA] (AS7-3437) JMS clients - Remote JNDI lookup does not work in EAP6/AS7

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on AS7-3437: ------------------------------------- JNP is not important in example code. "properties" should just express that lookups are remote. Main point of this jira was to have remote JNDI. Since AS7-1338 was re-opened, all discussions can move there. > JMS clients - Remote JNDI lookup does not work in EAP6/AS7 > ---------------------------------------------------------- > > Key: AS7-3437 > URL: https://issues.jboss.org/browse/AS7-3437 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: David Lloyd > Priority: Blocker > Fix For: No Release > > > EAP6/AS7 have not yet implemented remote jndi lookups. This feature is important for standalone jms clients to work and also ensure backward compatibility with EAP5/AS6 applications. Following piece of code should work without change: > Properties properties = new Properties(); > properties.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); > properties.setProperty("java.naming.provider.url", "jnp://server_hostname:1099"); > properties.setProperty("java.naming.factory.url.pkgs", "org.jnp.interfaces.NamingContextFactory"); > context = new InitialContext(properties); > ConnectionFactory cf = (ConnectionFactory) context.lookup("RemoteConnectionFactory"); > con = cf.createConnection(); > session = con.createSession(false, Session.CLIENT_ACKNOWLEDGE); > Queue queue = (Queue) context.lookup("/queue/test"); > For now there is a workaround but it's not suitable for us. Example code: > https://github.com/jbossas/jboss-as/tree/master/demos/legacy/src/main/jav... > There are AS7 jiras related to this missing feature which are closed as rejected/duplicated. In AS7-1338 J. Green explains that some kind of remote jndi functionality will be in AS 7.1 (as part of the EE full profile). Unfortunately AS 7.1 is still missing this feature. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1850) Domain - system properties for log, data, temp aren't reflected

by Rostislav Svoboda (JIRA)

Domain - system properties for log, data, temp aren't reflected --------------------------------------------------------------- Key: AS7-1850 URL: https://issues.jboss.org/browse/AS7-1850 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Scripts Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Alpha1 Some properties defined in https://docs.jboss.org/author/display/AS71/Command+line+parameters and in {{HostControllerEnvironment}} (org.jboss.as.host.controller) aren't reflected by current implementation. Affected properties: - jboss.domain.data.dir - jboss.domain.log.dir - jboss.domain.temp.dir In my scenario only jboss.domain.deployment.dir and jboss.domain.servers.dir were reflected. Structure for host-controller and process-controller logs + structure for data, log, tmp directories for server instances can't be mapped to that three properties. Maybe these properties could work: - jboss.domain.host-controller.log.dir - jboss.domain.process-controller.log.dir - jboss.domain.server-one.data.dir - jboss.domain.server-one.log.dir - jboss.domain.server-one.temp.dir - jboss.domain.server-xy.data.dir - jboss.domain.server-xy.log.dir - jboss.domain.server-xy.temp.dir Reproducer of my steps: {code} rm -rf xx-data xx-log xx-temp xx-deployment xx-servers mkdir xx-data xx-log xx-temp xx-deployment xx-servers bin/domain.sh -Djboss.domain.data.dir=xx-data -Djboss.domain.log.dir=xx-log -Djboss.domain.temp.dir=xx-temp -Djboss.domain.deployment.dir=xx-deployment -Djboss.domain.servers.dir=xx-servers bin/jboss-admin.sh --connect controller=127.0.0.1 command='deploy /home/rsvoboda/devel/JBQA-5161-scripts-testing/target/props.war --all-server-groups' bin/jboss-admin.sh --connect controller=127.0.0.1 command='undeploy props.war --all-relevant-server-groups' ls -al xx-data xx-log xx-temp xx-deployment xx-servers {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
6
0 / 0

[JBoss JIRA] (AS7-1820) CLONE - CLI - provide description for "add-jms-cf " command with examples

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-1820?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-1820. ------------------------------------ Resolution: Won't Fix The description will be the command is deprecated, connection-factory command should be used instead. > CLONE - CLI - provide description for "add-jms-cf " command with examples > ------------------------------------------------------------------------- > > Key: AS7-1820 > URL: https://issues.jboss.org/browse/AS7-1820 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.1.Final > > > Command "add-jms-cf" is missing description for all attributes. Could it be improved, please? Also examples of usages would be very helpful. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-895) Intermittent issues pushing content for deployment "full-replace" to slave host

by Brian Stansberry (JIRA)

Intermittent issues pushing content for deployment "full-replace" to slave host ------------------------------------------------------------------------------- Key: AS7-895 URL: https://issues.jboss.org/browse/AS7-895 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Intermittently seeing this: java.lang.AssertionError: "Operation was not applied successfully to any servers" at org.junit.Assert.fail(Assert.java:91) at org.jboss.as.test.integration.domain.DomainTestSupport.validateResponse(DomainTestSupport.java:124) at org.jboss.as.test.integration.domain.DeploymentManagementTestCase.executeOnMaster(DeploymentManagementTestCase.java:718) at org.jboss.as.test.integration.domain.DeploymentManagementTestCase.testManagedFullReplaceUnmanaged(DeploymentManagementTestCase.java:639) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) at org.apache.maven.surefire.Surefire.run(Surefire.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) Standard Output Reading response from http://127.0.0.1:8080/test/index.html: Reading response from http://127.0.0.1:8630/test/index.html: Reading response from http://127.0.0.1:8080/test/index.html: OK Reading response from http://127.0.0.1:8630/test/index.html: OK Failed response: { "outcome" => "failed", "result" => {"server-groups" => { "main-server-group" => { "main-one" => { "host" => "master", "response" => { "outcome" => "success", "result" => undefined, "compensating-operation" => { "operation" => "full-replace-deployment", "address" => [], "name" => "test.war", "content" => [{"hash" => bytes { 0x00, 0xbf, 0x50, 0x4d, 0x4b, 0x51, 0x74, 0x52, 0x3b, 0x21, 0x10, 0x3c, 0x80, 0xe6, 0x8b, 0x86, 0xe1, 0x19, 0x41, 0xf6 }}], "runtime-name" => "test.war" } } }, "main-three" => { "host" => "slave", "response" => { "outcome" => "failed", "failure-description" => "No deployment content with hash 00bf504d4b5174523b21103c80e68b86e11941f6 is available in the deployment content repository." } } }, "other-server-group" => {"other-two" => { "host" => "slave", "response" => { "outcome" => "failed", "failure-description" => "No deployment content with hash 00bf504d4b5174523b21103c80e68b86e11941f6 is available in the deployment content repository." } }} }}, "failure-description" => "Operation was not applied successfully to any servers" } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
7
0 / 0

[JBoss JIRA] (AS7-3178) Memory leak in controller client

by Stuart Douglas (Created) (JIRA)

Memory leak in controller client -------------------------------- Key: AS7-3178 URL: https://issues.jboss.org/browse/AS7-3178 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Stuart Douglas Assignee: Stuart Douglas Priority: Critical Fix For: 7.1.0.Final org.jboss.as.protocol.mgmt.AbstractMessageHandler registers a close handler but does not remove it. This means that every message is retained in memory until the connection is closed. If the messages are large this can result in a significant leak (such as in the CDI TCK, where each message is holding onto the deployment bytes). -- 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

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-3421) Upgrade Infinispan to 5.1.0.FINAL

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3421: --------------------------------- Summary: Upgrade Infinispan to 5.1.0.FINAL Key: AS7-3421 URL: https://issues.jboss.org/browse/AS7-3421 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Final -- 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

12 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012