September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBAS-2398) Check for unparameterized interface configuration

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2398?page=all ] Dimitris Andreadis resolved JBAS-2398. -------------------------------------- Resolution: Done Assignee: Dimitris Andreadis >From my tests (detailed in the forum post), using -b correctly binds the various ports. Only the jgroups stack may present a different behavior but the clustering team seems satisfied, or else somebody else can take it from here. > Check for unparameterized interface configuration > ------------------------------------------------- > > Key: JBAS-2398 > URL: http://jira.jboss.com/jira/browse/JBAS-2398 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 Final > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.GA > > > Make sure all interface configuration distributed with JBossAS uses the > ${jboss.bind.address:0.0.0.0} pattern to pickup the standard system property. > But be careful that 0.0.0.0 does not end up as a connection address for a client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1728) Statement.getConnection not working for remote client

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1728?page=all ] Dimitris Andreadis updated JBAS-1728: ------------------------------------- Component/s: JCA service (was: Remoting) > Statement.getConnection not working for remote client > ----------------------------------------------------- > > Key: JBAS-1728 > URL: http://jira.jboss.com/jira/browse/JBAS-1728 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Weston Price > Fix For: JBossAS-4.0.6.CR1 > > > the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService is not handling Statement.getConnection. It returns the real thing instead of a proxy --> Serialization exception!!. > This is related to JBAS-1678. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1728) Statement.getConnection not working for remote client

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1728?page=all ] Dimitris Andreadis updated JBAS-1728: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) Assignee: Weston Price > Statement.getConnection not working for remote client > ----------------------------------------------------- > > Key: JBAS-1728 > URL: http://jira.jboss.com/jira/browse/JBAS-1728 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Weston Price > Fix For: JBossAS-4.0.6.CR1 > > > the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService is not handling Statement.getConnection. It returns the real thing instead of a proxy --> Serialization exception!!. > This is related to JBAS-1678. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1984) HttpNamingContextFactory unable to reconnect

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1984?page=all ] Dimitris Andreadis updated JBAS-1984: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) Assignee: Tom Elrod Maybe Tom, can take a look at this case, for the next release. > HttpNamingContextFactory unable to reconnect > -------------------------------------------- > > Key: JBAS-1984 > URL: http://jira.jboss.com/jira/browse/JBAS-1984 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming, Remoting > Affects Versions: JBossAS-3.2.7 Final > Environment: XP > Reporter: Bernd Eckenfels > Assigned To: Tom Elrod > Fix For: JBossAS-4.0.6.CR1 > > > Unlike the normal JNP/RMI Connection the HttpNamingContextFactory created Context does not recover from a application server shutdown. If I repeat lookups, the exception after the application server is available again looks like this: > ex: javax.naming.CommunicationException: Could not obtain connection to any of these urls: http://127.0.0.1:8080/invoker/JNDIFactory [Root exception is javax.naming.CommunicationException: Failed to connect to server http:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server http:1099 [Root exception is java.net.UnknownHostException: http: http]]] > javax.naming.CommunicationException: Could not obtain connection to any of these urls: http://127.0.0.1:8080/invoker/JNDIFactory [Root exception is javax.naming.CommunicationException: Failed to connect to server http:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server http:1099 [Root exception is java.net.UnknownHostException: http: http]]] > at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1363) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:575) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:568) > at net.eckenfels.JNDITest.main(JNDITest.java:72) > Caused by: javax.naming.CommunicationException: Failed to connect to server http:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server http:1099 [Root exception is java.net.UnknownHostException: http: http]] > at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:250) > at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1348) > ... 3 more > Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server http:1099 [Root exception is java.net.UnknownHostException: http: http] > at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224) > ... 4 more > Caused by: java.net.UnknownHostException: http: http > at java.net.InetAddress.getAllByName0(InetAddress.java:1128) > at java.net.InetAddress.getAllByName0(InetAddress.java:1098) > at java.net.InetAddress.getAllByName(InetAddress.java:1061) > at java.net.InetAddress.getByName(InetAddress.java:958) > at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:61) > at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:220) > ... 4 more > Note the Unknown Host Exception, which looks pretty much like a destroyed or miss-parsed URL. Since the connection work with the same InitialContext instance before, the setup is correct: > p.put("java.naming.factory.initial", "org.jboss.naming.HttpNamingContextFactory"); > p.put("java.naming.provider.url", "http://127.0.0.1:8080/invoker/JNDIFactory"); > p.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); > p.put("jnp.disableDiscovery", "true"); > Context rootCtx = (Context)new InitialContext(p); > while(true) > { > try > { > // rootCtx = new InitialContext(p); > Context jmxCtx = (Context)rootCtx.lookup("/jmx/rmi"); > l = jmxCtx.list(""); > while(l.hasMore()) > { > System.out.println(" - " + l.next()); > } > } catch (Throwable t) { > System.out.println("ex: " + t); t.printStackTrace(System.out); > } > try{Thread.sleep(10000);}catch(Throwable t) { } > } > This sample code works if i uncomment the re-creation of the InitialContext, however this is neighter needed by the JNP/RMI Version nor does the exception look like sane handling. > The client is using jbossall-client.jar and jdk 1.5_04. Jboss 3.2.7 is running (unmodified default profile) on 1.5, too. Problem exists with 3.2.6, too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2037) Bug in the JBoss HTML adaptor.

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2037?page=all ] Dimitris Andreadis reassigned JBAS-2037: ---------------------------------------- Assignee: Amit Bhayani Amit, more jmx-console stuff, if you want to have a look. > Bug in the JBoss HTML adaptor. > ------------------------------ > > Key: JBAS-2037 > URL: http://jira.jboss.com/jira/browse/JBAS-2037 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2 Final, JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1 > Reporter: jean deruelle > Assigned To: Amit Bhayani > Fix For: JBossAS-4.0.6.CR1 > > > "The set of characters in a value is also limited. If > special characters may occur, it is recommended that the > value be quoted, using ObjectName.quote. If the value for a > given key is sometimes quoted, then it should always be > quoted. By default, if a value is a string (rather than a > number, say), then it should be quoted unless you are sure > that it will never contain special characters." quoted from > java management best practices (see > http://java.sun.com/products/JavaManagement/best-practices.html#mozTocId6... > in section ObjectNameSyntax) > When a JMX value is quoted, it causes problems to invoke methods through thr Jboss jmx web console : > So my feeling is that the problem comes from the jboss jmx > console jsp pages. > The thing is that the quotes in the jmx object name are not > encoded to the html format in the jsp pages and so the first > opening quote is interpreted as the final quote of the html > field. > Here is a quick fix for Jboss-3.2.6 : > Add the following lines to > %JBOSS_HOME%\server\all\deploy\jmx-console.war\inspectMBean.jsp > after line 141 > <%objectNameString=objectNameString.replaceAll("\"","""); > //objectNameString=URLEncoder.encode(objectNameString);%> > It was a quick fix to fit my needs but the > line should really be the one commented but in that case the > HtmlAdaptorServlet from Jboss cannot handle it correctly > because it doesn't do a URLDecoder.decode of the > objectNameString stored in the request parameter called "name". > But I might be wrong here in saying that it comes from > jboss, maybe I missed something along the way. > Can someone confirm this bug or help me out there ? > Thx > Best regards > Jean -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2131) Better support for BMT SFSB "mistakes"

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2131?page=all ] Dimitris Andreadis updated JBAS-2131: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) Assignee: Weston Price Weston, do you want to have a go with this, for the next release? > Better support for BMT SFSB "mistakes" > -------------------------------------- > > Key: JBAS-2131 > URL: http://jira.jboss.com/jira/browse/JBAS-2131 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-4.0.6.CR1 > > > Further to JBAS-2128 we should also implement some sort of listener on the transaction timeout. > Given the stupid BMT SFSB semantics (this part of the spec is one my favourite anti-patterns :-) > where a client can hog server resources. > sfsb.doBegin(); > doLongRunningProcess(); > sfsb.doCommit(); > And even crash during the doLongRunningProcess(). > We should allow the server to reclaim the resources from a transaction timeout more quickly. > Another option would be to allow a configuration that does a rollback() at transaction timeout. > But this would require some serious testing to make sure all JBoss code is checking transaction status correctly. > It would also confuse any non-j2ee compliant framework that registers transaction synchronizations > and then assumes their "thread local" is still valid from the timeout thread or they aren't threadsafe. > No names mentioned to protect the guilty :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-499) Rule not rendering activation group correctly

