January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-657) Implement versions of Client.removeListener() and Client.disconnect() which do not write to a broken server.

by Ron Sigal (JIRA)

Implement versions of Client.removeListener() and Client.disconnect() which do not write to a broken server. ------------------------------------------------------------------------------------------------------------ Key: JBREM-657 URL: http://jira.jboss.com/jira/browse/JBREM-657 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) >From Clebert Suconic: When a server is killed and failover is processed, we don't have at this point a way to disconnect a client from a dead server. I tried to call disconnect on those clients after failover and remoting does a socket communication. It looks we would need a new feature/new method such as client.removeLeases or client.disconnect(false); false means = send data or any other similar way. -- 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, 4 months

6
20
0 / 0

[JBoss JIRA] Created: (JBREM-654) a NullPointerException occures and is not handled in SocketServerInvoker and MultiplexServerInvoker

by Claudia Richter (JIRA)

a NullPointerException occures and is not handled in SocketServerInvoker and MultiplexServerInvoker --------------------------------------------------------------------------------------------------- Key: JBREM-654 URL: http://jira.jboss.com/jira/browse/JBREM-654 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport, transport-multiplex, transporter Affects Versions: 2.2.0.Alpha4, 2.2.0.Alpha3 (Bluto), 2.0.0.GA (Boon), 2.0.0.CR1 (Boon) Reporter: Claudia Richter Assigned To: Tom Elrod when trying to dynamically load keystores several times, it happens that the SocketServer is set to null and a NullPointerException is thrown. MultiplexServerInvoker and SocketServerInvoker are both not able to handle this Exception. Actually no NullPointerException should be thrown, but it happens. This Exception causes the Server to fail. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-650) Create bidirectional transport

by Ron Sigal (JIRA)

Create bidirectional transport ------------------------------ Key: JBREM-650 URL: http://jira.jboss.com/jira/browse/JBREM-650 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) JBossMessaging has a need for a transport which can do callbacks through a firewall, which implies the absence of a server socket on the client side. The multiplex transport satisfies this requirement, but its performance is not comparable with the performance of the socket transport. An alternative to multiplex with better performance is needed. As described by Ovidiu Feoderov: "A transport that basically opens a socket from client to server and uses the same socket to send stuff from client to server and from server to client (no ServerSocket on the client side) with minimal overhead. It should be something very simple. And fast." -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-392) disconnect() hangs forever on second client of group

by ?yvind Eikeland (JIRA)

disconnect() hangs forever on second client of group ---------------------------------------------------- Key: JGRP-392 URL: http://jira.jboss.com/jira/browse/JGRP-392 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Environment: Windows XP. java version "1.6.0" Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing) "UDP(mcast_addr=239.10.10.10;mcast_port=17000" + ";ip_ttl=8;" + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000):" + "PING(timeout=2000;num_initial_members=3):" + "MERGE2(min_interval=5000;max_interval=10000):" + "FD_SOCK:" + "VERIFY_SUSPECT(timeout=1500):" + "pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):" + "UNICAST(timeout=5000):" + "pbcast.STABLE(desired_avg_gossip=20000):" + "FRAG(frag_size=4096;down_thread=false;up_thread=false):" + "pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;" + "shun=false;print_local_addr=true):" + "pbcast.STATE_TRANSFER"; Reporter: ?yvind Eikeland Assigned To: Bela Ban Quite often, but not every time, when member 2 (not the coordinator) is disconnecting from the group, it will wait forever. This may be some configuration or network issue, but it would be very useful if a timeout could be specified in the JChannel.disconnect() method to get around this problem. Members are running in separate JVMs. when a member/client is leaving a channel, we're calling these methods: - channel.disconnect(); - channel.close(); This method is called from disconnect() today: disconnect_promise.getResult(); // wait for DISCONNECT_OK Instead, disconnect_promise.getResult(timeout); should be called. It does not seem to be possible to configure this timeout in the protocol 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

19 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (GPD-41) Finish action element configuration forms

by Koen Aers (JIRA)

Finish action element configuration forms ----------------------------------------- Key: GPD-41 URL: http://jira.jboss.com/jira/browse/GPD-41 Project: JBoss jBPM GPD Issue Type: Task Reporter: Koen Aers Assigned To: Koen Aers Configuration forms need to be added for: script, create-timer, cancel-timer and mail -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1135) Update WSRP dtd and doc to accommodate for addition of registration info

by Chris Laprun (JIRA)

Update WSRP dtd and doc to accommodate for addition of registration info ------------------------------------------------------------------------ Key: JBPORTAL-1135 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1135 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation, Portal WSRP Affects Versions: 2.6.Alpha1 Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.Alpha1 -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (SWAP-23) MyPortlet

by Jordi Andres (JIRA)

MyPortlet --------- Key: SWAP-23 URL: http://jira.jboss.com/jira/browse/SWAP-23 Project: PortletSwap Issue Type: Release Security Level: Public (Everyone can see) Components: Portlet_Contrib Reporter: Jordi Andres Assigned To: Roy Russo Estic provant això que no se ben be per a que serveix -- 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, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1220) WSRP session maintenance issue

by Julien Viet (JIRA)

WSRP session maintenance issue ------------------------------ Key: JBPORTAL-1220 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1220 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha1, 2.4.1 SP1 Environment: BEA Weblogic 8 as a consumer JBoss Portal as a producer Reporter: Julien Viet Assigned To: Chris Laprun Fix For: 2.6.CR1, 2.4.2 Final Attachments: Session.patch When the portal creates a session (done by the portlet container) the cookie is sent to the consumer but it does not send the cookie back. The solution I found that works (tested by a user from our community) is to leverare initCookie() to create an HTTP Session. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAOP-344) Add JBoss EULA to aop 2.0

by Kabir Khan (JIRA)

Add JBoss EULA to aop 2.0 ------------------------- Key: JBAOP-344 URL: http://jira.jboss.com/jira/browse/JBAOP-344 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-320) Arg annotation with number specifying the adice argument number

by Flavia Rainone (JIRA)

Arg annotation with number specifying the adice argument number --------------------------------------------------------------- Key: JBAOP-320 URL: http://jira.jboss.com/jira/browse/JBAOP-320 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Add a parameter to the annotation @Arg So that it receives the advice method argument number. This is for use in cases like: public void interceptedMethod(String original, String copy) { } And you want to receive the value of copy, not of original, on your advice: public void myAdvice(@Arg String copy) { } -- 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, 4 months

4
8
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 2007