[JBoss JIRA] Created: (AS7-1353) Load on startup is ignored - JaxWS webservice is always initialized first
by Alexander Rashed (JIRA)
Load on startup is ignored - JaxWS webservice is always initialized first
-------------------------------------------------------------------------
Key: AS7-1353
URL: https://issues.jboss.org/browse/AS7-1353
Project: Application Server 7
Issue Type: Feature Request
Components: Web Services
Affects Versions: 7.0.0.Final
Environment: Windows 7
Reporter: Alexander Rashed
Assignee: Alessio Soldano
I want to execute a servlet on startup to initialize my environment (for db access, resource management and so on).
This servlet just implements javax.servlet.Servlet.
The other services (using JaxWS) should be instantiated after the Startup-servlet to provide access to the created resources.
But they are always instantiated before the Startup-servlet, even if I use the <load-on-startup> parameter in the web.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-835) ejb-jar.xml doesn't need to define a session-type
by Carlo de Wolf (JIRA)
ejb-jar.xml doesn't need to define a session-type
-------------------------------------------------
Key: AS7-835
URL: https://issues.jboss.org/browse/AS7-835
Project: Application Server 7
Issue Type: Bug
Reporter: Carlo de Wolf
Assignee: Jason Greene
session-type in ejb-jar.xml does not need to be specified, the type might come from annotations.
{noformat}
21:56:21,759 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."ejbembed_vehicle_ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejbembed_vehicle_ejb.jar".PARSE: Failed to process phase PARSE of deployment "ejbembed_vehicle_ejb.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unknown session-type for session bean: EJBContextBean in deployment unit: deployment "ejbembed_vehicle_ejb.jar"
at org.jboss.as.ejb3.deployment.processors.dd.SessionBeanXmlDescriptorProcessor.processBeanMetaData(SessionBeanXmlDescriptorProcessor.java:96)
at org.jboss.as.ejb3.deployment.processors.dd.SessionBeanXmlDescriptorProcessor.processBeanMetaData(SessionBeanXmlDescriptorProcessor.java:64)
at org.jboss.as.ejb3.deployment.processors.dd.AbstractEjbXmlDescriptorProcessor.deploy(AbstractEjbXmlDescriptorProcessor.java:78)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 4 more
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-888) Deployment of persistence bundle fails
by Thomas Diesler (JIRA)
Deployment of persistence bundle fails
--------------------------------------
Key: AS7-888
URL: https://issues.jboss.org/browse/AS7-888
Project: Application Server 7
Issue Type: Bug
Reporter: Thomas Diesler
Assignee: Thomas Diesler
I am checking out the JBoss 7 beta3 version and got into a deployment problem: I have a persistence bundle (using static access) with a META-INF/persistence.xml file. Upon deployment it fails with the stacktrace below. Removing persistence.xml removes the error (but of cause criples the persistence functionality).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-945) NPE in OSGiXServiceParseProcessor
by David Bosschaert (JIRA)
NPE in OSGiXServiceParseProcessor
---------------------------------
Key: AS7-945
URL: https://issues.jboss.org/browse/AS7-945
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Scott Stark wrote:
I'm seeing this NPE when trying to deploy a resteasy war that only
contains a couple of the json related jars, apparently because the
jettison-1.2.jar include some osgi bundle attributes.
[198](ironmaideneployments) > ls agent-1.0.war/WEB-INF/lib/
jettison-1.2.jar resteasy-jettison-provider-2.2-RC-1.jar
[217](ironmaideneployments) > java DumpManifest
agent-1.0.war/WEB-INF/lib/resteasy-jettison-provider-2.2-RC-1.jar
Build-Jdk: 1.6.0_24
Built-By: billburke
Manifest-Version: 1.0
Created-By: Apache Maven
Archiver-Version: Plexus Archiver
[218](ironmaideneployments) > java DumpManifest
agent-1.0.war/WEB-INF/lib/jettison-1.2.jar
Export-Package:
org.codehaus.jettison.util;version=1.2,org.codehaus.jettison.badgerfish;uses:="org.codehaus.jettison.util,javax.xml.stream,org.codehaus.jettison.json,org.codehaus.jettison,javax.xml.namespace";version=1.2,org.codehaus.jettison.mapped;uses:="org.codehaus.jettison.util,javax.xml.stream,org.codehaus.jettison.json,org.codehaus.jettison,javax.xml.namespace";version=1.2,org.codehaus.jettison.json;version=1.2,org.codehaus.jettison;uses:="org.codehaus.jettison.json,javax.xml.parsers,javax.xml.transform.dom,javax.xml.stream.events,org.w3c.dom,javax.xml.namespace,org.codehaus.jettison.util,javax.xml.stream,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.stream";version=1.2
Private-Package: !*
Implementation-Title: Jettison
Implementation-Version: 1.2
Manifest-Version: 1.0
Tool: Bnd-0.0.160
Bundle-Name: jettison
Created-By: 1.6.0_17 (Apple Inc.)
Bundle-Version: 1.2
Bnd-LastModified: 1263724814999
Bundle-ManifestVersion: 2
Bundle-Description: A StAX implementation for JSON.
Bundle-SymbolicName: org.codehaus.jettison.jettison
Include-Resource: src/main/resources
Import-Package:
javax.xml.namespace,javax.xml.parsers,javax.xml.stream,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.stream,org.codehaus.jettison;version=1.2,org.codehaus.jettison.badgerfish;version=1.2,org.codehaus.jettison.json;version=1.2,org.codehaus.jettison.mapped;version=1.2,org.codehaus.jettison.util;version=1.2,org.w3c.dom
11:50:01,783 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3)
MSC00001: Failed to start service
jboss.deployment.unit."agent-1.0.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."agent-1.0.war".PARSE: Failed to process phase
PARSE of deployment "agent-1.0.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
[jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.lang.NullPointerException
at
org.jboss.as.osgi.deployment.OSGiXServiceParseProcessor.deploy(OSGiXServiceParseProcessor.java:55)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
... 4 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JGRP-1260) NPE in UUID.toString
by Adrian tarau (JIRA)
NPE in UUID.toString
--------------------
Key: JGRP-1260
URL: https://jira.jboss.org/browse/JGRP-1260
Project: JGroups
Issue Type: Bug
Affects Versions: 2.10
Environment: Linux/Cent OS 5.X
Reporter: Adrian tarau
Assignee: Bela Ban
Intermittent failures in NACKAK due to a NPE in UUID.toString
java.lang.NullPointerException
at org.jgroups.util.UUID.toString(UUID.java:183)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java:115)
at org.jgroups.Message.toString(Message.java:459)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java:115)
at
org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:880)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:671)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:120)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:132)
at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:177)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:270)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:210)
at org.jgroups.protocols.Discovery.up(Discovery.java:281)
at org.jgroups.protocols.PING.up(PING.java:67)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1009)
at org.jgroups.protocols.TP.access$100(TP.java:56)
at
org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1549)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1531)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBMESSAGING-1886) After clearBody() followed by QueueSession.recover() redelivered message is not correct
by Colin Mondesir (JIRA)
After clearBody() followed by QueueSession.recover() redelivered message is not correct
---------------------------------------------------------------------------------------
Key: JBMESSAGING-1886
URL: https://issues.jboss.org/browse/JBMESSAGING-1886
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP13
Reporter: Colin Mondesir
Assignee: Yong Hao Gao
After calling clearBody() on a message followed by QueueSession.recover() the re-delivered message does not contain the original body. I've verified this behaviour on EAP 4.3 CP09.
The spec states:
------------------------------------------
A consumer can modify a received message after calling either the clearBody or
clearProperties method to make the body or properties writable. If the consumer
modifies a received message, and the message is subsequently redelivered, the
redelivered message must be the original, unmodified message
------------------------------------------
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-1303) TestNG not supported by Arquillian Service
by Aslak Knutsen (JIRA)
TestNG not supported by Arquillian Service
------------------------------------------
Key: AS7-1303
URL: https://issues.jboss.org/browse/AS7-1303
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 7.0.1.Final
The Arquillian Service deployed during execution has a Deployment Processor hook to scan for "Test Deployments" so it can lookup the Module etc during execution. This scan assumes the TestDeployment will contain JUnits @RunWith annotation, which is true for JUnit, but not so much for other test frameworks.
Arquillian is built to work with any test framework so TestNG/ScalaTest/Spock etc are all valid targets.
Since the Arquillian Service is no longer a pre installed service, but deployed only during test execution, it could make sense to remove the scanning(used to filter out test deployment) and just consume all deployments during it's life time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-1325) Cannot create dependency on SNAPSHOT bundle
by Thomas Diesler (JIRA)
Cannot create dependency on SNAPSHOT bundle
-------------------------------------------
Key: AS7-1325
URL: https://issues.jboss.org/browse/AS7-1325
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Final
Reporter: Thomas Diesler
Assignee: Thomas Diesler
08:32:24,892 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "jboss-osgi-example-jbossas-webapp-1.0.0-SNAPSHOT.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"jboss-osgi-example-jbossas-webapp-1.0.0-SNAPSHOT.war\".CONFIGURE_MODULE missing [ jboss.module.information.service.\"deployment.jboss-osgi-example-jbossas-bundle\".\"1.0.0-SNAPSHOT\" ]"]}
08:32:24,893 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) Service status report
New missing/unsatisfied dependencies:
service jboss.module.information.service."deployment.jboss-osgi-example-jbossas-bundle"."1.0.0-SNAPSHOT" (missing)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months