July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBNAME-51) Delay in connecting when first of multiple providers is down can cause performance issue

by Dennis Reed (JIRA)

Delay in connecting when first of multiple providers is down can cause performance issue ---------------------------------------------------------------------------------------- Key: JBNAME-51 URL: https://issues.jboss.org/browse/JBNAME-51 Project: JBoss Naming Issue Type: Bug Components: jnpserver Affects Versions: 5.0.3.GA Reporter: Dennis Reed org.jnp.interfaces.NamingContext.checkRef always loops through the provider list in order, trying to connect to the first before checking for a cached connection to a later provider. This affects performance because it can cause a delay on every context created, waiting for a timeout on a node that is down. For instance, the following takes a very long time when node1 is down. ... env.put ( Context.PROVIDER_URL, "node1:1100,node2:1100" ); for ( int i = 0; i < 1000; ++ i ) { InitialContext ctx = new InitialContext ( env ); ... } If checkRef looked for a cached connection to any of the listed providers before trying to connect to an uncached one, there would only be a timeout delay on the very first connection attempt. Note: This would change the behavior of the client when node1 comes back up in the middle, so would not be eligible for an EAP patch release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
7
0 / 0

[JBoss JIRA] (JBNAME-59) HA-JNDI java.rmi.UnmarshallException doesn't failover

by Dennis Reed (JIRA)

Dennis Reed created JBNAME-59: --------------------------------- Summary: HA-JNDI java.rmi.UnmarshallException doesn't failover Key: JBNAME-59 URL: https://issues.jboss.org/browse/JBNAME-59 Project: JBoss Naming Issue Type: Bug Components: jnpserver Affects Versions: 5.0.3.GA Reporter: Dennis Reed Assignee: Dennis Reed During intensive HA-JNDI failover testing (constantly running "new InitialContext().lookup(...)" while starting and stopping JBoss instances, sometimes an HA-JNDI lookup just before the server goes down is throwing an exception without trying to fail over to the other HA-JNDI instance: ... Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:863) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:710) at javax.naming.InitialContext.lookup(InitialContext.java:351) at xxx.CustomCode (CustomCode.java:XXX) ... 25 more Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.jboss.ha.framework.server.HARMIServerImpl_Stub.invoke(Unknown Source) at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:225) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:327) at $Proxy4.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:750) ... 28 more Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:235) at java.io.DataInputStream.readByte(DataInputStream.java:241) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:189) ... 34 more Also a similar exception: Caused by: java.net.SocketException: socket write error: Connection reset by peer. at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method) at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:73) at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:137) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1632) at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:667) at sun.rmi.transport.StreamRemoteCall.releaseOutputStream(StreamRemoteCall.java:92) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:188) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.jboss.ha.framework.server.HARMIServerImpl_Stub.invoke(Unknown Source) at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:225) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:327) at $Proxy4.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:750) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:710) at javax.naming.InitialContext.lookup(InitialContext.java:351) ... Also javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.io.EOFException] ... Root cause is that java.rmi.UnmarshallException is not caught as an exception eligible for failover. -- 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

11 years, 11 months

1
6
0 / 0

[JBoss JIRA] (JBNAME-60) Retry HAJNDI call on ServiceUnavailableException

by Dennis Reed (JIRA)

Dennis Reed created JBNAME-60: --------------------------------- Summary: Retry HAJNDI call on ServiceUnavailableException Key: JBNAME-60 URL: https://issues.jboss.org/browse/JBNAME-60 Project: JBoss Naming Issue Type: Bug Components: jnp-client Affects Versions: 5.0.3.GA Reporter: Dennis Reed Assignee: Dennis Reed Retry a context.lookup call when a ServiceUnavailableException is received. This is a new exception added in HAJNDI for JBPAPP-8152/JBPAPP-8305 when the server is not ready to handle requests (starting up/shutting down). -- 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

11 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9177) Launch script does not work on Windows

by Max Rydahl Andersen (JIRA)

