January 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Eclipse IDE Portal Plugin] - JBoss 4 can't shutdown from MyEclipse

by cutethree

It throws error message: Exception in thread "main" javax.naming.NameNotFoundException: jmx not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) at org.jnp.server.NamingServer.getObject(NamingServer.java:543) at org.jnp.server.NamingServer.lookup(NamingServer.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.Shutdown.main(Shutdown.java:214) Seems the shutdown command doesn't work(My env is Windows XP ). From the windows command, I can start the server by running the run.bat file. Ctrl-C to shut it down. However, I can't shut it down by running shutdown.bat. The same error as using Eclipse, which executes the same command. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200716#4200716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200716

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

What do you mean like adding the namespace to the Java XmlElement annotation on the setSipServlets method in my SipMetaData class ? (I http://code.google.com/p/mobicents/source/browse/trunk/servers/sip-servle... ) I tried that too but it didn't work neither. I even tried to create my own ServletsMetatData and ServletMetatData classes and add the namespace in the same way to the different setters present in the ServletMetatData class but it didn't work neither. Shall I create an issue somewhere ? Alternatively is this the correct link to checkout the JBossXB project http://anonsvn.jboss.org/repos/common/jbossxb ? I can try to write a sandboxed testcase to try to replicate the problem on a smaller scale by creating 2 simple xsd with one importing the other and try to validate a simple xml file. Is there any guidelines or test I could duplicate to create the above-mentionned testcase ? Thanks in advance and for looking into it and try to help me out, that is highly appreciated BR Jean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200706#4200706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200706

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

What do you mean like adding the namespace to the Java XmlElement annotation on the setSipServlets method in my SipMetaData class ? (I http://code.google.com/p/mobicents/source/browse/trunk/servers/sip-servle... ) I tried that too but it didn't work neither. I even tried to create my own ServletsMetatData and ServletMetatData classes and add the namespace in the same way to the different setters present in the ServletMetatData class but it didn't work neither. Shall I create an issue somewhere ? Alternatively is this the correct link to checkout the JBossXB project http://anonsvn.jboss.org/repos/common/jbossxb ? I can try to write a sandboxed testcase to try to replicate the problem on a smaller scale by creating 2 simple xsd with one importing the other and try to validate a simple xml file. Is there any guidelines or test I could duplicate to create the above-mentionned testcase ? Thanks in advance and for looking into it and try to help me out, that is highly appreciated BR Jean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200705#4200705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200705

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by alex.loubyansky＠jboss.com

This seems like a SchemaBinding issue, i.e. the xml looks consistent with the XSD but the element not found in the SchemaBinding. I.e. Java annotations should specify the correct namespace. I'll look when later into this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200678#4200678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200678

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

This gives me : org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/deruelle/servers/jboss-5.0.0.GA/server/default/deploy/call-blocking-1.2-SNAPSHOT.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: {http://java.sun.com/xml/ns/javaee}servlet-name not found as a child of {http://www.jcp.org/xml/ns/sipservlet}servlet at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323) ... 22 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {http://java.sun.com/xml/ns/javaee}servlet-name not found as a child of {http://www.jcp.org/xml/ns/sipservlet}servlet at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:400) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 30 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200676#4200676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200676

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - JBCL-77

by kabir.khan＠jboss.com

When is jboss-cl 2.2.0 planned? I need the fix for https://jira.jboss.org/jira/browse/JBCL-77 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200674#4200674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200674

17 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: A few problems running the examples on different machine

by clebert.suconic＠jboss.com

You have checked it out from SVN, right? I also had some problems doing that on trunk. I guess it needs some quick tidy up on code in order to run it remotely. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200664#4200664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200664

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by alex.loubyansky＠jboss.com

What about this? <sip-app xmlns="http://www.jcp.org/xml/ns/sipservlet" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jcp.org/xml/ns/sipservlet http://www.jcp.org/xml/ns/sipservlet/sip-app_1_1.xsd" | xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xs="http://www.w3.org/2001/XMLSchema" | version="1.1"> | <app-name>org.mobicents.servlet.sip.example.CallBlockingApplication</app-name> | | <servlet> | <javaee:servlet-name>CallBlockingSipServlet</javaee:servlet-name> | <javaee:servlet-class>org.mobicents.servlet.sip.example.CallBlockingSipServlet</javaee:servlet-class> | <javaee:load-on-startup>1</javaee:load-on-startup> | </servlet> | </sip-app> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200658#4200658 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200658

17 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: A few problems running the examples on different machine

by adridi

"ataylor" wrote : ok, so it turns out that even tho the initial connection to jndi was happening the exported stub that was being returned still had an endpoint of localhost. This is because if the property java.rmi.server.hostname is not set it defaults to localhost, when the App Server starts up, setting this property is one of the first things it does. | | Ive changed the jbm-standalone-beans.xml to inject the host property from the configuration object so that we only need to configure it in one place. The configuration property also sets the java.rmi.server.hostname property when the host is set. Hi Andy, I installed JBM2 - beta release from trunk and was not able to run the examples, the following error was thrown: javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.2.115; nested exception is: java.net.ConnectException: Connection refused: connect It looks like you fixed it in the alpha release by injecting the hostname into the naming service from the configuration object. By checking "jbm-standalone-beans.xml", I noticed that your fix was rolled back. Can you please provide some light on this? Thanks, Abdel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200655#4200655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200655

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

In the meanwhile is there any way to disable xsd validation for a given entry in the SchemaResolverConfig bean ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200652#4200652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200652

17 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2009