koala jbpm部署中的若干问题

jiangma 发布于 2014/01/25 09:27
阅读 599
收藏 0

MySQL连接为什么挂死了?别踩坑!>>>

下载了新的jbpm部署包,总共3个 core,desinger,oss。  其中core 在8180端口中运行正常,desinger也能登录(8080端口),编辑,保存流程。但是发布的时候(url为:http://localhost:8180/Koala-Core/ws/jbpmService?_wadl)回报错(问题1):

=============== session-admin-710

java.lang.RuntimeException: HTTP GET请求失败,URL为http://localhost:8080/drools-guvnor/rest/packages/defaultPackage/assets/defaultPackage.Trade-image/binary;返回状态码为:404
    at org.openkoala.koala.jbpm.jbpmDesigner.applicationImpl.GunvorApplicationImpl.getHttpGetRequestByteArrayResponse(GunvorApplicationImpl.java:312)
    at org.openkoala.koala.jbpm.jbpmDesigner.applicationImpl.GunvorApplicationImpl.getPng(GunvorApplicationImpl.java:298)
    at org.openkoala.koala.jbpm.jbpmDesigner.applicationImpl.GunvorApplicationImpl.publichJBPM(GunvorApplicationImpl.java:94)
    at org.openkoala.koala.jbpm.designer.jbpmDesigner.web.action.jbpm.JbpmAction.publish(JbpmAction.java:121)
    at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)

   

oss登录总是说用户名错误(admin/admin)。为什么呢?? 错误信息(问题2):

