From: Sozet F. <flo...@at...> - 2008-12-03 10:49:04
|
These are the mysql results : mysql> select * from ProtectedLogData where nodeGUID=-1293910574 and counter=1120; +----------------------------------+-----------+-----------+------+--------+---------------+----------+-------------------------+---------------------+---------+--------------------------------------------------------------------+-------------+---------+--------------+-----------------------------+------------------------------+----------------------+-------------------------+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | pk | adminType | adminData | cAId | module | eventTime | username | certificateSerialNumber | certificateIssuerDN | eventId | eventComment | nodeGUID | counter | nodeIP | b64LinkedInEventIdentifiers | b64LinkedInEventsHash | currentHashAlgorithm | protectionKeyIdentifier | protectionKeyAlgorithm | b64Protection | +----------------------------------+-----------+-----------+------+--------+---------------+----------+-------------------------+---------------------+---------+--------------------------------------------------------------------+-------------+---------+--------------+-----------------------------+------------------------------+----------------------+-------------------------+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | f2a69c1e0a11951f5430c3d45497926f | 5 | NULL | 0 | 9 | 1228136652985 | NULL | NULL | NULL | 42 | Service __ProtectedLogVerificationService__ executed successfully. | -1293910574 | 1120 | 10.17.149.31 | suB90gAAAAAAAARf | v0pBBuMScx4rBAbqSVs3zb0DTjY= | SHA-1 | -395221696 | SHA1WithRSA | YqZ77+F/hWmYANhh2YAlqKUgaqXIj6N90lOmbJMCeYAHLHIzdzPRoEwO1fngskzkdyWQRaebU8fnp1xryYUvbedXhzXUmHWmYCwvN7KPbJt2fW7p0XH9l1lkOBMI5kpj4dWf0AWNb5gPfgBNHhy8IjGjTmIwF7l/le2uE3fvEIc/RCDc+UU714RBg9XX+iennzNejhCq4/IdzTfI9pt9A9GpE9fJQE5T33m4JTOS9O7p8jNcV/YUa5F8vYZbVVaUFXmIrtSuxp2RCzL646iVnfKO/s3lARtl57TFts3F9DYKqPfO7vIg6dk2BUb/gphm7VD6yvy+ZtJ/CAIJ1GnNBw== | | fc06507a0a11951f6c271b7ae567db08 | 5 | NULL | 0 | 2 | 1228293961559 | NULL | NULL | NULL | 2001 | Node-chain was accepted by CLI. | -1293910574 | 1120 | 10.17.149.31 | suB90gAAAAAAAARf | v0pBBuMScx4rBAbqSVs3zb0DTjY= | SHA-1 | -395221696 | SHA1WithRSA | UzbaQWU+ftDoDfSgC16nvu5Vp+GimZ0/OXMuII9EEX7bxrMSEFT/B7VhlDrJ63PEE4AmxzcSAe8b4FjbTig0cRPqcHRtP6GoS9hXfUZPKC82e5uQ2pJcJsVnraAb7l12HqojEdb1uIvHmkMBbGME9/NI76PF6V9sCvlNpEyX6r2cC1dcqh9kCEV8HIp0Q1ZO/rPwVWfSdmllW1yawhLXSjzbkbBFStZXKCHWQUmQApHxCRCXeftMSYvx/tID4kq1UnfQOoCY85Q3UMNYWsnfRYCIdEG4Iv679s6sTIoQ3BRaL3PiuoEc4Gm5Zn59BuTa3Lp8zsk43UC8/E0o3S9KSQ== | +----------------------------------+-----------+-----------+------+--------+---------------+----------+-------------------------+---------------------+---------+--------------------------------------------------------------------+-------------+---------+--------------+-----------------------------+------------------------------+----------------------+-------------------------+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.06 sec) mysql> select count(*) from ProtectedLogData where nodeGUID=-1293910574 and counter>1120; +----------+ | count(*) | +----------+ | 0 | +----------+ 1 row in set (0.02 sec) mysql> select * from ProtectedLogData where nodeGUID=-1293910574 and counter=1121; Empty set (0.04 sec) Florent -----Message d'origine----- De : Johan Eklund [mailto:ejb...@pr...] Envoyé : mercredi 3 décembre 2008 11:28 À : ejb...@li... Objet : Re: [Ejbca-develop] Log verification failed Strange.. What is in this log-post? mysql> select * from ProtectedLogData where nodeGUID=-1293910574 and counter=1120; Is this the last post in the chain? mysql> select count(*) from ProtectedLogData where nodeGUID=-1293910574 and counter>1120; Is the next one linking in 1120? mysql> select * from ProtectedLogData where nodeGUID=-1293910574 and counter=1121; /Johan Sozet Florent skrev: > Yes, I still have the error one hour after the "ejbca.sh log accept frozen" command : > > 2008-12-03 11:02:45,583 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. > 2008-12-03 11:03:37,677 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Could not fetch log event (-1293910574, 1120). > 2008-12-03 11:03:37,678 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at -1293910574 1120. > 2008-12-03 11:03:37,681 INFO [org.ejbca.core.model.log.Log4jLogDevice] December 3, 2008 11:03:37 AM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. > > even if I restart JBoss. > > -----Message d'origine----- > De : Johan Eklund [mailto:ejb...@pr...] > Envoyé : mercredi 3 décembre 2008 10:42 À : > ejb...@li... > Objet : Re: [Ejbca-develop] Log verification failed > > And this error keeps appearing? Just after signing frozen nodes (with a signature in the future) you might see this kind of error, but it should disappear after a couple of minutes.. > > Sozet Florent skrev: > >> Hello Johan, >> >> Thank you for your answer. >> >> I tried your command : >> >> ---------------------------- >> >> ./ejbca.sh log accept frozen >> Using JBoss JNDI provider... >> >> YOU ARE ABOUT TO SIGN UNVERIFIABLE LOG EVENTS IN THE PROTECTED LOG! >> >> This should only be used when log protection is first enabled or when recovering from a crash. >> Confirm this by entering "8819": 8819 >> >> Signing... >> SUCCESS! >> >> ---------------------------- >> >> These are the JBoss logs just after the command execution : >> >> ---------------------------- >> >> 2008-12-03 09:45:46,954 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >> 2008-12-03 09:45:51,616 INFO [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Accepted node-chain -1293910574. >> 2008-12-03 09:45:51,732 INFO [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Accepted node-chain 1590614036. >> 2008-12-03 09:46:37,255 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Could not fetch log event (-1293910574, 1120). >> 2008-12-03 09:46:37,255 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at -1293910574 1120. >> 2008-12-03 09:46:37,260 INFO [org.ejbca.core.model.log.Log4jLogDevice] December 3, 2008 9:46:37 AM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >> 2008-12-03 09:46:37,305 ERROR [org.ejbca.core.model.log.ProtectedLogDevice] Log-event (-1293910574, 1120) is missing in database. >> 2008-12-03 09:46:37,322 ERROR [org.ejbca.core.model.log.ProtectedLogDevice] Log-event (1590614036, 1086) is missing in database. >> 2008-12-03 09:47:08,325 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >> >> ---------------------------- >> >> After reboot JBoss, I still have the same error : >> >> ---------------------------- >> >> 2008-12-03 09:59:34,025 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >> 2008-12-03 10:00:25,908 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Could not fetch log event (-1293910574, 1120). >> 2008-12-03 10:00:25,908 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at -1293910574 1120. >> 2008-12-03 10:00:25,911 INFO [org.ejbca.core.model.log.Log4jLogDevice] December 3, 2008 10:00:25 AM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >> >> ---------------------------- >> >> Then, I retry this command : >> >> ---------------------------- >> >> ./ejbca.sh log accept frozen >> Using JBoss JNDI provider... >> >> YOU ARE ABOUT TO SIGN UNVERIFIABLE LOG EVENTS IN THE PROTECTED LOG! >> >> This should only be used when log protection is first enabled or when recovering from a crash. >> Confirm this by entering "2409": 2409 >> >> Signing... >> SUCCESS! >> >> ---------------------------- >> >> => Nothing in JBoss logs just after this command. >> >> And then, always this same error : >> >> ---------------------------- >> >> 2008-12-03 10:02:02,179 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >> 2008-12-03 10:02:51,027 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Could not fetch log event (-1293910574, 1120). >> 2008-12-03 10:02:51,028 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at -1293910574 1120. >> 2008-12-03 10:02:51,031 INFO [org.ejbca.core.model.log.Log4jLogDevice] December 3, 2008 10:02:51 AM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >> >> ---------------------------- >> >> Maybe I have something wrong in my database. >> I will reinstall a new test EJBCA with this protected logs functionnality. >> >> thanks, >> Best regards >> Florent >> >> -----Message d'origine----- >> De : Johan Eklund [mailto:ejb...@pr...] >> Envoyé : mardi 2 décembre 2008 22:07 >> À : ejb...@li... >> Objet : Re: [Ejbca-develop] Log verification failed >> >> Hi Sozet, >> >> Sorry for the delay, I missed that you have answered. >> >> Sorry, no. This is not normal. It means that the log contains a chain of events (for an EJBCA session) that isn't terminated with end-signature. >> This can happen if a node (EJBCA session) crashes or if someone has manipulated the database. >> >> The command >> bin/ejbca.sh log accept frozen >> will locate any such chain and put an end-signature on it. >> >> Was there anything in the log at the time of running "./ejbca.sh log accept all"? This feature is very complex, so it's hard to see what has gone wrong without more info. >> >> The design document at https://jira.primekey.se/browse/ECA-633 contains all the gory details on how this feature works and is recommended reading if you plan on using this in a production environment. >> >> Best Regards, >> Johan >> >> >> Sozet Florent skrev: >> >> >>> Hello, >>> >>> About my last post, do you think these errors, at regular intervals (each minute), are normal in JBoss logs when protected logs are activated ? >>> >>> 2008-12-02 15:38:42,981 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >>> 2008-12-02 15:39:11,178 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Frozen node. Nothing has been added to node -1293910574 for a long time. >>> 2008-12-02 15:39:11,178 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at -1293910574 1119. >>> 2008-12-02 15:39:11,179 INFO [org.ejbca.core.model.log.Log4jLogDevice] December 2, 2008 3:39:11 PM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >>> >>> thanks, >>> best regards, >>> >>> Florent >>> >>> -----Message d'origine----- >>> De : Sozet Florent >>> Envoyé : vendredi 28 novembre 2008 18:17 À : >>> ejb...@li... >>> Objet : RE: [Ejbca-develop] Log verification failed >>> >>> Hello Johan, >>> >>> I followed the instructions at the top of the config file : >>> >>> 1. Make sure EJBCA is using a database or database engine that >>> supports transactions (like MySQL's InnoDB) => all my tables have an >>> InnoDB engine >>> >>> 2. Make sure this device is enabled in conf/log.properties => OK >>> (see my log.properties configuration below) >>> >>> 3. Configure the protection token you want to use in this file >>> (CAName or URI) => CAName (TestAdmin) is OK >>> >>> 4. Run "ant clean" and "ant deploy" to deploy EJBCA with this new configuration. >>> => OK (build successful) >>> >>> 5. Start EJBCA >>> => OK : no errors >>> >>> 6. Run the ejbca CLI, "bin/ejbca.sh log accept all" or "bin\ejbca.cmd log accept all" >>> => >>> ------------------------------------ >>> ./ejbca.sh log accept all >>> Using JBoss JNDI provider... >>> >>> YOU ARE ABOUT TO SIGN UNVERIFIABLE LOG EVENTS IN THE PROTECTED LOG! >>> >>> This should only be used when log protection is first enabled or when recovering from a crash. >>> Confirm this by entering "4356": 4356 >>> >>> Signing... >>> SUCCESS! >>> ----------------------------------- >>> >>> But I still have the errors below : >>> >>> 2008-11-28 18:00:51,231 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >>> 2008-11-28 18:01:08,554 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Frozen node. Nothing has been added to node 1590614036 for a long time. >>> 2008-11-28 18:01:08,554 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at 1590614036 1085. >>> 2008-11-28 18:01:08,559 INFO [org.ejbca.core.model.log.Log4jLogDevice] November 28, 2008 6:01:08 PM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >>> >>> 2008-11-28 18:10:01,028 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >>> 2008-11-28 18:11:18,653 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >>> 2008-11-28 18:12:24,076 ERROR [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Frozen node. Nothing has been added to node 1590614036 for a long time. >>> 2008-11-28 18:12:24,077 ERROR [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification failed at 1590614036 1085. >>> 2008-11-28 18:12:24,081 INFO [org.ejbca.core.model.log.Log4jLogDevice] November 28, 2008 6:12:24 PM CET, CAId : 0, SERVICE, EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No user involved, Certificate : No certificate involved, Comment : Service __ProtectedLogVerificationService__ executed successfully. >>> 2008-11-28 18:12:27,866 INFO [org.ejbca.core.ejb.services.ServiceSessionSession] Service __ProtectedLogVerificationService__ edited. >>> >>> >>> Is this error normal ? >>> >>> Best regards >>> Florent >>> >>> -----Message d'origine----- >>> De : Johan Eklund [mailto:ejb...@pr...] >>> Envoyé : vendredi 28 novembre 2008 14:31 À : >>> ejb...@li... >>> Objet : Re: [Ejbca-develop] Log verification failed >>> >>> Hi Sozet, >>> >>> Have you followed the instructions at the top of the config file? >>> (Accepted the current state of the database..) >>> >>> Best Regards, >>> Johan >>> >>> Sozet Florent skrev: >>> >>> >>> >>>> Hello, >>>> >>>> I try to use the ProtectedLogDevice and I've got a lot of errors in >>>> JBoss logs, like this one : >>>> >>>> 2008-11-28 11:49:36,578 ERROR >>>> [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification >>>> failed at -613305852 0. >>>> >>>> 2008-11-28 11:49:36,584 INFO >>>> [org.ejbca.core.model.log.Log4jLogDevice] >>>> November 28, 2008 11:49:36 AM CET, CAId : 0, SERVICE, >>>> EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No >>>> user involved, Certificate : No certificate involved, Comment : >>>> Service __ProtectedLogVerificationService__ executed successfully. >>>> >>>> 2008-11-28 11:49:51,634 INFO >>>> [org.ejbca.core.ejb.services.ServiceSessionSession] Service >>>> __ProtectedLogVerificationService__ edited. >>>> >>>> If I restart JBoss in debug mode, these are the error logs I have : >>>> >>>> 2008-11-28 14:12:28,382 DEBUG >>>> [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.ProtectedLogD >>>> a t a ] Executing SQL: SELECT adminType, adminData, cAId, module, >>>> eventTime, username, certificateSerialNumber, certificateIssuerDN, >>>> eventId, eventComment, nodeGUID, counter, nodeIP, >>>> b64LinkedInEventIdentifiers, b64LinkedInEventsHash, >>>> currentHashAlgorithm, protectionKeyIdentifier, >>>> protectionKeyAlgorithm, b64Protection FROM ProtectedLogData WHERE >>>> (pk=?) >>>> >>>> 2008-11-28 14:12:28,384 DEBUG >>>> [org.ejbca.core.ejb.log.ProtectedLogSessionBean] >>>> <getProtectedLogEventRow >>>> >>>> 2008-11-28 14:12:28,384 ERROR >>>> [org.ejbca.core.ejb.log.ProtectedLogSessionBean] Frozen node. >>>> Nothing has been added to node 1590614036 for a long time. >>>> >>>> 2008-11-28 14:12:28,384 ERROR >>>> [org.ejbca.core.model.log.ProtectedLogVerifier] Log verification >>>> failed at 1590614036 1085. >>>> >>>> 2008-11-28 14:12:28,384 DEBUG >>>> [org.ejbca.core.model.log.ProtectedLogVerifier] <run >>>> >>>> 2008-11-28 14:12:28,384 DEBUG >>>> [org.ejbca.core.model.services.workers.ProtectedLogVerificationWork >>>> e >>>> r >>>> ] >>>> <ProtectedLogVerificationWorker done >>>> >>>> 2008-11-28 14:12:28,385 DEBUG >>>> [org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.LogConfig >>>> u r a tionData#findByPrimaryKey] Executing SQL: SELECT >>>> t0_LogConfigurationData.id FROM LogConfigurationData >>>> t0_LogConfigurationData WHERE t0_LogConfigurationData.id=? >>>> >>>> 2008-11-28 14:12:28,386 DEBUG >>>> [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.LogConfigurat >>>> i o n Data] Executing SQL: SELECT logConfiguration, >>>> logEntryRowNumber FROM LogConfigurationData WHERE (id=?) >>>> >>>> 2008-11-28 14:12:28,389 INFO >>>> [org.ejbca.core.model.log.Log4jLogDevice] >>>> November 28, 2008 2:12:28 PM CET, CAId : 0, SERVICE, >>>> EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No >>>> user involved, Certificate : No certificate involved, Comment : >>>> Service __ProtectedLogVerificationService__ executed successfully. >>>> >>>> In the configuration files of EJBCA, I put : >>>> >>>> - in conf/log.properties >>>> >>>> # Used log devices. >>>> >>>> # The devices will be displayed in reversed order in the Admin GUI. >>>> >>>> # Default is "Log4jLogDevice;OldLogDevice" for now. >>>> >>>> usedLogDevices=Log4jLogDevice;ProtectedLogDevice >>>> >>>> - in conf/logdevices/protectedlog.properties >>>> >>>> diff protectedlog.properties protectedlog.properties.sample >>>> >>>> 27c27 >>>> >>>> < protectionTokenReferenceType=CAName >>>> >>>> --- >>>> >>>> >>>> >>>> >>>>> #protectionTokenReferenceType=CAName >>>>> >>>>> >>>>> >>>> 34c34 >>>> >>>> < protectionTokenReference=TestAdmin >>>> >>>> --- >>>> >>>> >>>> >>>> >>>>> #protectionTokenReference=AdminCA1 >>>>> >>>>> >>>>> >>>> 76c76 >>>> >>>> < protectionHashAlgorithm=SHA-1 >>>> >>>> --- >>>> >>>> >>>> >>>> >>>>> #protectionHashAlgorithm=SHA-1 >>>>> >>>>> >>>>> >>>> 99d98 >>>> >>>> < verificationservice.active=true >>>> >>>> 102c101 >>>> >>>> < verificationservice.invokationinterval=1 >>>> >>>> --- >>>> >>>> >>>> >>>> >>>>> #verificationservice.invokationinterval=1 >>>>> >>>>> >>>>> >>>> 106c105 >>>> >>>> < verificationservice.freezetreshold=60 >>>> >>>> --- >>>> >>>> >>>> >>>> >>>>> #verificationservice.freezetreshold=60 >>>>> >>>>> >>>>> >>>> And when I stop JBoss, many many logs of error appears : >>>> >>>> 2008-11-28 11:50:44,357 INFO >>>> [org.ejbca.core.model.log.Log4jLogDevice] >>>> November 28, 2008 11:50:40 AM CET, CAId : 0, SERVICE, >>>> EVENT_INFO_SERVICEEXECUTED, Administrator : INTERNALUSER, User : No >>>> user involved, Certificate : No certificate involved, Comment : >>>> Service __ProtectedLogVerificationService__ executed successfully. >>>> >>>> 2008-11-28 11:51:11,726 ERROR >>>> [org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.LogConfig >>>> u >>>> r >>>> a >>>> tionData#findByPrimaryKey] >>>> Find failed >>>> >>>> org.jboss.util.NestedSQLException: No ManagedConnections available >>>> within configured blocking timeout ( 30000 [ms] ); - nested throwable: >>>> (javax.resource.ResourceException: No ManagedConnections available >>>> within configured blocking timeout ( 30000 [ms] )) >>>> >>>> at >>>> org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wra >>>> p >>>> p >>>> e >>>> rDataSource.java:95) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDB >>>> C >>>> A >>>> b >>>> stractQueryCommand.java:225) >>>> >>>> ....... >>>> >>>> Caused by: javax.resource.ResourceException: No ManagedConnections >>>> available within configured blocking timeout ( 30000 [ms] ) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.InternalManagedConnectionPool. >>>> g >>>> e >>>> t >>>> Connection(InternalManagedConnectionPool.java:303) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.JBossManagedConnectionPool$Bas >>>> e >>>> P >>>> o >>>> ol.getConnection(JBossManagedConnectionPool.java:613) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2.getMana >>>> g >>>> e >>>> d >>>> Connection(BaseConnectionManager2.java:347) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.TxConnectionManager.getManaged >>>> C >>>> o >>>> n >>>> nection(TxConnectionManager.java:330) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2.allocat >>>> e >>>> C >>>> o >>>> nnection(BaseConnectionManager2.java:402) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2$Connect >>>> i >>>> o >>>> n >>>> ManagerProxy.allocateConnection(BaseConnectionManager2.java:849) >>>> >>>> at >>>> org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wra >>>> p >>>> p >>>> e >>>> rDataSource.java:89) >>>> >>>> ... 96 more >>>> >>>> 2008-11-28 11:51:13,808 ERROR >>>> [org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand.ProtectedLo >>>> g >>>> D >>>> a >>>> ta] >>>> Error checking if entity exists >>>> >>>> org.jboss.util.NestedSQLException: No ManagedConnections available >>>> within configured blocking timeout ( 30000 [ms] ); - nested throwable: >>>> (javax.resource.ResourceException: No ManagedConnections available >>>> within configured blocking timeout ( 30000 [ms] )) >>>> >>>> .......... >>>> >>>> at >>>> org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wra >>>> p >>>> p >>>> e >>>> rDataSource.java:95) >>>> >>>> Caused by: javax.resource.ResourceException: No ManagedConnections >>>> available within configured blocking timeout ( 30000 [ms] ) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.InternalManagedConnectionPool. >>>> g >>>> e >>>> t >>>> Connection(InternalManagedConnectionPool.java:303) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.JBossManagedConnectionPool$Bas >>>> e >>>> P >>>> o >>>> ol.getConnection(JBossManagedConnectionPool.java:613) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2.getMana >>>> g >>>> e >>>> d >>>> Connection(BaseConnectionManager2.java:347) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.TxConnectionManager.getManaged >>>> C >>>> o >>>> n >>>> nection(TxConnectionManager.java:330) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2.allocat >>>> e >>>> C >>>> o >>>> nnection(BaseConnectionManager2.java:402) >>>> >>>> at >>>> org.jboss.resource.connectionmanager.BaseConnectionManager2$Connect >>>> i >>>> o >>>> n >>>> ManagerProxy.allocateConnection(BaseConnectionManager2.java:849) >>>> >>>> at >>>> org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wra >>>> p >>>> p >>>> e >>>> rDataSource.java:89) >>>> >>>> ... 134 more >>>> >>>> 2008-11-28 11:51:13,818 ERROR >>>> [org.jboss.ejb.plugins.LogInterceptor] >>>> EJBException in method: public abstract void >>>> org.ejbca.core.ejb.log.IProtectedLogSessionLocal.addProtectedLogEve >>>> n t R ow(org.ejbca.core.model.log.ProtectedLogEventRow), >>>> causedBy: >>>> >>>> javax.ejb.CreateException: Error checking if entity >>>> exists:org.jboss.util.NestedSQLException: No ManagedConnections >>>> available within configured blocking timeout ( 30000 [ms] ); - >>>> nested >>>> throwable: (javax.resource.ResourceException: No ManagedConnections >>>> available within configured blocking timeout ( 30000 [ms] )) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand.beforeInse >>>> r >>>> t >>>> ( >>>> JDBCInsertPKCreateCommand.java:105) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractCreateCommand.execute(JD >>>> B >>>> C >>>> A >>>> bstractCreateCommand.java:150) >>>> >>>> 2008-11-28 11:51:25,991 ERROR >>>> [org.ejbca.core.ejb.log.LogSessionSession] Error creating new log >>>> configuration data for caid 0. >>>> >>>> javax.ejb.DuplicateKeyException: Entity with primary key 0 already >>>> exists >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand.beforeInse >>>> r >>>> t >>>> ( >>>> JDBCInsertPKCreateCommand.java:99) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractCreateCommand.execute(JD >>>> B >>>> C >>>> A >>>> bstractCreateCommand.java:150) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.createEntity(JDBCSt >>>> o >>>> r >>>> e >>>> Manager.java:587) >>>> >>>> 2008-11-28 11:51:26,980 ERROR >>>> [org.jboss.ejb.plugins.LogInterceptor] >>>> EJBException in method: public abstract void >>>> org.ejbca.core.ejb.log.ILogSessionLocal.doSyncronizedLog(org.ejbca. >>>> c >>>> o >>>> r >>>> e.model.log.ILogDevice,org.ejbca.core.model.log.Admin,int,int,java. >>>> u >>>> t >>>> i >>>> l.Date,java.lang.String,java.security.cert.Certificate,int,java.lang. >>>> S >>>> tring,java.lang.Exception), >>>> causedBy: >>>> >>>> javax.ejb.DuplicateKeyException: Entity with primary key 0 already >>>> exists >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand.beforeInse >>>> r >>>> t >>>> ( >>>> JDBCInsertPKCreateCommand.java:99) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractCreateCommand.execute(JD >>>> B >>>> C >>>> A >>>> bstractCreateCommand.java:150) >>>> >>>> at >>>> org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.createEntity(JDBCSt >>>> o >>>> r >>>> e >>>> Manager.java:587) >>>> >>>> Have you got an idea about these errors ? >>>> >>>> thanks >>>> >>>> best regards >>>> >>>> Florent >>>> >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> -- >>>> >>>> Ce message et les pièces jointes sont confidentiels et réservés à >>>> l'usage exclusif de ses destinataires. Il peut également être >>>> protégé par le secret professionnel. Si vous recevez ce message par >>>> erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. >>>> L'intégrité du message ne pouvant être assurée sur Internet, la >>>> responsabilité du groupe Atos Origin ne pourra être recherchée >>>> quant au contenu de ce message. Bien que les meilleurs efforts >>>> soient faits pour maintenir cette transmission exempte de tout >>>> virus, l'expéditeur ne donne aucune garantie à cet égard et sa >>>> responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. >>>> >>>> This e-mail and the documents attached are confidential and >>>> intended solely for the addressee; it may also be privileged. If >>>> you receive this e-mail in error, please notify the sender >>>> immediately and destroy it. As its integrity cannot be secured on >>>> the Internet, the Atos Origin group liability cannot be triggered for the message content. >>>> Although the sender endeavours to maintain a computer virus-free >>>> network, the sender does not warrant that this transmission is >>>> virus-free and will not be liable for any damages resulting from >>>> any virus transmitted. >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> -- >>>> >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> --- This SF.Net email is sponsored by the Moblin Your Move >>>> Developer's challenge Build the coolest Linux based applications >>>> with Moblin SDK & win great prizes Grand prize is a trip for two to >>>> an Open Source event anywhere in the world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> ------------------------------------------------------------------- >>>> - >>>> - >>>> - >>>> -- >>>> >>>> _______________________________________________ >>>> Ejbca-develop mailing list >>>> Ejb...@li... >>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >>>> >>>> >>>> >>>> >>> -- >>> PrimeKey Solutions offers a commercial EJBCA support subscription >>> and training for EJBCA. Please see www.primekey.se or contact >>> in...@pr... for more information. >>> http://download.primekey.se/documents/ejbca_subscription.pdf >>> http://download.primekey.se/documents/ejbca_training.pdf >>> >>> >>> >>> >>> >>> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. >>> >>> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. >>> >>> >>> -------------------------------------------------------------------- >>> - >>> - >>> --- This SF.Net email is sponsored by the Moblin Your Move >>> Developer's challenge Build the coolest Linux based applications >>> with Moblin SDK & win great prizes Grand prize is a trip for two to >>> an Open Source event anywhere in the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> Ejbca-develop mailing list >>> Ejb...@li... >>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >>> >>> >>> >> -- >> PrimeKey Solutions offers a commercial EJBCA support subscription and >> training for EJBCA. Please see www.primekey.se or contact >> in...@pr... for more information. >> http://download.primekey.se/documents/ejbca_subscription.pdf >> http://download.primekey.se/documents/ejbca_training.pdf >> >> >> >> >> >> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. >> >> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. >> >> >> --------------------------------------------------------------------- >> - >> --- This SF.Net email is sponsored by the Moblin Your Move >> Developer's challenge Build the coolest Linux based applications with >> Moblin SDK & win great prizes Grand prize is a trip for two to an >> Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Ejbca-develop mailing list >> Ejb...@li... >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> >> > > > -- > PrimeKey Solutions offers a commercial EJBCA support subscription and > training for EJBCA. Please see www.primekey.se or contact > in...@pr... for more information. > http://download.primekey.se/documents/ejbca_subscription.pdf > http://download.primekey.se/documents/ejbca_training.pdf > > > > > > Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. > > > ---------------------------------------------------------------------- > --- This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & > win great prizes Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > -- PrimeKey Solutions offers a commercial EJBCA support subscription and training for EJBCA. Please see www.primekey.se or contact in...@pr... for more information. http://download.primekey.se/documents/ejbca_subscription.pdf http://download.primekey.se/documents/ejbca_training.pdf Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. |