[
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.
Windows file locking problem with the data/jnp-service.url file
---------------------------------------------------------------
Key: JBAS-7674
URL:
https://issues.jboss.org/browse/JBAS-7674
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Management services
Affects Versions: JBossAS-5.1.0.GA, 6.0.0.M1
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 6.0.0.M2
In some circumstances, windows is reporting the AS is holding a lock on the
data/jnp-service.url file when it isn't running.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira