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.
Product Version: NetBeans IDE Dev (Build 200803261205) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Userdir: C:\Documents and Settings\Lipin\.netbeans\dev GlassFish V2 UR2, b02 OpenESB components: Build080326 (from openesb_as9_ur2 branch) Steps to reproduce: 1. Start NetBeans 2. Open Services->Servers, start GlassFish V2 3. Start sun-(bpel,javaee,sql)-engine MBeanException that is caused by com.sun.jbi.management.system.ManagementException is thrown in the log.
Created attachment 59319 [details] server log
reproduced with 200803290011 on solaris x86.
Narayana, sql se is not implementing retrieveConfigurationDisplayData Operation. Operation retrieveConfigurationDisplayData is not implemented by MBean com.sun.ebi:ServiceType=Configuration,InstallationType=serviceEngines,IdentificationName=sun-sql-engine
Fix checked in
if it is the netbeans module issue, then what is the changeset id? would it be also fixed in release61 branch? if it is the runtime issue then would it be available in openesb_as9_ur2 branch builds of openesb components?
Reproduced with NetBeans 6.1 RC1 build (OpesESB components Build080408_1/openesb_as9_ur2, GlassFish V2UR2 b03). Attaching server.log and netbeans messages.log.
Created attachment 60015 [details] Server log (glassfish v2ur2 b03, openesb Build080408_1/openesb_as9_ur2)
Created attachment 60016 [details] NetBeans messages.log
Can you please let me know whats the service engine build you are using for this? Also can you please try the same uninstalling the sql engine from the current installation and then installing it from the http://download.java.net/jbi/binaries/open-jbi-components/main/nightly/latest/ojc/? Thanks,
> Can you please let me know whats the service engine build you are using for this? sqlse.jar:META-INF/jbi.xml says that it is build-number="080408_1" > Also can you please try the same uninstalling the sql engine from the current installation and then installing it from the http://download.java.net/jbi/binaries/open-jbi-components/main/nightly/latest/ojc/? This one works.
so looks like the fix was checked in main but not in openesb_as9_ur2 branch. Why?
I am not aware of such branch. Whenever we do some check in its into the open-jbi-components cvs. Bits are taken from here when it comes to the installer. So, if there is any such branch I can update that branch too. Thanks,
I am attaching the conversation I had with Lipin. Since the fix is working in the main line and bits for the said release have to come from another branch. I request either to give me the authentication for the required branch to check in or to down grade the same to p3/p4 so that when we integrate the bits from the main line the bug can be closed. Thanks, Narayana Rallabandi wrote: This can't be a P1 because it doesn't effect the functionality of the component in any manner. It only exposes couple of methods for management of the component. Thanks, Narayanaa Dmitry Lipin wrote: > Hi Narayana, > > As far as I understand, not all of your commits that do in main open-jbi-components cvs repository should go to the special branch. > The purpose of that branch is that it would be used for making builds for upcoming Java EE SDK 5 Update 5 and NetBeans 6.1. > > To commit to that branch, you should have the approval from EE SDK team that it is a stopper for EESDK and that they would make a respin to include this fix. > If it is not the stopper for EE SDK then you *cannot commit *to the branch. > > For more details on the branch please contact your manager or Suresh. > > Even though I filed the issue as P2 you should better contact QE team - likely it is P1. > > Thanks, > Dmitry
Changed target milestone.
Should be fixed now. Dima, would you please verify ?
It is still reproduced since Open ESB runtime has not been updated since then.
not a jbi manager bug... reassigned to openesb