May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-738) ServerThread/invoker still executing invocation after its related TransportServer was stopped

by craig bordelon (JIRA)

ServerThread/invoker still executing invocation after its related TransportServer was stopped --------------------------------------------------------------------------------------------- Key: JBREM-738 URL: http://jira.jboss.com/jira/browse/JBREM-738 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transporter Affects Versions: 2.2.0.Beta1 (Bluto) Environment: java 1.5 on solaris but doubt its specific to this one. Reporter: craig bordelon Assigned To: Tom Elrod get an exception on the third iteration of a transporter client to a transporter server where the client code is doing the same invoke each time. This should not happen as the first two iterations give correct result. The exception is thrown from the server side as apparently the jboss remoting internals are confused -- stating that a ServerInvoker is not in "started state". Exception is java.lang.reflect.UndeclaredThrowableException at $Proxy4.toString(Unknown Source) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuilder.append(StringBuilder.java:116) at proxy.Client.testClientCall(Client.java:38) at proxy.Client.main(Client.java:115) Caused by: org.jboss.remoting.ServerInvoker$InvalidStateException: Can not proc ess invocation request since is not in started state. at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:751) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(S erverThread.java:568) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread. java:390) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.ja va:164) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClient Invoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1548) at org.jboss.remoting.Client.invoke(Client.java:534) at org.jboss.remoting.Client.invoke(Client.java:522) at org.jboss.remoting.transporter.TransporterClient.invoke(TransporterC lient.java:297) to reproduce this (one way at least): run the transporter sample modified for the Client to execute the the makeClientCall multiple times. Now to get past the obvious first issue (socket in use) add new code for customerProcessor.releaseCustomer(processedCustomer.getCustomerId() in the Client just before the TransporterClient.destroyTransporterClient(customerProcessor); Implement this method in the CustomerProcessorImpl to use the id to locate (eg hash get()) the related ICustomer TransporterClient and destroy it and to the TransporterServer to stop it. This theoretically frees up the Customer "server" allowing for the next iteration by the Client. note that the processCustomer() implemenation is modified to store the TransporterClient and TransporterServer that are created here. ------------ I dug into the code a bit and what i gathered is that a ServerThread is trying to do processInvocation using a SocketServerInvoker that was already "stopped". I think the ServerThread itself should not be executing as the TransporterServer it should be involved with was already stopped. I posted to the jboss forum on issues i was having trying to make the transporter sample run from the client multiple times. See issue by "bord" on 4/17/2007 -- 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

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-591) Make asynchronous calls using Transporter

by vivek v (JIRA)

Make asynchronous calls using Transporter ----------------------------------------- Key: JBREM-591 URL: http://jira.jboss.com/jira/browse/JBREM-591 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transporter Reporter: vivek v Assigned To: Tom Elrod This came out of the user forum question, http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89224 Currently, there is a mechanism to do asynchronous calls and callbacks using InvocationHandler. As more and more people are using POJOs (via Transporter) for remoting it would be great if we can have the same features (both asynchronous calls and callbacks) available for the Transporter. Couple of use cases can be, Asynchronous Call ----------------------------- 1) Client makes a simple method call (using POJO) on server 2) Server gets the request and returns immediately to the Client. Now Client is free to do its own stuff without waiting or polling for the result. 3) Server starts processing the request 4) When the response is ready Server sends the response to the Client. Callbacks -------------------- 1) An alert happens on the server side 2) Server should be able to send the alert to the Client without Client requesting for it. -- 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

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBREM-585) there is the need to add a callback listener for ssl stream invocation

by Michael Voss (JIRA)

there is the need to add a callback listener for ssl stream invocation ---------------------------------------------------------------------- Key: JBREM-585 URL: http://jira.jboss.com/jira/browse/JBREM-585 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: stream Affects Versions: 2.0.0.CR1 (Boon) Reporter: Michael Voss Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) If want to use existing ssl connector for stream invocation (using Client.invoke(InputStream,Object,Connector) ) the client has to add a callback listener to run the the invocation properly I think stream invocation should also work without the need to add a callback listener if no listener is added the following exception is thrown: by stream sender: org.jboss.remoting.ConnectionFailedException: Connection has been shutdown: javax.net.ssl.SSLProtocolException: Illegal client handshake msg, 1 at org.jboss.remoting.transport.multiplex.MultiplexClientInvoker.handleConnect(MultiplexClientInvoker.java:111) at org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:252) at org.jboss.remoting.Client.connect(Client.java:391) at org.jboss.remoting.Client.connect(Client.java:383) at org.jboss.remoting.stream.StreamHandler.<init>(StreamHandler.java:77) at org.jboss.remoting.ServerInvoker.getStreamHandler(ServerInvoker.java:1253) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1225) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:983) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:447) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:520) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:257) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.remoting.Client.invoke(Client.java:604) at org.jboss.remoting.Client.invoke(Client.java:1211) by stream receiver: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLProto colException: Illegal client handshake msg, 1 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(Unknown Source) at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.jboss.remoting.transport.multiplex.InputMultiplexor$SingleGroupIn putThread.completeHeader(InputMultiplexor.java:608) at org.jboss.remoting.transport.multiplex.InputMultiplexor$SingleGroupIn putThread.doRun(InputMultiplexor.java:540) at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(St oppableThread.java:54) Caused by: javax.net.ssl.SSLProtocolException: Illegal client handshake msg, 1 at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source ) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un known Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source ) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source) at java.io.OutputStream.write(Unknown Source) at org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread .encode(OutputMultiplexor.java:580) at org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread .doRun(OutputMultiplexor.java:452) ... 1 more -- 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

