[JBoss JIRA] (AS7-2067) The ear file can not deploy under AS 7.0
by Candice Chen (Created) (JIRA)
The ear file can not deploy under AS 7.0
----------------------------------------
Key: AS7-2067
URL: https://issues.jboss.org/browse/AS7-2067
Project: Application Server 7
Issue Type: Bug
Components: EE, EJB
Affects Versions: 7.0.2.Final
Reporter: Candice Chen
Assignee: David Lloyd
Priority: Critical
I have an ear file names migrate.ear which contains one ejb jar (ejb.jar) and one war file (war.war), if I put the ejb jar to a ejb folder and war file to war folder, the ear can not be depoyed.
If I move the ejb jar to war file out, it can be deployed.
Below structuer can be deployed:
ejb.jar
lib/
lib/util-1.0-SNAPSHOT.jar
lib/version.jar
META-INF/
META-INF/application.xml
META-INF/MANIFEST.MF
war.war
Below structure can not be deployed:
ejb/
ejb/ejb.jar
lib/
lib/util-1.0-SNAPSHOT.jar
lib/version.jar
META-INF/
META-INF/application.xml
META-INF/MANIFEST.MF
war/
war/war.war
Below is the error:
http://community.jboss.org/message/630869#630869
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-3878) adding a new file to logging handler, fails without indication of error
by shay Matasaro (JIRA)
shay Matasaro created AS7-3878:
----------------------------------
Summary: adding a new file to logging handler, fails without indication of error
Key: AS7-3878
URL: https://issues.jboss.org/browse/AS7-3878
Project: Application Server 7
Issue Type: Bug
Components: ConfigAdmin
Affects Versions: 7.1.0.Final
Environment: ubuntu 11.10 , AS 7.1 Final
Reporter: shay Matasaro
Assignee: Thomas Diesler
adding a new file handler , without a specific path , fails with no indication of error.
Also since the dialog does contain a generic path for log files, not specifying a new one should work
here is the trace from log file
11:28:25,030 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 21) JBAS014616: Operation ("add") failed - address: ([
("subsystem" => "logging"),
("file-handler" => "hw.log")
]) - failure description: "JBAS014704: '' is an invalid value for parameter file. Values must have a minimum length of 1 characters"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (AS7-1370) Domain Management - Add support for database authentication.
by Darran Lofthouse (JIRA)
Domain Management - Add support for database authentication.
------------------------------------------------------------
Key: AS7-1370
URL: https://issues.jboss.org/browse/AS7-1370
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
It should be possible to define a database authentication element for authentication of incoming connections against a database.
Ideally the password should be obtainable from the database to allow us to use DIGEST authentication but if not a fallback to verify the password should be supported.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-3570) jboss-ejb3.xml is not valided
by Simon Walter (JIRA)
Simon Walter created AS7-3570:
---------------------------------
Summary: jboss-ejb3.xml is not valided
Key: AS7-3570
URL: https://issues.jboss.org/browse/AS7-3570
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.CR1b
Reporter: Simon Walter
Priority: Minor
When deploying a module with invalid jboss-ejb3.xml (missing <ejb-name> in <assembly-descriptor><security:security>) there
is no validation and an NPE is thrown at deployment time.
{noformat}
11:02:45,347 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service
jboss.deployment.subunit."xxx.ear"."xxx-impl.jar".POST_MODULE: org.jboss.msc.service.StartException in service
jboss.deployment.subunit."xxx.ear"."xxx-impl.jar".POST_MODULE: Failed to process phase POST_MODULE of subdeployment "xxx-impl.jar"
of deployment "xxx.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014402: Could not merge data for XXXImpl
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:75)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.merging.SecurityDomainMergingProcessor.handleDeploymentDescriptor(SecurityDomainMergingProcessor.java:83)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.processComponentConfig(AbstractMergingProcessor.java:93)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:73)
... 6 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months