[Installation, Configuration & DEPLOYMENT] - Error deploying war
by sk2009
11:32:27,408 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/D:/jboss-5.0.0.GA/server/default/deploy/application.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/D:/jboss-5.0.0.GA/server/default/deploy/application.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: Failed to start listener-class: the element is not repeatable, repeatable parent expected to be a model group but got element listener
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: Failed to start listener-class: the element is not repeatable, repeatable parent expected to be a model group but got element listener
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParent(SundayContentHandler.java:703)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:341)
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.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.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=4203115#4203115
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203115
17 years, 4 months
[Remoting] - Re: With SSLBisocket is there is java.rmi.server.hostname or
by ron.sigal＠jboss.com
Hi Ian,
Well, I just ran a test with the InvokerLocator
| sslbisocket://multihome:7777/foobar/services?datatype=serializable&homes=192.168.2.2:7777!10.11.12.119:7777&serializationtype=jboss
|
and didn't have any problems.
Looking at the code, in the absence of any explicit parameters, it should be the case that
| # of server sockets == # of homes == # of connect homes == # of secondary bind ports == # of secondary connect ports.
|
Could you run your code with TRACE logging for org.jboss.remoting and look for any related messages?
TheNelson" wrote :
| clients can only attach callback handlers to the one listed in connect_homes.
|
Just to be sure, note that the parameter should be "connecthomes".
"TheNelson" wrote :
| What's with the secondary port list?
|
The motivation for the bisocket transport was to allow the server to connect to the client without having a ServerSocket on the client. So, the bisocket client creates a "control" connection by connecting to a server side secondary ServerSocket bound to a secondary port, and, when, the server wants to get a socket connected to the client, it sends a request on the control connection, which causes the client to connect to the secondary ServerSocket to create the socket. OK so far? Two more points.
1. There's a secondary ServerSocket, each bound to a secondary bind host/port address, for each "primary" ServerSocket. The client asks for a list of secondary ServerSockets, and it can attempt to connect to any of them.
2. If there's a firewall between the client and the server, then the server should be configured with a"connecthomes" list. The BisocketServerInvoker will take the hosts from the "connecthomes" list, associate each host with a port from the "secondaryConnectPorts" list (or an anonymous port if there is no configured value for "secondaryConnectPorts"), and create a list of addresses for the client to use to create the control connection.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203111#4203111
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203111
17 years, 4 months
(no subject)
by Bounced mail
The original message was received at Tue, 20 Jan 2009 10:00:27 +0300
from lists.jboss.org [80.155.90.42]
----- The following addresses had permanent fatal errors -----
<jboss-user(a)lists.jboss.org>
17 years, 4 months
[JBoss Tools (users)] - Code completion, navigation in EL and configuration files
by dxxvi
I'm considering JBoss Tools as a replacement for MyEclipse which is very disappointing. I haven't used JBoss Tools before. These are my questions:
1) Does JBoss Tools support code completion/suggestion in EL? For example, I have a JSF-managed bean named `bean'; is there a code completion when I type `<h:outputText value="#{bean.' in a xhtml file?
2) If code completion is supported in EL, does JBoss Tools supports code completion for variables defined with <c:set>? For example with the JSF-managed bean above, if I write `<c:set var="x" value="#{bean}"/>', is there code completion when I type `<h:outputText value="#{x.'?
3) Does JBoss Tools support refactoring in EL? For example, I have a JSF-managed bean named `bean' which has a member variable named `prop1' and getter and setter methods (getProp1 and setProp1); in the xhtml file, I have `<h:outputText value="#{bean.prop1}"/>'; if I change `prop1' to `property1', will the setter and getter method names change too? and will the `prop1' in EL change to `property1'?
4) If I ctrl+click on a bean name in EL, will I be taken to the bean definition in the faces-config.xml file? And in the faces-config.xml file, if I ctrl+click on the class name, will I be taken to the Java source file?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203108#4203108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203108
17 years, 4 months
[Management, JMX/JBoss] - MBean depends on a stateless EJB
by franbekh
Hello,
I'm developing a MBean that needs a dependency on an deployed EJB. As described in the WIKI, I tried the -Tag and the @Depends annotation (see http://www.jboss.org/community/docs/DOC-9879). The SAR-Archive is deployed withing my EAR.
@Depends("jboss.j2ee:jndiName=MySchedulerBean,service=EJB3")
public class StartupService extends ServiceMBeanSupport implements StartupServiceMBean
{
@EJB
MyScheduler scheduler;
....
public void createService()
{
scheduler.start();
}
}
The dependant bean is a stateless session bean. The JBoss version I'm using is 4.2.3. During the startup of jboss I get the following error message:
--- MBeans waiting for other MBeans ---
ObjectName: my.company:service=StartupService
State: CONFIGURED
I Depend On:
jboss.j2ee:jndiName=MySchedulerBean,service=EJB3
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:jndiName=MySchedulerBean,service=EJB3
State: NOTYETINSTALLED
Depends On Me:
my.company:service=StartupService
It seems that the MBean deployer is waiting for the EJB to get ready, but it failed. Can someone tell me where my mistake is. I just want to make sure that the EJB is available for using.
Thanks in advance,
Bernd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203107#4203107
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203107
17 years, 4 months