14 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-9099) Handle reconnection of hosts to the domain

by Brian Stansberry (JIRA)

Handle reconnection of hosts to the domain ------------------------------------------ Key: JBAS-9099 URL: https://issues.jboss.org/browse/JBAS-9099 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.CR1 Establish processes for host controllers to reconnect to the master domain controller if communication is disrupted and thereafter synchronize themselves (and their servers) with the domain. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
8
0 / 0

[JBoss JIRA] Created: (JBAS-9369) Implement Namespace resolution policy

by David Lloyd (JIRA)

Implement Namespace resolution policy ------------------------------------- Key: JBAS-9369 URL: https://issues.jboss.org/browse/JBAS-9369 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE, Naming Reporter: David Lloyd Assignee: John Bailey Fix For: 7.0.0.Beta4 Perform the following automatic translations: * {{foo/bar/baz}} becomes {{java:jboss/env/foo/bar/baz}} ** if a component is in scope, instead use {{java:comp/env/foo/bar/baz}} or {{java:module/env/foo/bar/baz}} as appropriate * {{java:/foo/bar/baz}} => {{java:jboss/root/foo/bar/baz}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-8338) handling of service start failure

by Alexey Loubyansky (JIRA)

handling of service start failure --------------------------------- Key: JBAS-8338 URL: https://jira.jboss.org/browse/JBAS-8338 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 In this case, the exception is logged, and all the service's dependents will be trapped in a waiting state. This type of error will typically be due to transient conditions, like an incorrectly configured IP address, disk space issues, and so on. The correct behavior here is to log the error and let the user decide (based on the GUI or perhaps by deployment plan policy) whether to fix the issue and retry the failed service, let the error stand, or pull out the deployment unit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (SECURITY-440) JBossXACML:: bug identified implementing RBAC

by Anil Saldhana (JIRA)

JBossXACML:: bug identified implementing RBAC --------------------------------------------- Key: SECURITY-440 URL: https://jira.jboss.org/jira/browse/SECURITY-440 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Reporter: Anil Saldhana Assignee: Anil Saldhana -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (SECURITY-590) RequestAttributeFactory.createTimeAttributeType(attName, issuer) API call causes a parsing exception

by Asankha Perera (JIRA)

RequestAttributeFactory.createTimeAttributeType(attName, issuer) API call causes a parsing exception ---------------------------------------------------------------------------------------------------- Key: SECURITY-590 URL: https://issues.jboss.org/browse/SECURITY-590 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Environment: Version was 2.0.6.Final Reporter: Asankha Perera Assignee: Anil Saldhana Priority: Minor Using the API call RequestAttributeFactory.createTimeAttributeType(attName, issuer) causes a "ParsingException: couldn't create http://www.w3.org/2001/XMLSchema#time attribute based on DOM node" Note that with the above API call, we do not supply any time string, but assume that the current time is used. As a comparison the similar API call RequestAttributeFactory.createDateTimeAttributeType(attName, issuer) works without any issues - hence it seems logical that the createTimeAttributeType() contains a possible bug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1293) Cleanup dependencies of ejb3-core

by Carlo de Wolf (JIRA)

Cleanup dependencies of ejb3-core --------------------------------- Key: EJBTHREE-1293 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1293 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 The goal is to have ejb3-core not depend on any jboss-as artifacts. -- 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

14 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2057) Fix testsuite regression related to HornetQ integration

by Carlo de Wolf (JIRA)

Fix testsuite regression related to HornetQ integration ------------------------------------------------------- Key: EJBTHREE-2057 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2057 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Priority: Critical Fix For: EJB3_1 1.0.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
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 2011