[JBoss Portal] - Re: Compile Jboss 32bit on Linux 64bit
by PeterJ
Not sure what you are asking. The JVM is a virtual machine that defines its own instruction set and architecture, including the size of the data types. This virtual machine, within which Java apps run, is the same regardless of the architecture of the host environment, whether 32, 64 or even 48 bits (we have a JVM that runs on a 48bit machine, and JBoss AS runs without changes). Thus, a 64-bit JVM running on a 64-bit Linux OS provides the exact same virtual machine environment for Java applications as would a 32-bit JVM running on Windows (well, because the 64-bit JVM has a larger available memory area, you can assign larger heaps than for a 32-bit JVM). This is what makes the "compile once, run everywhere" mantra for Java true.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241294#4241294
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241294
16 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: Can't get use-try-lock to work
by fishribs
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
16 years, 9 months