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 178177 - Unexpected MySQL Server Commands Log appears at the Output tab
Summary: Unexpected MySQL Server Commands Log appears at the Output tab
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: MySQL (show other bugs)
Version: 6.x
Hardware: PC Windows XP x64
: P3 normal with 1 vote (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-04 19:42 UTC by davisn
Modified: 2010-07-14 13:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Output Log Image (10.37 KB, image/png)
2009-12-04 19:42 UTC, davisn 		Details
Attached correct Output Log Image (12.97 KB, image/png)
2009-12-04 19:43 UTC, davisn 		Details
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 davisn 2009-12-04 19:42:03 UTC 
Created attachment 92163 [details]
Output Log Image

When select deploy/run an EJB module on GlassFish v3 Domain server, 2 of the "MySQl Server Commands" log appears at the Output tab. Please see the attached screen shot for the problem in graphic

Steps To Reproduce:
1. Install Netbean RC2
2. Start the IDE with a new userdir
2. From Services tab, click to expand Databases node -> highlight the jdbc:derby://localhost....[..on APP] node
3. Create an EJB module
4. Right-click the created EJB module and select run menu
BUG:
  The Server was started -> EJB module was deployed; howerver in addition to the EJB Module, Java DB..,GlassFish v3 Domain log, the 2 MySQl Server Commands also appear
Comment 1 davisn 2009-12-04 19:43:55 UTC 
Created attachment 92164 [details]
Attached correct Output Log Image

Reattached the correct image
Comment 2 Vince Kraemer 2009-12-05 21:29:43 UTC 
The v3 plugin does not attempt to do operation on mysql... It does start derby, though... so there may be something in the db code that triggers this.

I cannot reproduce the problem, so I cannot find the link between the v3 server starting and these command log windows.

Assigning to db.  They should be able to point me in the right direction.
Comment 3 Jiri Rechtacek 2010-06-18 10:46:13 UTC 
The NetBeans support for MySQL listens on each DB operation to detect when it can initializes itself. That's the reason that unexpected MySQL output.
Comment 4 Jiri Rechtacek 2010-07-14 13:01:38 UTC 
I'm not able to reproduce it in NB6.9.1. It seems to be fixed within NB6.9/NB6.9.1 development.