[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Andrew Oliver updated JBAS-6392: -------------------------------- Attachment: patch patch.jar 1. first a patch that does this (against a checkout of the 4.2 branch at least) 2. a compiled version that you can use by doing jar -xf patch.jar into a directory and then from that directory jar -uf $JBOSS_HOME/client/jbossall-client.jar org/jboss/naming/*.class (note this assumes you use jboss naming in your client, if you use all the little jars then you will have to figure out which one has HttpNamingContextFactory.class in it) 3. I'll commit this in a sec for later release in 4.2.4 and possibly 5.0.x if I manage to get it to build. This is a pretty minor little feature that mainly people got used to using in WebLogic but it is a pretty good idea anyhow. Note the patch differs slightly from the way that LoginInitialContextFactory works. LoginContextFactory fails if there is no auth.conf (which there is not by default) which is a major pain in Java Web Start style apps. This trys for the default behavior but if that fails it does the smart thing and uses the default username/password style login module configuration (the DummyConfiguration) without regards to a conf file. This is much nicer IMO. I'd fix LoginInitialContextFactory but then I'd have to refactor where these are to avoid duplicating the same code in both places. I'm unencumbered with a desire to do that at the moment. If someone else wants to maybe create all of these in one module ( instead of some in security and some in server etc) and maybe give some sanity to the names (subclass them with classes with the old names for compatibility) then I'll go factor this out into common code and add balance to the force. On the whole LoginInitialContextFactory is kind of boneheaded. If someone set SECURITY_PRINCIPAL then they probably want this behavior, if they didn't then they don't no need for special versions of things. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Andrew Oliver reassigned JBAS-6392: ----------------------------------- Assignee: Andrew Oliver (was: Scott M Stark) -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Andrew Oliver updated JBAS-6392: -------------------------------- Attachment: patch50 patch50 is for the 50 branch. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Andrew Oliver commented on JBAS-6392: ------------------------------------- Is that a public address? I don't have access to it. I have this problem in 4.2 generally with the HTTP invoker WHENEVER I've used it at least once regardless of this change. It isn't related to initiating a Jaas authentication. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Andrew Oliver commented on JBAS-6392: ------------------------------------- The error I get whenever unified servlet invoker is used looks like this: 14:12:26,514 ERROR [Connector] invalid Object Name javax.management.InstanceNotFoundException: jboss.remoting:service=invoker,transport=servlet is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523) at org.jboss.mx.server.MBeanServerImpl.unregisterMBean(MBeanServerImpl.java:383) at org.jboss.remoting.transport.Connector.stop(Connector.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Regardless of this patch. The server still shuts down. I note that Tomcat undeploys my servlet before this message appears. Indicates to me that I may be missing a depends or something (I followed the wiki instructions). It doesn't actually prevent the server from stopping. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6392?page=com.atlassian.jira.plug... ] Brian Stansberry reopened JBAS-6392: ------------------------------------ -- 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