Launch script does not work on Windows --------------------------------------- Key: JBAS-9177 URL: https://issues.jboss.org/browse/JBAS-9177 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen Priority: Critical Launching AS 7 does not work on windows. Several issues: Quoting java_home causes error: set JAVA_HOME="C:\Program Files\Java\jdk1.6.0_24" Y:\products\jboss 7.0.0.Beta1\bin>standalone.bat Config file not found Y:\products\jboss 7.0.0.Beta1\bin\standalone.conf.bat Files\Java\jdk1.6.0_24"" was unexpected at this time. Non quoting and you get this: Y:\products\jboss 7.0.0.Beta1\bin>set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_2 4 Y:\products\jboss 7.0.0.Beta1\bin>standalone.bat Config file not found Y:\products\jboss 7.0.0.Beta1\bin\standalone.conf.bat =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: Y:\products\jboss 7.0.0.Beta1 JAVA: C:\Program Files\Java\jdk1.6.0_24\bin\java JAVA_OPTS: -Dprogram.name=standalone.bat -server =============================================================================== Exception in thread "main" java.lang.NoClassDefFoundError: 7/0/0/Beta1\standalon e\log\boot/log Caused by: java.lang.ClassNotFoundException: 7.0.0.Beta1\standalone\log\boot.log at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: 7.0.0.Beta1\standalone\log\boot.log. Program wil l exit. Press any key to continue . . . And it seem to be looking for standalone.conf.bat which does not exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

6
13
0 / 0

[JBoss JIRA] (AS7-5136) Source Build Failure using Maven3 and Java version 1.6

by Peer Mohamed (JIRA)

Peer Mohamed created AS7-5136: --------------------------------- Summary: Source Build Failure using Maven3 and Java version 1.6 Key: AS7-5136 URL: https://issues.jboss.org/browse/AS7-5136 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Peer Mohamed Assignee: Paul Gier build failed. (maven3, java 1.6, gitbash) 15:14:13,654 ERROR (main) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:430> JBAS014612: Opera tion ("evil") failed - address: ([]): java.lang.RuntimeException: this handler is evil.. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-con troller: There are test failures -- 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

11 years, 11 months

3
6
0 / 0

[JBoss JIRA] (AS7-5009) Cannot invoke remote EJB3 from OSGi Bundle

by Thomas Diesler (JIRA)

11 years, 11 months

1
7
0 / 0

[JBoss JIRA] (JBJCA-846) Add -o option

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-846: ------------------------------------- Summary: Add -o option Key: JBJCA-846 URL: https://issues.jboss.org/browse/JBJCA-846 Project: IronJacamar Issue Type: Task Components: AS Reporter: Jesper Pedersen Assignee: Lin Gao Fix For: 1.1.0.Beta2 Add an -o option to the resource adapter information tool such that a specific file name can be specified, e.g. {noformat} ./rar-info.sh -o myreport.txt eis.rar {noformat} -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (JBJCA-845) Add --stdout option

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-845: ------------------------------------- Summary: Add --stdout option Key: JBJCA-845 URL: https://issues.jboss.org/browse/JBJCA-845 Project: IronJacamar Issue Type: Task Components: AS Reporter: Jesper Pedersen Assignee: Lin Gao Fix For: 1.1.0.Beta2 Add a --stdout option to the resource adapter information that will output the report to stdout instead of to a file -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-5109) When starting JBoss AS -b should work no matter how I start JBoss AS to bind it to the local interface

by Jim Tyrrell (JIRA)

Jim Tyrrell created AS7-5109: -------------------------------- Summary: When starting JBoss AS -b should work no matter how I start JBoss AS to bind it to the local interface Key: AS7-5109 URL: https://issues.jboss.org/browse/AS7-5109 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry When starting JBoss as with the following command: ./domain.sh -b 192.168.193.139 -Djboss.domain.base.dir=/home/jimtyrrell/Servers/machine1/ --host-config=host-master.xml It does not bind to the passed in IP Address. Instead it binds to localhost 127.0.0.1. It should have bound to 192.168.192.139 in this instance. Instead I had to pass in the parameter like this: ./domain.sh -Djboss.domain.base-dir=/home/jimtyrrell/Servers/machine1/ --host-config=host-master.xml -Djboss.bind.address.management=192.168.193.139 Please expand this ticket to any and all shipped configuration starting files so that the host binding works per the help info via a -b binding. -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-5130) Upgrade JGroups to 3.0.11.Final

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5130: --------------------------------- Summary: Upgrade JGroups to 3.0.11.Final Key: AS7-5130 URL: https://issues.jboss.org/browse/AS7-5130 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) -- 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

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2012