09:36:57,155 DEBUG [FilterChainProxy] Converted URL to lowercase, from: '/j_spring_security_check'; to: '/j_spring_security_check'
09:36:57,155 DEBUG [FilterChainProxy] Candidate is: '/j_spring_security_check'; pattern is /**; matched=true
09:36:57,155 DEBUG [FilterChainProxy] /j_spring_security_check at position 1 of 12 in additional filter chain; firing Filter: 'SecurityContextPersistenceFilter'
09:36:57,155 DEBUG [HttpSessionSecurityContextRepository] HttpSession returned null object for SPRING_SECURITY_CONTEXT
09:36:57,155 DEBUG [HttpSessionSecurityContextRepository] No SecurityContext was available from the HttpSession: org.eclipse.jetty.server.session.HashedSession:kvi7w0x7co9e1vqjyhkj6sh17@1600133090. A new one will be created.
09:36:57,155 DEBUG [FilterChainProxy] /j_spring_security_check at position 2 of 12 in additional filter chain; firing Filter: 'LogoutFilter'
09:36:57,155 DEBUG [FilterChainProxy] /j_spring_security_check at position 3 of 12 in additional filter chain; firing Filter: 'AuthenticationFilter'
09:36:57,155 DEBUG [AuthenticationFilter] Request is to process authentication
09:36:57,156 DEBUG [ProviderManager] Authentication attempt using org.openkoala.koala.auth.ss3adapter.provider.LoginAuthenticationProvider
09:36:57,156 DEBUG [DefaultListableBeanFactory] Returning cached instance of singleton bean 'transactionManager'
09:36:57,156 DEBUG [DefaultListableBeanFactory] Returning cached instance of singleton bean 'transactionManager_security'
09:36:57,156 DEBUG [DefaultListableBeanFactory] Returning cached instance of singleton bean 'transactionManager_gqc'
09:36:57,156 DEBUG [DefaultListableBeanFactory] Returning cached instance of singleton bean 'transactionManager_org'
09:36:57,156 DEBUG [JpaTransactionManager] Creating new transaction with name [org.openkoala.application.impl.UserApplicationImpl.findByUserAccount]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; 'transactionManager_security'
09:36:57,156 DEBUG [SessionImpl] Opened session at timestamp: 13906138171
09:36:57,156 DEBUG [JpaTransactionManager] Opened new EntityManager [org.hibernate.ejb.EntityManagerImpl@d8b6d3d] for JPA transaction
09:36:57,156 DEBUG [AbstractTransactionImpl] begin
09:36:57,156 DEBUG [LogicalConnectionImpl] Obtaining JDBC connection
09:36:57,158 DEBUG [LogicalConnectionImpl] Obtained JDBC connection
09:36:57,158 DEBUG [JdbcTransaction] initial autocommit status: true
09:36:57,158 DEBUG [JdbcTransaction] disabling autocommit
09:36:57,158 DEBUG [JpaTransactionManager] Exposing JPA transaction as JDBC transaction [org.springframework.orm.jpa.vendor.HibernateJpaDialect$HibernateConnectionHandle@2fc868cd]
09:36:57,159 DEBUG [SQL] select user0_.id as id0_, user0_.version as version0_, user0_.ABOLISH_DATE as ABOLISH4_0_, user0_.CREATE_DATE as CREATE5_0_, user0_.NAME as NAME0_, user0_.SERIAL_NUMBER as SERIAL7_0_, user0_.SORT_ORDER as SORT8_0_, user0_.CREATE_OWNER as CREATE9_0_, user0_.ISVALID as ISVALID0_, user0_.EMAIL as EMAIL0_, user0_.IS_SUPER as IS12_0_, user0_.LAST_LOGIN_TIME as LAST13_0_, user0_.LAST_MODIFY_TIME as LAST14_0_, user0_.USER_ACCOUNT as USER15_0_, user0_.USER_DESC as USER16_0_, user0_.USER_PASSWORD as USER17_0_ from KS_IDENTITY user0_ where user0_.IDENTITY_TYPE='User' and user0_.USER_ACCOUNT=? and user0_.ABOLISH_DATE>? limit ?
Hibernate: select user0_.id as id0_, user0_.version as version0_, user0_.ABOLISH_DATE as ABOLISH4_0_, user0_.CREATE_DATE as CREATE5_0_, user0_.NAME as NAME0_, user0_.SERIAL_NUMBER as SERIAL7_0_, user0_.SORT_ORDER as SORT8_0_, user0_.CREATE_OWNER as CREATE9_0_, user0_.ISVALID as ISVALID0_, user0_.EMAIL as EMAIL0_, user0_.IS_SUPER as IS12_0_, user0_.LAST_LOGIN_TIME as LAST13_0_, user0_.LAST_MODIFY_TIME as LAST14_0_, user0_.USER_ACCOUNT as USER15_0_, user0_.USER_DESC as USER16_0_, user0_.USER_PASSWORD as USER17_0_ from KS_IDENTITY user0_ where user0_.IDENTITY_TYPE='User' and user0_.USER_ACCOUNT=? and user0_.ABOLISH_DATE>? limit ?
09:36:57,160 DEBUG [StatefulPersistenceContext] Initializing non-lazy collections
09:36:57,161 DEBUG [JpaTransactionManager] Initiating transaction commit
09:36:57,161 DEBUG [JpaTransactionManager] Committing JPA transaction on EntityManager [org.hibernate.ejb.EntityManagerImpl@d8b6d3d]
09:36:57,161 DEBUG [AbstractTransactionImpl] committing
09:36:57,161 DEBUG [JdbcTransaction] committed JDBC Connection
09:36:57,161 DEBUG [JdbcTransaction] re-enabling autocommit
09:36:57,161 DEBUG [JpaTransactionManager] Closing JPA EntityManager [org.hibernate.ejb.EntityManagerImpl@d8b6d3d] after transaction
09:36:57,161 DEBUG [EntityManagerFactoryUtils] Closing JPA EntityManager
09:36:57,161 DEBUG [LogicalConnectionImpl] Releasing JDBC connection
09:36:57,161 DEBUG [LogicalConnectionImpl] Released JDBC connection
09:36:57,161 DEBUG [ConnectionProxyHandler] HHH000163: Logical connection releasing its physical connection
09:36:57,161 DEBUG [AuthenticationFilter] Authentication request failed: org.springframework.security.core.userdetails.UsernameNotFoundException: Username not found.
09:36:57,161 DEBUG [AuthenticationFilter] Updated SecurityContextHolder to contain null Authentication
09:36:57,161 DEBUG [AuthenticationFilter] Delegating to authentication failure handler org.openkoala.koala.auth.ss3adapter.LoginFailureHandler@b607217
09:36:57,161 DEBUG [DispatcherServlet] DispatcherServlet with name 'spring' processing POST request for [/login.koala]
09:36:57,162 DEBUG [RequestMappingHandlerMapping] Looking up handler method for path /login.koala
09:36:57,165 DEBUG [RequestMappingHandlerMapping] Returning handler method [public java.lang.String org.openkoala.bpm.KoalaBPM.web.controller.auth.BaseController.login()]
09:36:57,165 DEBUG [DefaultListableBeanFactory] Returning cached instance of singleton bean 'baseController'
09:36:57,165 DEBUG [DispatcherServlet] Rendering view [org.springframework.web.servlet.view.JstlView: name 'login'; URL [/pages/login.jsp]] in DispatcherServlet with name 'spring'
09:36:57,166 DEBUG [JstlView] Forwarding to resource [/pages/login.jsp] in InternalResourceView 'login'
09:36:57,167 DEBUG [HttpSessionSecurityContextRepository] SecurityContext is empty or anonymous - context will not be stored in HttpSession.
09:36:57,167 DEBUG [DispatcherServlet] Successfully completed request
09:36:57,167 DEBUG [HttpSessionSecurityContextRepository] SecurityContext is empty or anonymous - context will not be stored in HttpSession.




问题3:下载的最新包防盗jboss下面发布并不成功,启动jboss没反应。 我是从 源码重新构建的。。


问题4:请问koala发布的drools-guvnor和designer和官方(jboss drools)的drools-guvnor 和 designer有什么区别,是否加了自己应用代码或配置。  因为koala发布的drools-guvnor和designer这两个war包不能在jboss7下部署。如果有所改动原版的drools-guvnor和designer能否提供下这两个包的修改后的源码,以便我可以从源码重新打包发布到jboss下面。

加载中
0
j
jiangma

已找到部分答案:

1:java.lang.RuntimeException: HTTP GET请求失败,URL为http://localhost:8080/drools-guvnor/rest/packages /defaultPackage/assets/defaultPackage.Trade-image/binary;返回状态码为:404

这是因为没有生成defaultPackage包下面的Trade流程生成png图片

2 OSS登录失败时因为security模块的版本问题引起。 目前我就直接在源代码中让admin输入任何一个密码都可以登录。 我的项目得改成mybatis的 所以权限数据库等这些我得好好研究。

写完流程,要点击png生成图片 否则后面404
如果从其他地发导入流程则packagename is not valid。 因为你自己写的包名和xml或json中也带有的包名不一致。改成一致的(两处:注1,注2)
Steps to Reproduce:
1. Create new package "pkg1"
2. Create new BPMN2 process in package "pkg1"
3. Import BPMN2 process into asset. It is attached.
4. Click on view PNG
5. Validate
可发布的流程在资产中显示为一个绿色的对号
注1 jbpm2
<bpmn2:process id="aaa.jiandan" drools:packageName="aaa" name="jiandan" isExecutable="true"> 
注2 json:
{"executable":true,"package":"aaa","vardefs":"","adhocprocess":"false","imports":"","globals":"","id":"aaa.jiandan","version":"","timeunit":"s","currency":"","targetnamespace":"http://

aaa为包名,jiandan为流程名称

 


3但是我又遇到一个问题是:发布完了流程,但是oss模块中新建表单,关联流程中是空的,不知道怎么回事。 在designer中发布成功,在oss中没反应

在koala-designer中流程引擎中新建流程引擎,名称fff,url为:http://localhost:8180/Koala-Core/ws/jbpmService?_wadl 保存。

流程管理中新建流程保存流程,发布(到fff),成功之后,在流程引擎管理中的fff浏览中说没有数据。

0
j
jiangma
上面第三个问题也找到了,是我自己把源码该了,可以发布,发起流程了。。。。。。。
返回顶部
顶部