May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4762) Remote naming fails to work with IPv6 provider URL

by jaikiran pai (JIRA)

jaikiran pai created AS7-4762: --------------------------------- Summary: Remote naming fails to work with IPv6 provider URL Key: AS7-4762 URL: https://issues.jboss.org/browse/AS7-4762 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.2.Final (EAP) Reporter: jaikiran pai Assignee: John Bailey Priority: Critical Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to connection creation failures for code like: {code} final Properties env = new Properties(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); env.put(Context.PROVIDER_URL, "remote://::1:4447); context = new InitialContext(env); // Perform the JNDI lookups context.lookup("java:jboss/exported/jms/queue/test); {code} This fails with: {code} Caused by: java.lang.IllegalArgumentException: destination address may not be null at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105) at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104) ... 10 more {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, 12 months

3
12
0 / 0

[JBoss JIRA] (AS7-4671) Add an anonymous authenticator to the http interface

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4671: ------------------------------------- Summary: Add an anonymous authenticator to the http interface Key: AS7-4671 URL: https://issues.jboss.org/browse/AS7-4671 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 Where no authentication is to occur on the http management interface we should still establish a security context for the purpose of operations such as whoami, auditing and even ACLs based on anonymous access. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] (JBEE-113) Add relocations for out of date org.jboss.spec artifact ids

by Pete Muir (JIRA)

Pete Muir created JBEE-113: ------------------------------ Summary: Add relocations for out of date org.jboss.spec artifact ids Key: JBEE-113 URL: https://issues.jboss.org/browse/JBEE-113 Project: JBoss JavaEE Spec APIs Issue Type: Task Reporter: Pete Muir Assignee: Paul Gier This will help indicate to users that they are out of date. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-4509) CLONE - Server start without any problem or message even specification of IP address(-s) is ambiguous

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-4509?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-4509. ------------------------------- This is exactly what I was looking for. Works fine. > CLONE - Server start without any problem or message even specification of IP address(-s) is ambiguous > ----------------------------------------------------------------------------------------------------- > > Key: AS7-4509 > URL: https://issues.jboss.org/browse/AS7-4509 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Brian Stansberry > Labels: eap6_ipv6 > Fix For: 7.1.2.Final (EAP) > > > In IPv6 world it is possible if two or more network interfaces has the same IPv6 address. It is legally and true especially in Link-local address scope. > So if we configure 2 or more network interfaces with a manually defined IPv6 address (link-local prefix fe80::/10 is the best) and try to start-up EAP and do this like:{code}./standalone.sh -Djava.net.preferIPv4Stack=false -b=fe80::200:ff:fe00:5 -bmanagement=fe80::200:ff:fe00:5 -c standalone-full.xml{code}there isn't *any* warning message reported, nor any notice that this specification is ambiguous. > I prefer in a such case to reject this specification as ambiguous (especially for the case - there is a risk of accidentally open EAP instance to the world), refuse start with error message and immediately exit. Although this situation has its roots in administrator mistake, it can became very hard risk of customer's data when it will be overseen for awhile. (*) > (*) some case-studies report blind clear MS Windows station is attacked up to 10 minutes from it boot when is directly connected to unsecure Internet network without any firewall etc... my own personal experience is at least the same... - yes, it is dangerous to work in a such environment and situation on a Internet directly connected server host, but an admins really works like that... > Anyway - the missed part of specification needed for correct set-up in this case is *zone id* identifier. When it is supplied, star-up is correct. > Although this is really +edge case+ of using EAP and its configuration, it can accidentally expose customer's sensitive data so we should take it very carefully. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3501) Link the image of a bpmn process directly to this process

by Philipp Ossler (JIRA)

Philipp Ossler created JBRULES-3501: --------------------------------------- Summary: Link the image of a bpmn process directly to this process Key: JBRULES-3501 URL: https://issues.jboss.org/browse/JBRULES-3501 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.3.0.Final Reporter: Philipp Ossler Assignee: Mark Proctor The image of a bpmn process is saved as other (png) asset in guvnor. So the image is not linked to the process or a specific version of the process. It would be better if the image is linked with the process and has the same version. The rest service could be extended like this: [http://{your-address}/drools-guvnor/rest/packages/{your-package}/assets/{your-process-id}/image] -- 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, 12 months

