The following exception happens when stopping JBoss server. I am using the
latest download of JBoss Portal.
10:46:04,270 ERROR [MainDeployer] Undeployment failed: file:/D:/jboss-4.0.2/serv
er/default/deploy/jboss-portal.sar/portal-core.war/WEB-INF/portlet.xml
java.lang.NullPointerException
"reverbel" wrote : Which JBoss configuration are you using? The "default"
server config does not include CORBA/IIOP support. Use the "all" server config.
|
| Regards,
|
| Francisco
I am new to JBoss, could you let me know how to start the all configuration?
Thanks,
Qdot
View the orig
Per J2EE specification,
"All web, enterprise bean, and application client containers are required to
provide an ORB instance in the JNDI namespace under the name java:comp/ORB"
I am using the following code to try get ahold of the default ORB instance in
the EJB code:
InitialContext context =
Thanks, Dimitris.
It is surprising that not many people voting for this feature, since JSR-160
JMX Remote APIs is already incorporated in J2SE 1.5. Some other application
server vendors already support it like WebLogic 9.0.
View the original post :
http://www.jboss.org/index.html?module=bb&op=
As title. Thanks.
-qdotlu
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877726#3877726
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877726
-
Is there a road map for the support of JMX Remote API?
Thanks,
"[EMAIL PROTECTED]" wrote : We don't fully suppor jsr160 yet, but Tom Elrod
from the JBossRemoting project is working on this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869782#3869782
Reply
If it is supported, which JAR file is the implementation packaged into?
Thanks,
-Mark
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869646#3869646
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869646
Yes, we could register a empty GaugeMonitor in the client side and then call
the "set attribute" methods the populate the content of the GaugeMonitor. But
it is not as convenient as populating the content of GaugeMonitor and then
create the MBean through RMIAdaptor. It is one remote call versus
I want to build an application that I can use a Web GUI in the front end to
display all the existing MBeans registered with the MBean server. If I want to
create a monitor against one MBean attribute, I have to ask the MBean Server to
create one Montior MBean in the client side through RMIAdapto
If I created one GaugeMonitor instance from the client side, and set proper
values, I am having problem using the RMIAdaptor to register it with a backend
JBoss JMX Agent. It was complaining certain field is not Serializable.
Other Monitor implementations have the similar problem.
Is this a bug
If i use the RMIAdaptor to register one GaugeMonitor to the JMX agent, and then
register the same GaugeMonitor again, the existing one is not replaced, neither
an exception is thrown. If there are Listeners registered with the old instance
of GaugeMonitor, the notification will be send by the o
11 matches
Mail list logo
