Section 2.2.3 describes enabling security service for the jmx console.
Following the steps exactly on my installation results in perpetual HTTP 401
responses from the web server, correct username-password-be-damned.
None of the log files were modified during this authentication attempt. As fa
"visolvejboss" wrote :
|
| You can export DISPLAY variable in run.sh file of jboss, so that when the
startup script in init.d calls the run.sh file, the DISPLAY variable will be
exported.
|
|
Thank you for again for responding, but it seems to me like the problem still
stands:
When
I have a question about a topic posted at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88092
What are the conditions under which the Database Manager Tool can connect to my
X-Windows Server? Is there a practical way to do this?
View the original post :
http://www.jboss.com/index.
OK, thanks for your response and I can do that, BUT I have a followup question
for everyone:
I am starting my server using an init.d script which brings the service online
in runlevel 3, which seems to me like the "normal" way I would want to start
and use this server. If I have to login and s
I am having significant headaches trying to get through this section. Please
see my post to other forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88092
It looks like a great tool, and I would like to try it out for possible use.
But I could suggest cutting this section out
I am either going to lose my head or rip my hair out. Please suggest how to
configure so that these swing components will be able to have a window. Thanks
in advance. I am using :
RHEL4
| jdk1.5.0_07
| jboss4.0.4.GA-ejb3 -c all
| connecting from WindowsXP using putty and XMing
|
|
