Attached are two subsets extracted from JBoss log that I had encountered while trying to execute the script - install ./configPhase3.sh and started using the application of the RC-1 release on our new environment. It seems that the problem is related to TRIM data files. If I start using the application, it seems that it causes some more errors
Can you provide some hints ? Thank you in advance.
First set of error log received when executing ./configPhase3.sh
2009-07-02 10:07:10,380 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-02 10:07:11,517 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-12288 failed with error: Required trim observation not found in Trim Header table
2009-07-02 10:07:11,517 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
Second set of error log generated when using the application
2009-07-02 11:08:21,657 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/Tolven].[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
at org.apache.catalina.connector.Response.getWriter(Response.java:604)
at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186)
at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:117)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Additional notes: I tried to follow the instructions more then twice, errors still happened at the phase 3 with same error messages that were captured in the first set of error log. While the JBoss server is able to be up and accept the user connection but no sample data were displayed (after they have been generated and stored in the data base). Any time I had tried to add any "new" record (.ie. provider, location etc..), nothing was happened...I did not see anything in the jboss log..I would appreciate that if your team can provide some hint so I can move forward..thks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had also found these warning messages on the plugin component - org.tolven.component.jboss
Phase 1 configuration
2009-07-03 18:06:16,269 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:102)
2009-07-03 18:06:16,270 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 105)
2009-07-03 18:06:16,270 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 105)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The following are some WARNING messages received when starting JBoss. It was extracted from ../server/tolven/log/server.log. I wonder whether or not it would affect subsequent processes as described in the previous messages.
2009-07-08 15:17:20,670 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2629463222436228511.war/
2009-07-08 15:17:20,745 WARN [org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
2009-07-08 15:17:21,185 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,764 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,835 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,857 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,864 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,866 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,875 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,882 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,883 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,891 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,898 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,900 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,904 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp2089091749921090515tolven.ear-contents/tolvenTRIMBrowse-exp.war/
2009-07-08 15:17:22,443 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp2089091749921090515tolven.ear-contents/tolvenWEB-exp.war/
2009-07-08 15:17:22,773 INFO [org.tolven.web.ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
2009-07-08 15:17:22,870 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
2009-07-08 15:17:23,000 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
2009-07-08 15:17:23,013 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
2009-07-08 15:17:23,022 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote
HTTP/1.1 on http-0.0.0.0-8443
2009-07-08 15:17:23,033 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 31s:543ms
2009-07-08 15:17:33,130 INFO [org.tolven.security.auth.KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The first error you mentioned:
"Required trim observation not found in Trim Header table"
has nothing to do with the warnings you have subsequently mentioned. I have not been able to reproduce your error, but it does not occur when all the steps in the configuration guide are followed. Therefore, it is likely you missed a step. I would suggest that you go back to the configuration guide, and proceed from "Application Metadata " paying particular attention to all the steps, in the order given. You've probably added all of the necessary entries to tolven-config/plugins.xml, but double check. The other steps can be repeated without harm to ensure that you executed them the first time.
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your reply message. In fact, I have tried the whole process more than 5 times to ensure that I would not miss any thing. After receiving your suggestions, I decided to go through the same exercise again after wiping out the entire database (postgres) so I can start from scratch.
However, after executing the script - configPhase3.sh, I still have the same issue (even before starting Application Metadata Section. Below is the excerpt from the jboss log which lists some ERROR messages I got it today
tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-09 13:50:04,260 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-09 13:50:08,865 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-09 13:50:09,025 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-09 13:50:09,987 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-0 failed with error: Required trim observation not found in Trim Header table
2009-07-09 13:50:09,987 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
I still encountered the same following problems with RC1 after completing the entire procedure as described in the documentation
1. Sample data seems to be generated as indicated in the server log but the GUI does not show them. Which main table is storing these sample patient records (it it the table - "document")
2. No feedback on any NEW action such as adding new patient, new location or new provider.
In summary, none of core functionality is working except for the preference option.
Thanks a lot for your assistance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had seen these warning messages recorded in the jboss log. Do you get the same warning messages on your server log ? Is it critical ?
2009-07-09 13:39:27,600 WARN [org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
2009-07-09 13:39:28,080 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,576 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,659 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,682 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,690 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,691 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,701 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,708 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,710 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,718 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,726 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,728 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,732 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp5254667646496887755tolven.ear-contents/tolvenTRIMBrowse-exp.war/
2009-07-09 13:39:29,225 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp5254667646496887755tolven.ear-contents/tolvenWEB-exp.war/
2009-07-09 13:39:29,560 INFO [org.tolven.web.ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
2009-07-09 13:39:29,628 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trims do not exist in the configuration until the Application Metadata section, because that is where they are introduced. There won't even be trims in the repositoryRuntime at that point for a clean install. I would therefore say that the problem you describe cannot occur for a first install before the Application Metadata section OR you did not clean your environment properly after returning to "start from scratch".
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One other thing I should have added to my previous post for you....when you restarted from scratch, what were the contents of the <config-dir>/repositoryLocal/plugins directory?
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks again for suggestions. I had followed your advices by doing the following:
1. wipe out the entire Postgred - by dropping the database and recreate it
2. wipe out the entive tolven-RC1 directory including the associated tolven-RC1
3. rebuild the openldap environment
4. I have completed the entire configuration process up to the very last step.
and of course I had followed the installation steps very closely, I still received the same outcomes:
1. Some warning message - dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2 - FROM configPhase1
Notes: I am not too sure that it's critical
2. Same error messages when executing the last configPhase 3
Below is the excerpt of the run logs. If you can answer me some fundamental questions about the application behavior that I had encountered when attempting using the application
1. If I chose an new action to add new patient, provider, location, there is no feedback at all. No message was recorded in the JBoss log. The previous version (beta4) did not behave that way. Can it be caused by the issue I had encountered during the installation ?
2. Sample patient data process seems to be processed successfully but I did not see the list of GUI nor in the database..( I am not too sure which table would hold patient record..my guess is the document table as I previously saw in the beta-4 version)
Thank you for your patience with me.
LOGS:
ConfigPhase1
1. From ../log/tolven.log - obtained a warning message
2009-07-10 09:42:37,516 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:112)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 111)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 111)
ConfigPhase2 -- looks good
From ../log/tolven.log
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.component.ldap.init@0.0.1 (active/total: 8 of 111)
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 9 of 111)
10:06:10,299 INFO [PostgresqlInit] *** start ***
10:06:10,299 INFO [PostgresqlInit] Execute SQL file /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql with URL jdbc:postgresql://localhost:5432/postgres?ssl=true
10:06:10,329 INFO [TolvenSQL] About to execute sql /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [SQLExec] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [TolvenSQL] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,412 INFO [SQLExec] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] sql complete
10:06:10,413 INFO [PostgresqlInit] *** end ***
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.postgresql.init@0.0.1 (active/total: 10 of 111)
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.database.init@0.0.1 (active/total: 11 of 111)
10:06:10,414 INFO [TolvenApplication] Successful execution of : org.tolven.component.ldap.init,org.tolven.component.database.init
From JBoss log -- looks good
10:09:12,324 INFO [SunJaxwsDeploymentAspect] Add Endpoint
name=TrimServiceImpl
implementation=org.tolven.ws.trim.TrimServiceImpl
url-pattern=/trim/*
enable-mtom=false
10:09:12,345 INFO [TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2465955049420773516.war/
10:09:12,560 WARN [DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
10:09:13,035 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,619 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,680 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,704 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,712 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,713 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,723 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,729 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,731 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,739 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,746 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,748 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,752 INFO [TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenTRIMBrowse-exp.war/
10:09:14,240 INFO [TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenWEB-exp.war/
10:09:14,633 INFO [ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
10:09:14,690 INFO [EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
10:09:14,880 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
10:09:14,906 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
10:09:14,955 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
10:09:14,963 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 35s:538ms
10:09:24,946 INFO [KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
First ConfigPhase3 -- looks good -- no error
10:23:14,420 INFO [AdminAssembler] MDBUser keystore: /usr/local/medatos/tolven-RC1-config/credentials/mdbuser/tolvendev-mdbuser.p12
10:23:14,513 INFO [TolvenConfigWrapper] Load JSSE keystore for admin
10:23:14,515 INFO [TolvenConfigWrapper] Load JSSE truststore for admin
10:23:14,516 INFO [AdminAssembler] *** end ***
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.assembler.admin@0.0.4 (active/total: 7 of 111)
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.library.jasperreports@0.0.1 (active/total: 8 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.remoteclient@0.0.1 (active/total: 9 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jboss@0.0.1 (active/total: 10 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.tolvenclient@0.0.2 (active/total: 11 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.javaee@0.0.1 (active/total: 12 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 13 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.component.application.jboss@0.0.1 (active/total: 14 of 111)
10:23:14,519 INFO [StandardPluginManager] plug-in started - org.tolven.library.application@0.0.1 (active/total: 15 of 111)
10:23:14,532 INFO [Application] *** start ***
10:23:14,547 INFO [Application] Starting for user: admin to jnp://localhost:1099
10:23:33,797 INFO [Application] Update MDBUser mdbuser
10:23:33,797 INFO [TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
10:23:34,213 INFO [Application] Update MDBUser completed
10:23:34,213 INFO [Application] *** end ***
10:23:34,213 INFO [StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 111)
10:23:34,214 INFO [TolvenApplication] Successful execution of : org.tolven.component.application
Download Application and Trims Metadata
OK
Second ConfigPhase3
2009-07-10 10:38:44,779 INFO [org.tolven.security.auth.KeyLoginModule] login for mdbuser with roles: tolvenWriteGen,tolvenWriteInvitation,tolvenWeb,tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-10 10:38:44,893 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-10 10:38:50,338 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-10 10:38:50,500 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-10 10:38:51,369 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4096 failed with error: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
1. Error messages still happened when executing the configPhase3 (after updating the Metadata)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I posted a specific question on 2009-07-09 16:28....I don't recall seeing the answer to that. Maybe you missed it?
"In addition" to that question:
1. When you executed configPhase3 the second time, what were the contents of repositoryLocal/plugins directory?
2. If there were any contents, were they also in tolven-config/repositoryRuntime/plugins ?
Joe
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for not answering your questions directly. I did follow your advices one more time and wiped out the entire tolven-RC1 and the corresponding tolven-config where repositoryLocal was stored. In addition, I also reset the database server too (dropdb command followed by createdb command).
To answer specifically your questions you had raised. Yes I did see two files that were generated after completing the Meta-data update section (prior to executing configPhase3 - second time). These two files have been generated and stored in both directories (local and runtime)
Please read my previous message posted - 2009-07-10 14:56. If possible, can you please specifically answer my questions listed in that message regarding some symptoms I had encountered after completing the installation.
Your help would be much appreciated. Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks again for suggestions. I had followed your advices by doing the following:
1. wipe out the entire Postgred - by dropping the database and recreate it
2. wipe out the entive tolven-RC1 directory including the associated tolven-RC1
3. rebuild the openldap environment
4. I have completed the entire configuration process up to the very last step.
and of course I had followed the installation steps very closely, I still received the same outcomes:
1. Some warning message - dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2 - FROM configPhase1
Notes: I am not too sure that it's critical
2. Same error messages when executing the last configPhase 3
Below is the excerpt of the run logs. If you can answer me some fundamental questions about the application behavior that I had encountered when attempting using the application
1. If I chose an new action to add new patient, provider, location, there is no feedback at all. No message was recorded in the JBoss log. The previous version (beta4) did not behave that way. Can it be caused by the issue I had encountered during the installation ?
2. Sample patient data process seems to be processed successfully but I did not see the list of GUI nor in the database..( I am not too sure which table would hold patient record..my guess is the document table as I previously saw in the beta-4 version)
Thank you for your patience with me.
LOGS:
ConfigPhase1
1. From ../log/tolven.log - obtained a warning message
2009-07-10 09:42:37,516 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:112)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 111)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 111)
ConfigPhase2 -- looks good
From ../log/tolven.log
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.component.ldap.init@0.0.1 (active/total: 8 of 111)
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 9 of 111)
10:06:10,299 INFO [PostgresqlInit] *** start ***
10:06:10,299 INFO [PostgresqlInit] Execute SQL file /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql with URL jdbc:postgresql://localhost:5432/postgres?ssl=true
10:06:10,329 INFO [TolvenSQL] About to execute sql /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [SQLExec] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [TolvenSQL] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,412 INFO [SQLExec] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] sql complete
10:06:10,413 INFO [PostgresqlInit] *** end ***
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.postgresql.init@0.0.1 (active/total: 10 of 111)
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.database.init@0.0.1 (active/total: 11 of 111)
10:06:10,414 INFO [TolvenApplication] Successful execution of : org.tolven.component.ldap.init,org.tolven.component.database.init
From JBoss log -- looks good
10:09:12,324 INFO [SunJaxwsDeploymentAspect] Add Endpoint
name=TrimServiceImpl
implementation=org.tolven.ws.trim.TrimServiceImpl
url-pattern=/trim/*
enable-mtom=false
10:09:12,345 INFO [TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2465955049420773516.war/
10:09:12,560 WARN [DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
10:09:13,035 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,619 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,680 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,704 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,712 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,713 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,723 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,729 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,731 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,739 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,746 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,748 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,752 INFO [TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenTRIMBrowse-exp.war/
10:09:14,240 INFO [TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenWEB-exp.war/
10:09:14,633 INFO [ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
10:09:14,690 INFO [EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
10:09:14,880 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
10:09:14,906 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
10:09:14,955 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
10:09:14,963 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 35s:538ms
10:09:24,946 INFO [KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
First ConfigPhase3 -- looks good -- no error
10:23:14,420 INFO [AdminAssembler] MDBUser keystore: /usr/local/medatos/tolven-RC1-config/credentials/mdbuser/tolvendev-mdbuser.p12
10:23:14,513 INFO [TolvenConfigWrapper] Load JSSE keystore for admin
10:23:14,515 INFO [TolvenConfigWrapper] Load JSSE truststore for admin
10:23:14,516 INFO [AdminAssembler] *** end ***
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.assembler.admin@0.0.4 (active/total: 7 of 111)
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.library.jasperreports@0.0.1 (active/total: 8 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.remoteclient@0.0.1 (active/total: 9 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jboss@0.0.1 (active/total: 10 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.tolvenclient@0.0.2 (active/total: 11 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.javaee@0.0.1 (active/total: 12 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 13 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.component.application.jboss@0.0.1 (active/total: 14 of 111)
10:23:14,519 INFO [StandardPluginManager] plug-in started - org.tolven.library.application@0.0.1 (active/total: 15 of 111)
10:23:14,532 INFO [Application] *** start ***
10:23:14,547 INFO [Application] Starting for user: admin to jnp://localhost:1099
10:23:33,797 INFO [Application] Update MDBUser mdbuser
10:23:33,797 INFO [TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
10:23:34,213 INFO [Application] Update MDBUser completed
10:23:34,213 INFO [Application] *** end ***
10:23:34,213 INFO [StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 111)
10:23:34,214 INFO [TolvenApplication] Successful execution of : org.tolven.component.application
Download Application and Trims Metadata
OK
Second ConfigPhase3
2009-07-10 10:38:44,779 INFO [org.tolven.security.auth.KeyLoginModule] login for mdbuser with roles: tolvenWriteGen,tolvenWriteInvitation,tolvenWeb,tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-10 10:38:44,893 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-10 10:38:50,338 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-10 10:38:50,500 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-10 10:38:51,369 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4096 failed with error: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
1. Error messages still happened when executing the configPhase3 (after updating the Metadata)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unless you have a typo, there are no messages at 14:56? Try pasting the URL instead
But to complete this thread:
I finally got around to being able to clean out both my database and LDAP, download the JBoss and kit, and carry out the installation and configuration steps. That means I had only the code downloaded from the plugin server, which means the same code as you (I think I have already advised you to get the kit from: http://tolven.org/download/\)
I cannot reproduce the bug. I have not heard or seen any other reports of anyone else seeing the same error as you. If any turn up, they may provide other clues.
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your effort for trying to reproduce the errors. One thing I had noticed that I always downloaded both tolven-RC1.zip and tolven-jboss-4.2.2.GA.zip from Sourceforge. I had found that tolven-RC1.zip downloaded from http://tolven.org/download is not the same as the one downloaded from Sourceforge.net (using the Unix diff command or look at the size). I will try the entire process again this morning and will let you know the outcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can use the following command to determine the version:
. ./tpf.sh -version
Early versions did not recognize this command, but those from 0.0.1 onwards do. But your problem does not appear to be related to even this.
I tested your case with the documentation on the wiki and had no problems for either windows or linux. I use a cut down version of that which also works and is pasted below. It assumes a fresh start i.e. standard plugins.xml as installed. Basically, if you download the kit and install it as I specified, and have JBoss, the database and LDAP installed correctly, executing the commands below in the specified order cannot fail (typos aside :-). So try the commands below, and in particular for your case, wait at the point indicated. The commands are grouped in blocks, and if you have the same paths as those shown, you should be able to copy and paste the group of commands into a shell window altogether and just let them execute as a group. Because I can't detect your particular problem, wait until each block shows no activity in either the tolven.log or the server.log.
# Ensure jdbc driver is set correctly in tolven-config/plugins.xml
#Now ensure that the com.myorg.* and org.tolven.deploy.allergies, org.tolven.deploy.breastproblems etc shown in the Configuration Guide are available in the tolven-config/plugins.xml
./repositoryInit.sh
./configPhase1.sh
#copy credentials as specified in the configuration guide & restart db and ldap
Unfortunately I still ran into the same problems on configPhase3.sh and had followed exactly the same instructions you had posted with the brief version. One of my colleague has tried to follow the instructions posted on wiki, he also encountered the same problems. We have tried in both Unix and Window environments. Without having a basic understanding about the meta-data relationship, it's very hard for us to overcome this problem. None of the core functionality is working as expected. We can step into the code through the debugger but I am not too sure that it would help us to identify the root cause.
Thanks again.
I repost it the latest error recorded in the jboss log I had encountered this evening:
2009-07-12 22:10:55,001 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-12 22:10:55,839 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-0 failed with error: Required trim observation not found in Trim Header table
2009-07-12 22:10:55,839 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK...I think this is some kind of timing issue in the application (assuming that you are only using files which were downloaded). Let's try a proof:
1) Make a backup copy of the trims zip in your repositoryLocal
2) Now remove every file from the zip EXCEPT the observation.trim.xml file
3) Execute the genMetadata command, which you have been doing earlier
4) Now execute configPhase3 to put that single trim in the database
5) Now place your backup (including the same observation file) back in repositoryLocal
6) Execute the genMetadata command, which you have been doing earlier
7) Now execute configPhase3 to put that file in the database
Let me know what happens
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I forgot to add, for the seven step test I just added a little while ago, there is no need to reinstall everything. You can carry out the steps from the point at which the error occurred.
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After following your suggestions to test the theory of timing issue, I still ran into the same problems. It seems that the process of activating trim headers via JMS MDB is failing due to some missing observation entries. Is it possible to identify which observation entry is missing and which table should be checked ? The current count of the table app.trim_header on our database server is 115 (before executing the vocabulary plugins batch process - tpf).
The following is the excerpt extracted from both tolven and jboss logs
1. Load only observation.trim.xml (com.myorg.trims) via configPhase3.sh
From tolven.log
2009-07-13 08:58:06,349 INFO [org.tolven.component.application.Application] Load trims...
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
2009-07-13 08:58:06,350 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/observation.trim.xml
2009-07-13 08:58:06,366 INFO [org.tolven.component.application.Application] Load trims completed
2009-07-13 08:58:06,366 INFO [org.tolven.component.application.Application] *** end ***
2009-07-13 08:58:06,367 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 118)
2009-07-13 08:58:06,367 INFO [org.tolven.command.TolvenApplication] Successful execution of : org.tolven.component.application
From Jboss server.log
2009-07-13 08:58:04,995 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-13 08:58:06,368 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-13 08:58:06,600 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4 failed with error: Required trim observation not found in Trim Header table
2009-07-13 08:58:06,600 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2. Load all trims - com.myorg.trims) via configPhase3.sh after restoring them
From tolven.log
2009-07-13 09:28:01,700 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
2009-07-13 09:28:01,701 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/tumorReceptors.trim.xml
2009-07-13 09:28:01,758 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/pathologyStaging.trim.xml
2009-07-13 09:28:01,764 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastRadiationOccurrence.trim.xml
2009-07-13 09:28:01,769 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastCoreBiopsyProcedure.trim.xml
2009-07-13 09:28:01,779 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/problem.trim.xml
2009-07-13 09:28:01,784 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/boneProcedure.trim.xml
2009-07-13 09:28:01,789 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastLocationVS.trim.xml
2009-07-13 09:28:01,793 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/coreNeedleBiopsyLymphProcedure.trim.xml
From Jboss serve.log
2009-07-13 09:28:02,473 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-13 09:28:02,703 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-6 failed with error: Required trim observation not found in Trim Header table
2009-07-13 09:28:02,703 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
200
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After wiping out the entire database and following your proposed steps to trim down com.myorg.trims-0.0.1.zip on the first pass of configPhase3 to load only observation.trim.xml file, Once the 'observation' entry has been loaded into the app.trim_header table, all the other TRIM entries have been successfully loaded.
It seems that some basic functionality is now working although I still have to spend more time to conduct some more testing. Can you open this as a bug and provide some solution for this issue ? I would not mind to be your QA tester.
Thanks a lot for your help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It appears to be a system-dependent timing issue that most people do not appear to experience. It was one of the other developers who suggested the strip down of the plugin approach, after indicating that he may have seen it once before, but it does not happen for him even now on the same system.
You threw me for a while when you indicated that the steps I proposed had no effect, so I thought it might be something else after all. But it has already been reported, with possibilities for its cause. Once a fix has been released, I will remember to update this thread.
Thanks
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I encountered this issue a couple of times. I thought it's a timing issue, but apparently it is not. Here is what you can do for debugging the configuration
1) Open query tool in pgadmin(or the client application to run query on postgres) run the below command
select * from app.trim_header where name ='observation'
Since the configPhase3 saying it can not find a trim header with name 'observation', you should not see any records returned. If you see a record that'll be an error that we did not noticed yet.
2) Take a backup of the org.tolven.prototype.application.trim-0.0.1.zip under tolven-config\repositoryRuntime\plugins.
3) Extract the zip file to a temporary location and open a file 'observation.trim.xml'. Open a file observation.trim.xml under 'trim' directory. In this check for a tag <name>(I see this in line 8). It should look like this '<name>observation</name>'. If you see a different value in the <name> tag you are having a different set of trims(atleast one) other than trims from catalog.
Let me know.
-Srini.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I encountered this issue a couple of times. I thought it's a timing issue, but apparently it is not. Here is what you can do for debugging the configuration
1) Open query tool in pgadmin(or the client application to run query on postgres) run the below command
select * from app.trim_header where name ='observation'
Since the configPhase3 saying it can not find a trim header with name 'observation', you should not see any records returned. If you see a record that'll be an error that we did not noticed yet.
2) Take a backup of the org.tolven.prototype.application.trim-0.0.1.zip under tolven-config\repositoryRuntime\plugins.
3) Extract the zip file to a temporary location and open a file 'observation.trim.xml'. Open a file observation.trim.xml under 'trim' directory. In this check for a tag <name>(I see this in line 8). It should look like this '<name>observation</name>'. If you see a different value in the <name> tag you are having a different set of trims(atleast one) other than trims from catalog.
Let me know.
-Srini.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Support,
Attached are two subsets extracted from JBoss log that I had encountered while trying to execute the script - install ./configPhase3.sh and started using the application of the RC-1 release on our new environment. It seems that the problem is related to TRIM data files. If I start using the application, it seems that it causes some more errors
Can you provide some hints ? Thank you in advance.
First set of error log received when executing ./configPhase3.sh
2009-07-02 10:07:10,380 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-02 10:07:11,517 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-12288 failed with error: Required trim observation not found in Trim Header table
2009-07-02 10:07:11,517 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-02 10:07:11,517 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
2009-07-02 10:07:11,518 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
Second set of error log generated when using the application
2009-07-02 11:08:21,657 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/Tolven].[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
at org.apache.catalina.connector.Response.getWriter(Response.java:604)
at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186)
at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:117)
Additional notes: I tried to follow the instructions more then twice, errors still happened at the phase 3 with same error messages that were captured in the first set of error log. While the JBoss server is able to be up and accept the user connection but no sample data were displayed (after they have been generated and stored in the data base). Any time I had tried to add any "new" record (.ie. provider, location etc..), nothing was happened...I did not see anything in the jboss log..I would appreciate that if your team can provide some hint so I can move forward..thks
I had also found these warning messages on the plugin component - org.tolven.component.jboss
Phase 1 configuration
2009-07-03 18:06:16,269 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:102)
2009-07-03 18:06:16,270 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 105)
2009-07-03 18:06:16,270 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 105)
The following are some WARNING messages received when starting JBoss. It was extracted from ../server/tolven/log/server.log. I wonder whether or not it would affect subsequent processes as described in the previous messages.
2009-07-08 15:17:20,670 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2629463222436228511.war/
2009-07-08 15:17:20,745 WARN [org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
2009-07-08 15:17:21,185 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,764 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,835 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,857 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,864 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,866 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,875 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,882 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,883 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,891 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-08 15:17:21,898 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-08 15:17:21,900 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-08 15:17:21,904 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp2089091749921090515tolven.ear-contents/tolvenTRIMBrowse-exp.war/
2009-07-08 15:17:22,443 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp2089091749921090515tolven.ear-contents/tolvenWEB-exp.war/
2009-07-08 15:17:22,773 INFO [org.tolven.web.ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
2009-07-08 15:17:22,870 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
2009-07-08 15:17:23,000 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
2009-07-08 15:17:23,013 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
2009-07-08 15:17:23,022 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote
HTTP/1.1 on http-0.0.0.0-8443
2009-07-08 15:17:23,033 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 31s:543ms
2009-07-08 15:17:33,130 INFO [org.tolven.security.auth.KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
The first error you mentioned:
"Required trim observation not found in Trim Header table"
has nothing to do with the warnings you have subsequently mentioned. I have not been able to reproduce your error, but it does not occur when all the steps in the configuration guide are followed. Therefore, it is likely you missed a step. I would suggest that you go back to the configuration guide, and proceed from "Application Metadata " paying particular attention to all the steps, in the order given. You've probably added all of the necessary entries to tolven-config/plugins.xml, but double check. The other steps can be repeated without harm to ensure that you executed them the first time.
Joe
Joe,
Thanks for your reply message. In fact, I have tried the whole process more than 5 times to ensure that I would not miss any thing. After receiving your suggestions, I decided to go through the same exercise again after wiping out the entire database (postgres) so I can start from scratch.
However, after executing the script - configPhase3.sh, I still have the same issue (even before starting Application Metadata Section. Below is the excerpt from the jboss log which lists some ERROR messages I got it today
tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-09 13:50:04,260 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-09 13:50:08,865 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-09 13:50:09,025 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-09 13:50:09,987 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-0 failed with error: Required trim observation not found in Trim Header table
2009-07-09 13:50:09,987 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-09 13:50:09,987 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
I still encountered the same following problems with RC1 after completing the entire procedure as described in the documentation
1. Sample data seems to be generated as indicated in the server log but the GUI does not show them. Which main table is storing these sample patient records (it it the table - "document")
2. No feedback on any NEW action such as adding new patient, new location or new provider.
In summary, none of core functionality is working except for the preference option.
Thanks a lot for your assistance.
I had seen these warning messages recorded in the jboss log. Do you get the same warning messages on your server log ? Is it critical ?
2009-07-09 13:39:27,600 WARN [org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
2009-07-09 13:39:28,080 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,576 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,659 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,682 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,690 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,691 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,701 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,708 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,710 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,718 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
2009-07-09 13:39:28,726 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
2009-07-09 13:39:28,728 WARN [org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
2009-07-09 13:39:28,732 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp5254667646496887755tolven.ear-contents/tolvenTRIMBrowse-exp.war/
2009-07-09 13:39:29,225 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp5254667646496887755tolven.ear-contents/tolvenWEB-exp.war/
2009-07-09 13:39:29,560 INFO [org.tolven.web.ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
2009-07-09 13:39:29,628 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
No...this has nothing to do with your issue.
Joe
Trims do not exist in the configuration until the Application Metadata section, because that is where they are introduced. There won't even be trims in the repositoryRuntime at that point for a clean install. I would therefore say that the problem you describe cannot occur for a first install before the Application Metadata section OR you did not clean your environment properly after returning to "start from scratch".
Joe
One other thing I should have added to my previous post for you....when you restarted from scratch, what were the contents of the <config-dir>/repositoryLocal/plugins directory?
Joe
Joe,
Thanks again for suggestions. I had followed your advices by doing the following:
1. wipe out the entire Postgred - by dropping the database and recreate it
2. wipe out the entive tolven-RC1 directory including the associated tolven-RC1
3. rebuild the openldap environment
4. I have completed the entire configuration process up to the very last step.
and of course I had followed the installation steps very closely, I still received the same outcomes:
1. Some warning message - dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2 - FROM configPhase1
Notes: I am not too sure that it's critical
2. Same error messages when executing the last configPhase 3
Below is the excerpt of the run logs. If you can answer me some fundamental questions about the application behavior that I had encountered when attempting using the application
1. If I chose an new action to add new patient, provider, location, there is no feedback at all. No message was recorded in the JBoss log. The previous version (beta4) did not behave that way. Can it be caused by the issue I had encountered during the installation ?
2. Sample patient data process seems to be processed successfully but I did not see the list of GUI nor in the database..( I am not too sure which table would hold patient record..my guess is the document table as I previously saw in the beta-4 version)
Thank you for your patience with me.
LOGS:
ConfigPhase1
1. From ../log/tolven.log - obtained a warning message
2009-07-10 09:42:37,516 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:112)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 111)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 111)
ConfigPhase2 -- looks good
From ../log/tolven.log
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.component.ldap.init@0.0.1 (active/total: 8 of 111)
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 9 of 111)
10:06:10,299 INFO [PostgresqlInit] *** start ***
10:06:10,299 INFO [PostgresqlInit] Execute SQL file /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql with URL jdbc:postgresql://localhost:5432/postgres?ssl=true
10:06:10,329 INFO [TolvenSQL] About to execute sql /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [SQLExec] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [TolvenSQL] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,412 INFO [SQLExec] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] sql complete
10:06:10,413 INFO [PostgresqlInit] *** end ***
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.postgresql.init@0.0.1 (active/total: 10 of 111)
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.database.init@0.0.1 (active/total: 11 of 111)
10:06:10,414 INFO [TolvenApplication] Successful execution of : org.tolven.component.ldap.init,org.tolven.component.database.init
From JBoss log -- looks good
10:09:12,324 INFO [SunJaxwsDeploymentAspect] Add Endpoint
name=TrimServiceImpl
implementation=org.tolven.ws.trim.TrimServiceImpl
url-pattern=/trim/*
enable-mtom=false
10:09:12,345 INFO [TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2465955049420773516.war/
10:09:12,560 WARN [DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
10:09:13,035 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,619 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,680 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,704 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,712 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,713 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,723 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,729 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,731 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,739 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,746 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,748 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,752 INFO [TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenTRIMBrowse-exp.war/
10:09:14,240 INFO [TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenWEB-exp.war/
10:09:14,633 INFO [ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
10:09:14,690 INFO [EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
10:09:14,880 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
10:09:14,906 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
10:09:14,955 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
10:09:14,963 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 35s:538ms
10:09:24,946 INFO [KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
First ConfigPhase3 -- looks good -- no error
10:23:14,420 INFO [AdminAssembler] MDBUser keystore: /usr/local/medatos/tolven-RC1-config/credentials/mdbuser/tolvendev-mdbuser.p12
10:23:14,513 INFO [TolvenConfigWrapper] Load JSSE keystore for admin
10:23:14,515 INFO [TolvenConfigWrapper] Load JSSE truststore for admin
10:23:14,516 INFO [AdminAssembler] *** end ***
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.assembler.admin@0.0.4 (active/total: 7 of 111)
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.library.jasperreports@0.0.1 (active/total: 8 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.remoteclient@0.0.1 (active/total: 9 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jboss@0.0.1 (active/total: 10 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.tolvenclient@0.0.2 (active/total: 11 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.javaee@0.0.1 (active/total: 12 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 13 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.component.application.jboss@0.0.1 (active/total: 14 of 111)
10:23:14,519 INFO [StandardPluginManager] plug-in started - org.tolven.library.application@0.0.1 (active/total: 15 of 111)
10:23:14,532 INFO [Application] *** start ***
10:23:14,547 INFO [Application] Starting for user: admin to jnp://localhost:1099
10:23:33,797 INFO [Application] Update MDBUser mdbuser
10:23:33,797 INFO [TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
10:23:34,213 INFO [Application] Update MDBUser completed
10:23:34,213 INFO [Application] *** end ***
10:23:34,213 INFO [StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 111)
10:23:34,214 INFO [TolvenApplication] Successful execution of : org.tolven.component.application
Download Application and Trims Metadata
OK
Second ConfigPhase3
2009-07-10 10:38:44,779 INFO [org.tolven.security.auth.KeyLoginModule] login for mdbuser with roles: tolvenWriteGen,tolvenWriteInvitation,tolvenWeb,tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-10 10:38:44,893 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-10 10:38:50,338 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-10 10:38:50,500 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-10 10:38:51,369 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4096 failed with error: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
1. Error messages still happened when executing the configPhase3 (after updating the Metadata)
I posted a specific question on 2009-07-09 16:28....I don't recall seeing the answer to that. Maybe you missed it?
"In addition" to that question:
1. When you executed configPhase3 the second time, what were the contents of repositoryLocal/plugins directory?
2. If there were any contents, were they also in tolven-config/repositoryRuntime/plugins ?
Joe
Joe
Joe,
Sorry for not answering your questions directly. I did follow your advices one more time and wiped out the entire tolven-RC1 and the corresponding tolven-config where repositoryLocal was stored. In addition, I also reset the database server too (dropdb command followed by createdb command).
To answer specifically your questions you had raised. Yes I did see two files that were generated after completing the Meta-data update section (prior to executing configPhase3 - second time). These two files have been generated and stored in both directories (local and runtime)
from ../tolven-RC1-config/repositoryLocal
-rw-r--r-- 1 root root 48633 Jul 10 10:26 com.myorg.applications-0.0.1.zip
-rw-r--r-- 1 root root 131815 Jul 10 10:27 com.myorg.trims-0.0.1.zip
===
From ../tolven-RC1-config/repositoryRuntime/plugins
=========================================
-rw-r--r-- 1 root root 131815 Jul 10 10:38 com.myorg.trims-0.0.1.zip
-rw-r--r-- 1 root root 48633 Jul 10 10:38 com.myorg.applications-0.0.1.zip
Please read my previous message posted - 2009-07-10 14:56. If possible, can you please specifically answer my questions listed in that message regarding some symptoms I had encountered after completing the installation.
Your help would be much appreciated. Thanks again.
Joe,
Thanks again for suggestions. I had followed your advices by doing the following:
1. wipe out the entire Postgred - by dropping the database and recreate it
2. wipe out the entive tolven-RC1 directory including the associated tolven-RC1
3. rebuild the openldap environment
4. I have completed the entire configuration process up to the very last step.
and of course I had followed the installation steps very closely, I still received the same outcomes:
1. Some warning message - dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2 - FROM configPhase1
Notes: I am not too sure that it's critical
2. Same error messages when executing the last configPhase 3
Below is the excerpt of the run logs. If you can answer me some fundamental questions about the application behavior that I had encountered when attempting using the application
1. If I chose an new action to add new patient, provider, location, there is no feedback at all. No message was recorded in the JBoss log. The previous version (beta4) did not behave that way. Can it be caused by the issue I had encountered during the installation ?
2. Sample patient data process seems to be processed successfully but I did not see the list of GUI nor in the database..( I am not too sure which table would hold patient record..my guess is the document table as I previously saw in the beta-4 version)
Thank you for your patience with me.
LOGS:
ConfigPhase1
1. From ../log/tolven.log - obtained a warning message
2009-07-10 09:42:37,516 WARN [org.java.plugin.standard.StandardPluginManager] dependencies loop detected during activation of plug-in {PluginDescriptor: uid=org.tolven.component.jboss@0.0.2}
java.lang.Exception: fake exception to view stack trace
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:436)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.checkPrerequisites(StandardPluginManager.java:469)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:397)
at org.java.plugin.standard.StandardPluginManager.activatePlugin(StandardPluginManager.java:245)
at org.tolven.command.TolvenApplication.startRequiredPlugins(TolvenApplication.java:87)
at org.tolven.command.TolvenApplication.startApplication(TolvenApplication.java:56)
at org.java.plugin.boot.Boot.boot(Boot.java:346)
at org.java.plugin.boot.Boot.main(Boot.java:243)
at org.tolven.plugin.boot.TPFBoot.main(TPFBoot.java:112)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 21 of 111)
2009-07-10 09:42:37,517 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.tomcatserver@0.0.1 (active/total: 22 of 111)
ConfigPhase2 -- looks good
From ../log/tolven.log
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.component.ldap.init@0.0.1 (active/total: 8 of 111)
10:06:10,297 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 9 of 111)
10:06:10,299 INFO [PostgresqlInit] *** start ***
10:06:10,299 INFO [PostgresqlInit] Execute SQL file /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql with URL jdbc:postgresql://localhost:5432/postgres?ssl=true
10:06:10,329 INFO [TolvenSQL] About to execute sql /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [SQLExec] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,368 INFO [TolvenSQL] Executing resource: /usr/local/medatos/tolven-RC1-config/build/temp/.jpf-shadow/org.tolven.component.postgresql.init@0.0.1/pre-appserver-initialization.sql
10:06:10,412 INFO [SQLExec] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] 20 of 20 SQL statements executed successfully
10:06:10,413 INFO [TolvenSQL] sql complete
10:06:10,413 INFO [PostgresqlInit] *** end ***
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.postgresql.init@0.0.1 (active/total: 10 of 111)
10:06:10,413 INFO [StandardPluginManager] plug-in started - org.tolven.component.database.init@0.0.1 (active/total: 11 of 111)
10:06:10,414 INFO [TolvenApplication] Successful execution of : org.tolven.component.ldap.init,org.tolven.component.database.init
From JBoss log -- looks good
10:09:12,324 INFO [SunJaxwsDeploymentAspect] Add Endpoint
name=TrimServiceImpl
implementation=org.tolven.ws.trim.TrimServiceImpl
url-pattern=/trim/*
enable-mtom=false
10:09:12,345 INFO [TomcatDeployer] deploy, ctxPath=/ws, warUrl=.../tmp/deploy/tolven.ear-tolvenWS.jar2465955049420773516.war/
10:09:12,560 WARN [DeploymentDescriptorParserExt] bypass collectDocs(), it doesnt work for EJB endpoints
10:09:13,035 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,619 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,680 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,704 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,712 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,713 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,723 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,729 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,731 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,739 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.ResourceLoader
10:09:13,746 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.api.pipe.TubelineAssemblerFactory
10:09:13,748 WARN [RuntimeModelDeploymentAspect] Unable to resolve SPI for type: class com.sun.xml.ws.assembler.ServerPipelineHook
10:09:13,752 INFO [TomcatDeployer] deploy, ctxPath=/trimBrowse, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenTRIMBrowse-exp.war/
10:09:14,240 INFO [TomcatDeployer] deploy, ctxPath=/Tolven, warUrl=.../tmp/deploy/tmp4458618097063899892tolven.ear-contents/tolvenWEB-exp.war/
10:09:14,633 INFO [ConfigureListener] ### INFO ### WEB TIER INJECTION NOT IN OPERATION
10:09:14,690 INFO [EARDeployer] Started J2EE application: file:/usr/local/medatos/tolven-jboss-4.2.2.GA/server/tolven/deploy/tolven.ear
10:09:14,880 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
10:09:14,906 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
10:09:14,955 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
10:09:14,963 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 35s:538ms
10:09:24,946 INFO [KeyLoginModule] login for tolvenGuest with roles: tolvenDemoRegister,tolvenWriteInvitation,tolvenRegister
First ConfigPhase3 -- looks good -- no error
10:23:14,420 INFO [AdminAssembler] MDBUser keystore: /usr/local/medatos/tolven-RC1-config/credentials/mdbuser/tolvendev-mdbuser.p12
10:23:14,513 INFO [TolvenConfigWrapper] Load JSSE keystore for admin
10:23:14,515 INFO [TolvenConfigWrapper] Load JSSE truststore for admin
10:23:14,516 INFO [AdminAssembler] *** end ***
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.assembler.admin@0.0.4 (active/total: 7 of 111)
10:23:14,516 INFO [StandardPluginManager] plug-in started - org.tolven.library.jasperreports@0.0.1 (active/total: 8 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.remoteclient@0.0.1 (active/total: 9 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jboss@0.0.1 (active/total: 10 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.tolvenclient@0.0.2 (active/total: 11 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.javaee@0.0.1 (active/total: 12 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.library.jdbcdriver@0.0.1 (active/total: 13 of 111)
10:23:14,517 INFO [StandardPluginManager] plug-in started - org.tolven.component.application.jboss@0.0.1 (active/total: 14 of 111)
10:23:14,519 INFO [StandardPluginManager] plug-in started - org.tolven.library.application@0.0.1 (active/total: 15 of 111)
10:23:14,532 INFO [Application] *** start ***
10:23:14,547 INFO [Application] Starting for user: admin to jnp://localhost:1099
10:23:33,797 INFO [Application] Update MDBUser mdbuser
10:23:33,797 INFO [TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
10:23:33,797 INFO [TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
10:23:34,213 INFO [Application] Update MDBUser completed
10:23:34,213 INFO [Application] *** end ***
10:23:34,213 INFO [StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 111)
10:23:34,214 INFO [TolvenApplication] Successful execution of : org.tolven.component.application
Download Application and Trims Metadata
OK
Second ConfigPhase3
2009-07-10 10:38:44,779 INFO [org.tolven.security.auth.KeyLoginModule] login for mdbuser with roles: tolvenWriteGen,tolvenWriteInvitation,tolvenWeb,tolvenWriteRule,tolvenMobile,tolvenWS,tolvenBrowse
2009-07-10 10:38:44,893 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-10 10:38:50,338 INFO [org.tolven.security.auth.KeyLoginModule] login for admin with roles: tolvenWriteAdminApp,tolvenAdminAppDLQ,tolvenTrimBrowser,tolvenAdminApp,tolvenTrimUpload,tolvenAdmin
2009-07-10 10:38:50,500 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-10 10:38:51,369 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4096 failed with error: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-10 10:38:51,369 ERROR [STDERR] at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
2009-07-10 10:38:51,370 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
1. Error messages still happened when executing the configPhase3 (after updating the Metadata)
Unless you have a typo, there are no messages at 14:56? Try pasting the URL instead
But to complete this thread:
I finally got around to being able to clean out both my database and LDAP, download the JBoss and kit, and carry out the installation and configuration steps. That means I had only the code downloaded from the plugin server, which means the same code as you (I think I have already advised you to get the kit from: http://tolven.org/download/\)
I cannot reproduce the bug. I have not heard or seen any other reports of anyone else seeing the same error as you. If any turn up, they may provide other clues.
Joe
Joe,
Thanks for your effort for trying to reproduce the errors. One thing I had noticed that I always downloaded both tolven-RC1.zip and tolven-jboss-4.2.2.GA.zip from Sourceforge. I had found that tolven-RC1.zip downloaded from http://tolven.org/download is not the same as the one downloaded from Sourceforge.net (using the Unix diff command or look at the size). I will try the entire process again this morning and will let you know the outcome.
You can use the following command to determine the version:
. ./tpf.sh -version
Early versions did not recognize this command, but those from 0.0.1 onwards do. But your problem does not appear to be related to even this.
I tested your case with the documentation on the wiki and had no problems for either windows or linux. I use a cut down version of that which also works and is pasted below. It assumes a fresh start i.e. standard plugins.xml as installed. Basically, if you download the kit and install it as I specified, and have JBoss, the database and LDAP installed correctly, executing the commands below in the specified order cannot fail (typos aside :-). So try the commands below, and in particular for your case, wait at the point indicated. The commands are grouped in blocks, and if you have the same paths as those shown, you should be able to copy and paste the group of commands into a shell window altogether and just let them execute as a group. Because I can't detect your particular problem, wait until each block shows no activity in either the tolven.log or the server.log.
# Ensure jdbc driver is set correctly in tolven-config/plugins.xml
. ./tpfenv.sh
./repositoryInit.sh
./copyplugin.sh -src http://tolven.org/download -srcId org.tolven.prototype.applications -dest /usr/local/tolven-config/repositoryLocal/plugins -destId com.myorg.applications
./copyplugin.sh -src http://tolven.org/download -srcId org.tolven.prototype.application.trim -dest /usr/local/tolven-config/repositoryLocal/plugins -destId com.myorg.trims
./genMetadata.sh -plugins /usr/local/tolven-config/repositoryLocal/plugins -liburl file:///usr/local/tolven-config/repositoryLocal -outdir /usr/local/tolven-config/repositoryLocal
#Now ensure that the com.myorg.* and org.tolven.deploy.allergies, org.tolven.deploy.breastproblems etc shown in the Configuration Guide are available in the tolven-config/plugins.xml
./repositoryInit.sh
./configPhase1.sh
#copy credentials as specified in the configuration guide & restart db and ldap
./configPhase2.sh
#start JBoss
./updateDBIndexes.sh
./tpf.sh -plugin org.tolven.appserverproperties -load
./tpf.sh -plugin org.tolven.passwordrecovery -load
./configPhase3.sh
# Wait for server.log activity to cease
./plugin.sh -plugin org.tolven.deploy.breastproblems
./plugin.sh -plugin org.tolven.deploy.diagnoses
./plugin.sh -plugin org.tolven.deploy.immunization
./plugin.sh -plugin org.tolven.deploy.procedures
./plugin.sh -plugin org.tolven.deploy.rxnorm
./plugin.sh -plugin org.tolven.deploy.allergies
Joe,
Unfortunately I still ran into the same problems on configPhase3.sh and had followed exactly the same instructions you had posted with the brief version. One of my colleague has tried to follow the instructions posted on wiki, he also encountered the same problems. We have tried in both Unix and Window environments. Without having a basic understanding about the meta-data relationship, it's very hard for us to overcome this problem. None of the core functionality is working as expected. We can step into the code through the debugger but I am not too sure that it would help us to identify the root cause.
Thanks again.
I repost it the latest error recorded in the jboss log I had encountered this evening:
2009-07-12 22:10:55,001 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-12 22:10:55,839 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-0 failed with error: Required trim observation not found in Trim Header table
2009-07-12 22:10:55,839 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-12 22:10:55,840 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-
OK...I think this is some kind of timing issue in the application (assuming that you are only using files which were downloaded). Let's try a proof:
1) Make a backup copy of the trims zip in your repositoryLocal
2) Now remove every file from the zip EXCEPT the observation.trim.xml file
3) Execute the genMetadata command, which you have been doing earlier
4) Now execute configPhase3 to put that single trim in the database
5) Now place your backup (including the same observation file) back in repositoryLocal
6) Execute the genMetadata command, which you have been doing earlier
7) Now execute configPhase3 to put that file in the database
Let me know what happens
Joe
I forgot to add, for the seven step test I just added a little while ago, there is no need to reinstall everything. You can carry out the steps from the point at which the error occurred.
Joe
Joe,
After following your suggestions to test the theory of timing issue, I still ran into the same problems. It seems that the process of activating trim headers via JMS MDB is failing due to some missing observation entries. Is it possible to identify which observation entry is missing and which table should be checked ? The current count of the table app.trim_header on our database server is 115 (before executing the vocabulary plugins batch process - tpf).
The following is the excerpt extracted from both tolven and jboss logs
1. Load only observation.trim.xml (com.myorg.trims) via configPhase3.sh
From tolven.log
2009-07-13 08:58:06,349 INFO [org.tolven.component.application.Application] Load trims...
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.provider.url=jnp://localhost:1099
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.initial=org.jboss.naming.NamingContextFactory
2009-07-13 08:58:06,349 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
2009-07-13 08:58:06,350 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/observation.trim.xml
2009-07-13 08:58:06,366 INFO [org.tolven.component.application.Application] Load trims completed
2009-07-13 08:58:06,366 INFO [org.tolven.component.application.Application] *** end ***
2009-07-13 08:58:06,367 INFO [org.java.plugin.standard.StandardPluginManager] plug-in started - org.tolven.component.application@0.0.1 (active/total: 16 of 118)
2009-07-13 08:58:06,367 INFO [org.tolven.command.TolvenApplication] Successful execution of : org.tolven.component.application
From Jboss server.log
2009-07-13 08:58:04,995 INFO [org.tolven.security.auth.KeyLoginModule] logout for mdbuser
2009-07-13 08:58:06,368 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-13 08:58:06,600 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-4 failed with error: Required trim observation not found in Trim Header table
2009-07-13 08:58:06,600 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 08:58:06,601 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2. Load all trims - com.myorg.trims) via configPhase3.sh after restoring them
From tolven.log
2009-07-13 09:28:01,700 INFO [org.tolven.client.TolvenClient] jndi: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
2009-07-13 09:28:01,701 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/tumorReceptors.trim.xml
2009-07-13 09:28:01,758 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/pathologyStaging.trim.xml
2009-07-13 09:28:01,764 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastRadiationOccurrence.trim.xml
2009-07-13 09:28:01,769 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastCoreBiopsyProcedure.trim.xml
2009-07-13 09:28:01,779 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/problem.trim.xml
2009-07-13 09:28:01,784 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/boneProcedure.trim.xml
2009-07-13 09:28:01,789 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/breastLocationVS.trim.xml
2009-07-13 09:28:01,793 INFO [org.tolven.client.load.LoadTRIM] Load TRIM: /usr/local/tolven-config/build/temp/.jpf-shadow/com.myorg.trims@0.0.1/trim/coreNeedleBiopsyLymphProcedure.trim.xml
From Jboss serve.log
2009-07-13 09:28:02,473 INFO [org.tolven.app.bean.TrimBean] Activating Trim Headers...
2009-07-13 09:28:02,703 INFO [org.tolven.app.bean.AdminAppMDB] Message ID:JBM-6 failed with error: Required trim observation not found in Trim Header table
2009-07-13 09:28:02,703 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: Required trim observation not found in Trim Header table
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2009-07-13 09:28:02,703 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
200
Joe,
After wiping out the entire database and following your proposed steps to trim down com.myorg.trims-0.0.1.zip on the first pass of configPhase3 to load only observation.trim.xml file, Once the 'observation' entry has been loaded into the app.trim_header table, all the other TRIM entries have been successfully loaded.
It seems that some basic functionality is now working although I still have to spend more time to conduct some more testing. Can you open this as a bug and provide some solution for this issue ? I would not mind to be your QA tester.
Thanks a lot for your help
It appears to be a system-dependent timing issue that most people do not appear to experience. It was one of the other developers who suggested the strip down of the plugin approach, after indicating that he may have seen it once before, but it does not happen for him even now on the same system.
You threw me for a while when you indicated that the steps I proposed had no effect, so I thought it might be something else after all. But it has already been reported, with possibilities for its cause. Once a fix has been released, I will remember to update this thread.
Thanks
Joe
I encountered this issue a couple of times. I thought it's a timing issue, but apparently it is not. Here is what you can do for debugging the configuration
1) Open query tool in pgadmin(or the client application to run query on postgres) run the below command
select * from app.trim_header where name ='observation'
Since the configPhase3 saying it can not find a trim header with name 'observation', you should not see any records returned. If you see a record that'll be an error that we did not noticed yet.
2) Take a backup of the org.tolven.prototype.application.trim-0.0.1.zip under tolven-config\repositoryRuntime\plugins.
3) Extract the zip file to a temporary location and open a file 'observation.trim.xml'. Open a file observation.trim.xml under 'trim' directory. In this check for a tag <name>(I see this in line 8). It should look like this '<name>observation</name>'. If you see a different value in the <name> tag you are having a different set of trims(atleast one) other than trims from catalog.
Let me know.
-Srini.
I encountered this issue a couple of times. I thought it's a timing issue, but apparently it is not. Here is what you can do for debugging the configuration
1) Open query tool in pgadmin(or the client application to run query on postgres) run the below command
select * from app.trim_header where name ='observation'
Since the configPhase3 saying it can not find a trim header with name 'observation', you should not see any records returned. If you see a record that'll be an error that we did not noticed yet.
2) Take a backup of the org.tolven.prototype.application.trim-0.0.1.zip under tolven-config\repositoryRuntime\plugins.
3) Extract the zip file to a temporary location and open a file 'observation.trim.xml'. Open a file observation.trim.xml under 'trim' directory. In this check for a tag <name>(I see this in line 8). It should look like this '<name>observation</name>'. If you see a different value in the <name> tag you are having a different set of trims(atleast one) other than trims from catalog.
Let me know.
-Srini.