[Design of JBoss internal QA (Test Suite)] - Problem with start ant task in trunk
by ivanneto
I was trying to run some testsuite tests and noticed that after starting a server with the "start" ant task, the server was started but the ant script stayed blocked and a long time after failed. I looked at the server log and the server was started correctly. So, I thought that the "start" task wasn't able to detect that the server was successfully initiated.
Looking at:
org.jboss.test.util.server.ServerController.isServerStarted(Server server)
I saw how the "start" ant task checks to see if the server has been started. It opens a HttpURLConnection to the server and then calls getResponseCode(). With an old version of the SVN trunk (some months old), the getResponseCode() returns 200 and everything works OK. With the SVN trunk version from yesterday (05/24/2007), I don't know why the server answers with the HTTP 400 code. Then this check:
if (responseCode > 0 && responseCode < 400)
in ServerController.isServerStarted() fails and the ant "start" task fails.
My point is: if there's a Web server answering with a 400 code, shouldn't org.jboss.test.util.server.ServerController assume that the server has been started correctly?
Regards,
Ivan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048370#4048370
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048370
16 years, 11 months
[Design of JBoss Remoting, Unified Invokers] - Re: http-invoker and authentication info
by jimbrady
For what its worth, I can't find any evidence that the Servlet is being called at all. I have fairly detailed logging of the security side switched on. I see the following:
2007-05-24 15:48:39,205 TRACE [org.jboss.web.tomcat.security.SecurityAssociationValve] End invoke, callerGenericPrincipal[james-vincent.brady(a)db.com()]
2007-05-24 15:48:39,205 TRACE [org.jboss.security.SecurityAssociation] clear, server=true
2007-05-24 15:48:39,970 TRACE [org.jboss.web.tomcat.security.SecurityAssociationValve] Begin invoke, callerGenericPrincipal[james-vincent.brady(a)db.com()]
2007-05-24 15:48:39,970 TRACE [org.jboss.security.SecurityAssociation] pushRunAsIdentity, runAs=null
2007-05-24 15:48:39,970 TRACE [org.jboss.web.tomcat.security.RunAsListener] JMXInvokerServlet, runAs: null
2007-05-24 15:48:39,970 TRACE [org.jboss.web.tomcat.security.RunAsListener] JMXInvokerServlet, runAs: null
Notice JMXInvokerServlet (not my version - I wonder why) runAs null.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048313#4048313
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048313
16 years, 11 months
[Design of JBoss jBPM] - Re: console updates
by david.lloyd＠jboss.com
"tom.baeyens(a)jboss.com" wrote : i saw the removal of the old console.
|
| i same the addition of the new webapp resources. but i didn't see any new java classes. could it be that you forgot to synchronize them ?
Nope, there are none. I had to choose between reimplementing everything yet again, or simply using my mostly-built component libraries. I went with the latter option. As such, so far there has been no need for additional code within the console itself.
also i would like the hibernate.cfg.xml file to be moved to another location then the java sources. cause it conflicts with the main jpdl test suite in the default eclipse configuration. probably the easiest if you move it to a console/src/main/resources or console/src/main/config folder
"tom.baeyens(a)jboss.com" wrote : also, you should build the hibernate.cfg.xml dynamically from the source hibernate.cfg.xml
|
| otherwise the referenced hibernate mappings and configurations will get out of sync (as they are already)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048284#4048284
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048284
16 years, 11 months
[Design of JBoss Remoting, Unified Invokers] - Re: http-invoker and authentication info
by jimbrady
Thanks for replying. It doesn't quite fit my case because in my case, I don't have the credentials (I just have a Tomcat Valve that extracts the user from a cookie and passes that through without a password.) But I have got the authentication to work (the invoker JNDIFactory is protected and it gets through that), the problem is that the principal is not getting to the session bean. I can't even get to the session bean if it is protected, and this connection rejection occurs before the marshalled invocation is established in the InvokerServlet. I can't understand why JBOSS doesn't have an answer to this, because one of the justifications for using HTTP tunneling is to establish the user credentials.
Only protecting the JNDI interface is rather pointless from my point of view. I want to use SSO from a java application using the cookie set up from the browser.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048263#4048263
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048263
16 years, 11 months