Further update: First, this is for jboss-5.0.1.GA. Second: This seems to be an incompatibility in a configuration attribute type. In initializing the datasource, the class LocalManagedConnectionFactory is being used. This extends BaseWrapperManagedConnectionFactory, which has a method
| public void setUseTryLock(int useTryLock) | This would be set by ManagedConnectionFactoryDeployment.setManagedConnectionFactoryAttribute(). I believe the value is coming from DataSourceDeploymentMetaData: | @ManagementProperty(name="use-try-lock", description="The internal lock timeout", | includeInTemplate=true) | public long getUseTryLock() | However, the setter takes an int. The property is defined as a long. The reflection in the method that sets it is looking for something that takes a long, and does not find it. It logs it as a trace, since its not required to be there, so no warning is indicated. In short, there doesn't seem to be a way to configure the use-try-lock timeout. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241293#4241293 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241293 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