2
1
0 / 0

[JBoss JIRA] (JGRP-1458) SEQUENCER delivers the same message more than once

by David Hotham (JIRA)

David Hotham created JGRP-1458: ---------------------------------- Summary: SEQUENCER delivers the same message more than once Key: JGRP-1458 URL: https://issues.jboss.org/browse/JGRP-1458 Project: JGroups Issue Type: Bug Affects Versions: 3.0.9 Reporter: David Hotham Assignee: Bela Ban This issue is certainly exposed by my running with a retransmit task in SEQUENCER (per JGRP-1449). However, I think that it could be hit anyway at a change of view; and I'm sure it's a bug! In SeqnoTable$Entry.add(seqno), the final branch "seqno > next_to_receive" always returns true. But it should return the return code from seqnos.add(seqno) (ie, false if the seqno has already been added). The consequence is that Sequencer's received_table.add() returns true even for a message that has already been delivered, so the message is delivered a second time. Looking at this code raised another question, for which I should maybe raise a separate ticket. Let me know if you'd prefer me to do so. I think that when SeqnoTable.add() creates a new Entry, it always creates Entry(0) (because SeqnoTable.next_to_receive is always 0). Is that true? and if so, is it correct? A might join a group long after some other member B has already broadcast the messages with sequence numbers 0,1,2, say. Then since A will never receive those messages, isn't it going to end up with an Entry for B in which the Set of seqnos just grows indefinitely? It looks to me as though maybe when it creates a new entry it should do so with Entry(seqno) rather than Entry(next_to_receive). Or have I misunderstood something? -- 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, 12 months

2
3
0 / 0

[JBoss JIRA] (AS7-4658) Versify that the deploy operation is guranteed to wait for the Bundle to get installed

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4658: ----------------------------------- Summary: Versify that the deploy operation is guranteed to wait for the Bundle to get installed Key: AS7-4658 URL: https://issues.jboss.org/browse/AS7-4658 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.2.Final-redhat1 The bundle must be istalled into the framework before the INSTALL phase complets. -- 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, 12 months

2
6
0 / 0

[JBoss JIRA] (AS7-4148) Clustering performance in events of failure/membership change is poor and timeouts

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4148: ----------------------------------- Summary: Clustering performance in events of failure/membership change is poor and timeouts Key: AS7-4148 URL: https://issues.jboss.org/browse/AS7-4148 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.2.Final Clustering performance in events of failure/membership change is poor probably mainly due to errors causing timeouts AS7-4143 and AS7-4144. -- 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, 12 months

2
3
0 / 0

[JBoss JIRA] (AS7-3896) TS: Some tests missing from <includes> and are not run.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3896: --------------------------------- Summary: TS: Some tests missing from <includes> and are not run. Key: AS7-3896 URL: https://issues.jboss.org/browse/AS7-3896 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.1.Final Attachments: MissedTests.txt -- 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, 12 months

5
15
0 / 0

[JBoss JIRA] (AS7-2325) Get rid of reflection configuring the ProtocolHandler in WebConnectorService

by Kabir Khan (Created) (JIRA)

Get rid of reflection configuring the ProtocolHandler in WebConnectorService ---------------------------------------------------------------------------- Key: AS7-2325 URL: https://issues.jboss.org/browse/AS7-2325 Project: Application Server 7 Issue Type: Feature Request Components: Web Reporter: Kabir Khan Assignee: Remy Maucherat Fix For: 7.1.0.CR1 A lot of the set methods do {code} if (ssl.hasDefined(Constants.PASSWORD)) { Method m = connector.getProtocolHandler().getClass().getMethod("setSSLPassword", String.class); m.invoke(connector.getProtocolHandler(), ssl.get(Constants.PASSWORD).asString()); } if (ssl.hasDefined(Constants.CERTIFICATE_KEY_FILE)) { Method m = connector.getProtocolHandler().getClass().getMethod("setSSLCertificateKeyFile", String.class); m.invoke(connector.getProtocolHandler(), ssl.get(Constants.CERTIFICATE_KEY_FILE).asString()); } //etc. {code} The ProtocolHandler inteface does not expose them, so maybe they should go there or another common interface for configuring PH's -- 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, 12 months

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