[JBoss Tools] - Re: How to setup JBoss EAP 6 in Eclipse Indigo
by henk de boer
henk de boer [https://community.jboss.org/people/henk53] created the discussion
"Re: How to setup JBoss EAP 6 in Eclipse Indigo"
To view the discussion, visit: https://community.jboss.org/message/819549#819549
--------------------------------------------------------------
> ulrichromahn wrote:
>
> Daniel,
>
> good for you.
>
> But wouldn't it be great if you could share with us how exactly you did it? :)
> Apparently, this is not trivial to do.
Well, it is absolutely trivial: install Eclipse 4.2 Java EE. Install JBoss Tools from Marketplace (you'll automatically get 4.0.1). Then from servers select JBoss Enterprise Application Platform 6.1 (Tech Preview), and in the new server dialog point it to the directory where you unzipped JBoss EAP 6.1.
It's a shame that 6.1 is only supported for Eclipse 4.2. Why does JBoss change so much between JBoss EAP versions that (appearently) such dramatic changes are needed to the WTP runtime?
Note that JBoss EAP 6.1 is also the default that you get at OpenShift. Everyone got automatically upgraded to it when it was released last week, so OpenShift users don't have a choice. They can't stay at 6.0.1.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/819549#819549]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months
[jBPM] - JBPM + LDAP - can login, but HumanTask error appears in the jboss log
by aemdtuc
aemdtuc [https://community.jboss.org/people/aemdtuc] created the discussion
"JBPM + LDAP - can login, but HumanTask error appears in the jboss log"
To view the discussion, visit: https://community.jboss.org/message/819124#819124
--------------------------------------------------------------
Hi.
I've setup the jbpm-installer to work with LDAP, and I could manage to authenticate and get the roles. I can perfectly walk through the jBPM-Console. But looking at JBoss log, I see an error that I think that comes from the Human Task.
Here is how I configured the LDAP:
Jboss standalone.xml
<authentication>
<login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required">
<module-option name="bindDN" value="LDAP_USER_DN"/>
<module-option name="bindCredential" value="LDAP_USER_PASSWD "/>
<module-option name="baseCtxDN" value=""/>
<module-option name="baseFilter" value="(&(objectClass=user)(userPrincipalName={0}))"/>
<module-option name="rolesCtxDN" value=""/>
<module-option name="roleFilter" value="(&(objectClass=group)(member:1.2.840.113556.1.4.1941:={1}))"/>
<module-option name="roleAttributeID" value="cn"/>
<module-option name="java.naming.provider.url" value="ldap://domain:port"/>
<module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/>
<module-option name="allowEmptyPasswords" value="true"/>
<module-option name="throwValidateError" value="true"/>
</login-module>
</authentication>
jbpm-gwt-console-server.war web.xml
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/login.html</form-login-page>
<form-error-page>/login_failed.html</form-error-page>
</form-login-config>
</login-config>
<security-role>
<role-name>Write</role-name>
</security-role>
<security-role>
<role-name>Read</role-name>
</security-role>
jbpm-human-task-war.war jbpm.usergroup.callback.properties
ldap.bind.user=CN\=User,OU\=Users,OU\=Company Users,OU\=Company,DC\=company-1234,DC\=com
ldap.bind.pwd=Passwd
ldap.user.ctx=
ldap.role.ctx=
#ldap.user.roles.ctx=ou\=Roles,dc\=my-domain,dc\=com
ldap.user.filter=(&(objectClass=user)(userPrincipalName\={0}))
ldap.role.filter=
ldap.user.roles.filter=(&(objectClass=group)(member:1.2.840.113556.1.4.1941:\={0}))
#ldap.user.attr.id=
#ldap.roles.attr.id=
java.naming.provider.url=ldap://domain:port
jbpm-human-task-war.war web.xml
<init-param>
<param-name>user.group.callback.class</param-name> <param-value>org.jbpm.task.identity.LDAPUserGroupCallbackImpl</param-value> </init-param>
The jbpm.usergroup.callback.properties is located under jbpm-human-task-war.war/WEB-INF/classes.
The error message is the following:
ERROR [stderr] (Thread-68) javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name ''
ERROR [stderr] (Thread-68) at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
ERROR [stderr] (Thread-68) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
ERROR [stderr] (Thread-68) at javax.naming.directory.InitialDirContext.search(Unknown Source)
ERROR [stderr] (Thread-68) at org.jbpm.task.identity.LDAPUserGroupCallbackImpl.existsUser(LDAPUserGroupCallbackImpl.java:128)
ERROR [stderr] (Thread-68) at org.jbpm.task.service.TaskServiceSession.doCallbackUserOperation(TaskServiceSession.java:1225)
ERROR [stderr] (Thread-68) at org.jbpm.task.service.TaskServiceSession.getTasksOwned(TaskServiceSession.java:763)
ERROR [stderr] (Thread-68) at org.jbpm.task.service.TaskServerHandler.messageReceived(TaskServerHandler.java:309)
ERROR [stderr] (Thread-68) at org.jbpm.task.service.hornetq.HornetQTaskServerHandler.messageReceived(HornetQTaskServerHandler.java:43)
ERROR [stderr] (Thread-68) at org.jbpm.task.service.hornetq.BaseHornetQTaskServer.run(BaseHornetQTaskServer.java:104)
ERROR [stderr] (Thread-68) at java.lang.Thread.run(Unknown Source)
As you can see in the error message, when trying to create the LDAP context, it doesn't bind a user and password. So when it tries to make the search it fails.
I'm not sure if it doesn't bind correctly because my properties file is wrong, or because the human task has a bug.
Any help I'll appreciate.
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/819124#819124]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months
[JBoss Web Services] - Performance Issues with ?wsdl
by spyhunter99
spyhunter99 [https://community.jboss.org/people/spyhunter99] created the discussion
"Performance Issues with ?wsdl"
To view the discussion, visit: https://community.jboss.org/message/758131#758131
--------------------------------------------------------------
Jboss 5.1.0GA, JbossWS native 3.4.0
also present in Jboss 5.1.2 eap with JbossWS native 3.1.2sp13
I've been noticing that each time something requests the wsdl from my web service endpoint, there is a huge spike in CPU usage on the server. Upon further investigation, I checked out the class definition for the service
@WebService(serviceName="service1", name="service1", targetNamespace="urn:service1")
public class Service1Impl
{
//stuff
}
and then compared the wsdl presented by Jbossws with the one I had started with (top down) and they were different so I'm assuming that in this case, JbossWS generates a wsdl on the fly using reflection. The problem is that this is on every request. This probably should be cached somehow.
Continuing the investigation, I tried adding the wsdlLocation parameter to the class and deployed.
@WebService(serviceName="service1", name="service1", targetNamespace="urn:service1", wsdlLocation="WEB-INF/wsdl/my.wsdl")
public class Service1Impl
{
//stuff
}
The ?wsdl url now returns the same wsdl that I had created from the top down approach, which is good, however I'm still getting a significant delay when loading the ?wsdl endpoint and high CPU usage when pressing refresh a bunch of times. I'm not sure what's happening, but there should be no to little delay for this after the first time the wsdl is presented. It seems clear that there is no caching mechanism.
Question 1: how can I reduce the CPU usage and delay for returning the service?wsdl endpoint?
Question 2: is there a way to disable the auto generation of ?wsdl url and replace it with something else?
Question 3: is there any kind of cache mechanism that exists to resolve this?
Question 4: does the cxf stack provide any way to resolve this?
A few notes: all supporting files (i.e. imports) MUST be in WEB-INF/wsdl), if placed anywhere else, deployment tends to fail. My web service is actually a seperate jar bundled within a WAR file and thus the wsdl/xsd files must bein the WAR's WEB-INF/wsdl folder.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/758131#758131]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months