Topic
  • 17 replies
  • Latest Post - ‏2008-08-27T07:45:22Z by bergamo
SystemAdmin
SystemAdmin
37422 Posts

Pinned topic Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

‏2008-06-04T15:57:29Z |
Everything worked great on 6.1.0.15 and after installing the latest fixpack, 6.1.0.17, I can no longer deploy any EAR file with an EJB 2.1 in it.

Here is the stack trace I get. It appears a class is missing from the WAS install. I confirmed this on 3 separate app servers that have been upgraded:

29 DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
6/4/08 10:46:06:225 CDT 00000029 DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
6/4/08 10:46:06:227 CDT 00000029 DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
6/4/08 10:46:06:230 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy Shutting down workbench.
6/4/08 10:46:06:232 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy Error executing deployment: java.lang.NoClassDefFoundError. Error is com.ibm.etools.common.internal.migration.plugin.MigrationPlugin.
6/4/08 10:46:06:234 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
6/4/08 10:46:06:237 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.isBackwardsCompatibility Enabled(ResourceProperties.java:691)
6/4/08 10:46:06:239 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.savePreferences(Resource Properties.java:214)
6/4/08 10:46:06:243 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.setGenerationFolder(Reso urceProperties.java:336)
6/4/08 10:46:06:257 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.getGenerationFolder(Reso urceProperties.java:432)
6/4/08 10:46:06:260 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.plugin.EJBDeployOperation.<init>(EJBDeployOperation.ja va:210)
6/4/08 10:46:06:263 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.invokeDeploymentCodegen(Ba tchExtension.java:1882)
6/4/08 10:46:06:268 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:832)
6/4/08 10:46:06:270 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:770)
6/4/08 10:46:06:272 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtensio n.java:544)
6/4/08 10:46:06:273 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.ja va:435)
6/4/08 10:46:06:275 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtensi on.java:418)
6/4/08 10:46:06:290 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
6/4/08 10:46:06:293 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)
6/4/08 10:46:06:295 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExt ension.java:382)
6/4/08 10:46:06:300 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:34 5)
6/4/08 10:46:06:301 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.jav a:78)
6/4/08 10:46:06:303 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecl ipseAppLauncher.java:92)
6/4/08 10:46:06:304 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLa uncher.java:68)
6/4/08 10:46:06:320 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
6/4/08 10:46:06:321 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
6/4/08 10:46:06:323 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
6/4/08 10:46:06:325 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:43)
6/4/08 10:46:06:327 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at java.lang.reflect.Method.invoke(Method.java:618)
6/4/08 10:46:06:329 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java: 275)
6/4/08 10:46:06:331 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:99)
6/4/08 10:46:06:332 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:83)
6/4/08 10:46:06:334 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:313)
6/4/08 10:46:06:345 CDT 00000029 DeployEJBTask I ADMA0158I: EJBDeploy EJBDeploy level: o0812.04
6/4/08 10:46:06:367 CDT 00000027 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files (x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_00000027_ 08.06.04_10.46.06_0.txt
6/4/08 10:46:06:382 CDT 00000027 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files (x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_00000027_ 08.06.04_10.46.06_0.txt
6/4/08 10:46:06:383 CDT 00000027 DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: com.ibm.websphere.management.exception.AdminException: ADMA0063E: An error occurred in EJB deployment - http://An unexpected exception was thrown. Halting execution.
at com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJBTask. java:355)
at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
at java.lang.Thread.run(Thread.java:810)

Anyone have any ideas?

Message was edited by: GrantGochnaer
Updated on 2008-08-27T07:45:22Z at 2008-08-27T07:45:22Z by bergamo
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-06-04T16:43:20Z  
    Reverting back to 6.1.0.15 fixed the problem where I can now install EAR files with EJB 2.1 beans however we need some of the fixes in 6.1.0.17 so reverting isn't a great option for us.

    I noticed with fix pack 15, in the folder \base_v61\deploytool\itp\plugins there is the file:
    com.ibm.etools.common.migration_1.0.103.v200708011131.jar which contains the MigrationPlugin class. Once FP 17 is installed, this JAR remains but another has been added called: com.ibm.etools.common.migration_1.0.104.v200803060930.jar. What's interesting is the new JAR from FP17 has the MigrationPlugin class so I'm confused why in FP17, I get the class not found exception. It's almost like the app server isn't including this JAR in the classpath.
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-06-04T19:29:55Z  
    Good to know I'm not the only one.

    I have confirmed this problem exists both on Windows and Linux ES 4
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-06-04T19:33:56Z  
    Same error message being generated as well on the windows platform that I am running WebSphere on, FP 15 to FP 17. Just wanted to post this wasnt an isolated error message.

    edited
    Also running Feature Pack for EJB3.0 and WebServices ... both upgraded from FP 15 to FP17.

    Message was edited by: cweinrich
    Updated on 2008-06-04T19:33:56Z at 2008-06-04T19:33:56Z by SystemAdmin
  • adbdkb
    adbdkb
    115 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-06-04T21:49:52Z  
    Reverting back to 6.1.0.15 fixed the problem where I can now install EAR files with EJB 2.1 beans however we need some of the fixes in 6.1.0.17 so reverting isn't a great option for us.

    I noticed with fix pack 15, in the folder \base_v61\deploytool\itp\plugins there is the file:
    com.ibm.etools.common.migration_1.0.103.v200708011131.jar which contains the MigrationPlugin class. Once FP 17 is installed, this JAR remains but another has been added called: com.ibm.etools.common.migration_1.0.104.v200803060930.jar. What's interesting is the new JAR from FP17 has the MigrationPlugin class so I'm confused why in FP17, I get the class not found exception. It's almost like the app server isn't including this JAR in the classpath.
    A kind of related question. I have downloaded the .pak files for the fp17, but haven't been able to find the 6.1.0.17 update installer and the documentation mentions that that is what we need to use & if I try with 6.1.0.15 version of the installer, the .pak files are not selectable.

    Could you please let me know, how were you able to install fp17? What could I be missing?

    Thanks
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-06-04T22:01:40Z  
    • adbdkb
    • ‏2008-06-04T21:49:52Z
    A kind of related question. I have downloaded the .pak files for the fp17, but haven't been able to find the 6.1.0.17 update installer and the documentation mentions that that is what we need to use & if I try with 6.1.0.15 version of the installer, the .pak files are not selectable.

    Could you please let me know, how were you able to install fp17? What could I be missing?

    Thanks
    adbdkb,

    Try this link:
    http://w ww-1.ibm.com/support/docview.wss?rs=180&uid=swg27009393
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-05T15:19:54Z  
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.

    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15

    Thanks

    Pierre
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-05T19:41:56Z  
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.

    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15

    Thanks

    Pierre
    You may want to ensure that you've applied the 6.1.0.17 maintenance for the EJB 3.0 feature pack. It should have been applied at the same time as the 6.1.0.17 maintenance for the base app server.

    Could you describe what you are seeing in more detail -- error messages, stack traces, etc.? That might help trigger some ideas.

    If all else fails, you may want to open a PMR with IBM Support. (I mention that on this newsgroup from time to time, just to remind folks that this NG is only monitored on a time-available basis...PMRs are still the official way to get support.)

    pierre-emmanuel.meunier@lloydspharmacy.co.uk wrote:
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.

    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15

    Thanks

    Pierre
  • PetrH
    PetrH
    83 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-06T13:01:27Z  
    You may want to ensure that you've applied the 6.1.0.17 maintenance for the EJB 3.0 feature pack. It should have been applied at the same time as the 6.1.0.17 maintenance for the base app server.

    Could you describe what you are seeing in more detail -- error messages, stack traces, etc.? That might help trigger some ideas.

    If all else fails, you may want to open a PMR with IBM Support. (I mention that on this newsgroup from time to time, just to remind folks that this NG is only monitored on a time-available basis...PMRs are still the official way to get support.)

    pierre-emmanuel.meunier@lloydspharmacy.co.uk wrote:
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.

    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15

    Thanks

    Pierre
    Hello,
    I confirm the same problem as well.

    We don't have EJB3 Feature Pack installed at all and thus don't use it.
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-06T18:41:28Z  
    • PetrH
    • ‏2008-06-06T13:01:27Z
    Hello,
    I confirm the same problem as well.

    We don't have EJB3 Feature Pack installed at all and thus don't use it.
    Apologies, the problem reported above was "I have the same problem, WAS doesn't want to deploy EJB3 projects." In order to deploy EJB3 projects, the EJB 3.0 feature pack must be installed. So I was targeting that specific question.

    Are you saying that after upgrading WAS to 6.1.0.17, you're unable to deploy any EJBs, even EJB 2.1 and lower? If that's the case, please provide more details on what you're experiencing and we might be able to offer some advice. For example, any error messages? Snippets of SysOut.log showing exception stack trace?

    Petr.Hostalek@bsc-ideas.com wrote:
    Hello,

    I confirm the same problem as well.

    We don't have EJB3 Feature Pack installed at all and thus don't use it.
  • PetrH
    PetrH
    83 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-06T20:36:47Z  
    Apologies, the problem reported above was "I have the same problem, WAS doesn't want to deploy EJB3 projects." In order to deploy EJB3 projects, the EJB 3.0 feature pack must be installed. So I was targeting that specific question.

    Are you saying that after upgrading WAS to 6.1.0.17, you're unable to deploy any EJBs, even EJB 2.1 and lower? If that's the case, please provide more details on what you're experiencing and we might be able to offer some advice. For example, any error messages? Snippets of SysOut.log showing exception stack trace?

    Petr.Hostalek@bsc-ideas.com wrote:
    Hello,

    I confirm the same problem as well.

    We don't have EJB3 Feature Pack installed at all and thus don't use it.
    Hello,
    yes even EJB2.1 application deployment fails due to the same error which can be seen in the first post.

    I see you are from IBM. If you have an access to other people's PMRs, then take look at my PMR related to this issue (41205,756,000) which I recently got opened by IBM Support. I've already provided (uploaded to IBM ftp) some traces from the deployment manager such as another information as part of this PMR.

    Shortly the failure is (more can be seen in the related archive uploaded to IBM ftp):

    6/6/08 19:39:28:698 CEST 0000004a DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:707 CEST 0000004a DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:716 CEST 0000004a DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:718 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy Shutting down workbench.
    6/6/08 19:39:28:731 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy Error executing deployment: java.lang.NoClassDefFoundError. Error is com.ibm.etools.common.internal.migration.plugin.MigrationPlugin.
    6/6/08 19:39:28:740 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    6/6/08 19:39:28:751 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.isBackwardsCompatibility Enabled(ResourceProperties.java:691)
    6/6/08 19:39:28:760 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.savePreferences(Resource Properties.java:214)
    6/6/08 19:39:28:769 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.setGenerationFolder(Reso urceProperties.java:336)
    6/6/08 19:39:28:779 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.getGenerationFolder(Reso urceProperties.java:432)
    6/6/08 19:39:28:789 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.plugin.EJBDeployOperation.<init>(EJBDeployOperation.ja va:210)
    6/6/08 19:39:28:800 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.invokeDeploymentCodegen(Ba tchExtension.java:1882)
    6/6/08 19:39:28:810 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:832)
    6/6/08 19:39:28:819 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:770)
    6/6/08 19:39:29:015 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtensio n.java:544)
    6/6/08 19:39:29:025 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.ja va:435)
    6/6/08 19:39:29:034 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtensi on.java:418)
    6/6/08 19:39:29:043 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
    6/6/08 19:39:29:053 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)
    6/6/08 19:39:29:062 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExt ension.java:382)
    6/6/08 19:39:29:072 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:34 5)
    6/6/08 19:39:29:081 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.jav a:78)
    6/6/08 19:39:29:090 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecl ipseAppLauncher.java:92)
    6/6/08 19:39:29:100 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLa uncher.java:68)
    6/6/08 19:39:29:109 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    6/6/08 19:39:29:119 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    6/6/08 19:39:29:128 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    6/6/08 19:39:29:137 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:43)
    6/6/08 19:39:29:147 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at java.lang.reflect.Method.invoke(Method.java:618)
    6/6/08 19:39:29:156 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java: 275)
    6/6/08 19:39:29:166 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:99)
    6/6/08 19:39:29:174 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:83)
    6/6/08 19:39:29:184 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:313)
    6/6/08 19:39:29:193 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy EJBDeploy level: o0812.04
    6/6/08 19:39:29:207 CEST 00000049 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_00000049_08.06.06_1 9.39.29_0.txt
    6/6/08 19:39:29:256 CEST 00000049 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_00000049_08.06.06_1 9.39.29_0.txt
    6/6/08 19:39:29:266 CEST 00000049 DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
    at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:230)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil$1.run(DeployUtil.java:242)
    at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:11 8)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deployModule(DeployUtil.ja va:237)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deploy(DeployUtil.java:90)
    at com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJBTask. java:343)
    at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
    at java.lang.Thread.run(Thread.java:810)

    It's really the same as in the first post.

    EDIT: Just to make things more clear, after reverting back to 6.1.0.15 this problem disappeared (as expected). I tested this issue on WAS6.1.0.17 running on various platforms (Windows/x86. Linux/x86, HP-UX/IA64) and it occurs on all of them and with various ear files. And there's probably also something else wrong to Fix Pack 17 as on two environments I also got into the situation when EJB Deployment failed just like this:

    6/6/08 18:15:21:942 CEST 0000006f IscTaskProvid I IscTaskProvider provideServerInstallExtentions ear.getName JEAR.ear
    6/6/08 18:15:21:944 CEST 0000006f IscTaskProvid I IscTaskProvider provideServerInstallExtentions Added IscEarDeployTask to Vector
    6/6/08 18:15:23:518 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy Starting workbench.
    6/6/08 18:15:23:520 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy o0812.04
    6/6/08 18:15:23:729 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy framework search path: /was/IBM/WebSphere/AppServer/deploytool/itp/plugins
    6/6/08 18:15:25:563 CEST 0000006f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_0000006f_08.06.06_18.15.25_0.txt
    6/6/08 18:15:25:662 CEST 0000006f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_0000006f_08.06.06_18.15.25_0.txt
    6/6/08 18:15:25:665 CEST 0000006f DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
    at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:230)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil$1.run(DeployUtil.java:242)
    at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deployModule(DeployUtil.java:237)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deploy(DeployUtil.java:90)
    at com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJBTask.java:343)
    at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
    at java.lang.Thread.run(Thread.java:595)

    Which I resolved by cleaning the $WAS_PROFILE_HOME/configuration/ directory and then executing osgiCfgInit.sh script. Perhaps the OSGI configuration is somewhat incorrectly altered during the Fix Pack 17 installation and uninstallation (on one environment it occured after FP17 was installed, on another one after reverting to FP15)

    Message was edited by: PetrH
    Updated on 2008-06-06T20:36:47Z at 2008-06-06T20:36:47Z by PetrH
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-06T20:38:44Z  
    • PetrH
    • ‏2008-06-06T19:36:13Z
    Hello,
    yes even EJB2.1 application deployment fails due to the same error which can be seen in the first post.

    I see you are from IBM. If you have an access to other people's PMRs, then take look at my PMR related to this issue (41205,756,000) which I recently got opened by IBM Support. I've already provided (uploaded to IBM ftp) some traces from the deployment manager such as another information as part of this PMR.

    Shortly the failure is (more can be seen in the related archive uploaded to IBM ftp):

    6/6/08 19:39:28:698 CEST 0000004a DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:707 CEST 0000004a DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:716 CEST 0000004a DeployEJBTask W ADMA0087W: A warning is issued from the EJBDeploy program: An unexpected exception was thrown. Halting execution. severity 2
    6/6/08 19:39:28:718 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy Shutting down workbench.
    6/6/08 19:39:28:731 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy Error executing deployment: java.lang.NoClassDefFoundError. Error is com.ibm.etools.common.internal.migration.plugin.MigrationPlugin.
    6/6/08 19:39:28:740 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    6/6/08 19:39:28:751 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.isBackwardsCompatibility Enabled(ResourceProperties.java:691)
    6/6/08 19:39:28:760 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.savePreferences(Resource Properties.java:214)
    6/6/08 19:39:28:769 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.setGenerationFolder(Reso urceProperties.java:336)
    6/6/08 19:39:28:779 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.properties.ResourceProperties.getGenerationFolder(Reso urceProperties.java:432)
    6/6/08 19:39:28:789 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.plugin.EJBDeployOperation.<init>(EJBDeployOperation.ja va:210)
    6/6/08 19:39:28:800 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.invokeDeploymentCodegen(Ba tchExtension.java:1882)
    6/6/08 19:39:28:810 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:832)
    6/6/08 19:39:28:819 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEJBComponent(BatchE xtension.java:770)
    6/6/08 19:39:29:015 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtensio n.java:544)
    6/6/08 19:39:29:025 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.ja va:435)
    6/6/08 19:39:29:034 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtensi on.java:418)
    6/6/08 19:39:29:043 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
    6/6/08 19:39:29:053 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)
    6/6/08 19:39:29:062 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExt ension.java:382)
    6/6/08 19:39:29:072 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:34 5)
    6/6/08 19:39:29:081 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.jav a:78)
    6/6/08 19:39:29:090 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecl ipseAppLauncher.java:92)
    6/6/08 19:39:29:100 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLa uncher.java:68)
    6/6/08 19:39:29:109 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    6/6/08 19:39:29:119 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    6/6/08 19:39:29:128 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    6/6/08 19:39:29:137 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:43)
    6/6/08 19:39:29:147 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at java.lang.reflect.Method.invoke(Method.java:618)
    6/6/08 19:39:29:156 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java: 275)
    6/6/08 19:39:29:166 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:99)
    6/6/08 19:39:29:174 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:83)
    6/6/08 19:39:29:184 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:313)
    6/6/08 19:39:29:193 CEST 0000004a DeployEJBTask I ADMA0158I: EJBDeploy EJBDeploy level: o0812.04
    6/6/08 19:39:29:207 CEST 00000049 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_00000049_08.06.06_1 9.39.29_0.txt
    6/6/08 19:39:29:256 CEST 00000049 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_00000049_08.06.06_1 9.39.29_0.txt
    6/6/08 19:39:29:266 CEST 00000049 DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
    at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:230)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil$1.run(DeployUtil.java:242)
    at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:11 8)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deployModule(DeployUtil.ja va:237)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deploy(DeployUtil.java:90)
    at com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJBTask. java:343)
    at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
    at java.lang.Thread.run(Thread.java:810)

    It's really the same as in the first post.

    EDIT: Just to make things more clear, after reverting back to 6.1.0.15 this problem disappeared (as expected). I tested this issue on WAS6.1.0.17 running on various platforms (Windows/x86. Linux/x86, HP-UX/IA64) and it occurs on all of them and with various ear files. And there's probably also something else wrong to Fix Pack 17 as on two environments I also got into the situation when EJB Deployment failed just like this:

    6/6/08 18:15:21:942 CEST 0000006f IscTaskProvid I IscTaskProvider provideServerInstallExtentions ear.getName JEAR.ear
    6/6/08 18:15:21:944 CEST 0000006f IscTaskProvid I IscTaskProvider provideServerInstallExtentions Added IscEarDeployTask to Vector
    6/6/08 18:15:23:518 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy Starting workbench.
    6/6/08 18:15:23:520 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy o0812.04
    6/6/08 18:15:23:729 CEST 00000071 DeployEJBTask I ADMA0158I: EJBDeploy framework search path: /was/IBM/WebSphere/AppServer/deploytool/itp/plugins
    6/6/08 18:15:25:563 CEST 0000006f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_0000006f_08.06.06_18.15.25_0.txt
    6/6/08 18:15:25:662 CEST 0000006f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_0000006f_08.06.06_18.15.25_0.txt
    6/6/08 18:15:25:665 CEST 0000006f DeployEJBTask E ADMA0086E: An error occurred from the EJBDeploy program: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
    at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:230)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil$1.run(DeployUtil.java:242)
    at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deployModule(DeployUtil.java:237)
    at com.ibm.ejs.util.deployment.deploywrapper.DeployUtil.deploy(DeployUtil.java:90)
    at com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJBTask.java:343)
    at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
    at java.lang.Thread.run(Thread.java:595)

    Which I resolved by cleaning the $WAS_PROFILE_HOME/configuration/ directory and then executing osgiCfgInit.sh script. Perhaps the OSGI configuration is somewhat incorrectly altered during the Fix Pack 17 installation and uninstallation (on one environment it occured after FP17 was installed, on another one after reverting to FP15)

    Message was edited by: PetrH
    Hello Petr,
    My apologies...in the newsreader view on news.software.ibm.com the first post is:
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.
    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15
    Thanks
    Pierre

    On the web page view, I see the original post you are referring to. There is apparently a synchronization problem between the NNTP view and the web view.

    I looked at the PMR and saw that it was opened as severity 3. I recommend that it be raised to sev 2. If you have a critical issue with reverting back to 6.1.0.15, then you may want to raise the severity to 1.

    Petr.Hostalek@bsc-ideas.com wrote:
    Hello,

    yes even EJB2.1 application deployment fails due to the same error as can be seen in the first post.

    I see you are from IBM. If you have an access to other people's PMRs, then take look at my PMR related to this issue (41205,756,000) which I recently got opened by IBM Support. I've already provided (uploaded to IBM ftp) some traces from the deployment manager such as another information as part of this PMR.
  • PetrH
    PetrH
    83 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-07T00:11:32Z  
    Hello Petr,
    My apologies...in the newsreader view on news.software.ibm.com the first post is:
    Hi Guys

    I have the same problem, WAS doesn't want to deploy EJB3 projects.
    Has anyone found a solution yet? Apart from reverting back to 6.1.0.15
    Thanks
    Pierre

    On the web page view, I see the original post you are referring to. There is apparently a synchronization problem between the NNTP view and the web view.

    I looked at the PMR and saw that it was opened as severity 3. I recommend that it be raised to sev 2. If you have a critical issue with reverting back to 6.1.0.15, then you may want to raise the severity to 1.

    Petr.Hostalek@bsc-ideas.com wrote:
    Hello,

    yes even EJB2.1 application deployment fails due to the same error as can be seen in the first post.

    I see you are from IBM. If you have an access to other people's PMRs, then take look at my PMR related to this issue (41205,756,000) which I recently got opened by IBM Support. I've already provided (uploaded to IBM ftp) some traces from the deployment manager such as another information as part of this PMR.
    Hello,
    we're IBM Business Partners (ISV) so that's probably why our PMRs are set to low severity 3 by default.
    Actually it's not that big issue for us, but I wanted to make sure it will find its way to the IBM support so that's the main reason I contacted them.


    EDIT: I found a solution for this issue, but it works only partially so I decided to remove the instructions for now. If I figure out how to make it fully working I'll post the instructions here.

    Message was edited by: PetrH
    Updated on 2008-06-07T00:11:32Z at 2008-06-07T00:11:32Z by PetrH
  • PetrH
    PetrH
    83 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-06-13T16:18:05Z  
    • PetrH
    • ‏2008-06-06T21:45:32Z
    Hello,
    we're IBM Business Partners (ISV) so that's probably why our PMRs are set to low severity 3 by default.
    Actually it's not that big issue for us, but I wanted to make sure it will find its way to the IBM support so that's the main reason I contacted them.


    EDIT: I found a solution for this issue, but it works only partially so I decided to remove the instructions for now. If I figure out how to make it fully working I'll post the instructions here.

    Message was edited by: PetrH
    Hello again,

    finally I got a response from IBM support regarding this issue and it really is the OSGI cache issue what I first wrote about, but then decided to remove it because I faced another EJB deploy issue. But that another issue doesn't seem to be related to this one, so here we go with the workaround for the "java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    " on EJBDeploy:

    • stop all WAS processes
    • make backups of what you will be about to delete
    • delete $WAS_HOME/deploytool/itp/configuration/org.* (leave only config.ini in this directory)
    • delete $USER_INSTALL_ROOT/ejbdeploy/configuration/*

    the following three steps are probably unnecesary, these clear another OSGI cache which is not used for EJBDeploy tasks:
    • delete $USER_INSTALL_ROOT/configuration/* (I think it's not that necessary)
    • delete $USER_INSTALL_ROOT/temp/osgi_instance_location/* (I think it's not that necessary)
    • execute $USER_INSTALL_ROOT/bin/osgiCfgInit.sh (I think it's not that necessary)

    • start dmgr (also local node agent etc.) or server1 and perform the application deployment

    I have only Network Deployment edition accessible where the related OSGI cache data may be found in the $WAS_HOME/deploytool/itp/configuration/ and/or $USER_INSTALL_ROOT/ejbdeploy/configuration/ paths, but on Base and Express editions it might be a little different. Try to find them by yourselves and if they will be different, post the correct locations here.
    As for the another issue I found in WAS 6.1.0.17 only is that on RMIC the process fails with:

    6/7/08 13:09:03:307 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy Error generating RMI code: RMIC command failed on project: commons-gaas with message:
    6/7/08 13:09:03:319 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Could not load class javax.transaction.Synchronization.
    6/7/08 13:09:03:331 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Transaction contains an invalid argument type in method registerSynchronization.
    6/7/08 13:09:03:344 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Interceptor contains an invalid argument type in method afterTransactionBegin.
    6/7/08 13:09:03:356 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.SessionFactoryImplementor contains an invalid argument type in method openSession.
    6/7/08 13:09:03:368 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.Type contains an invalid argument type in method isEqual.
    6/7/08 13:09:03:379 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.Mapping contains an invalid argument type in method getIdentifierType.
    6/7/08 13:09:03:391 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.VersionType contains an invalid argument type in method sqlTypes.
    6/7/08 13:09:03:407 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.ReplicationMode contains an invalid argument type in method shouldOverwriteCurrentVersion.
    6/7/08 13:09:03:416 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Session contains an invalid argument type in method replicate.
    6/7/08 13:09:03:429 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.SessionFactory contains an invalid argument type in method openSession.
    6/7/08 13:09:03:649 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Lifecycle contains an invalid argument type in method onSave.
    6/7/08 13:09:03:664 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class EntityManager contains an invalid return type.
    6/7/08 13:09:03:678 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class ...EntityManager contains an invalid argument type in method create

    and it seem to fail wherever we use Hibernate 3 in the app.
    Again on WAS 6.1.0.15 everything works so the problem is on WAS 6.1.0.17 only.
    I informed IBM Support about this as well so I hope this will be figured out as well in some near future.

    Message was edited by: PetrH
    Updated on 2008-06-13T16:18:05Z at 2008-06-13T16:18:05Z by PetrH
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-07-10T19:18:35Z  
    • PetrH
    • ‏2008-06-13T16:16:52Z
    Hello again,

    finally I got a response from IBM support regarding this issue and it really is the OSGI cache issue what I first wrote about, but then decided to remove it because I faced another EJB deploy issue. But that another issue doesn't seem to be related to this one, so here we go with the workaround for the "java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    " on EJBDeploy:

    • stop all WAS processes
    • make backups of what you will be about to delete
    • delete $WAS_HOME/deploytool/itp/configuration/org.* (leave only config.ini in this directory)
    • delete $USER_INSTALL_ROOT/ejbdeploy/configuration/*

    the following three steps are probably unnecesary, these clear another OSGI cache which is not used for EJBDeploy tasks:
    • delete $USER_INSTALL_ROOT/configuration/* (I think it's not that necessary)
    • delete $USER_INSTALL_ROOT/temp/osgi_instance_location/* (I think it's not that necessary)
    • execute $USER_INSTALL_ROOT/bin/osgiCfgInit.sh (I think it's not that necessary)

    • start dmgr (also local node agent etc.) or server1 and perform the application deployment

    I have only Network Deployment edition accessible where the related OSGI cache data may be found in the $WAS_HOME/deploytool/itp/configuration/ and/or $USER_INSTALL_ROOT/ejbdeploy/configuration/ paths, but on Base and Express editions it might be a little different. Try to find them by yourselves and if they will be different, post the correct locations here.
    As for the another issue I found in WAS 6.1.0.17 only is that on RMIC the process fails with:

    6/7/08 13:09:03:307 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy Error generating RMI code: RMIC command failed on project: commons-gaas with message:
    6/7/08 13:09:03:319 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Could not load class javax.transaction.Synchronization.
    6/7/08 13:09:03:331 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Transaction contains an invalid argument type in method registerSynchronization.
    6/7/08 13:09:03:344 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Interceptor contains an invalid argument type in method afterTransactionBegin.
    6/7/08 13:09:03:356 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.SessionFactoryImplementor contains an invalid argument type in method openSession.
    6/7/08 13:09:03:368 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.Type contains an invalid argument type in method isEqual.
    6/7/08 13:09:03:379 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.Mapping contains an invalid argument type in method getIdentifierType.
    6/7/08 13:09:03:391 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.VersionType contains an invalid argument type in method sqlTypes.
    6/7/08 13:09:03:407 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.ReplicationMode contains an invalid argument type in method shouldOverwriteCurrentVersion.
    6/7/08 13:09:03:416 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Session contains an invalid argument type in method replicate.
    6/7/08 13:09:03:429 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.SessionFactory contains an invalid argument type in method openSession.
    6/7/08 13:09:03:649 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Lifecycle contains an invalid argument type in method onSave.
    6/7/08 13:09:03:664 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class EntityManager contains an invalid return type.
    6/7/08 13:09:03:678 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class ...EntityManager contains an invalid argument type in method create

    and it seem to fail wherever we use Hibernate 3 in the app.
    Again on WAS 6.1.0.15 everything works so the problem is on WAS 6.1.0.17 only.
    I informed IBM Support about this as well so I hope this will be figured out as well in some near future.

    Message was edited by: PetrH
    I'm seeing the same issue trying to update ITCAM for WAS 6.1 after upgrading WAS to 6.1.0.17. Did this issue ever get resolved? I'm trying the workaround listed with the OSGI cache.
  • SystemAdmin
    SystemAdmin
    37422 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-08-02T19:43:41Z  
    • PetrH
    • ‏2008-06-13T16:16:52Z
    Hello again,

    finally I got a response from IBM support regarding this issue and it really is the OSGI cache issue what I first wrote about, but then decided to remove it because I faced another EJB deploy issue. But that another issue doesn't seem to be related to this one, so here we go with the workaround for the "java.lang.NoClassDefFoundError: com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    " on EJBDeploy:

    • stop all WAS processes
    • make backups of what you will be about to delete
    • delete $WAS_HOME/deploytool/itp/configuration/org.* (leave only config.ini in this directory)
    • delete $USER_INSTALL_ROOT/ejbdeploy/configuration/*

    the following three steps are probably unnecesary, these clear another OSGI cache which is not used for EJBDeploy tasks:
    • delete $USER_INSTALL_ROOT/configuration/* (I think it's not that necessary)
    • delete $USER_INSTALL_ROOT/temp/osgi_instance_location/* (I think it's not that necessary)
    • execute $USER_INSTALL_ROOT/bin/osgiCfgInit.sh (I think it's not that necessary)

    • start dmgr (also local node agent etc.) or server1 and perform the application deployment

    I have only Network Deployment edition accessible where the related OSGI cache data may be found in the $WAS_HOME/deploytool/itp/configuration/ and/or $USER_INSTALL_ROOT/ejbdeploy/configuration/ paths, but on Base and Express editions it might be a little different. Try to find them by yourselves and if they will be different, post the correct locations here.
    As for the another issue I found in WAS 6.1.0.17 only is that on RMIC the process fails with:

    6/7/08 13:09:03:307 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy Error generating RMI code: RMIC command failed on project: commons-gaas with message:
    6/7/08 13:09:03:319 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Could not load class javax.transaction.Synchronization.
    6/7/08 13:09:03:331 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Transaction contains an invalid argument type in method registerSynchronization.
    6/7/08 13:09:03:344 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.Interceptor contains an invalid argument type in method afterTransactionBegin.
    6/7/08 13:09:03:356 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.SessionFactoryImplementor contains an invalid argument type in method openSession.
    6/7/08 13:09:03:368 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.Type contains an invalid argument type in method isEqual.
    6/7/08 13:09:03:379 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.engine.Mapping contains an invalid argument type in method getIdentifierType.
    6/7/08 13:09:03:391 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.type.VersionType contains an invalid argument type in method sqlTypes.
    6/7/08 13:09:03:407 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.ReplicationMode contains an invalid argument type in method shouldOverwriteCurrentVersion.
    6/7/08 13:09:03:416 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Session contains an invalid argument type in method replicate.
    6/7/08 13:09:03:429 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.SessionFactory contains an invalid argument type in method openSession.
    6/7/08 13:09:03:649 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class org.hibernate.classic.Lifecycle contains an invalid argument type in method onSave.
    6/7/08 13:09:03:664 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class EntityManager contains an invalid return type.
    6/7/08 13:09:03:678 CEST 0000006a DeployEJBTask I ADMA0158I: EJBDeploy error: Class ...EntityManager contains an invalid argument type in method create

    and it seem to fail wherever we use Hibernate 3 in the app.
    Again on WAS 6.1.0.15 everything works so the problem is on WAS 6.1.0.17 only.
    I informed IBM Support about this as well so I hope this will be figured out as well in some near future.

    Message was edited by: PetrH
    Hi,
    we have tried with workaround that you have write in your post an i have resolved my problem.
    Furthermore we do not have the possibility to try with 6.1.0.15 because we have not time.

    My version is a express edition.
    We use open JPA ad now seems all works fine.

    In the next days we try our application and send another feedback.

    Many thanks for your help!!!

    Fabiano
  • PetrH
    PetrH
    83 Posts

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploy

    ‏2008-08-04T13:17:23Z  
    I'm seeing the same issue trying to update ITCAM for WAS 6.1 after upgrading WAS to 6.1.0.17. Did this issue ever get resolved? I'm trying the workaround listed with the OSGI cache.
    Hello,

    which one do you mean?

    The initial one
    java.lang.NoClassDefFoundError. Error is com.ibm.etools.common.internal.migration.plugin.MigrationPlugin
    can be currently resolved by the already mentioned workaround, now officially described at http://w ww-1.ibm.com/support/docview.wss?rs=180&uid=swg21307298 and I was also informed that it will be fixed in following Fix Packs.

    The second one
    Could not load class javax.transaction.Synchronization
    requires a code modification (tools.jar) and is planned to be fixed in JDK 1.5.0 SR9 scheduled for release in early 2009.
    But you may contact the WebSphere support to obtain an internal fix.
  • bergamo
    bergamo
    1 Post

    Re: Upgrading WAS App server from 6.1.0.15 to 6.1.0.17 prevents EJBs deploying

    ‏2008-08-27T07:45:22Z  
    This worked for me :)