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 64048 - Deployment fails onto JBoss 4.0.3RC1
Summary: Deployment fails onto JBoss 4.0.3RC1
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: JBoss (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Libor Kotouc
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-09-11 12:27 UTC by jlaskowski
Modified: 2006-06-04 23:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jlaskowski 2005-09-11 12:27:02 UTC 
JBoss 4.0.3RC1 doesn't work properly with the recent NetBeans build. During web
application deployment, JBoss has started up, but NetBeans didn't recognize it.

NetBeans version: netbeans-5_0-daily-bin-200509072000-7_Sep_2005_2000
Comment 1 Jaroslav Pospisil 2005-09-12 08:47:29 UTC 
Could you please write more about your web deployment case and also specify your
JDK version and system you are using?
I've just tested JBoss4.0.3RC2 on the specified build and all works O.K.
My system is WinXP SP2,JDK 1.5.0_04.
Comment 2 jlaskowski 2005-09-17 21:36:19 UTC 
It mostly works now. I wrote 'mostly' because I saw some deployment failures,
but can't figure out what the steps to reproduce are.

I work with the latest sources that I built myself.

java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)

Microsoft Windows XP Professional
5.1.2600 Service Pack 2 Build 2600

JBoss [Zion] 4.0.3RC2 (build: CVSTag=Branch_4_0 date=200508131404)
Comment 3 Pavel Buzek 2005-11-09 20:25:39 UTC 
Did you get any error messages? Can you post them? Thanks.
Comment 4 Libor Kotouc 2005-11-14 17:27:50 UTC 
User has not provided any additional information, some fixes were already made
in the area of a server state detection, e.g. see issue 68484.

-> closing as WorksForMe