[JBoss Microcontainer Users] - Single Deployment Unit from multiple files inside a zip
by rareddy
Hi,
I am trying to write a new deployer for Teiid artifact which is a zip file. In there I have two xml files that I need to parse and gather metadata and deploy them as single unit.
To accomplish this, I wrote deployer that extends "MultipleVFSParsingDeployer" and defined mappings and the "parse" and "merge" calls are being called correctly on the XML files, however the DeploymentUnit supplied in each individual parse call is file itself rather than the parent zip file, thus I am ending up with two deployments at the end rather than one. Can you please help me how I can configure them to work under single deployment unit.
I also tried individual deployer for each of my XML file extending "AbstractVFSParsingDeployer" but the behaviour is same.
For example:
Foo.zip
- a.xml
- b.xml
while parsing "a.xml" and "b.xml" I would like "Foo.zip" as DeploymentUnit, instead of "Foo.zip#a.xml"
Thank you.
Ramesh..
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267860#4267860
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267860
16 years, 5 months
[Beginner's Corner] - Error with jboss start
by amira88
Hi,
i wanna create my tables from ejb3 entities by using jboss:but when i start
the jboss server it show me his errors;
14:33:44,041 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/
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:698)
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(Unknown Source)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence
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 resolve schema nsURI= location=persistence
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
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.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(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
14:33:49,737 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
14:33:49,922 INFO [MailService] Mail Service bound to java:/Mail
14:33:52,180 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
14:33:52,204 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
14:33:52,390 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
14:33:52,390 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
14:33:52,723 INFO [TransactionManagerService] Initializing recovery manager
14:33:52,966 INFO [TransactionManagerService] Recovery manager configured
14:33:52,966 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
14:33:53,010 INFO [TransactionManagerService] Starting transaction recovery manager
14:33:53,658 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080
14:33:53,659 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:33:53,660 INFO [StandardService] D�marrage du service jboss.web
14:33:53,663 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
14:33:54,260 INFO [Catalina] Server startup in 700 ms
14:33:54,282 INFO [TomcatDeployment] deploy, ctxPath=/invoker
14:33:55,007 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
14:33:55,068 INFO [TomcatDeployment] deploy, ctxPath=/web-console
14:33:55,532 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
14:33:55,555 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
14:33:55,604 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
14:33:55,627 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
14:33:55,659 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
14:33:55,769 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
14:33:55,819 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:33:55,823 INFO [RAMJobStore] RAMJobStore initialized.
14:33:55,823 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
14:33:55,823 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:33:55,824 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
14:33:57,087 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:33:57,557 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
14:33:57,670 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
14:33:57,679 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
14:33:57,679 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
14:33:57,747 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
14:33:57,747 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@81876b started
14:33:57,748 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
14:33:57,748 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@2bb129 started
14:33:57,750 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
14:33:57,752 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
14:33:57,752 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@13ec519 started
14:33:57,896 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:33:57,924 INFO [TomcatDeployment] deploy, ctxPath=/
14:33:57,989 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
14:33:58,088 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
14:33:58,103 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080
14:33:58,218 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:33:58,227 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 29s:283ms
HELP PLEASE
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267856#4267856
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267856
16 years, 5 months
[JBoss Cache Users] - MVCC and writeSkewCheck
by anothermarcus
HI everyone,
I'm using Jboss Tree Cache pojo version NAGA 3.0
How can I invoke an exception to see the behaviour of the writeSkewCheck?
I've seen several articles explaining the Phantom Read at a very high level, but down to an API user's level, how can I simulate a skewed write.
Say for example two threads within the same JVM do
| Cache internalCache = getCache();
|
| Node rootNode = internalCache.getRoot();
| Node sequenceNode = rootNode.getChild(Fqn.fromString(SEQUENCE_FQN));
|
| // READ
| Integer sequence = (Integer) sequenceNode.get(SEQUENCE_FQN);
|
| Thread.sleep(1000);
| // WRITE
| sequenceNode.put(SEQUENCE_FQN, sequence +1);
|
Will having two threads like this invoke a skewed write that will throw an exception to the user? If so, I'm not seeing it happen.
Thanks for any advice
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267844#4267844
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267844
16 years, 5 months
[Installation, Configuration & Deployment] - Re: How to configure when the server startup time is display
by menegazzo
Here is two log fragments:
1: using eclipse's add and remove projects feature
| ...
| 15:15:14,865 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 22s:747ms
| 15:15:19,724 INFO [EARDeployer] Init J2EE application: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/deploy/deploy-test-ear.ear/
| 15:15:20,568 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
| 15:15:20,599 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=deploy-test-ear.ear,jar=deploy-test-ejb.jar,name=TestBean,service=EJB3 with dependencies:
| 15:15:20,911 INFO [EJBContainer] STARTED EJB: br.com.deploytest.TestBean ejbName: TestBean
| 15:15:20,974 INFO [EJB3Deployer] Deployed: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/deploy/deploy-test-ear.ear/deploy-test-ejb.jar/
| 15:15:20,989 INFO [EARDeployer] Started J2EE application: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/deploy/deploy-test-ear.ear/
|
1: deploying an EAR (extracted or not) directly outside eclipse
| ...
| 15:17:11,428 INFO [EARDeployer] Init J2EE application: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/deploy/deploy-test-ear.ear
| 15:17:12,349 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
| 15:17:12,365 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=deploy-test-ear.ear,jar=deploy-test-ejb.jar,name=TestBean,service=EJB3 with dependencies:
| 15:17:12,756 INFO [EJBContainer] STARTED EJB: br.com.deploytest.TestBean ejbName: TestBean
| 15:17:12,818 INFO [EJB3Deployer] Deployed: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/tmp/deploy/tmp29727deploy-test-ear.ear-contents/deploy-test-ejb.jar
| 15:17:12,834 INFO [EARDeployer] Started J2EE application: file:/C:/ambienteDSI/jboss-4.2.2.GAX/server/default/deploy/deploy-test-ear.ear
| 15:17:13,037 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
| 15:17:13,084 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8443
| 15:17:13,131 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
| 15:17:13,146 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 24s:871ms
|
I'm thinking this is an eclipse behavior, what do you think?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267839#4267839
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267839
16 years, 5 months