[JBoss Web Services] - Can't deploy .war to JBOSS 6.0
by Sam W
Sam W [http://community.jboss.org/people/samwun9988] created the discussion
"Can't deploy .war to JBOSS 6.0"
To view the discussion, visit: http://community.jboss.org/message/587056#587056
--------------------------------------------------------------
Hello,
I don't understand the deployment of this simple war file is failed on jboss 6.0.
Here is the exception:
01:06:29,890 WARN [org.jboss.profileservice.deployment.hotdeploy.HDScanner] Failed to add deployment: vfs:///C:/jboss-6.0.0.Final/server/default/deploy/ResourceA.war: org.jboss.deployers.spi.DeploymentException: Failed to mount archive: "/C:/jboss-6.0.0.Final/server/default/deploy/ResourceA.war"
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.mountArchive(AbstractVFSArchiveStructureDeployer.java:132) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.determineStructure(AbstractVFSArchiveStructureDeployer.java:55) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:197) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:222) [:2.2.0.GA]
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1106) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:417) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:367) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:277) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.addDeployment(MainDeployerPlugin.java:77) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.addDeployment(ProfileControllerContext.java:133) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:221) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [:1.6.0_21]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) [:1.6.0_21]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_21]
at java.lang.Thread.run(Unknown Source) [:1.6.0_21]
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [:1.6.0_21]
at java.util.zip.ZipFile.<init>(Unknown Source) [:1.6.0_21]
at java.util.jar.JarFile.<init>(Unknown Source) [:1.6.0_21]
at java.util.jar.JarFile.<init>(Unknown Source) [:1.6.0_21]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:94) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:80) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.VFS.mountZip(VFS.java:428) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.VFS.mountZip(VFS.java:454) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.util.automount.Automounter$RegistryEntry.mount(Automounter.java:237) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.util.automount.Automounter$RegistryEntry.access$000(Automounter.java:208) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.util.automount.Automounter.mount(Automounter.java:117) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.vfs.util.automount.Automounter.mount(Automounter.java:77) [jboss-vfs.jar:3.0.0.GA]
at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.performMount(AbstractVFSArchiveStructureDeployer.java:145) [:2.2.0.GA]
at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.mountArchive(AbstractVFSArchiveStructureDeployer.java:128) [:2.2.0.GA]
... 32 more
I have deploy the same war file to tomcat , it is successful.
Can anyone please shed some light on me?
Thanks
sam
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/587056#587056]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Messaging] - message passing through underlying db
by Tim Coninx
Tim Coninx [http://community.jboss.org/people/timconinxrvp] created the discussion
"message passing through underlying db"
To view the discussion, visit: http://community.jboss.org/message/588347#588347
--------------------------------------------------------------
Hello,
We are using a system where three jboss servers with the same application are connected to the same db. The servers are not clustered, but rather serve different audiences.
Currently we are having a problem with our jms subsystem because a queue fills up too fast because messages are causing exceptions. Normally each server will process its own messages, but because we sometimes have to restart all servers (while a queue is still filled), they suddenly all three start processing all messages that are (at that point) in the db at the same time, meaning that the number of messages failing triples.
Now we want to have a dedicated (fourth) server to handle all messages. That one will be the only one with activated message driven beans. The messages will still be published however by the three other servers.
My question: is this possible, and how ? Because normally a message published by one server will never be processed by another server on the same db (unless the message is left in the db and the server restarted). Passing the messages through the messagesucker seems a bit farfetched, as the messages are already in the correct tables.
We're also not (directly) looking for clustering the servers... although this might become the first step
I accept 'rtfm' answers, but I'd like a general chapter to read then :)
Thanks in advance
Tim
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588347#588347]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Messaging] - Messages Stuck in 'Delivering State'.
by Gurvinderpal Narula
Gurvinderpal Narula [http://community.jboss.org/people/groovenarula] created the discussion
"Messages Stuck in 'Delivering State'."
To view the discussion, visit: http://community.jboss.org/message/588306#588306
--------------------------------------------------------------
Our system consists of one virtualized VMWare guest server running Red Hat Enterprise
Server 64 bit, Java HotSpot(TM) 64-Bit Server VM
and JBoss 5.1.0.GA. The machine runs a single instance of JBoss with Postgresql (running on a different server).
The JBOSS instance is dedicated to processing JMS Messages for 3 tomcat based web application clients again running on different servers.
We have made no other changes to JBOSS Messaging Postgresql Presistence manager's configuration other then disabling 'ChannelFactoryName'
<!-- <depends optional-attribute-name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</depends> -->
(referred the following : http://community.jboss.org/message/204473#204473 http://community.jboss.org/message/204473#204473 )
The JMS clients are all Spring based web applications that consumer messages from one of the queues on the jboss server.
We deployed this configuration to production this Monday. So far the server has been very stable. The only issue that we've run into is that there are (now) about 7 messages that are stuck in the 'Delivering' state since the last 3 days. So basically everytime we look at the queue's status using the jmx-console, it shows MessageCount is stuck at 7 and DeliveringCount is also stuck at 7. The tomcat servers have recevied several other messages since we've noticed these stuck messages. We tried to remove these messages using the 'removeAllMessages' operation, but we then saw an error in the jboss logs basically stating that messages that are in a DeliveringState cannot be removed.
I would like to know if someone can please help me find a way to delete these messages. Also we have not been able to reproduce this behavior in our development / test enviroment. So we're wondering if this could have been caused by some intermittent communication failure (network not available etc) between the Jboss Servers and Tomcat Servers. Does anyone know of any such issues with the JBM version (I believe it's 1.4.3 GA) bundled with JBOSS AS 5.1.0.
We do plan to upgrade to HornetQ in the near future (there is a critical bug in the current Final version of HornetQ that we're wait to be resolved in the next version before we migrate over the HornetQ).
So if anyboby can shed some light on what could cause messages to end up in a DeliveryState and what steps I can take to remove these messages from the queue, it will be much appreciated.
Thanks in advance.
Gurvinder
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588306#588306]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[jBPM] - TaskServer, persistence file and session
by Odelya Holiday
Odelya Holiday [http://community.jboss.org/people/odelyaholiday] created the discussion
"TaskServer, persistence file and session"
To view the discussion, visit: http://community.jboss.org/message/588542#588542
--------------------------------------------------------------
Hi!
I was wondering, I so in the emergency demo application that the TaskServer retrieves the persistence file for the the task server to start like this:
emf = Persistence.createEntityManagerFactory("org.jbpm.task");
taskService = new TaskService(emf, SystemEventListenerFactory.getSystemEventListener());
In the persistence examples, I saw that actually we create the session with the persistence like this:
EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.drools.persistence.jpa");
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
env.set(EnvironmentName.GLOBALS, new MapGlobalResolver());
env.set(EnvironmentName.TRANSACTION_MANAGER, TransactionManagerServices.getTransactionManager());
ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
If I am using persistence for the ksession, do I still need to start the TaskService with a new persistence,or the same persistence can be used for both like this:
EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.drools.persistence.jpa");
taskService = new TaskService(emf, SystemEventListenerFactory.getSystemEventListener());
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
env.set(EnvironmentName.GLOBALS, new MapGlobalResolver());
env.set(EnvironmentName.TRANSACTION_MANAGER, TransactionManagerServices.getTransactionManager());
ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588542#588542]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years