[ https://jira.jboss.org/browse/JBAS-7674?page=com.atlassian.jira.plugin.sy... ] Kenny MacLeod commented on JBAS-7674: ------------------------------------- This is still happening with 6.0.0 M3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-7674?page=com.atlassian.jira.plugin.sy... ] Sergio Salgueiro edited comment on JBAS-7674 at 7/30/10 9:43 AM: ----------------------------------------------------------------- Somehow, the "jnp-service.url" will get locked by cidaemon.exe (aka the Windows Indexing Service). A possible workaround would be to kill the cidaemon.exe process and the file would be free. Also, check the data folder as not indexed by this service. was (Author: sergiosalgueiro): Somehow, the "jnp-service.url" will get locked by cidaemon.exe (aka the Windows Indexing Service). A possible workaround would be to kill the cidaemon.exe process and the file would be free. Also, check the data foldar as not indexed by this service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-7674?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated JBAS-7674: ----------------------------------- Workaround Description: The purpose of the data/jnp-service.url is to allow JON to discover the socket on which the JNDI server is listening. If JON is not being used, the creation of this file can be eliminated. To do this, edit the deploy/naming-jboss-beans.xml file and comment out or delete the following bean: <bean name="NamingProviderURLWriter" class="org.jboss.naming.NamingProviderURLWriter"> <property name="server"><inject bean="JBossServer"/></property> <property name="bootstrapAddress"><inject bean="RemoteNamingBean" property="bindAddress"/></property> <property name="bootstrapPort"><inject bean="RemoteNamingBean" property="port"/></property> </bean> Workaround: [Workaround Exists] Added a workaround for users who are not using JON. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-7674?page=com.atlassian.jira.plugin.... ] oglueck commented on JBAS-7674: ------------------------------- Thanks, Brian. Unfortunately the issue is not as easy to reproduce as I like it too. Just tried twice and didn't occur. I am not using JON, so commenting out the bean as you suggested. Strange, I have been playing around with JBAS6 since two days only and already spotted a hard to reproduce bug :-) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-7674?page=com.atlassian.jira.plugin.... ] Saurabh Doshi commented on JBAS-7674: ------------------------------------- Kiling cidaemon.exe resolve this issue. Thanks Sergio -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira