[Design of POJO Server] - Re: JBAS-5953; jar override issue
by alesj
"dimitris(a)jboss.org" wrote :
| Obviously the usecase of re-deploying a jar is quite common and needs to be addressed. What if we jboss.vfs.forceNoReaper=true by default?
|
I would still leave it at false.
I was able to do a legit workaround the issue,
while global VFS setting is still at NoReaper==false.
I add the following piece to UndeployBrokenPackageUnitTestCase:
| assertTrue(thejar.delete()); // TODO - this should work
| Files.copy(goodjar, thejar);
| getLog().info("Redeploying testPackage: " + testPackage);
|
so that assert should complain before if things cannot me mounted together.
If I add the following code to old MainDeployer::deploy
| VFS vfs = VFS.getVFS(url);
| VFSUtils.enableNoReaper(vfs);
| VirtualFile file = vfs.getRoot();
| VFSDeployment deployment = deploymentFactory.createVFSDeployment(file);
|
the test passes w/o any problems.
In this case it's actually the file openness that prevents it from being overridden.
Reaper is holding it open for 5sec to get better read performance,
but the client == test tries to override it in less than 5sec.
I think users don't really intend to re-deploy things in less than 5sec,
so we should be fine. :-)
If this becomes a more serious issue for users,
we can always add some option to ProfileImpl,
to either use VFSUtils + VFS to enable/disable certain options.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190119#4190119
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190119
17 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - connection factories and connection params
by ataylor
Currently each connection factory has its own cofiguration for connection params. This means that if i want to change the hostname for the server i have to configure it in jbm-configuration.xml and then configure each connection factory individually which seems a bit of a pain.
Wouldn't it be better to take the defaults from the server configuration and allow overrides, so in the main server config we have
|
| <acceptor name="netty">
| <factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class>
| <params>
| <param key="jbm.remoting.netty.host" value="localhost" type="String"/>
| <param key="jbm.remoting.netty.port" value="5400" type="Integer"/>
| <param key="jbm.remoting.netty.tcpnodelay" value="true" type="Boolean"/>
| <param key="jbm.remoting.netty.tcpsendbuffersize" value="32768" type="Integer"/>
| <param key="jbm.remoting.netty.tcpreceivebuffersize" value="32768" type="Integer"/>
| <param key="jbm.remoting.netty.usenio" value="true" type="Boolean"/>
| <param key="jbm.remoting.netty.sslenabled" value="false" type="Boolean"/>
| </params>
| </acceptor>
and in the jbm-jndi.xml file we have
|
| <connection-factory name="ConnectionFactory">
| <connector config="netty"/>
| <entry name="ConnectionFactory"/>
| <entry name="/ConnectionFactory"/>
| <entry name="/XAConnectionFactory"/>
| <entry name="java:/ConnectionFactory"/>
| <entry name="java:/XAConnectionFactory"/>
| </connection-factory>
|
|
and then if the user wants to override anything they can, i.e.
<connection-factory name="ConnectionFactory">
| <connector config="netty">
| <params>
| <param key="jbm.remoting.netty.tcpnodelay" value="true" type="Boolean"/>
| </params>
| </connector>
| <entry name="ConnectionFactory"/>
| <entry name="/ConnectionFactory"/>
| <entry name="/XAConnectionFactory"/>
| <entry name="java:/ConnectionFactory"/>
| <entry name="java:/XAConnectionFactory"/>
| </connection-factory>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190028#4190028
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190028
17 years, 4 months