September 2006 - jboss-dev-forums

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

anonymous wrote : For JMS traffic (e.g. messages) going from server to client, how do you do this? Sorry, Tim, I'm not sure what "this" refers to. But, actually, when you start a callback connector on the client with the http transport, the server side invoker functions like an HTTP server. The message is handled by a Tomcat connector, which calls CoyoteInvoker.service(). Tom could tell you more about it. Before he replaced it with CoyoteInvoker, he wrote HTTPServerInvoker, which is an HTTP/1.1 complient server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973369#3973369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973369

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

ron_sigal wrote : | 1. JMSWireFormat can't expect to get passed ObjectInputStreams and ObjectOutputStreams. This has been discussed already, although I can't find the reference. I changed it to create object streams as necessary. | timfox wrote : | BTW all the stream stuff in the marshaller is a big pain. | I have been having related issues since as you realised remoting always passes in a ObjectInput/Ouput Stream. | In TRUNK I have changed all this so that now the underlying stream is passed in, so you're changes in that area may not be necessary. | It looks to me that you both applied similar changes concurrently on TRUNK and Branch_1_0. Since we need to get CR5 out ASAP, how about Ron checks in his changes, and we will reconcile them with the trunk later? ron_sigal wrote : | oos = SerializationStreamFactory.getManagerInstance("key").createOutput(out); | "key" has to be replaced by a suitable value. I assume it would be acceptable to just hard code "jboss", [...] | Messaging uses whatever serialization Remoting Connector was configured with, both on client-to-server marshalling and vice-versa. We need to keep this consistent. Take a look at CallbackSErverFactory, for example, to see how this is configured. timfox wrote : | For JMS traffic (e.g. messages) going from server to client, how do you do this? (Obviously you can't have a HTTP server on the client accepting connections) | Do you poll the server from the client intermittently, or do you piggyback server to client traffic on return values of client to server traffic, or both? | Reiterating the same questions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973368#3973368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973368

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: Designing Habanero - Configuration changes

by manik.surtani＠jboss.com

Isn't this unnecessarily complex? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973367#3973367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973367

19 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Custom Principal Propagation Related

by scott.stark＠jboss.org

Why isn't the custom principal triggering reauthentication in the ejb container? The realm authenticated the simple principal and this is what should be cached. The custom principal is a derived identity for application consumption only. Are there two security domains involved here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973365#3973365 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973365

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by clebert.suconic＠jboss.com

The problem is... if you set Lease (on Server) to -1, after its creation... whenever you receive a $PING$ you get an exception. At this point I just want to understand semantics of disabling lease on Serverinvoker. Maybe setLeasePeriod should be deprecated/removed if this is the correct semantic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973363#3973363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973363

19 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Custom Principal Propagation Related

by anil.saldhana＠jboss.com

The mismatch occurs because the jaas auth happens at the beginning of the workflow and the Client Login Module would have placed the custom principal on the stack. But since the authentication goes through fine, the JBossSecurityMgrRealm pushes its view of the username (a SimplePrincipal) on to the stack for use. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973362#3973362 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973362

19 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Custom Principal Propagation Related

by anil.saldhana＠jboss.com

Workflow: 1)User logs into webapp. 2) JBossSecurityMgrRealm gets called with userid=aaa,password=hello 3) JBossSecurityRealm.authenticate(username,pass) { //Create a simple principal to be passed to jaas SimplePrincipal sp = new SimplePrincipal(aaa); //Get the security manager securityMgr.isValid(sp,"hello"); /** Note in the isValid call, the jaas framework gets called and custom LM creates a custom principal. ClientLM pushes it on the SA stack. The SA stack has the custom principal on the stack. **/ //Ok SecurityAssociation.push(sp, hello); } 4) Request lands at the servlet. 5) In the servlet, there is call on an ejb (There is no explicit jaas login here) 6) In the proxy, the SecurityInterceptor picks up the latest principal from the SA stack (that happens to be the last call on the SA done by the SecurityMgrRealm) 7) The ejb is unhappy that it did not get the custom principal and chokes with a CCE. This usecase is when the web and the ejb components are in the same VM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973359#3973359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973359

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by tom.elrod＠jboss.com

I don't really understand what you are trying to achieve, so if can explain that better, can help with how to do it (i.e. stop future clients from establishing lease sessions, clean up current server side lease sessions, etc.). Currently the only way to disable leasing from the server side (meaning will tell any future clients doing initial lease query that server leasing is disabled AND clean up any current lease sessions in progress on the server side) is to remove all ConnectionListeners on the server side. Setting the lease period to negative value after lease management has been enabled, does not have any impact other then if remove all ConnectionListeners and then add a new ConnectionListener, leasing will NOT be enabled (since the lease period is negative). Admittedly, this is not well documented within remoting guide (I will update the doc). The change for JBREM-602 does prevent future clients doing a lease query from starting a lease session, but does not clean up an current lease sessions in progress. Should also mention that there is currently nothing within the code to prevent clients from sending lease ping once leasing has been disabled on the server side. They will just continue to send lease ping, which will be thrown away on the server side. So what I need to understand is exactly what it you need (requirements) and will make it happen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973357#3973357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973357

19 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Custom Principal Propagation Related

by scott.stark＠jboss.org

For propagation the ClientLoginModule needs to push the identity that was authenticated. When was the custom principal created? Describe the full workflow from incoming request to propagation to the ejb. The JBossSecurityMgrRealm cannot be involved in creating principals as its the security interceptor running in the context of the authentication request that has the knowledge and correct classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973354#3973354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973354

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by ovidiu.feodorov＠jboss.com

http://jira.jboss.com/jira/browse/JBREM-602 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973352#3973352 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973352

19 years, 6 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-dev-forums September 2006