[JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker
by mayankmit2002
Hello Ron,
Thanks for correcting me, in my configuration "socket.check_connection" was set to true, after setting it to false. one of my problem is fixed.
But till now, I'am just unable to set the socket time out at the client end when looking for the remote SLSB, even after setting the timeout value to 10000 ms
I'm creating my connection in the following way.
| private static Properties getContextProperties ()
| {
| final Properties props = new Properties();
| props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
| props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
| props.put("jnp.sotimeout", "10000");
| // props.put("jnp.timeout", "10000");
| props.put("timeout", "10000");
|
| if (mActiveNetworkAddress != null)
| {
| props.put(NamingContext.JNP_LOCAL_ADDRESS, mActiveNetworkAddress);
| }
|
| // for HA-JNDI lookup
|
| String partitionName = java.lang.System.getProperty("cms.partition.name", java.lang.System.getenv("COMPUTERNAME") + "_PARTITION");
| partitionName = partitionName.toUpperCase();
|
| // for auto discovery through partition name
| props.put(NamingContext.JNP_PARTITION_NAME, partitionName);
|
| props.put(NamingContext.JNP_DISABLE_DISCOVERY, "false");
|
| return props;
| }
|
I am passing above properties in the inital context.
is am missing some thing?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255232#4255232
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255232
16 years, 7 months
[jBPM Users] - Re: Deploying processes on Tomcat
by sebastian.s
The actual problem is that I don't succeed in deploying processes with the help of the ANT task. The tasks runs but it always deploys the processs to an in-memory database although I have specified the connection details in the build.xml file.
I have to say I am a bit confused because there are jdbc-properties and hibernate-properties. To be sure I set them both
| <property name="jdbc.driver" value="org.hsqldb.jdbcDriver"/>
| <property name="jdbc.url" value="jdbc:hsqldb:hsql://myserver.mydomain.de:1701"/>
| <property name="jdbc.username" value="sa"/>
| <property name="jdbc.password" value=""/>
|
| <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialec"/>
| <property name="hibernate.connection.driver_class" value="org.hsqldb.jdbcDriver"/>
| <property name="hibernate.connection.url" value="jdbc:hsqldb:hsql://myserver.mydomain.de:1701"/>
| <property name="hibernate.connection.username" value="sa"/>
| <property name="hibernate.connection.password" value=""/>
| <property name="hibernate.format_sql" value="true"/>
|
But obviously connection details are ignored:
| [jbpm-deploy] INFO: using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:mem:.
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255229#4255229
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255229
16 years, 7 months
[Security] - jboss j_security_check: russian letters password problem
by pashkinmv
I'm using JBoss 4.2.2 and standard FORM authorization.
Login page charset is UTF-8.
When I press submit button and it redirects me ÃÂ to j_securitry_check, in DatabaseServerLoginModule I have the password inÃÂ wrong encoding.
Example: entered password but using russial letters: "FUBA", in DatabaseServerLoginModule I have: "ÑÑва".
Any ideas how to solve this problem?
login-config.xml content:
<application-policy name="myPolicy">
<login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
<module-option name="dsJndiName">java:/jdbc/myUser</module-option>
<module-option name="principalsQuery">select password from login where login = ?</module-option>
<module-option name="rolesQuery">select role_name, NULL from v_user_role where login = ?</module-option>
<module-option name="hashAlgorithm">MD5</module-option>
<module-option name="hashEncoding">HEX</module-option>
<module-option name="hashCharset">UTF-8</module-option>
</login-module>
</application-policy>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255221#4255221
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255221
16 years, 7 months