November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2492) CLONE - Domain processes doesn't run with -server argument

by Rostislav Svoboda (Created) (JIRA)

CLONE - Domain processes doesn't run with -server argument ---------------------------------------------------------- Key: AS7-2492 URL: https://issues.jboss.org/browse/AS7-2492 Project: Application Server 7 Issue Type: Bug Components: Scripts Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 Java processes started with domain.sh/domain.bat doesn't contain '-server' argument. This was introduced with AS7-372 (PROCESS_CONTROLLER_JAVA_OPTS HOST_CONTROLLER_JAVA_OPTS) Scripts domain.sh/domain.bat []1 [2] are adding '-server' to JAVA_OPTS depending on JDK. All 'JAVA_OPTS=...' in domain.sh/.bat should be changed to work with PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS. [1] https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... [2] https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-351) Implement the HttpService ontop of JBossWeb

by Thomas Diesler (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated AS7-351: ------------------------------- Component/s: OSGi Forum Reference: https://community.jboss.org/thread/150701 (was: https://community.jboss.org/thread/150701) > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Web > Reporter: Thomas Diesler > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-340) Port generic bean <ejb> element

by Carlo de Wolf (Created) (JIRA)

Port generic bean <ejb> element ------------------------------- Key: JBMETA-340 URL: https://issues.jboss.org/browse/JBMETA-340 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Reporter: Carlo de Wolf Priority: Critical -- 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, 8 months

5
8
0 / 0

[JBoss JIRA] (AS7-2450) add hornetq native libs

by Andy Taylor (Created) (JIRA)

add hornetq native libs ----------------------- Key: AS7-2450 URL: https://issues.jboss.org/browse/AS7-2450 Project: Application Server 7 Issue Type: Task Reporter: Andy Taylor Assignee: Andy Taylor -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console

by Andre Dietisheim (Commented) (JIRA)

[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim commented on JBASM-38: --------------------------------------- this bug was falsely assigned to jboss tools. it concerns the shutdown batch for JBoss AS6. If I did not move it to the correct project, please move it further. > shutdown the second time throw stack trace to the console > --------------------------------------------------------- > > Key: JBASM-38 > URL: https://issues.jboss.org/browse/JBASM-38 > Project: JBoss AS Server Manager > Issue Type: Enhancement > Environment: JBossAS 6.0.0.Final "Neo", Windows 7 > Reporter: Larry Chan > Assignee: Shelly McGowan > Priority: Minor > > I'm filing for my coworker who doesn't have an account here. > shutdown.bat -o 16.89.22.157 > Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu > b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE > xception: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33 > 8) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto > ry.java:248) > at org.jboss.Shutdown.main(Shutdown.java:235) > Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi. > ConnectException: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :101) > at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j > ava:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect > or.java:1886) > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j > ava:1856) > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25 > 7) > ... 2 more > Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157; > nested exception is: > java.net.ConnectException: Connection refused: connect > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198 > ) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :97) > ... 7 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at java.net.Socket.<init>(Socket.java:375) > at java.net.Socket.<init>(Socket.java:189) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect > SocketFactory.java:22) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster > SocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 12 more > Press any key to continue . . . > EXPECTED BEHAVIOR: > It is better and more standard just output message of "already shutdown". -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1801) Unable to create new profiles via the CLI

by Chris Hiner (JIRA)

Unable to create new profiles via the CLI ----------------------------------------- Key: AS7-1801 URL: https://issues.jboss.org/browse/AS7-1801 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Chris Hiner Assignee: Alexey Loubyansky Running/profile=exampleprofile:add() from the CLI gives an error message: "outcome" => "failed", "failure-description" => {"domain-failure-description" => "Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to marshal configuration"}, "rolled-back" => true [Host Controller] Caused by: java.lang.IllegalArgumentException [Host Controller] at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.dmr.ModelNode.keys(ModelNode.java:1085) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.writeProfile(DomainXml.java:502) [jboss-as-controller-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
4
0 / 0

[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console

by Andre Dietisheim (Assigned) (JIRA)

[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim reassigned JBASM-38: ------------------------------------- Assignee: Shelly McGowan (was: Rob Stryker) > shutdown the second time throw stack trace to the console > --------------------------------------------------------- > > Key: JBASM-38 > URL: https://issues.jboss.org/browse/JBASM-38 > Project: JBoss AS Server Manager > Issue Type: Enhancement > Environment: JBossAS 6.0.0.Final "Neo", Windows 7 > Reporter: Larry Chan > Assignee: Shelly McGowan > Priority: Minor > > I'm filing for my coworker who doesn't have an account here. > shutdown.bat -o 16.89.22.157 > Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu > b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE > xception: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33 > 8) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto > ry.java:248) > at org.jboss.Shutdown.main(Shutdown.java:235) > Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi. > ConnectException: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :101) > at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j > ava:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect > or.java:1886) > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j > ava:1856) > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25 > 7) > ... 2 more > Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157; > nested exception is: > java.net.ConnectException: Connection refused: connect > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198 > ) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :97) > ... 7 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at java.net.Socket.<init>(Socket.java:375) > at java.net.Socket.<init>(Socket.java:189) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect > SocketFactory.java:22) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster > SocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 12 more > Press any key to continue . . . > EXPECTED BEHAVIOR: > It is better and more standard just output message of "already shutdown". -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console

by Andre Dietisheim (Moved) (JIRA)

[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim moved JBIDE-10074 to JBASM-38: ----------------------------------------------- Project: JBoss AS Server Manager (was: Tools (JBoss Tools)) Key: JBASM-38 (was: JBIDE-10074) Component/s: (was: JBossAS/Servers) > shutdown the second time throw stack trace to the console > --------------------------------------------------------- > > Key: JBASM-38 > URL: https://issues.jboss.org/browse/JBASM-38 > Project: JBoss AS Server Manager > Issue Type: Enhancement > Environment: JBossAS 6.0.0.Final "Neo", Windows 7 > Reporter: Larry Chan > Assignee: Rob Stryker > Priority: Minor > > I'm filing for my coworker who doesn't have an account here. > shutdown.bat -o 16.89.22.157 > Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu > b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE > xception: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33 > 8) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto > ry.java:248) > at org.jboss.Shutdown.main(Shutdown.java:235) > Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi. > ConnectException: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :101) > at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j > ava:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect > or.java:1886) > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j > ava:1856) > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25 > 7) > ... 2 more > Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157; > nested exception is: > java.net.ConnectException: Connection refused: connect > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198 > ) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :97) > ... 7 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at java.net.Socket.<init>(Socket.java:375) > at java.net.Socket.<init>(Socket.java:189) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect > SocketFactory.java:22) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster > SocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 12 more > Press any key to continue . . . > EXPECTED BEHAVIOR: > It is better and more standard just output message of "already shutdown". -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2380) Decide how to distribute jars that are intended for client use only

by Thomas Diesler (Created) (JIRA)

Decide how to distribute jars that are intended for client use only ------------------------------------------------------------------- Key: AS7-2380 URL: https://issues.jboss.org/browse/AS7-2380 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.1.0.Beta1 Shelly says: One question I have, though, is the jar, jboss-as-ee-deployment-7.1.0.Alpha2-SNAPSHOT.jar, is not even part of the build. How do we ship a compliant EE implementation with JSR-88 if it is not included? I have to pick this jar up from jboss-as/ee-deployment/target -- 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, 8 months

4
5
0 / 0

[JBoss JIRA] (AS7-2361) It appears there is no external JNDI port like 1099, even though the ports are in the console

by Jim Tyrrell (Created) (JIRA)

It appears there is no external JNDI port like 1099, even though the ports are in the console --------------------------------------------------------------------------------------------- Key: AS7-2361 URL: https://issues.jboss.org/browse/AS7-2361 Project: Application Server 7 Issue Type: Feature Request Components: Naming Reporter: Jim Tyrrell Assignee: John Bailey Many many customers use client lookups of JNDI contexts to get at what used to be called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is this be design? If so, this is going to be a problem for many current customers, as they do this today. -- 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, 8 months

9
15
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 November 2011