[JBoss JIRA] (WFLY-877) too many classes on classpath break RAR deployments without deployment descriptor
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-877?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen updated WFLY-877:
---------------------------------
Fix Version/s: (was: 9.0.0.Beta1)
> too many classes on classpath break RAR deployments without deployment descriptor
> ---------------------------------------------------------------------------------
>
> Key: WFLY-877
> URL: https://issues.jboss.org/browse/WFLY-877
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Marcel Šebek
> Assignee: Stefano Maestri
> Attachments: test-ra.zip
>
>
> An EAR containing a RAR and a large number of classes cannot be deployed, the exception depends on jboss version. For example, the latest 7.1 snapshot produces the following:
> 14:37:57,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "test-ear.ear"
> 14:37:57,499 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test-rar-2.0.0-SNAPSHOT.rar"
> 14:37:57,499 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test-ejb-2.0.0-SNAPSHOT.jar"
> 14:37:57,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "test-rar-2.0.0-SNAPSHOT.rar" of deployment "test-ear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
> at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:185)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:351)
> at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:332)
> at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:142)
> ... 6 more
> 14:37:58,104 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "test-ear.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"test-ear.ear\".\"test-rar-2.0.0-SNAPSHOT.rar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"test-ear.ear\".\"test-rar-2.0.0-SNAPSHOT.rar\".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment \"test-rar-2.0.0-SNAPSHOT.rar\" of deployment \"test-ear.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"test-ear.ear\".CLEANUP Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.CREATE Missing[jboss.ra.\"test-ear.ear#test-rar-2.0.0-SNAPSHOT\"]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".CLEANUP Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.VIEW.\"test.TestEventListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more transitive dependencies>]"]}
> 14:37:58,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test-ejb-2.0.0-SNAPSHOT.jar in 38ms
> 14:37:58,142 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment test-rar-2.0.0-SNAPSHOT.rar in 39ms
> 14:37:58,149 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment test-ear.ear in 46ms
> 14:37:58,152 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"test-ear.ear\".\"test-rar-2.0.0-SNAPSHOT.rar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"test-ear.ear\".\"test-rar-2.0.0-SNAPSHOT.rar\".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment \"test-rar-2.0.0-SNAPSHOT.rar\" of deployment \"test-ear.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"test-ear.ear\".CLEANUP Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.CREATE Missing[jboss.ra.\"test-ear.ear#test-rar-2.0.0-SNAPSHOT\"]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".CLEANUP Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.VIEW.\"test.TestEventListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more transitive dependencies>]"]}}}
> However, the same event (with slightly more readable exception) occurs in 7.2 snapshot too. An EAR that exhibits this is attached. If you comment out maven dependencies, you will be able to deploy the same EAR. If you put different dependencies, you will get the same error again. The problem seems to depend only on the classpath size, more classes causes the problem to occur more likely.
> The problem is that when JCA container builds ra.xml from JCA 1.6 annotations, for some reason the content of <resourceadapter-class> tag is null (the string "null"). As a workaround for resource adapters with large classpath, one can supply a deployment descriptor with just <resourceadapter-class> tag containing the correct value.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-1882) JCA should be able to access the CDI-enabled ValidatorFactory
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-1882?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-1882:
----------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> JCA should be able to access the CDI-enabled ValidatorFactory
> -------------------------------------------------------------
>
> Key: WFLY-1882
> URL: https://issues.jboss.org/browse/WFLY-1882
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Farah Juma
> Assignee: Stefano Maestri
> Fix For: 9.0.0.CR1
>
>
> The JCAValidatorFactory is currently a copy of an older version of the EE LazyValidatorFactory. The delegate of the EE LazyValidatorFactory was recently replaced with a CDI-enabled ValidatorFactory (see WFLY-529). JCA needs to be able to access the CDI-enabled ValidatorFactory as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-2160:
----------------------------------
Fix Version/s: (was: 9.0.0.Beta1)
> Allow Expression for datasource subsystem enabled property
> ----------------------------------------------------------
>
> Key: WFLY-2160
> URL: https://issues.jboss.org/browse/WFLY-2160
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Steven Rose
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: wildfly
>
> Currently the datasource sub system does not allow expressions. I would like to be able to do this: <datasource jta="true" jndi-name="java:/ds1DS" pool-name="ds1DS" enabled="${ds1.enabled}" use-java-context="true" use-ccm="true"> and set the ds1.enabled property via a properties file.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4431) IJ020017: Invalid archive
by Jesper Pedersen (JIRA)
Jesper Pedersen created WFLY-4431:
-------------------------------------
Summary: IJ020017: Invalid archive
Key: WFLY-4431
URL: https://issues.jboss.org/browse/WFLY-4431
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Priority: Critical
Fix For: 9.0.0.CR1
{noformat}
wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/tmp/vfs/temp/temp146a05eee4929397/content-167c9962bff9f1b5/contents/
{noformat}
is shown as path, where as
{noformat}
wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/tmp/vfs/temp/temp146a05eee4929397/content-167c9962bff9f1b5/content
{noformat}
should be used, or the .rar archive should be expanded into the directory
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4379) Always expose <transaction-support> for resource adapters
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-4379?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-4379:
----------------------------------
Priority: Critical (was: Major)
> Always expose <transaction-support> for resource adapters
> ---------------------------------------------------------
>
> Key: WFLY-4379
> URL: https://issues.jboss.org/browse/WFLY-4379
> Project: WildFly
> Issue Type: Task
> Components: JCA
> Reporter: Jesper Pedersen
> Assignee: Stefano Maestri
> Priority: Critical
> Fix For: 9.0.0.CR1
>
>
> The <transaction-support> setting for resource adapters should always be exposed in the DMR model - e.g. no "undefined".
> If the value isn't explicit defined by the deployment, then it will be obtained from the metadata repository of the archive in question.
> This also makes it clear that <xa-pool> is used for XATransaction deployments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4430) Remove transport from DWM
by Jesper Pedersen (JIRA)
Jesper Pedersen created WFLY-4430:
-------------------------------------
Summary: Remove transport from DWM
Key: WFLY-4430
URL: https://issues.jboss.org/browse/WFLY-4430
Project: WildFly
Issue Type: Task
Components: JCA
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Priority: Blocker
Fix For: 9.0.0.CR1
Remove 'transport' and 'transportType' from DWM. Use the unique name of the DWM for channel name
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4429) Refactor JCA subsystems
by Jesper Pedersen (JIRA)
Jesper Pedersen created WFLY-4429:
-------------------------------------
Summary: Refactor JCA subsystems
Key: WFLY-4429
URL: https://issues.jboss.org/browse/WFLY-4429
Project: WildFly
Issue Type: Task
Components: JCA
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Priority: Blocker
Fix For: 9.0.0.CR1
Make use of PASSIVE services, and PersistentResource in :jca:, :datasources: and :resource-adapters:
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3991) JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3991?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3991:
-----------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1195150|https://bugzilla.redhat.com/show_bug.cgi?id=1195150] from ASSIGNED to CLOSED
> JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3991
> URL: https://issues.jboss.org/browse/WFLY-3991
> Project: WildFly
> Issue Type: Enhancement
> Reporter: Manuel Blechschmidt
> Assignee: Jason Greene
> Labels: JS223, JavaScript, Scripting
>
> When using the ScriptManager in a JSF bean the following happens:
> ERROR [stderr] (default task-21) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> {code}
> package de.example.log.jsf;
> import java.io.ByteArrayOutputStream;
> import java.io.IOException;
> import java.io.PrintStream;
> import javax.enterprise.inject.Model;
> import javax.faces.application.FacesMessage;
> import javax.faces.context.FacesContext;
> import javax.inject.Inject;
> import javax.script.Bindings;
> import javax.script.ScriptEngine;
> import javax.script.ScriptEngineManager;
> import javax.script.ScriptException;
> @Model
> public class Scripting {
> private String script;
> private String output;
> private ScriptEngineManager mgr = new ScriptEngineManager();
> public static String utilJavaScript = "var print = function (s) { __newOut.print(s); }; var println = function (s) { __newOut.println(s); };";
> public String execute() {
> ScriptEngine jsEngine = mgr.getEngineByName("JavaScript");
> ByteArrayOutputStream outputBuffer = new ByteArrayOutputStream(8192);
> PrintStream newOut = new PrintStream(outputBuffer, true);
> Bindings bindings = jsEngine.createBindings();
> bindings.put("__newOut", newOut);
> try {
> jsEngine.eval(utilJavaScript + getScript(), bindings);
> } catch (ScriptException from) {
> FacesContext.getCurrentInstance().addMessage(
> null,
> new FacesMessage(from.getColumnNumber() + " "
> + from.getFileName() + " " + from.getLineNumber()
> + " " + from.getMessage()));
> return null;
> }
> newOut.close();
> String returnString = outputBuffer.toString();
> setOutput(returnString);
> try {
> outputBuffer.close();
> } catch (IOException e) {
> FacesContext.getCurrentInstance().addMessage(
> null,
> new FacesMessage(e.getLocalizedMessage()));
> }
> return null;
> }
> public String getScript() {
> return script;
> }
> public void setScript(String script) {
> this.script = script;
> }
> public String getOutput() {
> return output;
> }
> public void setOutput(String output) {
> this.output = output;
> }
> }
> {code}
> The script engines are configured in the following file:
> WILDFLY_HOME/modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory
> {code}
> com.sun.script.javascript.RhinoScriptEngineFactory
> jdk.nashorn.api.scripting.NashornScriptEngineFactory
> {code}
> It should be made sure that with every JDK JSR 223 compliant requests for a JavaScript engine will work out of the box.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months