Change CLI to Default to Remoting
by Darran Lofthouse
Hello all,
I am currently working on the following issue: -
https://issues.jboss.org/browse/WFLY-1664
Recent changes to the CLI mean that it is assuming unless told otherwise
that a HTTP Upgrade is going to be used when connecting to the server,
this means that command already used in scripts to connect to servers
are going to fail unless the scheme is included in the URI.
I chatted with David to see if there were any options to auto detect
this and fall back to pure Remoting if the remote side of the connection
is pure Remoting - however of the two options available they were both
fairly hacky or unreliable.
So the alternative is to drop the CLI back to assuming a pure Remoting
connection unless told otherwise.
- Calling connect or starting with -c will still use http-remoting
against the local server as that is defined in the jboss-cli.xml
- Calling connect or --controller with a host and port will assume
connecting directly to remoting.
- Users wanting HTTP upgrade to other servers will need to specify
http-remoting or https-remoting as the scheme when specifying the remote
address.
One other idea that I have had for the CLI if end users do want the
parameter to the connect command to be as short as possible is to add
multiple host aliases to the jboss-cli.xml - that way the protocol host
and port can be specified in the config and the alias passed to the
connect command. Additionally this would allow us to place different
SSL configuration against each host but.
Regards,
Darran Lofthouse.
10 years, 10 months
JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"
by Arun Gupta
Hello there ..
Trying to deploy a simple JMS sample that uses classic and simplified
API. The sample is available at:
https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receiv...
But the deployment is failing with:
07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
rolled back with the following failure message:
{"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]"
]}
Any suggestions ?
Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
10 years, 10 months
multinode testsuite
by Frank Langelage
I'm still trying to run the complete testsuite without everything where
multiple instances of WildFly are started (clustering, multinode, ...).
Main reason is I do not enough free memory resources.
And as I anyways only use WildFly in standalone mode I want to see the
other tests passing on my system but don't care about clustering.
I'm running build/test with "ksh build.sh clean install -DallTests
-Dts.noClustering -DnoMultinode" now.
I see that clustering testsuite code gets compiled but testsuite is not
executed. Fine!
But this does not work for multinode testsuite. Testsuite is executed,
although I have -DnoMultinode which is the activation property name in
pom.xml.
What am I missing?
The multinode tests seems to be configured bad some how.
I have WildFly sources located in directory /home/jboss/WildFly-8.0/.
Testsuite execution fails with
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running
org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.32 sec
<<< FAILURE!
Running org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.077
sec <<< FAILURE!
Running
org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043
sec <<< FAILURE!
Results :
Tests in error:
org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase:
jbossHome '/mbi/tools/jboss/8.0' must exist
org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase:
Arquillian has previously been attempted initialized, but failed. See
cause for previous exception
org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase:
Arquillian has previously been attempted initialized, but failed. See
cause for previous exception
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0
It does not use the server just build from sources in
/home/jboss/WildFly-8.0/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT but
tries to start the one in $JBOSS_HOME = /mbi/tools/jboss/8.0.
10 years, 10 months
MDB throwing InvalidPropertyException
by Arun Gupta
Sample has a MDB defined as:
@MessageDriven(mappedName = "java:global/jms/myAsyncQueue")
public class MessageReceiverAsync implements MessageListener {
...
}
The destination is specified on a Servlet as:
JMSDestinationDefinitions({@JMSDestinationDefinition(name =
"java:global/jms/mySyncQueue",
resourceAdapter = "jmsra",
interfaceName = "javax.jms.Queue",
destinationName="syncQueue",
description="My Sync Queue"),
@JMSDestinationDefinition(name = "java:global/jms/myAsyncQueue",
resourceAdapter = "jmsra",
interfaceName = "javax.jms.Queue",
destinationName="asyncQueue",
description="My Async Queue")
})
@WebServlet(urlPatterns = {"/TestServletSendAsync"})
public class TestServletSendAsync extends HttpServlet {
...
}
Complete sample is at:
https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive
Deploying this sample gives the error:
Caused by: java.lang.RuntimeException:
javax.resource.spi.InvalidPropertyException: Destination is mandatory
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:215)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:186)
at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
[wildfly-ee-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
... 6 more
Caused by: javax.resource.spi.InvalidPropertyException: Destination is mandatory
at org.hornetq.ra.inflow.HornetQActivationSpec.validate(HornetQActivationSpec.java:727)
[hornetq-ra-2.4.0.Beta2.jar:]
at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:184)
[ironjacamar-core-impl-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:213)
... 8 more
This deployed and worked fine on GlassFish.
Any thoughts on what is missing ?
Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
10 years, 10 months
build with all tests except clustering?
by Frank Langelage
When running
build.sh clean install -DallTests
clustering tests fail at different tests / with different problems.
Can I run build with allTests but without the clustering testsuite?
10 years, 10 months
JPA 2.1 in WildFly Beta2 Snapshot
by Arun Gupta
Hello there...
I've a simple sample defined at:
https://github.com/arun-gupta/javaee7-samples/tree/master/jpa/listeners
This sample shows how different JPA entity listeners can be specified.
Deploying this sample in WildFly trunk gives the following error:
05:28:54,709 ERROR [org.jboss.msc.service.fail] (ServerService Thread
Pool -- 59) MSC000001: Failed to start service
jboss.persistenceunit."jpa-listeners.war#myPU":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."jpa-listeners.war#myPU":
java.lang.IllegalStateException: JBAS016071: Singleton not set for
org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@639b9ef8.
This means that you are trying to access a weld deployment with a
Thread Context ClassLoader that is not associated with the deployment.
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:169)
[wildfly-jpa-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117)
[wildfly-jpa-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_45]
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463)
[wildfly-security-manager-1.0.0.Beta3.jar:1.0.0.Beta3]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:178)
[wildfly-jpa-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
Any suggestions on what is wrong ?
Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
10 years, 10 months
Java EE 7 and WildFly
by Arun Gupta
Hello there ...
Some of you may know me but let me introduce myself. I've joined Red
Hat as Director of Developer Advocacy last week and will be focusing
on JBoss Middleware. Read more about introduction at:
http://blog.arungupta.me/2013/10/farewell-from-oracle/
I would love to engage with you in making the developer experience
seamless for WildFly. I'm using a gmail id for now until my corporate
email is properly configured but feel free to reach out to me if you
have any questions.
Now to the technical part. I've created a bunch of Java EE 7 samples at:
http://github.com/arun-gupta/javaee7-samples
Originally, these samples were built/run on GlassFish and now I'm
trying to run them on WildFly. Some questions while I'm running these
samples ..
- Java EE 7 runtime require a database to be provisioned at runtime.
GlassFish download comes bundled with JavaDB. What is the typical
choice for WildFly developers ?
- How is the default JDBC resource configured for this database ? What
is the actual JDBC resource name ?
- Are any RI from GlassFish are used in WildFly ? I'd like to
understand where each of the JSR implementations in WildFly are coming
from ?
- How is a database associated with Batch RI configured for WildFly ?
- I've seen some samples are not working as expected. These might be
bugs either in sample or in WildFly. Should I file them in the issue
tracker for further discussion or discuss first and then file ?
Thanks
Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
10 years, 10 months
Build moving to Maven 3.1
by Tomaž Cerar
Hey guys,
In coming days we are moving build to require minimum of maven 3.1.0.
I would recommend anyone that hasn't done so yet, to upgrade to 3.1.x
(3.1.1 current latest).
New maven brings us some speed improvement (some people claim up to 15%)
and some improvements we need for some testsuite changes I am working on.
For now just heads up, I will send another mail when change is in master.
--
tomaz
10 years, 10 months
Problem with remoting
by Nikolaos Ballas
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi guys,
a small question. The remoting connection from external clients have
changed between jbossas 7.1.1 and wildfly?Also in jbossas7.1.1 the
necessary jars to be included in the project were hosted in maven.
Reading under the /bin/client the txt files it's stated explicity that
no maven dep will be available in the central repository. So how we
handle the dep?Manually adding in to our local repo?Not so go
solution.Last but not lease in the /stanalone/configuration
*.properties files they refer still to jboss as 7 :) the name is
change to wildfly right :D
regards
\n\m
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlJrhv4ACgkQM4d5SPwi8EsvHAD/dsSUabR7FVmkjgVK5pd7f2i2
l9miyjTkE+6Ddrwcp/EA/jhCQ/LWdqyfwDFHMaFw2ncuLAFFljwbLThisc+ebACk
=j5av
-----END PGP SIGNATURE-----
10 years, 10 months
