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.
Two days ago, the glassfish on my development PC started to give message while started up: javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.signature.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "domain.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.encryption.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.security.config" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.encryption.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.security.config" javax.management.InstanceNotFoundException: No object matches the specified name "server.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.dynamic.username.password" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.signature.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.dynamic.username.password" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.encryption.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.signature.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.encryption.key.alias" javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.signature.key.alias" I have been using Glassfish for more than one year, and it worked very well. I don't know what happened, and I spent two days trying to find out the reason. I found a lot of people had the same pain, ever since 2007. URLs like: http://www.nabble.com/Can%27t-Create-New-Enterprise-Application-Project-td19094638.html#a19094638 http://www.nabble.com/javax.management.InstanceNotFoundException-td18009805.html#a18009805 http://www.nabble.com/Exceptions-after-starting-GlassFish-v2-UR2-in-NB-6.1-RC2-td16897584.html#a16917969 It really hut my trust of the free Java EE application server. Any
You have included some error message that appear in the server log... but you have not described what operation that you are unable to perform. P1 is for issues that are actively blocking your ability to do work in the IDE. Please describe what development actions you are unable to perform after you see these messages in the server log.
it looks like initializing the tree of Nodes under the server is what triggers the messages. doing more investigation.
I normally build the j2ee cluster, which doesn't have the compapp modules in it. I can start the server from the IDE without seeing these message. I built the compapp.manager.jbi module into my "regular" j2ee cluster build. I start the IDE (j2ee+comp.manager.jbi). I expand the node tree and see the messages..... I stopped the server. Stopped the IDE. Cleaned compapp.manager.jbi project to pull the feature from my build. Started the IDE Started the server expanded the node tree No messages about unknown objects/names. I have to conclude that there are some incorrect assumptions being made in compapp.manager.jbi about the content of the config namespace.
One thing that I did notice.... Most of the names that aren't found are of the form blah.blah.blah.property.foo.bar.... where foo.bar is the name of the property.... One thing I have also noticed is the GF V2 namespace doesn't have properties that have a dot in their name... you find thing like blah.blah.blah.property.foo blah.blah.blah.property.bar blah.blah.blah.property.fooBar blah.blah.blah.property.FooBar blah.blah.blah.property.foo-bar the exceptions to that are the message-security-config element AND the property administrative.domain.name... So, this may be a server bug that the JBI config manager tickles... the jbi folks should probably work this out with the admin team to resolve this... the plugin is basically out of the picture.
I opened https://glassfish.dev.java.net/issues/show_bug.cgi?id=6042 against GF to track "that side" of the issue.
*** Issue 145248 has been marked as a duplicate of this issue. ***
*** Issue 149143 has been marked as a duplicate of this issue. ***
Since no obvious functionality is lost, I am downgrading it to P3. I have filed this ticket against the JBI runtime: https://open-esb.dev.java.net/issues/show_bug.cgi?id=706
*** Issue 150301 has been marked as a duplicate of this issue. ***
The bug is in GlassFish, not in NetBeans or OpenESB. There is a GlassFish issue that was filed on this: https://glassfish.dev.java.net/issues/show_bug.cgi?id=4518 I am leaving this ticket open for now as a place holder.
*** Issue 138725 has been marked as a duplicate of this issue. ***
*** Issue 134646 has been marked as a duplicate of this issue. ***
*** Issue 136758 has been marked as a duplicate of this issue. ***
*** Issue 137499 has been marked as a duplicate of this issue. ***
*** Issue 152757 has been marked as a duplicate of this issue. ***
Closing this out as it is a GlassFish bug and is tracked in GlassFish IssueTracker.
*** Issue 170080 has been marked as a duplicate of this issue. ***