[JBoss JIRA] Created: (JBAS-8907) ERROR Cannot remove deployment
by Stan Silvert (JIRA)
ERROR Cannot remove deployment
-------------------------------
Key: JBAS-8907
URL: https://issues.jboss.org/browse/JBAS-8907
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Alpha2
Reporter: Stan Silvert
I'm guessing that this is a Windows issue. When I drop any WAR in the the /deployments directory I get errors. I have to stop the server, manually delete the WAR, and then restart. This is on master and it it still happens if I run standalone.bat as administrator.
08:26:10,346 INFO [org.jboss.modules] JBoss Modules version 1.0.0.Beta14
08:26:10,849 INFO [org.jboss.msc] JBoss MSC version 1.0.0.Beta6
08:26:10,918 INFO [org.jboss.as] JBoss AS 7.0.0.Alpha2 "Halloween" starting
08:26:12,118 INFO [org.jboss.as.server] Activating core services
08:26:12,343 INFO [org.jboss.as] creating native management service using netwo
rk interface (default) port (9999)
08:26:12,358 INFO [org.jboss.as] creating http management service using network
interface (default) port (9990)
08:26:12,383 INFO [org.jboss.as.arquillian] Activating Arquillian Subsystem
08:26:12,397 INFO [org.jboss.as.ee] Activating EE subsystem
08:26:12,419 INFO [org.jboss.as.naming] Activating Naming Subsystem
08:26:12,534 INFO [org.jboss.as.osgi] Activating OSGi Subsystem
08:26:12,535 INFO [org.jboss.as.osgi] Activating OSGi Subsystem
08:26:12,633 INFO [org.jboss.as.webservices] Activating WebServices Extension
08:26:13,026 INFO [org.jboss.as.naming] Starting Naming Service
08:26:13,036 INFO [org.jboss.as.logging] Removing bootstrap log handlers
08:26:13,237 INFO [org.jboss.as.server.deployment] (pool-5-thread-1) Content wi
th name beanvalidation.war added at location C:\as7trunk\jboss-as\build\target\j
boss-7.0.0.Alpha2\standalone\data\content\bc\b1dd10818ff57c0db8b7e6cd4595424dc4b
6ef\content
08:26:13,240 ERROR [org.jboss.as.deployment] (pool-5-thread-1) Cannot remove dep
loyment content file C:\as7trunk\jboss-as\build\target\jboss-7.0.0.Alpha2\standa
lone\deployments\beanvalidation.war
08:26:13,260 INFO [org.jboss.wsf.common.management.AbstractServerConfig] (MSC s
ervice thread 1-2) JBoss Web Services - Stack CXF Server 4.0.0.Alpha1
08:26:13,286 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting
version 3.1.0.Beta2
08:26:13,484 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-
1) Starting remote JMX connector
08:26:13,733 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-1) live server is starting..
08:26:14,086 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-2) Starting Coyote HTTP/1.1 on http-8080
08:26:14,089 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Sta
rting deployment of "beanvalidation.war"
08:26:14,123 WARN [org.jboss.vfs] (MSC service thread 1-2) VFS was unable to se
t the URLStreamHandlerFactory. This will have unpredictable results
08:26:14,242 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-1) Started Netty Acceptor version 3.2.1.Final-r2319 127.0.0.1:5445
for CORE protocol
08:26:14,261 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-1) Started Netty Acceptor version 3.2.1.Final-r2319 127.0.0.1:5455
for CORE protocol
08:26:14,269 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
08:26:14,270 INFO [org.jboss.as.connector] (MSC service thread 1-1) Starting JC
A Subsystem (JBoss IronJacamar 1.0.0.Beta3)
08:26:14,821 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC serv
ice thread 1-2) Initializing Mojarra 2.0.4 (FCS b09) for context '/beanvalidatio
n'
08:26:15,617 INFO [javax.enterprise.resource.webcontainer.jsf.application] (MSC
service thread 1-2) JSF1048: PostConstruct/PreDestroy annotations present. Man
agedBeans methods marked with these annotations will have said annotations proce
ssed.
08:26:15,849 INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] (MSC s
ervice thread 1-2) JSF1027: [null] The ELResolvers for JSF were not registered w
ith the JSP container.
08:26:15,881 INFO [org.jboss.web] (MSC service thread 1-2) registering web cont
ext: /beanvalidation
08:26:15,882 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Com
pleted deployment of "beanvalidation.war" in 1793 ms
08:26:15,882 INFO [org.jboss.as] (MSC service thread 1-1) JBoss AS 7.0.0.Alpha2
"Halloween" started in 5756ms - Started 100 of 126 services (26 services are pa
ssive or on-demand)
08:26:20,916 ERROR [org.jboss.as.deployment] (pool-5-thread-1) Cannot remove dep
loyment content file C:\as7trunk\jboss-as\build\target\jboss-7.0.0.Alpha2\standa
lone\deployments\beanvalidation.war
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-2900) Consider concurrency tasks optimization (both Jacoby and Gauss-Seidel iterations)
by Michał Warecki (JIRA)
Consider concurrency tasks optimization (both Jacoby and Gauss-Seidel iterations)
---------------------------------------------------------------------------------
Key: JBRULES-2900
URL: https://issues.jboss.org/browse/JBRULES-2900
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-docs-planner
Affects Versions: FUTURE
Reporter: Michał Warecki
Assignee: Mark Proctor
Fix For: FUTURE
Will be great to support concurrency tasks optimization.
In example we have 3 tasks A, B, C and objective function 2A^2 + A*B + B^2 + AC. With Gass-Saidel iteration (where task B in time+2 depends on A in time+1 and C in time+2 depends on A in time+1) we can execute tasks A,B,C in order: A and BC cocurrently, so in 2 iterations. Without optimization tasks will be executed in 3 iterations (A , B, C).
We should support Jocoby iteration as well where tasks B and C does not depend on A in previous iteration.
This can be done with Gradient Method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-8863) Enable SAAJ functionalities
by Alessio Soldano (JIRA)
Enable SAAJ functionalities
---------------------------
Key: JBAS-8863
URL: https://issues.jboss.org/browse/JBAS-8863
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 7.0.0.Alpha2
Currently we have the javax.xml.soap.api module which contains jboss-saaj-api_1.3_spec-1.0.0.Final . That tries to load the com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl class when asked for a SAAJMetaFactory instance and no specific configuration is provided.
That class is in saaj-impl.jar, so either we ship that too in AS7 or we fix our saaj API for referencing the internal JDK SAAJMetaFactory impl.
After a brief chat with David on IRC, it seems the best solution is shipping saaj-impl.jar (com.sun.xml.messaging.saaj:saaj-impl)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (LOGTOOL-11) Refactor into Core Generation and Specific Annotation Processing Modules
by Ken Finnigan (JIRA)
Refactor into Core Generation and Specific Annotation Processing Modules
------------------------------------------------------------------------
Key: LOGTOOL-11
URL: https://issues.jboss.org/browse/LOGTOOL-11
Project: Log Tool
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta3
Reporter: Ken Finnigan
Assignee: David Lloyd
JBoss Solder/Seam would like to use their own annotations for generating message classes instead of those found within JBoss Logging, as recommended by David Lloyd.
At present the Annotation processor in Logging Tools specifically references the JBoss Logging annotations by package and imports them to use in generating the classes.
What we'd like is to create a core processing module that has common functionality that is agnostic of whatever annotations need to be processed, or what methods those annotations may have, and then modules bolted on top of that for specific JBoss Logging annotation processing.
This then allows the creation of a Solder/Seam specific annotation processor module that utilizes the core, without having to fork the entire project to achieve it.
Have discussed this with both James and David, and James is currently working on a prototype.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBJCA-480) Add jmx monitoring to jvm.
by Jeremy Whiting (JIRA)
Add jmx monitoring to jvm.
--------------------------
Key: JBJCA-480
URL: https://jira.jboss.org/browse/JBJCA-480
Project: IronJacamar
Issue Type: Task
Components: Performance
Environment: All environments.
Reporter: Jeremy Whiting
Assignee: Jesper Pedersen
Priority: Minor
This contribution changes the jmeter benchmarking to provide JMX monitoring.
Also the in memory database used is changed to HSQLDB due to it's ability to shutdown a standalone database.
The performance guide documentation has also been updated with instructions to control jvm processes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBCL-94) Spaces in URLs returned by getResource() should in vfszip: handler
by Ondrej Medek (JIRA)
Spaces in URLs returned by getResource() should in vfszip: handler
------------------------------------------------------------------
Key: JBCL-94
URL: https://jira.jboss.org/jira/browse/JBCL-94
Project: JBoss ClassLoader
Issue Type: Bug
Components: ClassLoader
Environment: JBoss AS 5.0.1, WinXP, JDK 1.6.0u12
Reporter: Ondrej Medek
Priority: Minor
Hi,
I have an EAR deployed as directory (not as JAR). Inside I have one service bean and a config directory. I have tried to deploy config directory as a plain directory and packed in the JAR. I have spotted different behaviour of handling spaces in the resource URLS returned by org.jboss.classloader.spi.base.BaseClassLoader when accessing the config directory. My service bean reads config direcory by:
this.getClass().getClassLoader().getResource("conf/")
I get the URL: vfsfile:/C:/Program%20Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/conf/
(Space is '%20')
however, when I put the resource in the JAR and access it by:
this.getClass().getClassLoader().getResource("prinsee-client.jar/conf")
I get the URL: vfszip:/C:/Program Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/prinsee-client.jar/conf/
(Space is ' ').
I think, the behaviour of vfszip: handler is wrong. The space should be always '%20'.
Cheers
andy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month