Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let me guess - you are using NetBeans 6.9 to develop and package the module and then you try to load it in VisualVM 1.2.* or jvisualvm? If that's the case you've just encountered a compatibility issue when modules targeted to NetBeans 6.9 platform are not easily installable in eg. NetBeans 6.8 based application (such as VisualVM 1.2.*). This is caused by NB6.9 platform compressing/uncompressing the module jars using pack200.</p> <p>In order to target the module to the older platform (and still build it using the lates IDE) you need to manually specify the module harness used by the plugins platform (go to "Tools/NetBeans Platforms/" and then select the "Harness" tab and choose the harness that comes from the binaries you can download <a href="https://visualvm.dev.java.net/build/build122.html" rel="nofollow noreferrer">here</a>. </p> <p>When you rebuild the module and create the NBM it should work in VisualVM 1.2.* as well as jvisualvm.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to package Java Agent as Visual VM plugin
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJB-
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to package Java Agent as Visual VM plugin
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThanks! This has solved the installation error. However, my agent and client jars are still not being bundled into the nbm file. At runtime I use http://github.com/mchr3k/org.intrace/blob/master/InTrace-VisualVM-Plugin/src/org/intrace/visualvm/Locator.java to find the path to these jars and this currently returns null when using the built nbm file. These jars are located correctly when I run the plugin directly from Netbeans: Agent Path: C:\Work\GitHub\InTrace\InTrace-VisualVM-Plugin\build\cluster\modules\ext\intrace-agent.jar. Do you know how I can solve this?
      singulars
      1. PO
      1. USmchr
    2. COActually, in order to access your 3rd party libraries you would need to create a library wrapper module, wrap in your jars (a simple wizard will help here) and then bundle the library wrapper and your actual module into one module suite (another project type). Check out http://wiki.netbeans.org/DevFaqWrapperModules for more information about library wrappers. Once you set-up your modules like this you can use InstalledFileLocator (http://bits.netbeans.org/dev/javadoc/index.html) to get the actual location of your jars.
      singulars
      1. PO
      1. USJB-
    3. COSuccess! I don't actually need to use any classes from these jars within VisualVM. I only need to have filesystem access to the jars. It was therefore sufficient for me to manually place the jars into release/modules/ext/ and it just worked (TM) - http://github.com/mchr3k/org.intrace/tree/master/InTrace-VisualVM/release/modules/ext/. Thanks for all your help.
      singulars
      1. PO
      1. USmchr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload