Menu
▾
▴
signserver-develop
You can subscribe to this list here.
| 2008 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2012 |
Jan
(1) |
Feb
(8) |
Mar
(10) |
Apr
|
May
(12) |
Jun
(2) |
Jul
(28) |
Aug
(15) |
Sep
(12) |
Oct
(2) |
Nov
|
Dec
(16) |
| 2013 |
Jan
(30) |
Feb
(1) |
Mar
|
Apr
(11) |
May
(2) |
Jun
(11) |
Jul
(15) |
Aug
(4) |
Sep
(1) |
Oct
(10) |
Nov
(1) |
Dec
(2) |
| 2014 |
Jan
(8) |
Feb
(13) |
Mar
(12) |
Apr
(24) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
|
Apr
|
May
(7) |
Jun
(7) |
Jul
(3) |
Aug
(5) |
Sep
(1) |
Oct
(8) |
Nov
(6) |
Dec
|
| 2016 |
Jan
|
Feb
(3) |
Mar
(5) |
Apr
(9) |
May
(26) |
Jun
(8) |
Jul
|
Aug
|
Sep
(11) |
Oct
(8) |
Nov
(1) |
Dec
(2) |
| 2017 |
Jan
(4) |
Feb
(7) |
Mar
(7) |
Apr
(4) |
May
(1) |
Jun
(5) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2018 |
Jan
(4) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2020 |
Jan
(3) |
Feb
|
Mar
(2) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Markus K. <ma...@pr...> - 2016-06-20 12:07:01
|
On 06/20/2016 03:51 AM, Tung, Tran wrote: >> On Jun 19, 2016, at 4:33 PM, Markus Kilås <ma...@pr... >> <mailto:ma...@pr...>> wrote: >> >> On 06/16/2016 09:28 AM, Tung, Tran wrote: >>> Dear Marcus, >>> Please see the attached image. It show that the server is nearly 100% >>> CPU usage when i load testing xml validator function >>> >> >> Hi Tung, >> >> What configuration are you using for your validators? >> Can you send your worker's configuration after dumping it from SignServer: >> $ bin/signserver dumpproperties all workers-configuration.properties >> >> Remember to remove any passwords (if any) before sending it to the >> mailing list. >> >> >> Regards, >> Markus >> PrimeKey Solutions AB >> >> Save time and money with an Enterprise support subscription. Please see >> www.primekey.se <http://www.primekey.se> for more information. >> https://www.primekey.se/technologies/products-overview/ >> https://www.primekey.se/service-support/support/ >> >> > > > Dear Markus, > Please find the attachment below. > Please note that: com.stb.signserver.CertificateValidator plugin just > return true for testing. > > Regards, > Tung > Hi Tung, I was finally able to reproduce the issue. This will be fixed in 3.7.4. Regards, Markus PrimeKey Solutions AB PrimeKey Solutions offers a commercial EJBCA & SignServer support subscription and training. Please see www.primekey.se or contact in...@pr... for more information. https://www.primekey.se/Services/Support/ https://www.primekey.se/Services/Training/ |
|
From: Tung, T. <tu...@sa...> - 2016-06-20 02:11:48
|
Dear Markus, Please find the attachment below. Please note that: com.stb.signserver.CertificateValidator plugin just return true for testing. Regards, Tung On Jun 19, 2016, at 4:33 PM, Markus Kilås <ma...@pr...<mailto:ma...@pr...>> wrote: On 06/16/2016 09:28 AM, Tung, Tran wrote: Dear Marcus, Please see the attached image. It show that the server is nearly 100% CPU usage when i load testing xml validator function Hi Tung, What configuration are you using for your validators? Can you send your worker's configuration after dumping it from SignServer: $ bin/signserver dumpproperties all workers-configuration.properties Remember to remove any passwords (if any) before sending it to the mailing list. Regards, Markus PrimeKey Solutions AB Save time and money with an Enterprise support subscription. Please see www.primekey.se<http://www.primekey.se> for more information. https://www.primekey.se/technologies/products-overview/ https://www.primekey.se/service-support/support/ Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. |
|
From: Markus K. <ma...@pr...> - 2016-06-19 09:33:53
|
On 06/16/2016 09:28 AM, Tung, Tran wrote: > Dear Marcus, > Please see the attached image. It show that the server is nearly 100% > CPU usage when i load testing xml validator function > Hi Tung, What configuration are you using for your validators? Can you send your worker's configuration after dumping it from SignServer: $ bin/signserver dumpproperties all workers-configuration.properties Remember to remove any passwords (if any) before sending it to the mailing list. Regards, Markus PrimeKey Solutions AB Save time and money with an Enterprise support subscription. Please see www.primekey.se for more information. https://www.primekey.se/technologies/products-overview/ https://www.primekey.se/service-support/support/ |
|
From: Tung, T. <tu...@sa...> - 2016-06-16 07:29:31
|
Dear Marcus, Please see the attached image. It show that the server is nearly 100% CPU usage when i load testing xml validator function [cid:191...@sa...] On Jun 15, 2016, at 2:33 PM, Tung, Tran <tu...@sa...<mailto:tu...@sa...>> wrote: Dear Marcus. I loadtest the xmvalidator plugin( not pdf signer plugin). Regards, Tung On Jun 15, 2016, at 1:17 PM, Marcus Lundblad <mar...@pr...<mailto:mar...@pr...>> wrote: ons 2016-06-15 klockan 04:12 +0000 skrev Tung, Tran: Dear support, I try to loadtest the signserver-ce-3.7.0 with hp loadrunner tool but it hang when loadtest tool post about 100 transaction with 2 concurrent users . /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/log/server.log.2016-06-09 Hi Tung! Are you using a PDF signer configured to include a timestamp in signed documents when getting this error? There have been issues with deadlocks in these situations. Since SignServer 3.5.2 there is an option to use an "internal" timestamping signer, by specifying a worker name of the timestamp signer instead of specifying it using the full URL. What this does is that it bypasses doing remote HTTP calls (which could result in the servlet connection pool being exhausted) and instead calls the timestamp signer internally using EJB calls. This would be configured something like: TSA_WORKER=TimeStampSigner or alternatively using the worker ID. You must also remove the TSA_URL property (as both these can not be set at the same time for one worker). Regards, Marcus 11:42:07,589 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/signserver].[GenericProcessServlet]] (http-/0.0.0.0:8443-37) JBWEB000236: Servlet.service() for servlet GenericProcessServlet threw exception: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:114) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:94) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.signserver.ejb.interfaces.IWorkerSession$ILocal$$$view13.process(Unknown Source) at org.signserver.web.GenericProcessServlet.processRequest(GenericProcessServlet.java:510) [classes:] at org.signserver.web.GenericProcessServlet.doPost(GenericProcessServlet.java:374) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: javax.transaction.RollbackException: ARJUNA016102: The transaction is not active! Uid is 0:ffff7f000001:4c6bf59a:5758f0f0:472a at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1155) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] ... 43 more Please support. Tung Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa...<mailto:as...@sa...> hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa...<mailto:as...@sa...> or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ SignServer-develop mailing list Sig...@li...<mailto:Sig...@li...> https://lists.sourceforge.net/lists/listinfo/signserver-develop Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. |
|
From: Tung, T. <tu...@sa...> - 2016-06-15 08:05:28
|
Dear Marcus. I loadtest the xmvalidator plugin( not pdf signer plugin). Regards, Tung On Jun 15, 2016, at 1:17 PM, Marcus Lundblad <mar...@pr...<mailto:mar...@pr...>> wrote: ons 2016-06-15 klockan 04:12 +0000 skrev Tung, Tran: Dear support, I try to loadtest the signserver-ce-3.7.0 with hp loadrunner tool but it hang when loadtest tool post about 100 transaction with 2 concurrent users . /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/log/server.log.2016-06-09 Hi Tung! Are you using a PDF signer configured to include a timestamp in signed documents when getting this error? There have been issues with deadlocks in these situations. Since SignServer 3.5.2 there is an option to use an "internal" timestamping signer, by specifying a worker name of the timestamp signer instead of specifying it using the full URL. What this does is that it bypasses doing remote HTTP calls (which could result in the servlet connection pool being exhausted) and instead calls the timestamp signer internally using EJB calls. This would be configured something like: TSA_WORKER=TimeStampSigner or alternatively using the worker ID. You must also remove the TSA_URL property (as both these can not be set at the same time for one worker). Regards, Marcus 11:42:07,589 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/signserver].[GenericProcessServlet]] (http-/0.0.0.0:8443-37) JBWEB000236: Servlet.service() for servlet GenericProcessServlet threw exception: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:114) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:94) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.signserver.ejb.interfaces.IWorkerSession$ILocal$$$view13.process(Unknown Source) at org.signserver.web.GenericProcessServlet.processRequest(GenericProcessServlet.java:510) [classes:] at org.signserver.web.GenericProcessServlet.doPost(GenericProcessServlet.java:374) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: javax.transaction.RollbackException: ARJUNA016102: The transaction is not active! Uid is 0:ffff7f000001:4c6bf59a:5758f0f0:472a at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1155) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] ... 43 more Please support. Tung Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa...<mailto:as...@sa...> hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa...<mailto:as...@sa...> or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ SignServer-develop mailing list Sig...@li...<mailto:Sig...@li...> https://lists.sourceforge.net/lists/listinfo/signserver-develop Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. |
|
From: Marcus L. <mar...@pr...> - 2016-06-15 06:18:08
|
ons 2016-06-15 klockan 04:12 +0000 skrev Tung, Tran: > Dear support, > I try to loadtest the signserver-ce-3.7.0 with hp loadrunner tool > but it hang when loadtest tool post about 100 transaction with 2 > concurrent users . > /home/signserver/jboss-eap-6.1.0/jboss-eap- > 6.1/standalone/log/server.log.2016-06-09 > > > > Hi Tung! Are you using a PDF signer configured to include a timestamp in signed documents when getting this error? There have been issues with deadlocks in these situations. Since SignServer 3.5.2 there is an option to use an "internal" timestamping signer, by specifying a worker name of the timestamp signer instead of specifying it using the full URL. What this does is that it bypasses doing remote HTTP calls (which could result in the servlet connection pool being exhausted) and instead calls the timestamp signer internally using EJB calls. This would be configured something like: TSA_WORKER=TimeStampSigner or alternatively using the worker ID. You must also remove the TSA_URL property (as both these can not be set at the same time for one worker). Regards, Marcus > > > > > > > 11:42:07,589 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/signserver].[GenericProcessServlet]] (http-/0.0.0.0:8443-37) JBWEB000236: Servlet.service() for servlet GenericProcessServlet threw exception: javax.ejb.EJBTransactionRolledbackException: > Transaction rolled back > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:114) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:94) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.signserver.ejb.interfaces.IWorkerSession$ILocal$$$view13.process(Unknown Source) > > at org.signserver.web.GenericProcessServlet.processRequest(GenericProcessServlet.java:510) [classes:] > > at org.signserver.web.GenericProcessServlet.doPost(GenericProcessServlet.java:374) [classes:] > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > > at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] > > Caused by: javax.transaction.RollbackException: ARJUNA016102: The transaction is not active! Uid is 0:ffff7f000001:4c6bf59a:5758f0f0:472a > > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1155) > > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > > ... 43 more > > > > > > > > > Please support. > > Tung > > > > > Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được > chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo > ngay cho Sacombank theo email > as...@sa...> hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được > chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. > Xin vui lòng xem > xét đến việc bảo vệ môi trường trước khi in. > > This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee > you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to > > as...@sa...> or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability > in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. > Please consider the environment > before printing this email. > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 > _______________________________________________ > SignServer-develop mailing list > Sig...@li...> https://lists.sourceforge.net/lists/listinfo/signserver-develop> |
|
From: Tung, T. <tu...@sa...> - 2016-06-15 04:13:34
|
Dear support, I try to loadtest the signserver-ce-3.7.0 with hp loadrunner tool but it hang when loadtest tool post about 100 transaction with 2 concurrent users . /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/log/server.log.2016-06-09 11:42:07,589 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/signserver].[GenericProcessServlet]] (http-/0.0.0.0:8443-37) JBWEB000236: Servlet.service() for servlet GenericProcessServlet threw exception: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:114) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:94) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.signserver.ejb.interfaces.IWorkerSession$ILocal$$$view13.process(Unknown Source) at org.signserver.web.GenericProcessServlet.processRequest(GenericProcessServlet.java:510) [classes:] at org.signserver.web.GenericProcessServlet.doPost(GenericProcessServlet.java:374) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: javax.transaction.RollbackException: ARJUNA016102: The transaction is not active! Uid is 0:ffff7f000001:4c6bf59a:5758f0f0:472a at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1155) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] ... 43 more Please support. Tung Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. |
|
From: Markus K. <ma...@pr...> - 2016-05-25 10:45:45
|
On 05/25/2016 12:15 PM, Pedro Luis Romaña Villar wrote: > It works fine but opening the result .p7s file with P7S Viewer, it > indicates that "Signature is not timestamped". > Is there any way to solve this issue? Is there any way to configure > CMSSigner with long term signature? Hello Pedro, Time-stamping has not been implemented in the CMS signer. But adding support for it should not be that much of work. The effort would maybe be in the order of 1-2 days for us. Best regards, Markus PrimeKey Solutions AB Save time and money with an Enterprise support subscription. Please see www.primekey.se for more information. https://www.primekey.se/technologies/products-overview/ https://www.primekey.se/service-support/support/ |
|
From: Pedro L. R. V. <pr...@ne...> - 2016-05-25 10:15:33
|
Hello, we are testing CMS signer, we have configures a cryptoworker with a jks keystore and one autogenerated certificate (with keytool). We have also configured the CMSWorker and tested via demo web page. It works fine but opening the result .p7s file with P7S Viewer, it indicates that "Signature is not timestamped". Is there any way to solve this issue? Is there any way to configure CMSSigner with long term signature? Thank you in advance. [cid:352100310@25052016-33CF] ________________________________ Pedro Luis Romaña Villar Área I+D+i pr...@ne... Oficina Bilbao [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png] |
|
From: Markus K. <ma...@pr...> - 2016-05-24 13:16:28
|
On 05/23/2016 11:50 AM, Tung, Tran wrote:
>
> Please find the attachment for standalone.xml.
I couldn't find any obvious issue with your datasources section. My is
just slightly different. I post it here also for reference:
--- from standalone.xml ---
<datasource jndi-name="java:/SignServerOracleDS"
pool-name="signserveroracleds" enabled="true">
<connection-url>jdbc:oracle:thin:@192.168.123.123:1555:XE</connection-url>
<driver>com.oracle</driver>
<pool>
<min-pool-size>3</min-pool-size>
<max-pool-size>5</max-pool-size>
</pool>
<security>
<user-name>signserver_trunk_eap6</user-name>
<password>signserver</password>
</security>
<validation>
<exception-sorter
class-name="org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter"/>
</validation>
<timeout>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>5</idle-timeout-minutes>
</timeout>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="com.mysql.jdbc.Driver" module="com.mysql">
<xa-datasource-class>com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
</driver>
<driver name="org.mariadb.jdbc.Driver" module="org.mariadb">
<xa-datasource-class>org.mariadb.jdbc.MySQLDataSource</xa-datasource-class>
</driver>
<driver name="com.oracle" module="com.oracle">
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
</driver>
</drivers>
---
Regards,
Markus
PrimeKey Solutions AB
|
|
From: Markus K. <ma...@pr...> - 2016-05-24 13:06:44
|
On 05/23/2016 11:50 AM, Tung, Tran wrote: > > How to turn on SQL logging ? One way could be to edit the persistence.xml and make sure both persistence-units has the following property and value: <property name="hibernate.show_sql" value="true"/> A quick way of making this change is to edit lib/SignServer-Entities-x.y.z.jar which has the persistence.xml under /META-INF/. Note: that this change will be removed in case you rebuild SignServer. After changing this file you need to deploy again: $ bin/signserver deploy Then when running you should see outputs like this for each SQL query it tries to perform: 14:59:08,829 INFO [stdout] (ServerService Thread Pool -- 88) Hibernate: select max(auditrecor0_.sequenceNumber) as col_0_0_ from AuditRecordData auditrecor0_ where auditrecor0_.nodeId=? Regards, Markus PrimeKey Solutions AB |
|
From: Tung, T. <tu...@sa...> - 2016-05-23 09:51:54
|
Hi Markus, How to turn on SQL logging ? Please find the attachment for standalone.xml. Thanks, Tung > On May 23, 2016, at 4:37 PM, Markus Kilås <ma...@pr...> wrote: > > Hi Tung, > > On 05/23/2016 04:20 AM, Tung, Tran wrote: >> java.sql.SQLSyntaxErrorException: ORA-00911: invalid character > > Its hard to tell from the log output why you get this one and from where > it comes. > Turning on SQL logging could maybe give a clue about what Oracle is > complaining about. > > How does your datasource configuration for SignServerDS looks like in > /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/config/standalone.xml > ? > > > Regards, > Markus > PrimeKey Solutions AB > > Save time and money with an Enterprise support subscription. Please see > www.primekey.se<http://www.primekey.se> for more information. > https://www.primekey.se/technologies/products-overview/ > https://www.primekey.se/service-support/support/ > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > _______________________________________________ > SignServer-develop mailing list > Sig...@li... > https://lists.sourceforge.net/lists/listinfo/signserver-develop Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in. This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email. |
|
From: Markus K. <ma...@pr...> - 2016-05-23 09:38:00
|
Hi Tung, On 05/23/2016 04:20 AM, Tung, Tran wrote: > java.sql.SQLSyntaxErrorException: ORA-00911: invalid character Its hard to tell from the log output why you get this one and from where it comes. Turning on SQL logging could maybe give a clue about what Oracle is complaining about. How does your datasource configuration for SignServerDS looks like in /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/config/standalone.xml ? Regards, Markus PrimeKey Solutions AB Save time and money with an Enterprise support subscription. Please see www.primekey.se for more information. https://www.primekey.se/technologies/products-overview/ https://www.primekey.se/service-support/support/ |
|
From: Tung, T. <tu...@sa...> - 2016-05-23 02:52:56
|
Hello.
I try to install signserver-ce-3.7.0 with oracle database. Here are deployment configuration:
[echo] Edition: CE
[echo]
[echo] ------------- SYSTEM PROPERTIES --------------
[echo] Ant version = Apache Ant(TM) version 1.9.7 compiled on April 9 2016
[echo] JRE version = 1.6.0_24
[echo] JRE vendor = Sun Microsystems Inc.
[echo] Java home = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
[echo] Java extensions dir = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
[echo] OS name = Linux
[echo] OS architecture = amd64
[echo] OS version = 2.6.32-279.el6.x86_64
[echo]
[echo] ------------- DEPLOY PROPERTIES --------------
[echo] app.version = SignServer CE 3.7.0
[echo] deploytools.version = 1.1.2
[echo] appserver.type = jboss
[echo] appserver.subtype = jbosseap6
[echo] appserver.home = /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1
[echo] datasource.jndi-name = SignServerDS
[echo] datasource.jndi-name-prefix = java:/
[echo] database.name = oracle
[echo] database.driver = oracle.jdbc.OracleDriver
[echo] database.nodb.location =
[echo]
[echo] Configuring EAR...
[echo]
[echo] Database type: oracle
[echo] DataSource mapping: java:/SignServerDS
[echo]
[dmdt] Module signservercommon: enabled
[dmdt] Module signserverejb: enabled
[dmdt] Module module.cesecore: enabled
[dmdt] Module adminws: enabled
[dmdt] Module clientws: enabled
[dmdt] Module signserverws: enabled
[dmdt] Module validationws: enabled
[dmdt] Module healthcheck: enabled
[dmdt] Module module.log4j: enabled
[dmdt] Module signserverweb: enabled
[dmdt] Module webdoc: enabled
[dmdt] Module module.cmssigner: enabled
[dmdt] Module module.mrtdsigner: enabled
[dmdt] Module module.mrtdsodsigner: enabled
[dmdt] Module module.odfsigner: enabled
[dmdt] Module module.ooxmlsigner: enabled
[dmdt] Module module.pdfsigner: enabled
[dmdt] Module module.renewal: enabled
[dmdt] Module module.signerstatusreport: enabled
[dmdt] Module module.statusproperties: enabled
[dmdt] Module module.tsa: enabled
[dmdt] Module module.xades: enabled
[dmdt] Module module.xmlsigner: enabled
[dmdt] Module module.xmlvalidator: enabled
[echo]
[echo] Post processing files...
[ppmt] Post processing module: signservercommon
[ppmt] Post processing module: signserverejb
[ppmt] Post processing module: signserverws
[ppmt] Post processing module: validationws
[ppmt] Post processing module: healthcheck
[echo]
[echo] Filtering jars...
[echo]
[echo] Configured EAR file available at: /home/signserver/signserver-ce-3.7.0/signserver-ce-3.7.0/tmp/signserver.ear
[echo]
[echo] Deploying /home/signserver/signserver-ce-3.7.0/signserver-ce-3.7.0/tmp/signserver.ear to /home/signserver/jboss-eap-6.1.0/jboss-eap-6.1/standalone/deployments
[echo]
[echo] Task completed 2016-05-20 15:08:03 +0700.
But when jboss is stared, The error happen. Here are exception
14:42:53,751 WARN [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (ServerService Thread Pool -- 54) IJ000305: Connection error occured: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@115e01c2[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@4eccf230 connection handles=0 lastUse=1463730173219 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@3152cf21 pool internal context=SemaphoreArrayListManagedConnectionPool@339c98d3[pool=signserverds] xaResource=LocalXAResourceImpl@32c57076[connectionListener=115e01c2 connectionManager=ea6ad47 warned=false currentXid=null productName=Oracle productVersion=Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options jndiName=java:/SignServerDS] txSync=null]: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:876)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1175)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1296)
at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1916)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1878)
at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
at org.jboss.jca.adapters.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:74)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1097)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:512)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:464)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:283)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getTransactionNewConnection(AbstractPool.java:495)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:374)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:70) [hibernate-entitymanager-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:292) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:214) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:157) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.connection(StatementPreparerImpl.java:56) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$1.doPrepare(StatementPreparerImpl.java:98) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:182) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:91) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl.buildBatchStatement(AbstractBatchImpl.java:138) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl.getBatchStatement(AbstractBatchImpl.java:127) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3036) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3499) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:88) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:362) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:354) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:275) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:328) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:52) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1233) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:403) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion(SynchronizationCallbackCoordinatorImpl.java:112) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization.beforeCompletion(RegisteredSynchronization.java:53) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:273)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:93)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:339) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:216) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal$$$view21.log(Unknown Source) [cesecore-interfaces-6.1.1.jar:]
at org.cesecore.audit.impl.integrityprotected.IntegrityProtectedDevice.log(IntegrityProtectedDevice.java:105) [cesecore-interfaces-6.1.1.jar:]
at org.cesecore.audit.log.InternalSecurityEventsLoggerSessionBean.log(InternalSecurityEventsLoggerSessionBean.java:71) [cesecore-ejb-6.1.1.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_24]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:226) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:376) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:218) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal$$$view22.log(Unknown Source) [cesecore-interfaces-6.1.1.jar:]
at org.cesecore.audit.log.SecurityEventsLoggerSessionBean.log(SecurityEventsLoggerSessionBean.java:93) [cesecore-ejb-6.1.1.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_24]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:226) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:376) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:218) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.cesecore.audit.log.SecurityEventsLoggerSessionLocal$$$view7.log(Unknown Source) [cesecore-interfaces-6.1.1.jar:]
at org.signserver.statusrepo.impl.StatusRepositorySessionBean.auditLog(StatusRepositorySessionBean.java:198) [SignServer-ejb.jar:]
at org.signserver.statusrepo.impl.StatusRepositorySessionBean.update(StatusRepositorySessionBean.java:129) [SignServer-ejb.jar:]
at org.signserver.statusrepo.impl.StatusRepositorySessionBean.update(StatusRepositorySessionBean.java:102) [SignServer-ejb.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_24]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.signserver.statusrepo.IStatusRepositorySession$ILocal$$$view32.update(Unknown Source) [SignServer-ejb-interfaces.jar:]
at org.signserver.web.StartServicesServlet.init(StartServicesServlet.java:161)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798)
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156)
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.6.0_24]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Please help!
Thanks,
Tung
Email này và những tài liệu đính kèm theo email là bảo mật và chỉ dành cho những cá nhân hoặc tổ chức được chỉ định nhận email. Nếu bạn không thuộc những người được chỉ định nhận email này, bạn vui lòng không sao chép, chuyển tiếp, tiết lộ thông tin hoặc sử dụng bất kỳ nội dung nào của email. Nếu bạn nhận được email này do lỗi của hệ thống, vui lòng xóa email này và tất cả các bản lưu khỏi hệ thống của bạn và thông báo ngay cho Sacombank theo email as...@sa... hoặc theo số điện thoại 1900 5555 88. Sacombank nghiêm cấm bất kỳ việc tiết lộ, sao chép, chuyển tiếp hoặc các hành động khác liên quan đến nội dung email này, trừ khi bạn là đối tượng được chỉ định nhận email. Chúng tôi không chịu trách nhiệm về vi rút máy tính, sai lạc dữ liệu, các trở ngại hoặc cản trở phát sinh từ hoặc liên quan đến email này. Xin vui lòng xem xét đến việc bảo vệ môi trường trước khi in.
This email and any attachments to it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the addressee you should not copy, forward, disclose the whole email or any part of it. If you have received this message in error of system, please delete it from your system and notify Sacombank immediately by e-mail to as...@sa... or via telephone 1900 5555 88. Any disclosing, copying, distributing or taking action in reliance on the contents of this email are strictly prohibited, unless you are the intended recipient. Sacombank does not accept liability in connection with errors in the email, computer virus, data corruption, interference or delay arising from or in connection with this email. Please consider the environment before printing this email.
|
|
From: Jordi B. U. <jb...@ne...> - 2016-05-20 09:50:56
|
We have been trying different options (with a deadline menacing) and it was the one my colleague got running. I tried 3.7 but got unsolved errors. We need to think slowly about it when some internal events go by. Bye, jordi -----Mensaje original----- De: Markus Kilås [mailto:ma...@pr...] Enviado el: viernes, 20 de mayo de 2016 11:09 Para: Jordi Blasi Uribarri; SignServer Developers Asunto: Re: [SignServer-develop] JDBC problem On 05/20/2016 11:02 AM, Jordi Blasi Uribarri wrote: > This is just to thank your help. Finally we got to get version 3.6 running with Glashfish and now we have defined different workers and entry forms for different users. > Great, thanks for the update. But may I ask, why SignServer 3.6? That is a more than a year old release. The latest community edition is 3.7.0. Cheers, Markus PrimeKey Solutions AB |
|
From: Markus K. <ma...@pr...> - 2016-05-20 09:09:38
|
On 05/20/2016 11:02 AM, Jordi Blasi Uribarri wrote: > This is just to thank your help. Finally we got to get version 3.6 running with Glashfish and now we have defined different workers and entry forms for different users. > Great, thanks for the update. But may I ask, why SignServer 3.6? That is a more than a year old release. The latest community edition is 3.7.0. Cheers, Markus PrimeKey Solutions AB |
|
From: Markus K. <ma...@pr...> - 2016-05-19 14:43:59
|
On 05/19/2016 04:13 PM, Jordi Blasi Uribarri wrote:
> I have changed the module.xml, rebuild the project and restarted the wildfly server but I get the same error, referring to version 2.7.2. I don't really know where the reference comes from.
>
> I don't know if that is the core of my problem as it is only a warning.
The warning about "Class Path entry" can be ignored. That is a known
issue. You get it with JBoss AS 7 / EAP 6 as well but it should not
cause any problem.
>What I see is that when I try to add the datasource with the following command:
>
>
> data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="root" --password="alfresco16" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
>
> I see the following error, referring also to what I understand is a dependency problem.
>
> 08:42:06,428 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "signserverds")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
> "jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
> ]}
> 08:42:06,440 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.data-source.reference-factory.signserverds (missing) dependents: [service jboss.naming.context.java.SignServerDS]
> service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
> service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
> WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
Yes, together with the "NoSuchMethodError:
org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V" it
looks like an issues with xmlsec 1.5.x vs 2.x.
I would expect that this could happen if you copied xmlsec-1.5.8
somewhere into Wildfly. Are you sure you removed that modification?
Maybe also need to clear standalone/tmp/.
If the problem is still present with an unmodified Wildfly then it could
be that it is picking up our xmlsec from within signserver.ear. To test
if this is the case you could open signserver.ear with a zip application
and remove the lib/xmlsec-1.5.8.jar and then restart the application
server and see if that helps.
Regards,
Markus
PrimeKey Solutions AB
>
> Best regards,
>
> Jordi
>
> -----Mensaje original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviado el: jueves, 19 de mayo de 2016 15:55
> Para: sig...@li...
> Asunto: Re: [SignServer-develop] JDBC problem
>
> On 05/19/2016 09:26 AM, Jordi Blasi Uribarri wrote:
>> 01:37:44,074 ERROR [org.jboss.msc.service.fail] (MSC service thread
>> 1-1)
>> MSC000001: Failed to start service jboss.ws.config:
>> org.jboss.msc.service.StartException in service jboss.ws.config:
>> Failed to start service
>>
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContr
>> ollerImpl.java:1904)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
>> ava:1142)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
>> java:617)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Caused by: java.lang.NoSuchMethodError:
>> org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V
>>
>> at
>> org.apache.wss4j.common.crypto.WSProviderConfig.initializeResourceBund
>> les(WSProviderConfig.java:199)
>>
>> at
>> org.apache.wss4j.common.crypto.WSProviderConfig.init(WSProviderConfig.
>> java:90)
>>
>> at
>> org.jboss.wsf.stack.cxf.config.CXFStackConfig.<init>(CXFStackConfigFac
>> tory.java:62)
>>
>> at
>> org.jboss.wsf.stack.cxf.config.CXFStackConfigFactory.getStackConfig(CX
>> FStackConfigFactory.java:47)
>>
>> at
>> org.jboss.ws.common.management.AbstractServerConfig.setStackConfig(Abs
>> tractServerConfig.java:361)
>>
>> at
>> org.jboss.ws.common.management.AbstractServerConfig.create(AbstractSer
>> verConfig.java:339)
>>
>> at
>> org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigIm
>> pl.java:70)
>>
>> at
>> org.jboss.as.webservices.service.ServerConfigService.start(ServerConfi
>> gService.java:70)
>>
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Ser
>> viceControllerImpl.java:1948)
>>
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContr
>> ollerImpl.java:1881)
>>
>> ... 3 more
>>
>
> It looks like Wildfly 10 is maybe expecting an other version of xmlsec (i.e. 2.x while SignServer uses 1.5.8).
>
> Have you tried if it works if you don't change the xmlsec and xalan versions in Wildfly? I.e. by not doing the change in modules/system/layers/base/org/apache/santuario/xmlsec/ and modules/system/layers/base/org/apache/xalan?
>
>
> Regards,
> Markus
> PrimeKey Solutions AB
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
PKI Specialist
PrimeKey Solutions AB
Lundagatan 16
SE-171 63 Solna
Sweden
Phone: +46 70 424 94 85
Email: mar...@pr...
https://www.primekey.se
|
|
From: Jordi B. U. <jb...@ne...> - 2016-05-19 14:14:09
|
I have changed the module.xml, rebuild the project and restarted the wildfly server but I get the same error, referring to version 2.7.2. I don't really know where the reference comes from.
I don't know if that is the core of my problem as it is only a warning. What I see is that when I try to add the datasource with the following command:
data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="root" --password="alfresco16" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
I see the following error, referring also to what I understand is a dependency problem.
08:42:06,428 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
08:42:06,440 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source.reference-factory.signserverds (missing) dependents: [service jboss.naming.context.java.SignServerDS]
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
Best regards,
Jordi
-----Mensaje original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviado el: jueves, 19 de mayo de 2016 15:55
Para: sig...@li...
Asunto: Re: [SignServer-develop] JDBC problem
On 05/19/2016 09:26 AM, Jordi Blasi Uribarri wrote:
> 01:37:44,074 ERROR [org.jboss.msc.service.fail] (MSC service thread
> 1-1)
> MSC000001: Failed to start service jboss.ws.config:
> org.jboss.msc.service.StartException in service jboss.ws.config:
> Failed to start service
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContr
> ollerImpl.java:1904)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
> ava:1142)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:617)
>
> at java.lang.Thread.run(Thread.java:745)
>
> Caused by: java.lang.NoSuchMethodError:
> org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V
>
> at
> org.apache.wss4j.common.crypto.WSProviderConfig.initializeResourceBund
> les(WSProviderConfig.java:199)
>
> at
> org.apache.wss4j.common.crypto.WSProviderConfig.init(WSProviderConfig.
> java:90)
>
> at
> org.jboss.wsf.stack.cxf.config.CXFStackConfig.<init>(CXFStackConfigFac
> tory.java:62)
>
> at
> org.jboss.wsf.stack.cxf.config.CXFStackConfigFactory.getStackConfig(CX
> FStackConfigFactory.java:47)
>
> at
> org.jboss.ws.common.management.AbstractServerConfig.setStackConfig(Abs
> tractServerConfig.java:361)
>
> at
> org.jboss.ws.common.management.AbstractServerConfig.create(AbstractSer
> verConfig.java:339)
>
> at
> org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigIm
> pl.java:70)
>
> at
> org.jboss.as.webservices.service.ServerConfigService.start(ServerConfi
> gService.java:70)
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Ser
> viceControllerImpl.java:1948)
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContr
> ollerImpl.java:1881)
>
> ... 3 more
>
It looks like Wildfly 10 is maybe expecting an other version of xmlsec (i.e. 2.x while SignServer uses 1.5.8).
Have you tried if it works if you don't change the xmlsec and xalan versions in Wildfly? I.e. by not doing the change in modules/system/layers/base/org/apache/santuario/xmlsec/ and modules/system/layers/base/org/apache/xalan?
Regards,
Markus
PrimeKey Solutions AB
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
SignServer-develop mailing list
Sig...@li...
https://lists.sourceforge.net/lists/listinfo/signserver-develop
|
|
From: Markus K. <ma...@pr...> - 2016-05-19 13:55:18
|
On 05/19/2016 09:26 AM, Jordi Blasi Uribarri wrote: > 01:37:44,074 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) > MSC000001: Failed to start service jboss.ws.config: > org.jboss.msc.service.StartException in service jboss.ws.config: Failed > to start service > > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > Caused by: java.lang.NoSuchMethodError: > org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V > > at > org.apache.wss4j.common.crypto.WSProviderConfig.initializeResourceBundles(WSProviderConfig.java:199) > > at > org.apache.wss4j.common.crypto.WSProviderConfig.init(WSProviderConfig.java:90) > > at > org.jboss.wsf.stack.cxf.config.CXFStackConfig.<init>(CXFStackConfigFactory.java:62) > > at > org.jboss.wsf.stack.cxf.config.CXFStackConfigFactory.getStackConfig(CXFStackConfigFactory.java:47) > > at > org.jboss.ws.common.management.AbstractServerConfig.setStackConfig(AbstractServerConfig.java:361) > > at > org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:339) > > at > org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigImpl.java:70) > > at > org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:70) > > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > > ... 3 more > It looks like Wildfly 10 is maybe expecting an other version of xmlsec (i.e. 2.x while SignServer uses 1.5.8). Have you tried if it works if you don't change the xmlsec and xalan versions in Wildfly? I.e. by not doing the change in modules/system/layers/base/org/apache/santuario/xmlsec/ and modules/system/layers/base/org/apache/xalan? Regards, Markus PrimeKey Solutions AB |
|
From: Markus K. <ma...@pr...> - 2016-05-19 12:21:17
|
On 05/19/2016 01:47 PM, Jordi Blasi Uribarri wrote: > Hi, > > > > We are testing the server and would like to understand how it works and > if it meets our needs. I guess there is some concept understanding > problem, so I will try to make it as clear as possible. > > > > We are able to sign files with the CMS worker and validate them > correctly. What we are not quite sure is who is actually signing them. > We would like to give different people the capability of signing files > as they are being generated for a later secure storage. What I see is > that every worker has a certificate configured and uses it to sign the > files. If I intend to set a multiuser environment do I need to create a > worker for every user? Os is it supposed to be a server/organization > level signing? How should I define, if possible, to create this multi > user configuration? > > > Thanks, > > Jordi > > > Documento sin título > ------------------------------------------------------------------------ > *Jordi Blasi Uribarri* > Área I+D+i > > jb...@ne... > Oficina Bilbao > > Hi Jordi, One of the main usages would be to have a server/organization level signing using one (or a few workers). You would then give access to this worker to the users that should be able to use it. For a smaller number of users (i.e. less then say 50-100 or so) it could also be possible to set up one worker per user in order to use individual keys and certificates. The limit here is mainly related to administration and the fact that the AdminGUI currently loads all workers when configuration changes are made so it does not scale that well when the numbers of workers are high. For a larger number of users where each should have individual keys and certificates one option would be to use the AuthorizedUsernameAliasSelector [1]. Using that the alias selector decides which key and certificate to use based on the user name of the user. In this case only one (or a few workers) would be configured that can be used by multiple users using different keys and certificates. [1] https://www.signserver.org/doc/current/manual/plugins.html#Alias%20Selectors Regards, Markus PrimeKey Solutions AB Save time and money with an Enterprise support subscription. Please see www.primekey.se for more information. https://www.primekey.se/technologies/products-overview/ https://www.primekey.se/service-support/support/ |
|
From: Jordi B. U. <jb...@ne...> - 2016-05-19 11:47:41
|
Hi, We are testing the server and would like to understand how it works and if it meets our needs. I guess there is some concept understanding problem, so I will try to make it as clear as possible. We are able to sign files with the CMS worker and validate them correctly. What we are not quite sure is who is actually signing them. We would like to give different people the capability of signing files as they are being generated for a later secure storage. What I see is that every worker has a certificate configured and uses it to sign the files. If I intend to set a multiuser environment do I need to create a worker for every user? Os is it supposed to be a server/organization level signing? How should I define, if possible, to create this multi user configuration? Thanks, Jordi ________________________________ Jordi Blasi Uribarri Área I+D+i jb...@ne... Oficina Bilbao [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png] |
|
From: Jordi B. U. <jb...@ne...> - 2016-05-19 07:26:58
|
Hi Marcus,
I did, and I retried it again. I see this in the log:
01:50:57,817 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
01:50:57,823 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source.reference-factory.signserverds (missing) dependents: [service jboss.naming.context.java.SignServerDS]
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
When it tries to deploy the application, server start I also see these errors:
01:37:44,049 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly-10.0.0.Final/standalone/deployments
01:37:44,054 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "signserver.ear" (runtime-name: "signserver.ear")
01:37:44,074 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V
at org.apache.wss4j.common.crypto.WSProviderConfig.initializeResourceBundles(WSProviderConfig.java:199)
at org.apache.wss4j.common.crypto.WSProviderConfig.init(WSProviderConfig.java:90)
at org.jboss.wsf.stack.cxf.config.CXFStackConfig.<init>(CXFStackConfigFactory.java:62)
at org.jboss.wsf.stack.cxf.config.CXFStackConfigFactory.getStackConfig(CXFStackConfigFactory.java:47)
at org.jboss.ws.common.management.AbstractServerConfig.setStackConfig(AbstractServerConfig.java:361)
at org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:339)
at org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigImpl.java:70)
at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:70)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
01:37:44,396 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,393 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,393 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,402 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
01:37:48,789 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xercesImpl.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,791 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xml-apis.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,791 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry serializer.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xml-apis.jar in /content/signserver.ear/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,811 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-SignServerWS.jar")
01:37:48,811 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-AdminWS.jar")
01:37:48,812 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "signserver.war")
01:37:48,812 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-ValidationWS.jar")
01:37:48,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "cesecore-ejb-6.1.1.jar")
01:37:48,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-war-Healthcheck.war")
01:37:48,815 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-war-Doc.war")
01:37:48,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-ClientWS.jar")
01:37:48,829 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb.jar")
01:37:48,859 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.ws.config" => "org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
Caused by: java.lang.NoSuchMethodError: org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V"}}
01:37:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "signserver.ear" (runtime-name : "signserver.ear")
01:37:48,936 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
01:37:49,114 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
01:37:49,115 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
01:37:49,115 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 11404ms - Started 287 of 589 services (11 services failed or missing dependencies, 376 services are lazy, passive or on-demand)
It looks like there is some problem with jar references. All the ones that were copied and referenced during installation process are giving errors.
This is what I did:
cp -P /opt/signserver/lib/ext/xmlsec-1.5.8.jar /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/santuario/xmlsec/main/
vi /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/santuario/xmlsec/main/module.xml
<resource-root path="xmlsec-1.5.8.jar"/>
cp /opt/signserver/lib/ext/xalan-2.7.2.jar /opt/signserver/lib/ext/serializer-2.7.2.jar /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/xalan/main/
vi /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/xalan/main/module.xml
<resource-root path="serializer-2.7.2.jar"/>
<resource-root path="xalan-2.7.2.jar"/>
wget https://downloads.mariadb.com/enterprise/698m-9ksy/connectors/java/connector-java-1.4.4/mariadb-java-client-1.4.4.jar
mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
cp -P /opt/mariadb-java-client-1.4.4.jar .
vi module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.mariadb">
<resources>
<resource-root path="mariadb-java-client-1.4.4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
Thanks,
Jordi
De: Marcus Lundblad [mailto:mar...@pr...]
Enviado el: jueves, 19 de mayo de 2016 9:18
Para: Jordi Blasi Uribarri; sig...@li...
Asunto: Re: [SignServer-develop] JDBC problem
ons 2016-05-18 klockan 15:08 +0000 skrev Jordi Blasi Uribarri:
Hi,
Hi Jordi!
I am trying to install sign server on a freshly installed fedora box. I have followed the install procedure described on the web as close as possible but I am finding problems to deploy the signserver on the app server.
I have installed it on wildfly 10 and mariaDB.
What I am seeing is that there is a problem with the jdbc driver configuration. On the server.xml log I can see this:
2016-05-19 04:26:29,475 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
2016-05-19 04:26:29,482 INFO [org.jboss.as.controller] (management-handler-thread - 3) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
I have created the module.xml file and moved the jar file.
mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
cp -P /opt/mariadb-java-client-1.4.4.jar .
vi module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.mariadb">
<resources>
<resource-root path="mariadb-java-client-1.4.4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
I also have run on the jboss-cli the following commands:
/subsystem=datasources/jdbc-driver=com.mysql.jdbc.Driver:add(driver-name=com.mysql.jdbc.Driver,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource)
:reload
data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="xxx" --password="xxx" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
Did you do a :reload (or restart the application server) after issuing the "data-source add" command?
//Marcus
In the Web interface of wildfly I have not seen any reference to this connection.
What I am doing wrong?
Thanks in advance.
Jordi
________________________________
Jordi Blasi Uribarri
Área I+D+i
jb...@ne...<mailto:jb...@ne...>
Oficina Bilbao
[http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
SignServer-develop mailing list
Sig...@li...<mailto:Sig...@li...>
https://lists.sourceforge.net/lists/listinfo/signserver-develop
|
|
From: Marcus L. <mar...@pr...> - 2016-05-19 07:18:31
|
ons 2016-05-18 klockan 15:08 +0000 skrev Jordi Blasi Uribarri:
> Hi,
Hi Jordi!
>
>
>
> I am trying to install sign server on a freshly installed fedora box. I have followed the install procedure described on the web as close as possible but I am finding problems to deploy the signserver on the app server.
>
>
>
> I have installed it on wildfly 10 and mariaDB.
>
>
>
> What I am seeing is that there is a problem with the jdbc driver configuration. On the server.xml log I can see this:
>
>
>
> 2016-05-19 04:26:29,475 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
>
> ("subsystem" => "datasources"),
>
> ("data-source" => "signserverds")
>
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
>
> "org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
>
> "jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
>
> ]}
>
> 2016-05-19 04:26:29,482 INFO [org.jboss.as.controller] (management-handler-thread - 3) WFLYCTL0183: Service status report
>
> WFLYCTL0184: New missing/unsatisfied dependencies:
>
> service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
>
> service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
>
>
>
>
>
> I have created the module.xml file and moved the jar file.
>
>
>
> mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
>
>
>
> cp -P /opt/mariadb-java-client-1.4.4.jar .
>
> vi module.xml
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I also have run on the jboss-cli the following commands:
>
>
>
> /subsystem=datasources/jdbc-driver=com.mysql.jdbc.Driver:add(driver-name=com.mysql.jdbc.Driver,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource)
>
> :reload
>
>
>
> data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver"
> --user-name="xxx" --password="xxx" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED
> --check-valid-connection-sql="select 1;"
Did you do a :reload (or restart the application server) after issuing
the "data-source add" command?
//Marcus
>
>
> In the Web interface of wildfly I have not seen any reference to this connection.
>
>
>
>
> What I am doing wrong?
>
>
>
> Thanks in advance.
>
>
>
> Jordi
>
>
>
>
<span class="-x-evo-quoted"><span class="-x-evo-quote-character">> </span></span>Documento sin título>
>
> Jordi Blasi Uribarri
>
> Área I+D+i
>
>
> jb...@ne...
>
> Oficina Bilbao
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
>
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> SignServer-develop mailing list
>
Sig...@li...>
https://lists.sourceforge.net/lists/listinfo/signserver-develop>
|
|
From: Jordi B. U. <jb...@ne...> - 2016-05-18 15:44:13
|
Hi,
I am trying to install sign server on a freshly installed fedora box. I have followed the install procedure described on the web as close as possible but I am finding problems to deploy the signserver on the app server.
I have installed it on wildfly 10 and mariaDB.
What I am seeing is that there is a problem with the jdbc driver configuration. On the server.xml log I can see this:
2016-05-19 04:26:29,475 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
2016-05-19 04:26:29,482 INFO [org.jboss.as.controller] (management-handler-thread - 3) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
I have created the module.xml file and moved the jar file.
mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
cp -P /opt/mariadb-java-client-1.4.4.jar .
vi module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.mariadb">
<resources>
<resource-root path="mariadb-java-client-1.4.4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
I also have run on the jboss-cli the following commands:
/subsystem=datasources/jdbc-driver=com.mysql.jdbc.Driver:add(driver-name=com.mysql.jdbc.Driver,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource)
:reload
data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="xxx" --password="xxx" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
In the Web interface of wildfly I have not seen any reference to this connection.
What I am doing wrong?
Thanks in advance.
Jordi
________________________________
Jordi Blasi Uribarri
Área I+D+i
jb...@ne...
Oficina Bilbao
[http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
|
|
From: Markus K. <ma...@pr...> - 2016-05-16 11:04:12
|
On 05/16/2016 12:03 PM, Konstantinos Dimkas wrote: >> On 13 May 2016, at 14:36, Markus Kilås <ma...@pr... >> <mailto:ma...@pr...>> wrote: >> >> On 05/13/2016 01:26 PM, Markus Kilås wrote: >>> Hello Konstantinos, >>> >>> Questions and answers like this could be very useful for other people as >>> well so please use the mailing list so that everybody can benefit from >>> the discussion. Alternatively if you need professional support you can >>> contact sa...@pr... <mailto:sa...@pr...>. >>> >>> Regards, >>> Markus >>> >>> >>> -------- Forwarded Message -------- >>> Subject: Signserver setup and jboss >>> Date: Fri, 13 May 2016 12:53:47 +0300 >>> From: Konstantinos Dimkas <ksd...@cs... >>> <mailto:ksd...@cs...>> >>> To: Markus Kilås <ma...@pr... <mailto:ma...@pr...>> >>> >>> >>> >>> Hello Markus, >>> >>> Thank you very much for your advice for the sign server setup. I am >>> still facing some problems with the installation and i could not >>> overcome the “No EJB handler available”. Due to the fact that i am new >>> to PKI (and i am still an intern at a non-profit organisation) i would >>> really appreciate it if you can point out to me a source with some more >>> detailed installation guidelines, i was not able to find more >>> instructions except from the official documentation. Also i would like >>> to know if there is a playbook for ansible to set up >>> jboss and signserver. >>> >>> >>> Thank you very much for your time, >>> Konstantinos Dimkas >>> >>> >> >> Did you check the output from the application server log? >> Without knowing if the application has started correctly we can only >> make wild guesses about what could be the problem. >> You could upload the server log to paste bin like, https://pastebin.ca/ >> and send the link here. >> >> Original discussion: >> https://sourceforge.net/p/signserver/mailman/message/35036165/ >> Cheers, >> Markus >> > Hello, > > I uploaded at pastern the output of the jboss standalone, the link is > the following: http://pastebin.ca/3601286 > I can spot some things that go wrong, but i would appreciate a more > detailed help. > > Thank you very much in advance, > Konstantinos Dimkas The first error I can see is the "Did not receive a response to the deployment operation": --- 12:52:39,813 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 12:52:39,814 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "signserver.ear" was rolled back with failure message Operation cancelled --- This means that JBoss failed to deploy/start SignServer and there is thus no idea to continue trying to access SignServer. The reason why this happen is not clear from the output. Maybe some more info could be available in the JBOSS_HOME/standalone/log/server.log. One issue that comes to mind, which could give this situation is a bug in JBoss 7 where JBoss hangs if you don't have more than 2 CPU cores available. In this case if you run in a virtual machine you need to assign more CPUs to the VM. Regards, Markus PrimeKey Solutions |
8 messages has been excluded from this view by a project administrator.
