[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.
by Michael Hauke (JIRA)
[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ]
Michael Hauke edited comment on WFLY-3189 at 9/16/14 3:29 PM:
--------------------------------------------------------------
Hi Rob,
as far as I see all the failed tests are in "testsuite/integration/smoke" and relate to "jboss-ejb-clustering_1_0.xsd", added by the pull the request.
"testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/StandardConfigsXMLValidationUnitTestCase.java" has a static initializer, which adds some XSD to a set called "EXCLUDED_SCHEMA_FILES", starting here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/smok..., with a reference to a Bug in Xercesj, including "jboss-ejb3-2_0.xsd", "jboss-ejb3-spec-2_0.xsd", "jboss-ejb-security_*.xsd" and so on, i.e. probably all the schemata redefining the "javaee" name space.
I added "jboss-ejb-clustering_1_0.xsd" to this set and ran the tests in "testsuite/integration/smoke" and got no failures, Maven says: "Tests run: 109, Failures: 0, Errors: 0, Skipped: 2". I don't know what's about the skipped tests.
I'd propose to add "jboss-ejb-clustering_1_0.xsd" to the excluded XSD. I don't know how to amend your pull request to include that. Maybe you could do that?
was (Author: mhauke):
Hi Rob,
as far as I see all the failed tests are in "testsuite/integration/smoke" and relate to "jboss-ejb-clustering_1_0.xsd", added by the pull the request.
"testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/StandardConfigsXMLValidationUnitTestCase.java" has a static initializer, which adds some XSD to a set called "EXCLUDED_SCHEMA_FILES", starting here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/smok..., with a reference to a Bug in Xercesj, including "jboss-ejb3-2_0.xsd", "jboss-ejb3-spec-2_0.xsd", "jboss-ejb-security_*.xsd" and so on, i.e. probably all the schemata redefining the "javaee" name space.
I added "jboss-ejb-clustering_1_0.xsd" to this set and ran the tests in "testsuite/integration/smoke" and got no failures, Maven says: "Tests run: 109, Failures: 0, Errors: 0, Skipped: 2", I don't know what's about the skipped tests.
I'd propose to add "jboss-ejb-clustering_1_0.xsd" to the excluded XSD. I don't know how to amend your pull request to include that. Maybe you could do that?
> Error validating jboss-ejb3.xml.
> --------------------------------
>
> Key: WFLY-3189
> URL: https://issues.jboss.org/browse/WFLY-3189
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Environment: WildFly 8.0.0.Final
> Reporter: shinzey shinzey
> Assignee: David Lloyd
> Attachments: p.patch
>
>
> I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error:
> {noformat}
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33]
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37]
> src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39]
> {noformat}
> The jboss-ejb3.xml is quite simple:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss:ejb-jar version="3.1" impl-version="2.0"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns:s="urn:security:1.1"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd
> http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd">
> <assembly-descriptor>
> <s:security>
> <ejb-name>*</ejb-name>
> <s:security-domain>testsd</s:security-domain>
> </s:security>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.
by Michael Hauke (JIRA)
[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ]
Michael Hauke edited comment on WFLY-3189 at 9/16/14 3:21 PM:
--------------------------------------------------------------
Hi Rob,
as far as I see all the failed tests are in "testsuite/integration/smoke" and relate to "jboss-ejb-clustering_1_0.xsd", added by the pull the request.
"testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/StandardConfigsXMLValidationUnitTestCase.java" has a static initializer, which adds some XSD to a set called "EXCLUDED_SCHEMA_FILES", starting here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/smok..., with a reference to a Bug in Xercesj, including "jboss-ejb3-2_0.xsd", "jboss-ejb3-spec-2_0.xsd", "jboss-ejb-security_*.xsd" and so on, i.e. probably all the schemata redefining the "javaee" name space.
I added "jboss-ejb-clustering_1_0.xsd" to this set and ran the tests in "testsuite/integration/smoke" and got no failures, Maven says: "Tests run: 109, Failures: 0, Errors: 0, Skipped: 2", I don't know what's about the skipped tests.
I'd propose to add "jboss-ejb-clustering_1_0.xsd" to the excluded XSD. I don't know how to amend your pull request to include that. Maybe you could do that?
was (Author: mhauke):
Hi Rob,
as far as I see all the failed tests are in "testsuite/integration/smoke" and relate to "jboss-ejb-clustering_1_0.xsd" (added by the pull the request).
"testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/StandardConfigsXMLValidationUnitTestCase.java" has a static initializer, which adds some XSD to a set called "EXLUDED_SCHEMA_FILES", starting here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/smok..., with a reference to a Bug in Xercesj, including "jboss-ejb3-2_0.xsd", "jboss-ejb3-spec-2_0.xsd", "jboss-ejb-security_*.xsd" and so on, i.e. probably all the schemata redefining the "javaee" name space.
I added "jboss-ejb-clustering_1_0.xsd" to this set and ran the tests in "testsuite/integration/smoke" and got no failures, Maven says: "Tests run: 109, Failures: 0, Errors: 0, Skipped: 2", I don't know what's about the skipped tests.
I'd propose to add "jboss-ejb-clustering_1_0.xsd" to the excluded XSD. I don't know how to amend your pull request to include that. Maybe you could do that?
> Error validating jboss-ejb3.xml.
> --------------------------------
>
> Key: WFLY-3189
> URL: https://issues.jboss.org/browse/WFLY-3189
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Environment: WildFly 8.0.0.Final
> Reporter: shinzey shinzey
> Assignee: David Lloyd
> Attachments: p.patch
>
>
> I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error:
> {noformat}
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33]
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37]
> src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39]
> {noformat}
> The jboss-ejb3.xml is quite simple:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss:ejb-jar version="3.1" impl-version="2.0"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns:s="urn:security:1.1"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd
> http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd">
> <assembly-descriptor>
> <s:security>
> <ejb-name>*</ejb-name>
> <s:security-domain>testsd</s:security-domain>
> </s:security>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2515) JBAS014249 if a fire and forget asynchronous ejb call is made
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2515?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2515:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1030936|https://bugzilla.redhat.com/show_bug.cgi?id=1030936] from MODIFIED to ON_QA
> JBAS014249 if a fire and forget asynchronous ejb call is made
> -------------------------------------------------------------
>
> Key: WFLY-2515
> URL: https://issues.jboss.org/browse/WFLY-2515
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Beta1, 8.0.0.CR1
> Environment: Beta2 SNAPSHOT
> Reporter: Wolf-Dieter Fink
> Assignee: David Lloyd
>
> If an ejb method
> @Asynchronous void fireAndForget(...)
> is called remote and the client disconnect an Exception JBAS014249 will be thrown if the async method return.
> {noformat}
> ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014249: Error invoking method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname : java.lang.NullPointerException
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 11:30:20,242 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.jboss.remoting3.NotOpenException: Writes closed
> at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:112)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:301)
> at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:68)
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2464) simpler (than OBJECT) parser for STRING parameters and properties
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2464?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2464:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1026319|https://bugzilla.redhat.com/show_bug.cgi?id=1026319] from MODIFIED to ON_QA
> simpler (than OBJECT) parser for STRING parameters and properties
> -----------------------------------------------------------------
>
> Key: WFLY-2464
> URL: https://issues.jboss.org/browse/WFLY-2464
> Project: WildFly
> Issue Type: Task
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.CR1
>
>
> At the moment a general parser (which recognizes objects, lists, properties, etc) is used for properties and parameters of type STRING. The problem with this is that some characters that appear special in values of types OBJECT, PROPERTY, LIST, etc have to be escaped in values of type STRING. E.g.
> --connection-url=jdbc:h2:~/unifiedpush;DB_CLOSE_DELAY=-1
> Here the equals sign before -1 has to be escaped, otherwise the value will be treated as PROPERTY and the equals sign as a name/value separator.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3429) Classloader leak in JBossCachedAuthenticationManager
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3429?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3429:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1103735|https://bugzilla.redhat.com/show_bug.cgi?id=1103735] from MODIFIED to ON_QA
> Classloader leak in JBossCachedAuthenticationManager
> ----------------------------------------------------
>
> Key: WFLY-3429
> URL: https://issues.jboss.org/browse/WFLY-3429
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Reporter: Josef Cacek
> Assignee: Emmanuel Hugonnet
> Priority: Critical
>
> When using a security domain with {{cache-type="default"}}, then the ModuleClassLoader instances related to deployments leak through JBossCachedAuthenticationManager.
> The problematic piece of code is the domainCache member variable which in the DomainInfo value holds a LoginContext instance. This LoginContext has member contextClassLoader which causes the leak. (It points to the ModuleClassLoader of the deployment).
> One option to solve this issue could be to remove the cache entries which are related to the undeployed application.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2011) jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2011?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2011:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1004856|https://bugzilla.redhat.com/show_bug.cgi?id=1004856] from MODIFIED to ON_QA
> jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element
> -------------------------------------------------------------------------------------
>
> Key: WFLY-2011
> URL: https://issues.jboss.org/browse/WFLY-2011
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Labels: ejb-jar.xml
> Fix For: 8.0.0.CR1
>
>
> If beans of an application are marked as clustered by using the jboss-ejb3.xml DD the behaviour is not consistent.
> From the XSD the <ejb-name> element can not be added multiple times.
> And the following configuration will be not valid:
> <assembly-descriptor>
> <c:clustering>
> <ejb-name>Bean1</ejb-name>
> <ejb-name>Bean2</ejb-name>
> <c:clustered>true</c:clustered>
> </c:clustering>
> </assembly-descriptor>
> The parser should throw an Exception and the application should not be deployed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2141) Unexpected non-integer input in vault.sh causes error
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2141?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2141:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 951011|https://bugzilla.redhat.com/show_bug.cgi?id=951011] from MODIFIED to ON_QA
> Unexpected non-integer input in vault.sh causes error
> -----------------------------------------------------
>
> Key: WFLY-2141
> URL: https://issues.jboss.org/browse/WFLY-2141
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.0.0.Alpha4
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
> Fix For: 8.0.0.Beta1
>
>
> Execute bin/vault.sh, then input a non-integer parameter cause:
> {noformat}
> Exception in thread "main" java.util.InputMismatchException
> at java.util.Scanner.throwFor(Scanner.java:909)
> at java.util.Scanner.next(Scanner.java:1530)
> at java.util.Scanner.nextInt(Scanner.java:2160)
> at java.util.Scanner.nextInt(Scanner.java:2119)
> at org.jboss.as.security.vault.VaultTool.main(VaultTool.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.modules.Module.run(Module.java:292)
> at org.jboss.modules.Main.main(Main.java:455)
> {noformat}
> Because VaultTool.main() only scans next token of the input as an int, better catch the InputMismatchException and exit peacefully as default action.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-92) cli deploy command with unpaired quotation mark causes StringIndexOutOfBoundsException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-92?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-92:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1139515|https://bugzilla.redhat.com/show_bug.cgi?id=1139515] from MODIFIED to ON_QA
> cli deploy command with unpaired quotation mark causes StringIndexOutOfBoundsException
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-92
> URL: https://issues.jboss.org/browse/WFCORE-92
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 1.0.0.Alpha5, 1.0.0.Alpha6
> Environment: * Windows Operating System is Must *
> Reporter: Jay Kumar SenSharma
> Assignee: Alexey Loubyansky
> Fix For: 1.0.0.Alpha6
>
>
> - CLI "deploy" command with open quote and tab for completion results in a "StringIndexOutOfBoundsException" exception
> - Type 'connect' to connect to the server or 'help' for the list of supported commands.
> {code}
> [disconnected /] connect
> [standalone@localhost:9999 /] deploy "d<Tab>
> [standalone@localhost:9990 /] deploy "djava.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1958)
> at org.jboss.as.cli.handlers.WindowsFilenameTabCompleter.complete(WindowsFilenameTabCompleter.java:54)
> at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:229)
> at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:73)
> at org.jboss.as.cli.CommandCompleter.doComplete(CommandCompleter.java:126)
> at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:63)
> at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:102)
> at org.jboss.aesh.console.Console.complete(Console.java:1155)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:550)
> at org.jboss.aesh.console.Console.read(Console.java:452)
> at org.jboss.aesh.console.Console.read(Console.java:346)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:178)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1283)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:254)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:312)
> at org.jboss.modules.Main.main(Main.java:460)
> Press any key to continue . . .
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years