March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3983) I have deployed a ejb3 in jboss7.1 server. I'm getting CommunicationException

by narendra reddy (JIRA)

narendra reddy created AS7-3983: ----------------------------------- Summary: I have deployed a ejb3 in jboss7.1 server. I'm getting CommunicationException Key: AS7-3983 URL: https://issues.jboss.org/browse/AS7-3983 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Environment: Windows environment Reporter: narendra reddy Assignee: jaikiran pai Fix For: 7.1.1.Final Dear friends, javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1452) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:597) Please help us, would appreciated. Thanks. -- 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

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3046) Can't pass authentication step to Web Admin console if two already created users has the same login name

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3046?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-3046. ------------------------------- It isn't able to have two users in this case now, closing as verified. > Can't pass authentication step to Web Admin console if two already created users has the same login name > -------------------------------------------------------------------------------------------------------- > > Key: AS7-3046 > URL: https://issues.jboss.org/browse/AS7-3046 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Blocker > > One part of this issue is due JBPAPP-7760. There isn't any check if user already exists when new one is creating. > Next part is new - I think is it useful and meaningful if we can create two users with the same user name but each belongs to different Realm, but in this case pass authentication dialog in Web Admin console isn't possible even for user belongs to ManagementRealm realm. > Also when I've created two identical users (both under ManagementRealm, it is possible now due to JBPAPP-7760), no one can pass the same step as above even they have the same password. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3044) bin/add-user.sh allows create two identical users

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3044?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-3044. ------------------------------- Verified, fixed... > bin/add-user.sh allows create two identical users > ------------------------------------------------- > > Key: AS7-3044 > URL: https://issues.jboss.org/browse/AS7-3044 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Fix For: 7.1.0.CR1 > > > bin/add-user.sh allows to create two identical users even you specify really the same input values (realm, login name and password). It created two lines in mgmt-users.properties. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3912) Unable to get Soapmessage in jboss 5.1.0 GA

by Murugan D (JIRA)

Murugan D created AS7-3912: ------------------------------ Summary: Unable to get Soapmessage in jboss 5.1.0 GA Key: AS7-3912 URL: https://issues.jboss.org/browse/AS7-3912 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Murugan D Assignee: Alessio Soldano When I execute context.getMessage().getSOAPBody() in jboss 5.1.0 GA AS. Then am getting the org.jboss.util.NotImplementedException exception. Code Snippet:- protected String extractOperation(SOAPMessageContext context) { SOAPBody body; try { body = context.getMessage().getSOAPBody(); } catch (SOAPException e) { logger.error("Error fetching the soap body. Exception=" + e, e); return null; } } -- 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

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3976) EJB client sometimes does not loadbalance

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3976: ----------------------------------- Summary: EJB client sometimes does not loadbalance Key: AS7-3976 URL: https://issues.jboss.org/browse/AS7-3976 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Critical Fix For: 7.1.1.Final I noticed that with a 2 node cluster, sometimes all sessions are created only on one node. Looks like cluster view is not updating properly on the client. See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Performance-Cluste... for logs. -- 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

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1412) ServerEnvironment accepts invalid or non-existent directory configurations

by Thomas Diesler (JIRA)

ServerEnvironment accepts invalid or non-existent directory configurations -------------------------------------------------------------------------- Key: AS7-1412 URL: https://issues.jboss.org/browse/AS7-1412 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Assignee: Brian Stansberry I tried changing the testsuite/pom.xml to allow tests to override certain AS7 modules, by adding a "testsuite" modules entry to the module.path. It looks like OSGI gets confused by multiple entries in the module path. module.path = /home/smarlow/work/as7/testsuite/compat/target/jbossas:/home/smarlow/work/as7/testsuite/compat/../../build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/modules server.log http://pastie.org/2278519 that shows what looks like an OSGI error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
11
0 / 0

