This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 127411 - EntApp deployment fails with IBM WS 6.1
Summary: EntApp deployment fails with IBM WS 6.1
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebSphere (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-14 16:51 UTC by kaa
Modified: 2008-03-03 17:58 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log (5.12 KB, text/plain)
2008-02-14 16:53 UTC, kaa
Details
activity.log (1.58 MB, text/plain)
2008-02-14 17:41 UTC, kaa
Details
ffdc log (12.31 KB, text/plain)
2008-02-14 17:41 UTC, kaa
Details
system Err log (154.47 KB, text/plain)
2008-02-14 17:42 UTC, kaa
Details
native sderr (1.35 KB, text/plain)
2008-02-14 17:42 UTC, kaa
Details
output window (3.78 KB, text/plain)
2008-02-18 16:10 UTC, kaa
Details
ffdc (12.84 KB, text/plain)
2008-02-18 16:12 UTC, kaa
Details
server exception log (5.50 KB, text/plain)
2008-02-18 16:13 UTC, kaa
Details
system Err log (270.55 KB, text/plain)
2008-02-18 16:14 UTC, kaa
Details
ejb jar (1.37 KB, application/octet-stream)
2008-02-18 16:42 UTC, kaa
Details
err message in admin console (52.55 KB, image/jpeg)
2008-02-18 16:43 UTC, kaa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kaa 2008-02-14 16:51:25 UTC
Product Version: NetBeans IDE Dev (Build 200802120006)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; MS932; ja_JP

Steps:

1. Add and Start WebSphere 6.1
2. Create Enterprise Application using IBM WS 6.1 in its wizrd
3. Deploy the app

There is deployment error. The same result without mbyte in names (both
ja and eng locales). I'm running in the Japan locale, using a pseudo localized Netbeans.
Comment 1 kaa 2008-02-14 16:53:10 UTC
Created attachment 56691 [details]
log
Comment 2 kaa 2008-02-14 16:57:17 UTC
IBM WebSphere Application Server V6.1.0.02008.02.12
Comment 3 Petr Hejl 2008-02-14 17:22:38 UTC
To properly evaluate I will need server log.

ADMA5014E

Most likely missing ejb bean in the ear project - thus invalid ejb module.
Comment 4 kaa 2008-02-14 17:41:24 UTC
Created attachment 56694 [details]
activity.log
Comment 5 kaa 2008-02-14 17:41:54 UTC
Created attachment 56695 [details]
ffdc log
Comment 6 kaa 2008-02-14 17:42:28 UTC
Created attachment 56696 [details]
system Err log
Comment 7 kaa 2008-02-14 17:42:52 UTC
Created attachment 56697 [details]
native sderr
Comment 8 Petr Hejl 2008-02-14 18:33:16 UTC
According to ffdc log the root cause is invalid ejb project (without any ejb bean).
Comment 9 kaa 2008-02-18 16:09:30 UTC
Tried to do the following:

1. Create EJB Module with Session bean (server: Web Sphere)
2. Created EntApp (server: Web Sphere)
3. Added the module to the app
4. Invoke Run from the pop-up

There was an exception in output window. With GFv2 in steps 1 and 2 the App was deployed ok.

Comment 10 kaa 2008-02-18 16:10:52 UTC
Created attachment 56819 [details]
output window
Comment 11 kaa 2008-02-18 16:12:23 UTC
Created attachment 56820 [details]
ffdc
Comment 12 kaa 2008-02-18 16:13:03 UTC
Created attachment 56821 [details]
server exception log
Comment 13 kaa 2008-02-18 16:14:00 UTC
Created attachment 56822 [details]
system Err log
Comment 14 Petr Hejl 2008-02-18 16:16:46 UTC
Do you have websphere domain security enabled for your profile?
Comment 15 Petr Hejl 2008-02-18 16:25:19 UTC
Can you deploy the ejb jar through admin console?
Comment 16 kaa 2008-02-18 16:41:49 UTC
I opened admin console. Then tried to deploy EJB jar located in the EJB Module\dist.
I got the following message: The EAR file might be corrupt or incomplete. 
Comment 17 kaa 2008-02-18 16:42:25 UTC
Created attachment 56824 [details]
ejb jar
Comment 18 kaa 2008-02-18 16:43:04 UTC
Created attachment 56826 [details]
err message in admin console
Comment 19 Petr Hejl 2008-02-18 22:11:11 UTC
Most likely caused by switching project created as ee5 to websphere. This is not allowed (websphere does not support
ee5). So it was a bug and it was fixed in changeset 42a9beb98875.

So if the reporter will confirm this, I'll close the issue.
Comment 20 kaa 2008-02-19 15:28:59 UTC
I agree to close if IMB WS does not support j2ee5.
Just one question: I see question marks in admin console (image 56826). Is it an issue?
Comment 21 Petr Hejl 2008-02-19 15:36:15 UTC
I'm not sure, but I would say it is related to WS - as it occurs while deploying directly through admin console. You
didn't use NetBeans while trying this. Am I right?
Comment 22 kaa 2008-02-19 15:40:45 UTC
Yes, you are right. I performed deployment from admin console.
NetBeans was used to generate jar file. 
Comment 23 Petr Hejl 2008-02-19 19:34:39 UTC
Ok, closing then. Not related to Netbeans.
Comment 24 kaa 2008-03-03 17:58:02 UTC
c