Loading...

XML

Word

Printable

Affects:

Release Notes
Workaround:

Workaround Exists
Workaround Description:

Hide

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>

Show
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>

In some circumstances, windows is reporting the AS is holding a lock on the data/jnp-service.url file when it isn't running.

blocks

JBPAPP-3364 On windows, a file is left behind occoasionally resulting in the server not being able to be restarted