by Michael Neale (JIRA)

Rule not rendering activation group correctly --------------------------------------------- Key: JBRULES-499 URL: http://jira.jboss.com/jira/browse/JBRULES-499 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1901) web-console shows dead archives after redeploy

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1901?page=all ] Dimitris Andreadis updated JBAS-1901: ------------------------------------- Comment: was deleted > web-console shows dead archives after redeploy > ---------------------------------------------- > > Key: JBAS-1901 > URL: http://jira.jboss.com/jira/browse/JBAS-1901 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.2 Final > Reporter: Bill Burke > Assigned To: Darran Lofthouse > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > if you redeploy an ear multiple times you will see it show up multiple times > under the web-console/j2ee applications tree in the applet. If you try to browse one of those dead archives, it will blow up the j2ee applications tree structure -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2008) web console statistics view does not show properly in Firefox

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2008?page=all ] Dimitris Andreadis updated JBAS-2008: ------------------------------------- Comment: was deleted > web console statistics view does not show properly in Firefox > ------------------------------------------------------------- > > Key: JBAS-2008 > URL: http://jira.jboss.com/jira/browse/JBAS-2008 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.2 Final > Environment: Firefox > Reporter: Kevin Barfield > Assigned To: Darran Lofthouse > Priority: Minor > > The statistics view in the web console has a box though it when viewed through the Firefox browser. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3188) Reduce the dependencies specified by web-console so it can be installed in more profiles.

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3188?page=all ] Dimitris Andreadis updated JBAS-3188: ------------------------------------- Component/s: Web Console (was: Installer) > Reduce the dependencies specified by web-console so it can be installed in more profiles. > ----------------------------------------------------------------------------------------- > > Key: JBAS-3188 > URL: http://jira.jboss.com/jira/browse/JBAS-3188 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: JBossAS-4.0.6.CR1 > > > The web-console has been implemented to it is not strictly dependent on the components it makes available through it's interface, if any component it makes available through the interface is not installed then initialisation will fail just for that component and it will not be added to the tree. The remaining components will still be added to the tree and the web-console will continue to work correctly. > The installer should be updated so the web-console is dependent on less components so it can be installed in more profiles. > This will also get rid of another problem where the web console is dependent on specifc versions of components e.g. At the moment it is dependent on the JDK 1.4 version of AOP so can not be installed in any profile that uses the JDK 5.0 version of AOP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

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 September 2006