Troubleshooting wifi connectivity is always a headache. I just spent 4 days fixing (actually, finding a workaround for) this problem. Everything worked fine when my PC is connected to a monitor. Then I switched display to my LCD TV with HDMI integrated sound and video. Then my wifi stopped working. The signal strength is perfect and I verified my password a million times (I'm using WPA-PSK). When I tried to connect, it simply fails. No error message, not even an error code! I suspected the HDMI integrated sound driver so I switched sound to the native Realtek driver, still no hope. Then I upgraded the wifi driver to the latest, it didn't help. Uninstalled and reinstalled the driver and rebooted, no difference. What was the...

It happened on Windows XP with JBoss 5.1.0.GA. This is the stack trace: 2010-07-30 16:39:52,177 ERROR [org.jboss.kernel.pl... According to " (SOLVED) JBAS-7674 solution for JBoss 5.1?? (Windows lock on jnp-service.url) ", the problem seemed to be solved for JBoss 6. In the meanwhile for JBoss 5, disabling Windows Indexing Service seemed to solve the problem. Quote from aforementioned link: It seemed that a file was being locked for some reason, and that file was obviously necessary for JBoss to start. Some further investigation (ok, I admit, I just tried to delete all of JBoss with the faith that it would fail on the locked file), it turns out that file was some file called jnp-service.url in the data directory of the default server. After downloading...

For the default profile, the admin password is stored in the file server/default/conf/props/jmx-console-users.properties . Simply change the password and save: # A sample users.properties file for use with the ... But most likely you are trying to secure the JBOSS server in a production environment, and changing the password only isn't enough. For example, the JMX console is still wide open after you made the above change. Securing the JMX Console and Web Console is quite a daunting task!

By default, JBOSS server binds only to localhost. Use the -b option to bind to all available IP addresses: sh bin/run.sh -b 0.0.0.0

Test with curl and default Apache doc. C:\>curl --dump-header - http://localhost HTTP/...

Oracle Web Cache version used: Oracle Application Server Web Cache 10.1.2.3.0 ... The test page is a simple Struts action sending a URL redirect: public ActionForward execute(ActionMapping map... Web Cache setup Origin server Host Name Port oas.host 7777 Site Host Name Port URL Path Prefix webcache.host 80 Test results Request directly to the OC4J (Oracle Application Server): C:\work\testAppWebApp2>curl --dump-header - http:/... Request to Oracle Web Cache: C:\work\testAppWebApp2>curl --dump-header - http:/... Notice that Oracle Web Cache correctly translated the host name in the header and HTML page. However, the port number remained that of the Oracle App Server.

Start remote desktop client by clicking Start and Run, then enter mstsc. Click the "Options" button, select the "Local Resources" tab, check "Clipboard" More options are available when you click the "More..." button (share local drives etc.).

Port 8080 is undoubtedly overused. You may want to change JBOSS to a port other than the default 8080. Edit the file $JBOSS_HOME/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and change the webserver port from 8080 to 8088: <bean class="org.jboss.services.bi... The XSLT at the bottom of the file transforms port 8080 in $JBOSS_HOME/server/default/deploy/jbossweb.sar/server.xml to 8088 specified in this file.

Download JBoss from http://www.jboss.org/jbossas/downloads/ Set environment variables JAVA_HOME and JBOSS_HOME Open a command prompt and enter %JBOSS_HOME%\bin\run.bat ( $JBOSS_HOME/bin/run.sh on *nix). Drop your WAR or EAR file into %JBOSS_HOME%\server\default\deploy