[JBoss JIRA] (AS7-3782) Incomplete IP addresses substitution in server configs via XSLT file changeIPAddresses.xsl

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3782?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-3782. ------------------------------- Verified, seems ok. > Incomplete IP addresses substitution in server configs via XSLT file changeIPAddresses.xsl > ------------------------------------------------------------------------------------------ > > Key: AS7-3782 > URL: https://issues.jboss.org/browse/AS7-3782 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > > When you specify *$node0* variable, you might expect appropriate changes in standalone*.xml config files. But there are several unmodified places, where "hard-coded" value *127.0.0.1* is used yet. > - This element exists in every config: > {code:xml} > <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host> > {code} > - This element exists in every *-full.xml config: > {code:xml} > <interface name="unsecure"> >  > <inet-address value="127.0.0.1"/> > </interface> > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3689) Update state icons

by Heiko Braun (JIRA)

Heiko Braun created AS7-3689: -------------------------------- Summary: Update state icons Key: AS7-3689 URL: https://issues.jboss.org/browse/AS7-3689 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.1.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

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3688) Update EAP look&feel

by Heiko Braun (JIRA)

Heiko Braun created AS7-3688: -------------------------------- Summary: Update EAP look&feel Key: AS7-3688 URL: https://issues.jboss.org/browse/AS7-3688 Project: Application Server 7 Issue Type: Task Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.1.Final Attachments: eap_gui_revised.png -- 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

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-3973) Yet another place where hardcoded IPv4 address scheme is used

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3973?page=com.atlassian.jira.plugin.s... ] Pavel Janousek updated AS7-3973: -------------------------------- Description: After the last Stuart commit and merge to upstream (on -Thursday- Wednesday morning CET time zone), there are still some places where hardcoded IPv4 address scheme is used. Wrong TestCases are: - org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase - org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase Both of them use 127.0.0.1 directly even -Dnode0=::1 - it seems to be some other magic inside them because [there|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-t...] TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like: {code} #127.0.0.1 localhost.localdomain #127.0.0.1 pjanouse.brq.redhat.com localhost ::1 localhost6.localdomain6 localhost6 localhost ::1 pjanouse.brq.redhat.com localhost 127.0.0.2 both ::2 both 2001:0000:1234:0000:0000:c1c0:abcd:0876 ip6 {code} I've got this result:{code} Tests in error: org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out {code} It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation. was: After the last Stuart commit and merge to upstream (on Thursday morning CET time zone), there are still some places where hardcoded IPv4 address scheme is used. Wrong TestCases are: - org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase - org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase Both of them use 127.0.0.1 directly even -Dnode0=::1 - it seems to be some other magic inside them because [there|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-t...] TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like: {code} #127.0.0.1 localhost.localdomain #127.0.0.1 pjanouse.brq.redhat.com localhost ::1 localhost6.localdomain6 localhost6 localhost ::1 pjanouse.brq.redhat.com localhost 127.0.0.2 both ::2 both 2001:0000:1234:0000:0000:c1c0:abcd:0876 ip6 {code} I've got this result:{code} Tests in error: org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out {code} It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation. > Yet another place where hardcoded IPv4 address scheme is used > ------------------------------------------------------------- > > Key: AS7-3973 > URL: https://issues.jboss.org/browse/AS7-3973 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Blocker > > After the last Stuart commit and merge to upstream (on -Thursday- Wednesday morning CET time zone), there are still some places where hardcoded IPv4 address scheme is used. > Wrong TestCases are: > - org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase > - org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase > Both of them use 127.0.0.1 directly even -Dnode0=::1 - it seems to be some other magic inside them because [there|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-t...] TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like: > {code} > #127.0.0.1 localhost.localdomain > #127.0.0.1 pjanouse.brq.redhat.com localhost > ::1 localhost6.localdomain6 localhost6 localhost > ::1 pjanouse.brq.redhat.com localhost > 127.0.0.2 both > ::2 both > 2001:0000:1234:0000:0000:c1c0:abcd:0876 ip6 > {code} > I've got this result:{code} > Tests in error: > org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out > org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out > org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out > org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out > {code} > It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation. -- 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

13 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012