Web Console 1.0.0.Beta3
by Heiko Braun
FYI, I've released Beta3 today. It's the version that will be shipped with JBoss 7.0.0.Beta2.
The console can be found at:
http://localhost:9990/console
The first thing you get to see is a Release Notes page, where I tried to explain the current
scope and what to expect.
Stay tuned,
Ike
13 years, 9 months
How to debug the AS7 process launched from as7/testsuite/integration?
by Scott Marlow
I tried to debug the AS launched via testsuite/integration "mvn install"
by issuing the following command:
mvn instll -Dmaven.surefire.debug="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8787"
The testsuite process pauses and waits for me to attach my debugger,
however it seems like we might be launching the AS in a separate
process. None of my breakpoints in the target
org.jboss.as.testsuite.integration.jpa.epcpropagation.EPCPropagationTestCase
test are triggered. My breakpoints in other AS7 code that I know we
reach, are also not triggered. I must be attaching to the wrong process.
Has anyone figured out a solution? I tried changing standalone.xml as
suggested here
http://community.jboss.org/wiki/WritingaAS7TestCaseintestsuitemodule but
that didn't help.
Thanks,
Scott
13 years, 9 months
How would you typically consume an MSC service from a JEE deployment?
by David Bosschaert
Hi all,
Just trying to figure out how an end user would typically consume an MSC
service from a JEE deployment such as a Servlet or EJB...
How do we expect our customer to consume MSC services? (In my case the
MSC service is registered through the OSGi layer...)
I guess the ideal way would be through some sort of injection...
Thanks,
David
13 years, 9 months
How to set up a domain with multiple hosts?
by Heiko W.Rupp
Hi,
how do I set up a domain with multiple hosts and server groups having managed servers
on multiple hosts?
One way could be to edit the configuration to support this and then distribute the server zip
around to all machines.
Or is there a way ,where I edit the configuration on the domain controller, distribute a
(stripped down) version of the zip and basically start it on a non-dc-host via
domain.sh --real-controller=otherhost:9990 ?
Thanks
Heiko
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
13 years, 9 months
Providing server name on command line?
by Heiko W.Rupp
Hi,
Currently the only place on the command line that makes it possible to identify a
managed AS is the logfile path, so I basically have to grep for it there.
Is there a (better) way to obtain the name of a managed as - perhaps by querying
it directly?
Thanks
Heiko
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
13 years, 9 months
Help with git push ssh:...
by Scott Stark
So I'm trying to use the "Pushing changes to a public repository"
proceedure from the git book, but run into the following error. Note
that I did not first export the repository as a bare one as described
earlier as I missed that. I just scpd the entire repo/workspace over to
this box, did the JBAS-9151 work, and wanted to push that out to the copy.
[191](ironmaiden:jboss-as) > git push
root@ec2-174-129-102-73.compute-1.amazonaws.com:jboss-as master
Counting objects: 692, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (191/191), done.
Writing objects: 100% (537/537), 91.39 KiB, done.
Total 537 (delta 205), reused 476 (delta 174)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare
repository
remote: error: is denied, because it will make the index and work tree
inconsistent
remote: error: with what you pushed, and will require 'git reset --hard'
to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration
variable t
remote: error: 'ignore' or 'warn' in the remote repository to allow
pushing int
remote: error: its current branch; however, this is not recommended
unless you
remote: error: arranged to update its work tree to match what you pushed
in som
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default
behaviour, se
remote: error: 'receive.denyCurrentBranch' configuration variable to
'refuse'.
To root@ec2-174-129-102-73.compute-1.amazonaws.com:jboss-as
! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to
'root@ec2-174-129-102-73.compute-1.amazonaws.com:jboss-as'
The status of the remote repo is:
[root@ip-10-78-94-50 jboss-as]# git status
# On branch master
# Your branch is ahead of 'origin/master' by 1715 commits.
#
nothing to commit (working directory clean)
[root@ip-10-78-94-50 jboss-as]#
I'll go through and re-export the local repo as a bare one and see if
that works, but would setting receive.denyCurrentBranch=ignore or warn
allow me to just update the remote repo for local use only? I'll never
push or pull anything from it.
13 years, 9 months
Missing cause on jboss.network.default: failed to resolve interface default error
by Scott Stark
When starting up with a loopback address that is other than 127.0.0.1
(I'll get to that later), this exception happens:
14:31:16,275 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to
start service jboss.network.default:
org.jboss.msc.service.StartException in service jboss.network.default:
failed to resolve interface default
at
org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:101)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_20]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_20]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Now I have seen this msg not be displayed at all, so under some
circumstances it is being lost.
Now, for the loopback address issue. The libra (our cloud project)
server instances generate unique loopback addresses, but do not want to
create a unique loopback device or aliases on the loopback device for
some reason. How do I specify that the default address should use a
specific address, but still match the loopback interface? Looking at the
interface-criteriaGroup schema, you cannot do something like?
<interfaces>
<interface name="default">
<inet-address value="127.0.250.5"/>
<loopback />
</interface>
13 years, 9 months
