January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4749) HTML object tag should be used instead of applet

by Sylvain Avril (JIRA)

HTML object tag should be used instead of applet ------------------------------------------------ Key: JBAS-4749 URL: http://jira.jboss.com/jira/browse/JBAS-4749 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.2.2.GA Reporter: Sylvain Avril Assigned To: Darran Lofthouse Priority: Minor The HTML applet tag is deprecated. It can lead to strange behavior. For exemple for my Windows PC, it try to use the 1.3.1 JVM instead of the 1.5.0 which is the default for applets. Some doc could be found here : http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_ta... -- 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

18 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-681) Consolidate JMS related aspects into one JMS aspect

by Tim Fox (JIRA)

Consolidate JMS related aspects into one JMS aspect --------------------------------------------------- Key: JBMESSAGING-681 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it. Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow. We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack. -- 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

18 years, 4 months

4
28
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1198) Support SSL

by Jeff Mesnil (JIRA)

Support SSL ----------- Key: JBMESSAGING-1198 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1198 Project: JBoss Messaging Issue Type: Sub-task Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha the new remoting code which is based on MINA does not support SSL. All communications between JMS clients and servers must support SSL regardless of the transport which is used (TCP, HTTP) -- 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4765) jboss_5_0.xsd from ejb3 is not included with the other dtds/schemas in the docs directory of the AS output build

by Dimitris Andreadis (JIRA)

jboss_5_0.xsd from ejb3 is not included with the other dtds/schemas in the docs directory of the AS output build ---------------------------------------------------------------------------------------------------------------- Key: JBAS-4765 URL: http://jira.jboss.com/jira/browse/JBAS-4765 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XML services Reporter: Dimitris Andreadis Assigned To: Carlo de Wolf Fix For: JBossAS-5.0.0.Beta3 The output docs directory of the jboss AS build, should contain all exported dtds/schemas. We use those to update the www.jboss.org site. -- 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

18 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1101) Create pluggable JNDI Binding Strategy

by Andrew Lee Rubinger (JIRA)

Create pluggable JNDI Binding Strategy -------------------------------------- Key: EJBTHREE-1101 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1101 Project: EJB 3.0 Issue Type: Feature Request Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3, Branch_4_2 Current JNDI Binding Strategy is based on packaging and ejb-name. Create a pluggable mechanism in which any implementation may adhere to a contract to define JNDI names. -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-111) Remove commented out code

by Anil Saldhana (JIRA)

Remove commented out code ------------------------- Key: SECURITY-111 URL: http://jira.jboss.com/jira/browse/SECURITY-111 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.2-BETA3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA As part of the Beta3 upgrade, implementation code was commented out. They need to be replaced after sometime. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-477) javassist.NotFoundException on Singleton Undeployment

by Flavia Rainone (JIRA)

javassist.NotFoundException on Singleton Undeployment ----------------------------------------------------- Key: JBAOP-477 URL: http://jira.jboss.com/jira/browse/JBAOP-477 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.5.GA Reporter: Flavia Rainone JBoss AOP is getting a javassist.NotFoundException on undeployment of ha-singleton components. -- 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1108) Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster

by Ovidiu Feodorov (JIRA)

Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster ---------------------------------------------------------------------------------- Key: JBMESSAGING-1108 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1108 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor This is just an initial finding. I don't have more details at this point. I will investigate if necessary. -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-884) HTTP transport barfs in stress tests with read timed out

by Tim Fox (JIRA)

HTTP transport barfs in stress tests with read timed out -------------------------------------------------------- Key: JBMESSAGING-884 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-884 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.GA When running the stress tests. The HTTP transport intermittently barfs with: Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:327) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:133) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1538) at org.jboss.remoting.Client.invoke(Client.java:527) at org.jboss.remoting.Client.invoke(Client.java:515) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:182) ... 19 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:313) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:606) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:554) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:939) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:274) ... 25 more This only occurs under high load. I suspect the server side tomcat server is having problems dealing with so many concurrent poll requests and times them out. -- 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

18 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-857) HTTP stress tests fail

by Ovidiu Feodorov (JIRA)

HTTP stress tests fail ---------------------- Key: JBMESSAGING-857 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-857 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA The HTTP stress tests have been temporarily commented out. To be enabled and fixed for 1.2.0.GA. -- 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

18 years, 4 months

3
11
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 January 2008