7 Replies Latest reply on Nov 19, 2011 7:52 AM by Vijayendra Bhati

    Same code 2 deployments fails on 1 (sadly mine)

    terryh1 Newbie

      I have a problem that should be simple but I cannot seem to get around it.  We are beginning a port to JBoss (V5.1).  My co-worker did a lot of work to get the project started and has things coming up in JBoss – basically a good start.  Now I am starting on the project.  But I cannot deploy the code.  We have gone so far as to determine that if I take a copy of his jboss directory with the project deployed I can start it (JBoss server under eclipse) and it works.  I have checked out the exact same source from subversion that he is using.  But when I deploy this project from my eclipse to JBoss it fails to deploy. 

       

      It seems certain there is some difference between our two eclipse setups.  But we cannot find one. The error I’m getting is:

       

      10:00:40,448 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/ state=PreReal mode=Manual requiredState=Real

      • org.jboss.deployers.spi.DeploymentException: Error deploying: DataSourceDependencyResolver

            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

       

      And finally the somewhat unexpected error, but I don’t expect this really means much:

      DEPLOYMENTS IN ERROR:

        Deployment "vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/" is in error due to the following reason(s): java.lang.IllegalStateException: DataSourceDependencyResolver is already installed.

       

       

       

      Of possible interest, but probably not, if I do not clear out the temp directory the next time I try to start the server I get a different error:

       

      10:17:15,506 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/ state=PreReal mode=Manual requiredState=Real

      • org.jboss.deployers.spi.DeploymentException: Error deploying: MessageDestinationReferenceResolver

            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

       

      OR Somtimes (probably just timing)


      10:35:54,374 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/ state=PreReal mode=Manual requiredState=Real

      org.jboss.deployers.spi.DeploymentException: Error deploying: Ejb3MetadataProcessingDeployer

          at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

       

       

      I have just about worn out google on this problem and am beginning to fear they'll delete my profile, so any advice on where to even look would be fantastically appreciated.

        • 1. Re: Same code 2 deployments fails on 1 (sadly mine)
          Peter Johnson Master

          With only a partial stack trace it is often hard to tell what the problem is. The more interesting parts of the stack trace are the "caused by" clauses, if any. And at times it helps to have all of the log output related to the app being deployed.

           

          The first error seems to suggest that DataSourceDependencyResolver was deployed earlier, perhaps via another application. What other applications are deployed?

          • 2. Re: Same code 2 deployments fails on 1 (sadly mine)
            terryh1 Newbie

            I didn't want to spam my post, but just because "I" don't see anything interesting in the stack trace doesn't mean there isn't anything there.  There  are no other applications deployed at all - just the normal JMX stuff for a default server.  Here is the entire log (not all that big I suppose)

             

            12:05:15,189 INFO  [ServerImpl] Starting JBoss (Microcontainer)...

            12:05:15,189 INFO  [ServerImpl] Release ID: JBoss [EAP] 5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)

            12:05:15,189 INFO  [ServerImpl] Bootstrap URL: null

            12:05:15,189 INFO  [ServerImpl] Home Dir: C:\jboss-eap-5.1\jboss-as

            12:05:15,189 INFO  [ServerImpl] Home URL: file:/C:/jboss-eap-5.1/jboss-as/

            12:05:15,189 INFO  [ServerImpl] Library URL: file:/C:/jboss-eap-5.1/jboss-as/lib/

            12:05:15,189 INFO  [ServerImpl] Patch URL: null

            12:05:15,189 INFO  [ServerImpl] Common Base URL: file:/C:/jboss-eap-5.1/jboss-as/common/

            12:05:15,189 INFO  [ServerImpl] Common Library URL: file:/C:/jboss-eap-5.1/jboss-as/common/lib/

            12:05:15,189 INFO  [ServerImpl] Server Name: default

            12:05:15,189 INFO  [ServerImpl] Server Base Dir: C:\jboss-eap-5.1\jboss-as\server

            12:05:15,189 INFO  [ServerImpl] Server Base URL: file:/C:/jboss-eap-5.1/jboss-as/server/

            12:05:15,189 INFO  [ServerImpl] Server Config URL: file:/C:/jboss-eap-5.1/jboss-as/server/default/conf/

            12:05:15,189 INFO  [ServerImpl] Server Home Dir: C:\jboss-eap-5.1\jboss-as\server\default

            12:05:15,189 INFO  [ServerImpl] Server Home URL: file:/C:/jboss-eap-5.1/jboss-as/server/default/

            12:05:15,189 INFO  [ServerImpl] Server Data Dir: C:\jboss-eap-5.1\jboss-as\server\default\data

            12:05:15,189 INFO  [ServerImpl] Server Library URL: file:/C:/jboss-eap-5.1/jboss-as/server/default/lib/

            12:05:15,189 INFO  [ServerImpl] Server Log Dir: C:\jboss-eap-5.1\jboss-as\server\default\log

            12:05:15,189 INFO  [ServerImpl] Server Native Dir: C:\jboss-eap-5.1\jboss-as\server\default\tmp\native

            12:05:15,189 INFO  [ServerImpl] Server Temp Dir: C:\jboss-eap-5.1\jboss-as\server\default\tmp

            12:05:15,189 INFO  [ServerImpl] Server Temp Deploy Dir: C:\jboss-eap-5.1\jboss-as\server\default\tmp\deploy

            12:05:15,876 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss-eap-5.1/jboss-as/server/default/conf/bootstrap.xml

            12:05:16,610 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]

            12:05:16,626 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]

            12:05:17,048 INFO  [CopyMechanism] VFS temp dir: C:\jboss-eap-5.1\jboss-as\server\default\tmp

            12:05:17,048 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.

            12:05:18,048 INFO  [ServerInfo] Java version: 1.6.0_13,Sun Microsystems Inc.

            12:05:18,048 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_13-b03)

            12:05:18,048 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 11.3-b02,Sun Microsystems Inc.

            12:05:18,048 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86

            12:05:18,048 INFO  [ServerInfo] VM arguments: -Djboss.home=C:\jboss-eap-5.1\jboss-as -Djava.library.path=C:\Program Files\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin -Djava.endorsed.dirs=C:\jboss-eap-5.1\jboss-as\lib\endorsed -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djboss.home=C:/jboss-eap-5.1/jboss-as -Djava.library.path=C:\OraClient -Djava.endorsed.dirs=C:/jboss-eap-5.1/jboss-as/lib/endorsed

            12:05:18,064 INFO  [JMXKernel] Legacy JMX core initialized

            12:05:21,423 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8183/

            12:05:25,720 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core

            12:05:25,720 INFO  [NativeServerConfig] 3.1.2.SP7

            12:05:27,048 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@fbcb70[ defaultDomain='jboss' ]

            12:06:03,531 INFO  [PersistenceModificationChecker] C:\jboss-eap-5.1\jboss-as\server\default\deploy\GXSU99Gen-DS-ds.xml 1311191092000 // 1311351444804

            12:06:04,640 INFO  [MailService] Mail Service bound to java:/Mail

            12:06:05,312 WARN  [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

            12:06:07,203 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP07) - JBoss Inc.

            12:06:07,203 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer

            12:06:07,421 INFO  [TransactionManagerService] Initializing recovery manager

            12:06:07,578 INFO  [TransactionManagerService] Recovery manager configured

            12:06:07,578 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference

            12:06:07,609 INFO  [TransactionManagerService] Starting transaction recovery manager

            12:06:07,953 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\OraClient

            12:06:07,999 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8180

            12:06:07,999 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8109

            12:06:08,015 INFO  [StandardService] Starting service jboss.web

            12:06:08,031 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.10

            12:06:08,078 INFO  [Catalina] Server startup in 66 ms

            12:06:08,093 INFO  [TomcatDeployment] deploy, ctxPath=/web-console

            12:06:09,562 INFO  [TomcatDeployment] deploy, ctxPath=/invoker

            12:06:09,593 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws

            12:06:09,687 INFO  [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

            12:06:09,687 INFO  [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

            12:06:09,703 INFO  [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/jms-ra.rar/META-INF/ra.xml

            12:06:09,703 INFO  [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/mail-ra.rar/META-INF/ra.xml

            12:06:09,734 INFO  [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

            12:06:09,812 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main

            12:06:09,843 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

            12:06:09,843 INFO  [RAMJobStore] RAMJobStore initialized.

            12:06:09,843 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

            12:06:09,843 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2

            12:06:09,843 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

            12:06:09,968 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=IEFE-DS' to JNDI name 'java:IEFE-DS'

            12:06:09,999 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=TGMS-DS' to JNDI name 'java:TGMS-DS'

            12:06:10,031 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=XAOracleDS' to JNDI name 'java:XAOracleDS'

            12:06:10,718 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

            12:06:11,421 INFO  [ServerPeer] JBoss Messaging 1.4.7.GA server [0] started

            12:06:12,281 INFO  [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover

            12:06:12,281 INFO  [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing

            12:06:12,327 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4557 has leasing enabled, lease period 10000 milliseconds

            12:06:12,327 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1cb79b7 started

            12:06:12,327 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4557 has leasing enabled, lease period 10000 milliseconds

            12:06:12,327 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@183a37a started

            12:06:12,343 INFO  [QueueService] Queue[/queue/testDestination] started, fullSize=200000, pageSize=2000, downCacheSize=2000

            12:06:12,343 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000

            12:06:12,343 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000

            12:06:12,343 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4557 has leasing enabled, lease period 10000 milliseconds

            12:06:12,343 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@c3ea8d started

            12:06:12,421 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

            12:06:12,531 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console

            12:06:12,624 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/admin-console'

            12:06:15,405 INFO  [TomcatDeployment] deploy, ctxPath=/GXSU99Generator

            12:06:15,437 INFO  [STDOUT] GXS U99 Gen Starting up

            12:06:16,359 INFO  [STDOUT] Starting up

            12:06:16,843 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/ state=PreReal mode=Manual requiredState=Real

            org.jboss.deployers.spi.DeploymentException: Error deploying: DataSourceDependencyResolver

                at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

                at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:130)

                at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:52)

                at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

                at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)

                at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

                at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

                at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

                at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)

                at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

                at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

                at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

                at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

                at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

                at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

                at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

                at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

                at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

                at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

                at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

                at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

                at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

                at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

                at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

                at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

                at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

                at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

                at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

                at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

                at org.jboss.Main.boot(Main.java:221)

                at org.jboss.Main$1.run(Main.java:556)

                at java.lang.Thread.run(Thread.java:619)

            Caused by: java.lang.IllegalStateException: DataSourceDependencyResolver is already installed.

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:719)

                at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

                at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:125)

                ... 34 more

            12:06:16,874 INFO  [TomcatDeployment] deploy, ctxPath=/

            12:06:16,905 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console

            12:06:16,984 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey@1809715[domain=default, server=default, name=default]

            12:06:16,984 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

             

            DEPLOYMENTS IN ERROR:

              Deployment "vfsfile:/C:/jboss-eap-5.1/jboss-as/server/default/deploy/Event_Subscriber.war/" is in error due to the following reason(s): java.lang.IllegalStateException: DataSourceDependencyResolver is already installed.

             

            12:06:16,999 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8180

            12:06:17,015 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8109

            12:06:17,015 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)] Started in 1m:1s:826ms

            • 3. Re: Same code 2 deployments fails on 1 (sadly mine)
              Peter Johnson Master

              Where in Event_Subscriber.war is DataSourceDependencyResolver being referenced?

               

              What is in your web.xml and jboss-web.xml?

               

              Are there any other *.xml files in the app?

               

              I would help immensely if the person who wrote the error message would have bothered to tell us where the code was looking when it decided that it had to register DataSourceDependencyResolver again!!!

              • 4. Re: Same code 2 deployments fails on 1 (sadly mine)
                terryh1 Newbie

                Before I begin to answer, YES!!!!! Wouldn't it have been just grand if the person putting out the message would have included ANY diagnositic information at all.  I am quite certain I could fix this if I had any idea what it was actually complaining about.  I've also spent a fair amount of time researching these states: Pre-real, configured, real etc.  As far as I can tell they are not documented anywhere at all, neither a list of possible states or what they mean.  Probably because this isn't supposed to be my concern, but it sure has become my concern now!

                </rant>

                 

                I don't know what is dragging in the DataSourceDependencyResolver.  I don't really know what that is beyond the obvious implications from it's name.  The application was running in a stand alone JVM.  It has JMX and JPA.  I expected the main issues migrating to JBoss would be with the JPA.  It is currently toplink, but I want to switch to eclipselink, mostly because several years ago I had reall (no REALLY) bad experiences with hibernate.  It's likely better now, but we didn't part exactly as friends.  Anyhow, my assumption is that DataSourceDependencyResolver has something to do with the JPA code.

                 

                I did learn that for the guy that has this working, he does not deploy it under eclipse, he just copies it over.  But that doesn't seem to me like it should ultimately make a difference.  It makes me suspect something about the eclipse setup, but I've been through that in great detail, which didn't take long because there isn't much there, and came up empty.

                 

                The only XML files in the app are the persistence.xml of course, which I know to be badly wrong - more so now as I lost some updates in my desperate attempts to get to a working state.  Specifically I need it to work with the OCI driver and lost all those changes!  In general I have found it quite difficult to find CURRENT documentation on persistence.xml.  It seems to change dramatically with every release.

                 

                ?xml version="1.0" encoding="UTF-8"?>

                <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" version="2.0">

                     <persistence-unit name="TGES_SubscriberPU"

                              transaction-type="JTA">  <!-- new attribute -->

                               <provider>

                                   org.eclipse.persistence.jpa.PersistenceProvider

                             </provider>

                       <jta-data-source>java:/XAOracleDS</jta-data-source>

                        <class>com.iefe.tgesSubscriber.jpa.EventDeadLetter</class>

                        <properties>

                            <property name="jboss.entity.manager.jndi.name" value="java:/IefeEntityManager" />

                            <property name="jboss.entity.manager.factory.name" value="java:/IefeEntityManagerFactory" />

                                    <property    name="eclipselink.target-database"

                                        value="org.eclipselink.persistence.platform.database.oracle"/>

                            <property name="eclipselink.target-server"

                                        value="JBoss"/>

                            <property name="eclipselink.weaving"

                                        value="false"/>

                            <property name="eclipselink.logging.level"

                                        value="FINEST"/>

                            <!-- enable SQL parameter binding visibility logging to override ER 329852 -->

                            <property name="eclipselink.logging.parameters"

                                        value="true"/>

                        </properties>

                    </persistence-unit>

                </persistence>

                 

                 

                The web.xml I havne't looked at at all but is pretty baren at this point.  It is also fairly wrong for what we want, but I'm putting it here just so no one will ask::

                 

                <?xml version="1.0" encoding="UTF-8"?>

                <web-app id="WebApp_ID" version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

                  <listener>

                      <listener-class>

                          com.iefe.ContextListener

                      </listener-class>

                  </listener>

                    <display-name>TGES Subscriber</display-name>

                  <welcome-file-list>

                    <welcome-file>index.html</welcome-file>

                    <welcome-file>index.htm</welcome-file>

                    <welcome-file>index.jsp</welcome-file>

                    <welcome-file>default.html</welcome-file>

                    <welcome-file>default.htm</welcome-file>

                    <welcome-file>default.jsp</welcome-file>

                  </welcome-file-list>

                  </web-app>

                • 5. Re: Same code 2 deployments fails on 1 (sadly mine)
                  Peter Johnson Master

                  >>I did learn that for the guy that has this working, he does not deploy it under eclipse, he just copies it over.  But that doesn't seem to me like it should ultimately make a difference.

                   

                  Have you tried it with not using Eclipse? Eclipse often does things to be "helpful" and instead screws things up beyond all hope. Just scan the forums and you will see quite often that the first recommendation to solving a problem is to not use Eclipse and instead do everything from the command line.

                  • 6. Re: Same code 2 deployments fails on 1 (sadly mine)
                    terryh1 Newbie

                    I sort of did this in that when I took a copy of his directory it ran, but that doesn't prove much, the only thing different at that point was the CPU.  I really like doing it all in eclispe, very convenient.  But I suppose comparted to working, it is not so convenient.  I hadn't looked for eclipse problems because this is a relatively new revelation.  But if I had to manually deploy it and use the eclipse remote debugger that wouldn't be the end of the world. 

                     

                    Thanks, I'll give that a try.  Today we have a new fire that must be addressed so this is on hold, but once I finish herding the cats maybe I can get back to real work.

                    • 7. Re: Same code 2 deployments fails on 1 (sadly mine)
                      Vijayendra Bhati Newbie

                      Terry I am also facing the same issue.Could you please tell me how you resolved this issue ?

                      Thanks,

                      Vijayendra Bhati