[JBoss Messaging] - Re: Thread Pool questions
by andy.miller＠jboss.com
"gaohoward" wrote : Hi,
|
| I don't know if jms-ds.xml has such a parameter, you can ask the JCA forum about it. JBoss remoting does has such a parameter, you can read about it in the jboss remoting's doc. The remoting configuration file is set at the JBM server side only.
|
I know there is a JCA thread pool, as I already talked to them, and that's not what I'm after.
I find maxPoolSize in jms-ds.xml in the current releases of AS, so I also know about that.
So, what I'm trying to make sure I understand is what parameter does what? The remoting configuration seems an unlikely place to be setting a thread pool for an in JVM invocation.
For example, in EJB 3 land, there is a thread pool for remote clients that make EJB calls, but that is bypassed when the call comes from within the same JVM.
I would expect the same behavior from messaging, where the remoting configuration would be only for remote clients, and there would be different behavior for the in JVM calls.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240840#4240840
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240840
16 years, 9 months
[Security & JAAS/JBoss] - Re: Single Sign On with LDAP Examples
by rathinaganesh
Greetings,
I am trying to do the same thing, Install Federated SSO and test it.
I am using
Jboss-4.2.2.GA on Windows XP
OpenDS-1.2.0 on FreeBSD
I have set up the OpenDS for the testuser login.
Previously, I got the error as testuser is not activated. So, I took out the source from the trunk mentioned above. Updated the trunk and build the sso sar and ear files.
The security-config.xml inside the jboss-sso-test.ear\META-INF looks like this
|
| <!-- The JAAS login configuration file for the java:/jaas/jbossweb-form-auth
| security domain used by the security-spec test case
| -->
| <policy>
| <application-policy name="jboss-sso">
| <authentication>
| <login-module code="org.jboss.security.idm.UsernameAndPasswordLoginModule" flag="sufficient">
| <module-option name="unauthenticatedIdentity">guest</module-option>
| <module-option name="password-stacking">useFirstPass</module-option>
| <!--module-option name="hashAlgorithm">MD5</module-option>
| <module-option name="hashEncoding">HEX</module-option-->
| <module-option name="authenticatedRoles">Authenticated,RegisteredUsers</module-option>
| </login-module>
| <login-module code="org.jboss.security.idm.UsernameAndPasswordLoginModule" flag="sufficient">
| <module-option name="unauthenticatedIdentity">guest</module-option>
| <module-option name="password-stacking">useFirstPass</module-option>
| <module-option name="authenticatedRoles">Authenticated,RegisteredUsers</module-option>
| </login-module>
| </authentication>
| </application-policy>
| </policy>
|
|
The sso.cfg.xml file under jboss-sso.sar looks like this
|
| <login>
| <provider id="si:jboss-sso:ldap:login" class="org.jboss.security.idm.ldap.HashAlgorithmRemoverLDAPIdentityProvider">
| <property name="connectionURL">
| jdbc:ldap://10.10.60.4:389/dc=jboss,dc=com?SEARCH_SCOPE:=subTreeScope&secure:=false&concat_atts:=true&size_limit:=10000000
| </property>
| <property name="username">uid=admin,dc=jboss,dc=com</property>
| <property name="password">jbossrocks</property>
| <property name="identityOu">People</property>
| <property name="roleOu">roles</property>
| </provider>
| </login>
|
|
and this is how it looks like in the ldapsearch
| /usr/local/OpenDS-1.2.0/bin/ldapsearch -s sub -b cn=testuser,ou=People,dc=jboss,dc=com "(objectclass=*)"
| dn: cn=testuser,ou=People,dc=jboss,dc=com
| objectClass: person
| objectClass: inetOrgPerson
| objectClass: organizationalPerson
| objectClass: top
| mail: [EMAIL PROTECTED]
| uid: test
| cn: testuser
| displayName: Test User
| sn: true
|
When I try to use testuser and secret as login and password, I get login failed on the jsp. I am not getting any errors on the jboss server log.
On the OpenDS log, I see the following message.
|
| [29/Jun/2009:11:19:54 -0700] CONNECT conn=176 from=10.10.1.145:3241 to=10.10.60.4:389 protocol=LDAP
| [29/Jun/2009:11:19:54 -0700] BIND REQ conn=176 op=0 msgID=19 type=SIMPLE dn="uid=admin,dc=jboss,dc=com"
| [29/Jun/2009:11:19:54 -0700] BIND RES conn=176 op=0 msgID=19 result=0 authDN="uid=admin,dc=jboss,dc=com" etime=1
| [29/Jun/2009:11:19:54 -0700] SEARCH REQ conn=176 op=1 msgID=20 base="cn=testuser,ou=People,dc=jboss,dc=com" scope=wholeSubtree filter="(objectClass=*)" attrs="cn"
| [29/Jun/2009:11:19:54 -0700] SEARCH RES conn=176 op=1 msgID=20 result=0 nentries=1 etime=2
| [29/Jun/2009:11:19:54 -0700] UNBIND REQ conn=176 op=2 msgID=21
| [29/Jun/2009:11:19:54 -0700] DISCONNECT conn=176 reason="Client Unbind"
| [29/Jun/2009:11:19:54 -0700] CONNECT conn=177 from=10.10.1.145:3242 to=10.10.60.4:389 protocol=LDAP
| [29/Jun/2009:11:19:54 -0700] BIND REQ conn=177 op=0 msgID=22 type=SIMPLE dn="uid=admin,dc=jboss,dc=com"
| [29/Jun/2009:11:19:54 -0700] BIND RES conn=177 op=0 msgID=22 result=0 authDN="uid=admin,dc=jboss,dc=com" etime=1
| [29/Jun/2009:11:19:54 -0700] SEARCH REQ conn=177 op=1 msgID=23 base="cn=testuser,ou=People,dc=jboss,dc=com" scope=wholeSubtree filter="(objectClass=*)" attrs="cn,sn,userPassword,givenName,displayName,o,employeeType,title,postalAddress,mail,telephoneNumber"
| [29/Jun/2009:11:19:54 -0700] SEARCH RES conn=177 op=1 msgID=23 result=0 nentries=1 etime=1
| [29/Jun/2009:11:19:54 -0700] UNBIND REQ conn=177 op=2 msgID=24
| [29/Jun/2009:11:19:54 -0700] DISCONNECT conn=177 reason="Client Unbind"
| [29/Jun/2009:11:19:54 -0700] CONNECT conn=178 from=10.10.1.145:3243 to=10.10.60.4:389 protocol=LDAP
| [29/Jun/2009:11:19:54 -0700] BIND REQ conn=178 op=0 msgID=25 type=SIMPLE dn="uid=admin,dc=jboss,dc=com"
| [29/Jun/2009:11:19:54 -0700] BIND RES conn=178 op=0 msgID=25 result=0 authDN="uid=admin,dc=jboss,dc=com" etime=1
| [29/Jun/2009:11:19:54 -0700] SEARCH REQ conn=178 op=1 msgID=26 base="cn=testuser,ou=People,dc=jboss,dc=com" scope=wholeSubtree filter="(objectClass=*)" attrs="cn"
| [29/Jun/2009:11:19:54 -0700] SEARCH RES conn=178 op=1 msgID=26 result=0 nentries=1 etime=1
| [29/Jun/2009:11:19:54 -0700] UNBIND REQ conn=178 op=2 msgID=27
| [29/Jun/2009:11:19:54 -0700] DISCONNECT conn=178 reason="Client Unbind"
| [29/Jun/2009:11:19:54 -0700] CONNECT conn=179 from=10.10.1.145:3244 to=10.10.60.4:389 protocol=LDAP
| [29/Jun/2009:11:19:54 -0700] BIND REQ conn=179 op=0 msgID=28 type=SIMPLE dn="uid=admin,dc=jboss,dc=com"
| [29/Jun/2009:11:19:54 -0700] BIND RES conn=179 op=0 msgID=28 result=0 authDN="uid=admin,dc=jboss,dc=com" etime=1
| [29/Jun/2009:11:19:54 -0700] SEARCH REQ conn=179 op=1 msgID=29 base="cn=testuser,ou=People,dc=jboss,dc=com" scope=wholeSubtree filter="(objectClass=*)" attrs="cn,sn,userPassword,givenName,displayName,o,employeeType,title,postalAddress,mail,telephoneNumber"
| [29/Jun/2009:11:19:54 -0700] SEARCH RES conn=179 op=1 msgID=29 result=0 nentries=1 etime=1
| [29/Jun/2009:11:19:54 -0700] UNBIND REQ conn=179 op=2 msgID=30
| [29/Jun/2009:11:19:54 -0700] DISCONNECT conn=179 reason="Client Unbind"
|
|
Am I making some mistake here? I am struck with this. I am not able to proceed further. Any pointers or help on this would be really great.
Thanks,
Ganesh.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240839#4240839
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240839
16 years, 9 months
[Management, JMX/JBoss] - HtmlAdaptorServer from JBoss 3.2.7 is not found in JBoss 5.1
by alskor
I need to migrate a Jboss 3.2.7 application to Jboss 5.1.0GA.
I see there's deploy\jmx-html-adaptor1.sar\META-INF\jboss-service.xml file in my old Jboss 3.2.7 install:
<server>
| <mbean code="com.sun.jdmk.comm.HtmlAdaptorServer" name="jboss.jmx:type=Adaptor,name=HTML">
| <attribute name="MaxActiveClientCount">10</attribute>
| <attribute name="Parser" />
| <attribute name="Port">49802</attribute>
| </mbean>
| </server>
|
I also have some java code to shutdown our server remotely using this connector on port 49802:
| public static void shutdown(String host, int port) {
| System.out.println("Shutting down server at " + host + ":" + port);
|
| try {
| URL url = new URL("http", host, port, COMMAND);
| url.getContent();
| } catch (Exception ignore) {
| System.err.println("ignoring " + ignore.toString());
| }
| System.out.println("Shutdown complete.");
| }
|
| private static final String COMMAND
| = "/InvokeAction//jboss%2Esystem%3Atype%3DServer/action=shutdown?action=shutdown";
|
I don't see "\jmx-html-adaptor1.sar" folder in new JB5 server. what's the equivalent of this stuff in jboss 5?
basically, I just need to shutdown the server remotely.
For this particular need I could use this solution from http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/In... :
9.3.4. Stopping the Server
|
| To shutdown the server, you simply issue a Ctrl-C sequence in the console in which JBoss was started. Alternatively, you can use the shutdown.sh command.
|
| [bin]$ ./shutdown.sh -S
|
| The shutdown script supports the following options:
|
| A JMX client to shutdown (exit or halt) a remote JBoss server.
|
| usage: shutdown [options] <operation>
|
| options:
| -h, --help Show this help message (default)
| -D<name>[=<value>] Set a system property
| -- Stop processing options
| -s, --server=<url> Specify the JNDI URL of the remote server
| -n, --serverName=<url> Specify the JMX name of the ServerImpl
| -a, --adapter=<name> Specify JNDI name of the MBeanServerConnection to use
| -u, --user=<name> Specify the username for authentication
| -p, --password=<name> Specify the password for authentication
|
| operations:
| -S, --shutdown Shutdown the server
| -e, --exit=<code> Force the VM to exit with a status code
| -H, --halt=<code> Force the VM to halt with a status code
|
but anyway - what happened to this deploy\jmx-html-adaptor1.sar service in JBoss 5.1.0? it existed in JBoss 3.2.7
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240836#4240836
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240836
16 years, 9 months
[JBoss jBPM] - do timers and multithreaded environment cause db deadlocking
by johndvm
I was wondering if there were any issues with using timers and multi-threaded execution.
I am using JBPM 3.2.6-SP1 and it seems like when I run two threads through my process workflow, I get a database deadlock.
It seems like 1 thread is holding open a transaction for the duration of the entire workflow, and has locked the JBPM_JOB table, and another thread starts and as it tries to transition between stages, it tries to delete from the JBPM_JOB table, and the entire thing gets deadlocked. It appears the problem is with trying to delete the timer at the same node.
org.jbpm.JbpmException: could not delete timers by name 'validate' for Token(/)
at org.jbpm.db.JobSession.deleteTimersByName(JobSession.java:216)
at org.jbpm.scheduler.db.DbSchedulerService.deleteTimersByName(DbSchedulerService.java:64)
at org.jbpm.scheduler.def.CancelTimerAction.execute(CancelTimerAction.java:46)
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:281)
Is this something that is known, or have other people been able to use JBPM with timers in a multi-threaded environment?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240829#4240829
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240829
16 years, 9 months