The Source for Java Technology Collaboration

Home » java.net Forums » GlassFish » GlassFish

Thread: autodeployment bug, problem with Birt Report Viewer and one suggestion

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 12 - Last Post: Mar 25, 2006 5:15 PM by: vbkraemer
vladperl

Posts: 94
autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 3, 2006 10:20 AM
  Click to reply to this thread Reply

I'm really upset.
For during the month I can't make the Birt Report Viewer to work with GlassFish.
I'm changing GlassFish versions and changing The Birt Report Viewer versions and still stuck.
One time that was problem with security manager(that was fixed later),
other time that was something with database connection and now I just can't make auto deployment.
I want to make custom version of the Birt Report Viewer using JSF 1.2 and the last things from Java EE 5.
I can't do it with Tomcat because the last version of Tomcat doesn't support Java EE 5.
Please help me to make the Birt report viewer(www.eclipse.org/birt) run on the Glassfish.
I have one suggestion.
You have place "popular frameworks and applications running on GlassFish".
It's time to make place "popular frameworks and applications that can't run on GlassFish".

My environment:
Windows XP
Build 39

server.log:
[#|2006-03-03T12:23:16.651-0500|WARNING|sun-appserver-pe9.0|javax.enterprise.tools.launcher|_ThreadID=10;_ThreadName=main;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]

[#|2006-03-03T12:23:16.666-0500|INFO|sun-appserver-pe9.0|javax.enterprise.tools.launcher|_ThreadID=10;_ThreadName=main;|
C:/Program Files/Java/jdk1.5.0_06/jre/..\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/glassfish/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/glassfish/lib/endorsed
-Djava.security.policy=C:/glassfish/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/glassfish/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/glassfish/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/glassfish/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_06/jre/../jre/lib/ext;C:/glassfish/domains/domain1/lib/ext;C:/glassfish/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar,struts.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/glassfish/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,%MFWK_HOME%/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/glassfish/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,%MFWK_HOME%/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Program Files/Java/jdk1.5.0_06/jre/../lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/glassfish/imq/lib/jaxm-api.jar,C:/glassfish/imq/lib/fscontext.jar,C:/glassfish/imq/lib/imqbroker.jar,C:/glassfish/imq/lib/imqjmx.jar,C:/glassfish/imq/lib/imqxm.jar,C:/glassfish/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/glassfish/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help
-Dcom.sun.aas.classloader.serverClassPath=C:/glassfish/lib/install/applications/jmsra/imqjmsra.jar,C:/glassfish/imq/lib/jaxm-api.jar,C:/glassfish/imq/lib/fscontext.jar,C:/glassfish/imq/lib/imqbroker.jar,C:/glassfish/imq/lib/imqjmx.jar,C:/glassfish/lib/ant/lib/ant.jar,C:/glassfish/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/glassfish/config
-Djava.library.path=C:\glassfish\lib;C:\glassfish\lib;C:\Program Files\Java\jdk1.5.0_06\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\glassfish\lib;C:\glassfish\bin;C:\glassfish\bin;C:\glassfish\lib;D:\SPS\app\xptc\bin;C:\Perl\bin\;C:\Program Files\Borland\Delphi7\Bin;C:\Program Files\Borland\Delphi7\Projects\Bpl\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0_06\bin;C:\apache-ant-1.6.5\bin;C:\glassfish\bin;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\Common Files\Adobe\AGL;C:\Program Files\SSH Communications Security\SSH Secure Shell
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/glassfish
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/glassfish/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]

[#|2006-03-03T12:23:18.229-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5098: AS Socket Service Initialization has been completed.|#]

[#|2006-03-03T12:23:19.120-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]

[#|2006-03-03T12:23:20.479-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2006-03-03T12:23:20.573-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]

[#|2006-03-03T12:23:22.995-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]

[#|2006-03-03T12:23:23.729-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://itsystem-1-2.midwood.doctorlevit.com:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://itsystem-1-2.midwood.doctorlevit.com:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]

[#|2006-03-03T12:23:23.729-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]

[#|2006-03-03T12:23:23.745-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|autoDeployment status dir missing, creating a new one|#]

[#|2006-03-03T12:23:23.776-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Selecting file C:\glassfish\lib\install\applications\MEjbApp.ear for autodeployment.|#]

[#|2006-03-03T12:23:25.432-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed with moduleid = MEjbApp|#]

[#|2006-03-03T12:23:25.620-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:25.667-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:25.667-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Successfully autodeployed : C:\glassfish\lib\install\applications\MEjbApp.ear.|#]

[#|2006-03-03T12:23:25.682-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Selecting file C:\glassfish\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]

[#|2006-03-03T12:23:30.417-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed with moduleid = __ejb_container_timer_app|#]

[#|2006-03-03T12:23:30.542-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:30.589-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:30.589-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Successfully autodeployed : C:\glassfish\lib\install\applications\__ejb_container_timer_app.ear.|#]

[#|2006-03-03T12:23:30.589-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Selecting file C:\glassfish\lib\install\applications\__JWSappclients.ear for autodeployment.|#]

[#|2006-03-03T12:23:30.979-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed with moduleid = __JWSappclients|#]

[#|2006-03-03T12:23:31.042-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:31.073-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;success;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

[#|2006-03-03T12:23:31.073-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy] Successfully autodeployed : C:\glassfish\lib\install\applications\__JWSappclients.ear.|#]

[#|2006-03-03T12:23:31.120-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|SMGT0007: Self Management Rules service is enabled|#]

[#|2006-03-03T12:23:31.135-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]

[#|2006-03-03T12:24:13.855-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\SimpleExportDataDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:13.855-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\SimpleExportDataDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/SimpleExportDataDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/SimpleExportDataDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/SimpleExportDataDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/SimpleExportDataDialogFragment)|#]

[#|2006-03-03T12:24:13.855-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\SimpleExportDataDialogFragment.class.|#]

[#|2006-03-03T12:24:13.871-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExceptionDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:13.871-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExceptionDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExceptionDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExceptionDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExceptionDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExceptionDialogFragment)|#]

[#|2006-03-03T12:24:13.871-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExceptionDialogFragment.class.|#]

[#|2006-03-03T12:24:13.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\EngineFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:13.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\EngineFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/EngineFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/EngineFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/EngineFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/EngineFragment)|#]

[#|2006-03-03T12:24:13.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\EngineFragment.class.|#]

[#|2006-03-03T12:24:13.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\servlet\ViewerServlet.class for autodeployment.|#]

[#|2006-03-03T12:24:13.902-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\servlet\ViewerServlet.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/servlet/ViewerServlet (wrong name: org/eclipse/birt/report/viewer/servlet/ViewerServlet) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/servlet/ViewerServlet (wrong name: org/eclipse/birt/report/viewer/servlet/ViewerServlet)|#]

[#|2006-03-03T12:24:13.902-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\servlet\ViewerServlet.class.|#]

[#|2006-03-03T12:24:13.949-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis-ant.jar for autodeployment.|#]

[#|2006-03-03T12:24:13.965-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@16a5bcb;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@16a5bcb"|#]

[#|2006-03-03T12:24:13.965-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis-ant.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis-ant.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis-ant.jar|#]

[#|2006-03-03T12:24:13.980-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis-ant.jar.|#]

[#|2006-03-03T12:24:13.996-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\chart-engine.jar for autodeployment.|#]

[#|2006-03-03T12:24:14.105-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@1f5d699;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@1f5d699"|#]

[#|2006-03-03T12:24:14.105-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\chart-engine.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\chart-engine.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\chart-engine.jar|#]

[#|2006-03-03T12:24:14.105-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\chart-engine.jar.|#]

[#|2006-03-03T12:24:14.121-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterGroupFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:14.121-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterGroupFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ParameterGroupFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ParameterGroupFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ParameterGroupFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ParameterGroupFragment)|#]

[#|2006-03-03T12:24:14.121-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterGroupFragment.class.|#]

[#|2006-03-03T12:24:14.137-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ParameterDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:14.137-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ParameterDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ParameterDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ParameterDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ParameterDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ParameterDialogFragment)|#]

[#|2006-03-03T12:24:14.152-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ParameterDialogFragment.class.|#]

[#|2006-03-03T12:24:14.168-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis.jar for autodeployment.|#]

[#|2006-03-03T12:24:14.371-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@753c22;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@753c22"|#]

[#|2006-03-03T12:24:14.371-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis.jar|#]

[#|2006-03-03T12:24:14.371-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\axis.jar.|#]

[#|2006-03-03T12:24:14.371-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ScalarParameterBean.class for autodeployment.|#]

[#|2006-03-03T12:24:14.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ScalarParameterBean.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ScalarParameterBean (wrong name: org/eclipse/birt/report/viewer/bean/ScalarParameterBean) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ScalarParameterBean (wrong name: org/eclipse/birt/report/viewer/bean/ScalarParameterBean)|#]

[#|2006-03-03T12:24:14.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ScalarParameterBean.class.|#]

[#|2006-03-03T12:24:14.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\model.jar for autodeployment.|#]

[#|2006-03-03T12:24:14.840-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@40f3c1;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@40f3c1"|#]

[#|2006-03-03T12:24:14.840-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\model.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\model.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\model.jar|#]

[#|2006-03-03T12:24:14.855-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\model.jar.|#]

[#|2006-03-03T12:24:14.871-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\wsdl4j-1.5.1.jar for autodeployment.|#]

[#|2006-03-03T12:24:14.887-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@5e6a13;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@5e6a13"|#]

[#|2006-03-03T12:24:14.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\wsdl4j-1.5.1.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\wsdl4j-1.5.1.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\wsdl4j-1.5.1.jar|#]

[#|2006-03-03T12:24:14.887-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\wsdl4j-1.5.1.jar.|#]

[#|2006-03-03T12:24:14.902-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportContentFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:14.902-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportContentFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/ReportContentFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/ReportContentFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/ReportContentFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/ReportContentFragment)|#]

[#|2006-03-03T12:24:14.918-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportContentFragment.class.|#]

[#|2006-03-03T12:24:14.933-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\PreviewFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:14.933-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\PreviewFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/PreviewFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/PreviewFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/PreviewFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/PreviewFragment)|#]

[#|2006-03-03T12:24:14.980-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\PreviewFragment.class.|#]

[#|2006-03-03T12:24:14.980-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportDataDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:14.980-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportDataDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExportDataDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExportDataDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExportDataDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExportDataDialogFragment)|#]

[#|2006-03-03T12:24:14.996-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportDataDialogFragment.class.|#]

[#|2006-03-03T12:24:14.996-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\BaseFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.012-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\BaseFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/BaseFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/BaseFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/BaseFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/BaseFragment)|#]

[#|2006-03-03T12:24:15.012-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\BaseFragment.class.|#]

[#|2006-03-03T12:24:15.027-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterFragmentPage.class for autodeployment.|#]

[#|2006-03-03T12:24:15.027-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterFragmentPage.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ParameterFragmentPage (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ParameterFragmentPage) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ParameterFragmentPage (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ParameterFragmentPage)|#]

[#|2006-03-03T12:24:15.027-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ParameterFragmentPage.class.|#]

[#|2006-03-03T12:24:15.043-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\DocumentFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.043-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\DocumentFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/DocumentFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/DocumentFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/DocumentFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/DocumentFragment)|#]

[#|2006-03-03T12:24:15.058-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\DocumentFragment.class.|#]

[#|2006-03-03T12:24:15.058-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\BaseDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.074-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\BaseDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/BaseDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/BaseDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/BaseDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/BaseDialogFragment)|#]

[#|2006-03-03T12:24:15.074-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\BaseDialogFragment.class.|#]

[#|2006-03-03T12:24:15.074-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportReportDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.090-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportReportDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExportReportDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExportReportDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/ExportReportDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/ExportReportDialogFragment)|#]

[#|2006-03-03T12:24:15.090-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\ExportReportDialogFragment.class.|#]

[#|2006-03-03T12:24:15.090-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\DialogContainerFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.105-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\DialogContainerFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/DialogContainerFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/DialogContainerFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/DialogContainerFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/DialogContainerFragment)|#]

[#|2006-03-03T12:24:15.105-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\DialogContainerFragment.class.|#]

[#|2006-03-03T12:24:15.137-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\engine.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.230-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@1f53293;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@1f53293"|#]

[#|2006-03-03T12:24:15.230-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\engine.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\engine.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\engine.jar|#]

[#|2006-03-03T12:24:15.230-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\engine.jar.|#]

[#|2006-03-03T12:24:15.246-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\FramesetFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.262-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\FramesetFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/FramesetFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/FramesetFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/FramesetFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/FramesetFragment)|#]

[#|2006-03-03T12:24:15.262-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\FramesetFragment.class.|#]

[#|2006-03-03T12:24:15.277-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\saaj.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.277-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@b55c7f;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@b55c7f"|#]

[#|2006-03-03T12:24:15.277-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\saaj.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\saaj.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\saaj.jar|#]

[#|2006-03-03T12:24:15.293-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\saaj.jar.|#]

[#|2006-03-03T12:24:15.308-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\RadioButtonParameterFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.308-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\RadioButtonParameterFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/RadioButtonParameterFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/RadioButtonParameterFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/RadioButtonParameterFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/RadioButtonParameterFragment)|#]

[#|2006-03-03T12:24:15.324-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\RadioButtonParameterFragment.class.|#]

[#|2006-03-03T12:24:15.324-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.340-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/ReportFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/ReportFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/layout/ReportFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/layout/ReportFragment)|#]

[#|2006-03-03T12:24:15.340-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\layout\ReportFragment.class.|#]

[#|2006-03-03T12:24:15.355-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\flute.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.371-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@836869;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@836869"|#]

[#|2006-03-03T12:24:15.371-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\flute.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\flute.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\flute.jar|#]

[#|2006-03-03T12:24:15.371-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\flute.jar.|#]

[#|2006-03-03T12:24:15.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ViewerAttributeBean.class for autodeployment.|#]

[#|2006-03-03T12:24:15.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ViewerAttributeBean.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ViewerAttributeBean (wrong name: org/eclipse/birt/report/viewer/bean/ViewerAttributeBean) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ViewerAttributeBean (wrong name: org/eclipse/birt/report/viewer/bean/ViewerAttributeBean)|#]

[#|2006-03-03T12:24:15.387-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ViewerAttributeBean.class.|#]

[#|2006-03-03T12:24:15.402-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.common_2.2.0.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.433-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@b3a5d1;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@b3a5d1"|#]

[#|2006-03-03T12:24:15.433-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.common_2.2.0.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.common_2.2.0.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.common_2.2.0.jar|#]

[#|2006-03-03T12:24:15.433-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.common_2.2.0.jar.|#]

[#|2006-03-03T12:24:15.449-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\jaxrpc.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.449-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@4b62a7;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@4b62a7"|#]

[#|2006-03-03T12:24:15.449-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\jaxrpc.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\jaxrpc.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\jaxrpc.jar|#]

[#|2006-03-03T12:24:15.465-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\jaxrpc.jar.|#]

[#|2006-03-03T12:24:15.465-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\birt-oda.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.480-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@139ef3a;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@139ef3a"|#]

[#|2006-03-03T12:24:15.480-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\birt-oda.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\birt-oda.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\birt-oda.jar|#]

[#|2006-03-03T12:24:15.480-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\birt-oda.jar.|#]

[#|2006-03-03T12:24:15.496-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\sac.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.496-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@88e83d;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@88e83d"|#]

[#|2006-03-03T12:24:15.496-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\sac.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\sac.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\sac.jar|#]

[#|2006-03-03T12:24:15.512-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\sac.jar.|#]

[#|2006-03-03T12:24:15.512-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\PrintDialogFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.512-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\PrintDialogFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/PrintDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/PrintDialogFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/dialog/PrintDialogFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/dialog/PrintDialogFragment)|#]

[#|2006-03-03T12:24:15.543-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\dialog\PrintDialogFragment.class.|#]

[#|2006-03-03T12:24:15.543-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ParameterGroupBean.class for autodeployment.|#]

[#|2006-03-03T12:24:15.543-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ParameterGroupBean.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ParameterGroupBean (wrong name: org/eclipse/birt/report/viewer/bean/ParameterGroupBean) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/bean/ParameterGroupBean (wrong name: org/eclipse/birt/report/viewer/bean/ParameterGroupBean)|#]

[#|2006-03-03T12:24:15.558-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\bean\ParameterGroupBean.class.|#]

[#|2006-03-03T12:24:15.558-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\oda.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.574-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@156e0b4;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@156e0b4"|#]

[#|2006-03-03T12:24:15.574-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\oda.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\oda.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\oda.jar|#]

[#|2006-03-03T12:24:15.574-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\oda.jar.|#]

[#|2006-03-03T12:24:15.590-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\resource\Resources.class for autodeployment.|#]

[#|2006-03-03T12:24:15.590-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\resource\Resources.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/resource/Resources (wrong name: org/eclipse/birt/report/viewer/resource/Resources) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/resource/Resources (wrong name: org/eclipse/birt/report/viewer/resource/Resources)|#]

[#|2006-03-03T12:24:15.605-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\resource\Resources.class.|#]

[#|2006-03-03T12:24:15.605-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.ecore.xmi_2.2.0.jar for autodeployment.|#]

[#|2006-03-03T12:24:15.621-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.deploy.shared.InputJarArchive@335297;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8003: archivist instantiation failure for null; type = com.sun.enterprise.deployment.deploy.shared.InputJarArchive@335297"|#]

[#|2006-03-03T12:24:15.621-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.ecore.xmi_2.2.0.jar. -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.ecore.xmi_2.2.0.jar -- Cannot determine the Java EE module type for C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.ecore.xmi_2.2.0.jar|#]

[#|2006-03-03T12:24:15.652-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\org.eclipse.emf.ecore.xmi_2.2.0.jar.|#]

[#|2006-03-03T12:24:15.652-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\Fragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.652-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\Fragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/Fragment (wrong name: org/eclipse/birt/report/viewer/aggregation/Fragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/Fragment (wrong name: org/eclipse/birt/report/viewer/aggregation/Fragment)|#]

[#|2006-03-03T12:24:15.652-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\Fragment.class.|#]

[#|2006-03-03T12:24:15.683-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ScalarParameterFragment.class for autodeployment.|#]

[#|2006-03-03T12:24:15.683-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ScalarParameterFragment.class. -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ScalarParameterFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ScalarParameterFragment) -- birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggregation/parameter/ScalarParameterFragment (wrong name: org/eclipse/birt/report/viewer/aggregation/parameter/ScalarParameterFragment)|#]

[#|2006-03-03T12:24:15.699-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Autodeploy failed : C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\classes\org\eclipse\birt\report\viewer\aggregation\parameter\ScalarParameterFragment.class.|#]

[#|2006-03-03T12:24:15.715-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|[AutoDeploy] Selecting file C:\glassfish\domains\domain1\autodeploy\birt\WEB-INF\lib\js.jar for autodeployment.|#]

[#|2006-03-03T12:24:18.121-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;com.sun.enterprise.deployment.archivist.AppClientArchivist@f507d2;_RequestID=1756b623-3674-4376-91cf-d44007ac1a81;|"DPL8001: descriptor failure com.sun.enterprise.deployment.archivist.AppClientArchivist@f507d2"|#]

[#|2006-03-03T12:24:18.215-0500|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Timer-3;|deployed with moduleid = birt_WEB-INF_lib_js|#]

[#|2006-03-03T12:24:18.309-05

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 3, 2006 8:08 PM   in response to: vladperl
  Click to reply to this thread Reply

Vladperl,

I want to verify that you have copied the birt war file to the autodeploy directory.

If you are doing something like 'javac -d <AUTODEPLOY-DIR>/birt BIRTCLASSES', you may be running into issues because that isn't a well tested use-case.

Or, you could use asadmin's deploydir command... Which you can read about in this article: http://developers.sun.com/prodtech/appserver/reference/techart/deployment.html

The article was writtenb for SJSAS 8.x, but is very applicable to GlassFish.

vladperl

Posts: 94
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 5, 2006 9:23 PM   in response to: vbkraemer
  Click to reply to this thread Reply

> I want to verify that you have copied the birt war
> file to the autodeploy directory.

Hi Vince,
Thank you, for your response.
You asked the right question about war file.
This time I for deployment choose to copy folder of the birt viewer to autodeploy folder. For some reason I have believed that copy of web application folder to autodeploy one of the way to make application deployment on glassfish. On tomcat you can copy app folder or war file for deployment. By the way why glassfish doesn't support
this way of deployment?
After your notice regarding war file I check out related documentation and realized that I was wrong trying to use copy directory approach to deployment.
After that I tried to make deployment of application from server admin console with checked verifier.
And got the errors:


---------------------------
STATIC VERIFICATION RESULTS
---------------------------


----------------------------------
NUMBER OF FAILURES/WARNINGS/ERRORS
----------------------------------
# of Failures : 2
# of Warnings : 0
# of Errors : 0

-----------------------------
RESULTS FOR WEB-RELATED TESTS
-----------------------------

--------------
FAILED TESTS :
--------------

Test Name : tests.web.ParamValue
Test Assertion : Web application's param-value exists.
Test Description : For [ C:\birt-runtime-2_1_0\WebViewerExample ]
param-value must not be an empty string.
For [ C:\birt-runtime-2_1_0\WebViewerExample ]
param-value must not be an empty string.
For [ C:\birt-runtime-2_1_0\WebViewerExample ]
param-value must not be an empty string.
For [ C:\birt-runtime-2_1_0\WebViewerExample ]
param-value must not be an empty string.

Test Name : tests.web.WebArchiveClassesLoadable
Test Assertion : All classes in this Web Archive are loadable excluding classes used in JSPs. The test AllJSPsMustBeCompilable takes care of reporting non portable errors in JSP classes.
Test Description : For [ C:\birt-runtime-2_1_0\WebViewerExample ]

Failed to find following classes:
[
org.eclipse.core.runtime.IExtension
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipseExtension
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.eclipse.core.runtime.IPath
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipsePath
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.eclipse.core.runtime.IConfigurationElement,
org.eclipse.core.runtime.IExtension,
org.eclipse.core.runtime.IExtensionPoint,
org.osgi.framework.Bundle,
org.eclipse.core.runtime.Platform
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.eclipse.core.runtime.IExtensionRegistry
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipseExtensionRegistry
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.osgi.framework.Bundle
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipseBundle
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.eclipse.core.runtime.IConfigurationElement,
org.eclipse.core.runtime.CoreException
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipseConfigurationElement
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet

Failed to find following classes:
[
org.eclipse.core.runtime.IExtensionPoint
]

referenced in the following call stack :

at org.eclipse.birt.core.framework.eclipse.EclipseExtensionPoint
at org.eclipse.birt.core.framework.eclipse.EclipsePlatform
at org.eclipse.birt.core.framework.Platform
at org.eclipse.birt.report.engine.api.ReportEngine
at org.eclipse.birt.report.service.ReportEngineService
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet
at org.eclipse.birt.report.servlet.ViewerServlet


Please either bundle the above mentioned classes in the application or use optional packaging support for them.


----------------------------------
END OF STATIC VERIFICATION RESULTS
----------------------------------

After disabling verifier I got partially working report viewer. For example I could change values of report parameters but can't get any resulting data on report.
After I used direct url that render report (without viewer) http://localhost:8080/birt-viewer/run?__report=report/ProductCatalog.rptdesign

I got the following:
There are errors on the report page:
- There are error(s) in report : report

Error0 : odaconsumer.CannotOpenConnection ( 1 time(s) )
detail : org.eclipse.birt.data.engine.core.DataException: Cannot open the connection for the driver: org.eclipse.birt.report.data.oda.sampledb
Failed to get connection.
Failed to start database 'jar:(C:\birt-runtime-2_1_0\WebViewerExample\plugins\org.eclipse.birt.report.data.oda.sampledb\db\BirtSample.jar)BirtSample', see the next exception for details.
at org.eclipse.birt.data.engine.odaconsumer.ConnectionManager.openConnection(ConnectionManager.java:136)
at org.eclipse.birt.data.engine.executor.DataSource.newConnection(DataSource.java:154)
at org.eclipse.birt.data.engine.executor.DataSource.open(DataSource.java:147)
at org.eclipse.birt.data.engine.impl.DataSourceRuntime.openOdiDataSource(DataSourceRuntime.java:150)
at org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.openDataSource(PreparedQuery.java:881)
at org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.prepareExecution(PreparedQuery.java:700)
at org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.access$000(PreparedQuery.java:537)
at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:226)
at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:145)
at org.eclipse.birt.report.engine.data.dte.DteDataEngine.execute(DteDataEngine.java:205)
at org.eclipse.birt.report.engine.executor.QueryItemExecutor.openResultSet(QueryItemExecutor.java:62)
at org.eclipse.birt.report.engine.executor.TableItemExecutor.execute(TableItemExecutor.java:122)
at org.eclipse.birt.report.engine.executor.ReportExecutorVisitor.visitTableItem(ReportExecutorVisitor.java:188)
at org.eclipse.birt.report.engine.ir.TableItemDesign.accept(TableItemDesign.java:69)
at org.eclipse.birt.report.engine.executor.ReportExecutor.execute(ReportExecutor.java:125)
at org.eclipse.birt.report.engine.executor.ReportExecutor.execute(ReportExecutor.java:89)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:175)
at org.eclipse.birt.report.service.ReportEngineService.runAndRenderReport(Unknown Source)
at org.eclipse.birt.report.presentation.aggregation.layout.EngineFragment.doService(Unknown Source)
at org.eclipse.birt.report.presentation.aggregation.BaseFragment.service(Unknown Source)
at org.eclipse.birt.report.servlet.ViewerServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:822)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:244)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:181)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:223)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:666)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:573)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:843)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: org.eclipse.birt.report.data.oda.jdbc.JDBCException: Failed to get connection.
Failed to start database 'jar:(C:\birt-runtime-2_1_0\WebViewerExample\plugins\org.eclipse.birt.report.data.oda.sampledb\db\BirtSample.jar)BirtSample', see the next exception for details.
at org.eclipse.birt.report.data.oda.jdbc.Connection.connectByUrl(Connection.java:155)
at org.eclipse.birt.report.data.oda.jdbc.Connection.open(Connection.java:111)
at org.eclipse.birt.report.data.oda.sampledb.SampleDBDriver$SampleDBConnection.open(SampleDBDriver.java:74)
at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaConnection.open(OdaConnection.java:239)
at org.eclipse.birt.data.engine.odaconsumer.ConnectionManager.openConnection(ConnectionManager.java:124)
... 47 more
Caused by: SQL Exception: Failed to start database 'jar:(C:\birt-runtime-2_1_0\WebViewerExample\plugins\org.eclipse.birt.report.data.oda.sampledb\db\BirtSample.jar)BirtSample', see the next exception for details.
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doConnect(JDBCDriverManager.java:148)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getConnection(JDBCDriverManager.java:94)
at org.eclipse.birt.report.data.oda.sampledb.SampleDBJDBCConnectionFactory.getConnection(SampleDBJDBCConnectionFactory.java:65)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doConnect(JDBCDriverManager.java:140)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getConnection(JDBCDriverManager.java:94)
at org.eclipse.birt.report.data.oda.jdbc.Connection.connectByUrl(Connection.java:150)
... 51 more
---------------------------------------------------

Probably I have the problem with birt-viewer because the application using eclipse plugins including plugin for database example.
Could you help me to make run birt reports on glassfish?

To download and instructions follow the link:
http://download.eclipse.org/birt/downloads

Pick up: birt-runtime-2.1M5.zip
Also to check out report, download report model from
http://www.eclipse.org/birt/phoenix/examples/solution/ProductCatalog.rptdesign
and save the file under folder "report" of the viewer.
To run report:
http://localhost:8080/birt-viewer/run?__report=report/ProductCatalog.rptdesign

Thank you,
Vladimir

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 6, 2006 12:36 PM   in response to: vladperl
  Click to reply to this thread Reply

Vladimir,

I want to dig into this problem, since it seems like it is just a configuration issue.

Unfortunately, my boss has piled a fair bit of work on me at the moment.

I will ask a couple colleques to look at it.

I cannot make any promises at this point, though.

Keep a watch on this thread.

vbk

vladperl

Posts: 94
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 6, 2006 8:51 PM   in response to: vbkraemer
  Click to reply to this thread Reply

> I want to dig into this problem, since it seems like
> it is just a configuration issue.
>
> Unfortunately, my boss has piled a fair bit of work
> on me at the moment.
>
> I will ask a couple colleques to look at it.
>
> I cannot make any promises at this point, though.

Hi Vince,
I'm grateful for your efforts to help me out.
That's ok for me to wait for solution a little more time.

> Keep a watch on this thread.
Believe me I will keep look on the thread :)

Thank you,
Vladimir

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 13, 2006 12:32 PM   in response to: vladperl
  Click to reply to this thread Reply

Okay, I got the birt viewer to run on GlassFsh.

I can duplicate your error...

What database is your report trying to use?

Have you added the appropriate driver to GF (or "ported" your data to the Derby database that GF "knows"?)

Did you start the database server?

vbk

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 13, 2006 2:16 PM   in response to: vbkraemer
  Click to reply to this thread Reply

I re-read this message and realized, I was playing with the wrong release of BIRT...

BUT, when I go to the download page for 2.1M5, none of the mirrors I have tried (all the US mirrors) want to let me have the bits.

vbk

vladperl

Posts: 94
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 13, 2006 2:38 PM   in response to: vbkraemer
  Click to reply to this thread Reply

Hi Vince,
> Okay, I got the birt viewer to run on GlassFsh.
>
> I can duplicate your error...
I'm glad to here that.

> What database is your report trying to use?
In fact I'm working with two database one of them MySQL 4.1 and other MS SQL Server 2000.
More of that I'm ready to start some experiments with sample of database supplied with Birt. This sample database included in one of the plugin that go with birt viewer and use Derby.

> Have you added the appropriate driver to GF (or
> "ported" your data to the Derby database that GF
> "knows"?)

I put database drivers under plugin.
Here is path on my computer with tomcat:
C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\birt\plugins\org.eclipse.birt.report.data.oda.jdbc\drivers

I'm using drivers:
mysql-connector-java-3.1.12-bin.jar
sqljdbc.jar

Because plugin already have database drivers I have though I don't have to add database driver directly to GF. Why they called it's plugin after all :)

> Did you start the database server?

MySQL Server and MS Server were started and reports worked with tomcat. Regarding Derby I did not start it. I supposed that plugins take care about everythings because database server Derby and database example included in plugins and plugins know what to do.
At least for Tomcat I didn't take any additional steps.
I know only that Birt included also plugin for tomcat maybe that why I don't have to make additional steps like registration database drivers or starting database server in case of using Derby.
I don't have much experience working with plugins.

Please let me know what I have to do now to make it work.

Thank you,
Vladimir

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 13, 2006 8:41 PM   in response to: vladperl
  Click to reply to this thread Reply

this issue appears to be caused by an incompatability between the datafile in the sample and the version of derby.jar that is used in GlassFish...

If I replace the derby.jar that is packaged with GlassFish with the derby.jar that is packaged in the BIRT web application, the SalesInvoice.rptdesign displays correctly.

If I replace the derby.jar in the web application with the derby.jar from GlassFish, the report fails to display correctly.

Do you know which build of derby is used in BIRT?

Do you know which derby build was used to create the BirtSample database in the BirtSample.jar?

vbk

vladperl

Posts: 94
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 14, 2006 10:47 AM   in response to: vbkraemer
  Click to reply to this thread Reply

Hi Vince,
> this issue appears to be caused by an incompatability
> between the datafile in the sample and the version of
> derby.jar that is used in GlassFish...
>
> If I replace the derby.jar that is packaged with
> GlassFish with the derby.jar that is packaged in the
> BIRT web application, the SalesInvoice.rptdesign
> displays correctly.

I have replaced derby.jar like you described above and it really works.

> If I replace the derby.jar in the web application
> with the derby.jar from GlassFish, the report fails
> to display correctly.

I did not try that because I'm sure you are correct in this case also.

By the way I tried again to deploy my reports that use MS SQL Server and MySQL Server and suddenly the reports are working now. I guess something was fixed in the build 40.

> Do you know which build of derby is used in BIRT?
I checked out manifests from relevant jar files and found only minor difference.

glassfish(build 40) derby.jar:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.1
Created-By: 1.4.2_03-b02 (Sun Microsystems Inc.)
Bundle-Vendor: Apache Software Foundation
Bundle-Activator: org.apache.derby.osgi.EmbeddedActivator
Bundle-Name: Apache Derby 10.0
Bundle-Version: 10.0.2000001
Import-Package: java.sql
DynamicImport-Package: *
Export-Package: org.apache.derby.authentication,org.apache.derby.datab
ase,org.apache.derby.io,org.apache.derby.jdbc,org.apache.derby.vti
-------------------------------------------------

birt(2.1 milestone 5) derby.jar:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.1
Created-By: 1.4.2_03-b02 (Sun Microsystems Inc.)
Bundle-Vendor: Apache Software Foundation
Bundle-Activator: org.apache.derby.osgi.EmbeddedActivator
Bundle-Name: Apache Derby 10.0
Bundle-Version: 10.0.2000001
Import-Package: java.sql
DynamicImport-Package: *
Export-Package: org.apache.derby.authentication,org.apache.derby.datab
ase,org.apache.derby.io,org.apache.derby.jdbc,org.apache.derby.vti
--------------------------------------------------------

As you can see there is a difference only in bundle version.

> Do you know which derby build was used to create the
> BirtSample database in the BirtSample.jar?

BirtSample included with the Birt framework and
build file for report viewer just make copy already existing plugin with this database. So I can't know which derby build was used during creating the database.
But on page http://download.eclipse.org/birt/downloads/
you can find link: Demo Database. The demo database package includes sql and data files for defining and loading the database into Derby and MySQL. Using this package you can regenerate demo database with derby version supplied with GF.

From my side I could ask the Birt team to update derby.jar to more fresh version of the derby server.

Still I have the question why GF did not try to use derby server that located inside the birt plugin?
It's really strange. What do you think?

Thanks a lot for your help.

Vladimir

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 14, 2006 12:31 PM   in response to: vladperl
  Click to reply to this thread Reply

Well,

I heard from somebody that "knows" how to ask derby what version it is, to use the sysinfo.ksh/.bat script.

From that I learned the GF bundles 10.1.1.0 (presently).

I also learned that birt 2.0.1 and birt 2.1M5 both have a derby.jar that "says" it is 10.0.2.1....

So, it looks like birt is "behind the times".. GF is, too. (just not quite as far).

vbk

vladperl

Posts: 94
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 14, 2006 12:46 PM   in response to: vbkraemer
  Click to reply to this thread Reply

> I heard from somebody that "knows" how to ask derby
> what version it is, to use the sysinfo.ksh/.bat
> script.
>
> From that I learned the GF bundles 10.1.1.0
> (presently).
>
> I also learned that birt 2.0.1 and birt 2.1M5 both
> have a derby.jar that "says" it is 10.0.2.1....

I have took the manifest files for previous post
from the same jar file :) I forgot that I replaced derby.jar in GF from Birt.
Below is manifest file from real glassfish's derby.jar.
Sorry for confusing.

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.1
Created-By: 1.4.2_07-b05 (Sun Microsystems Inc.)
Bundle-Vendor: Apache Software Foundation
Bundle-Activator: org.apache.derby.osgi.EmbeddedActivator
Bundle-Name: Apache Derby 10.1
Bundle-Version: 10.1.1000000.208786
DynamicImport-Package: *
Export-Package: org.apache.derby.authentication,org.apache.derby.datab
ase,org.apache.derby.io,org.apache.derby.jdbc,org.apache.derby.vti
---------------------------------------

As you can see manifest files show the same numbers
you got using Derby script.

> So, it looks like birt is "behind the times".. GF is,
> too. (just not quite as far).

I will try to convince the Birt team to update Derby.
Only one question left is why derby from glassfish have priority over derby that includes in plugin?
I even did not start derby server that belong to GF.

vbkraemer

Posts: 280
Re: autodeployment bug, problem with Birt Report Viewer and one suggestion
Posted: Mar 25, 2006 5:15 PM   in response to: vbkraemer
  Click to reply to this thread Reply

I have a "better" solution for deploying BIRT: http://blogs.sun.com/roller/page/vkraemer?entry=birt_and_glassfish

I ran the birt.war file through the Java EE 5 verifier... It had some complaints, which may explain why deploying BIRT is non-trivial...

vbk




 XML java.net RSS