dmr: server instances?
by Heiko Braun
is the 'server' node the element that contains server instances?
{
"address" => [("host" => "local")],
"operation" => "read-resource"
}
outcome' : 'success',
'result' :
{
[...]
'server-config' :
{
'server-one' :
{
},
'server-two' :
{
},
'server-three' :
{
}
},
[...]
'server' :
{
}
},
'compensating-operation' :
{
}
15 years
EAR Deployed, but doesn't work
by Andrig Miller
Okay, everyone. Now that I have my EAR deployed successfully, I tried to execute the application from my browser. It doesn't do anything and there is no error in the log.
I'm hitting the application across the network with http://192.168.1.22:8080/Order, were the IP is the address of my server where I'm running the app, and the /Order is the root context defined for the war in application.xml. It should return an HTML form.
I changed in standalone.xml the IP address from 127.0.0.1 to 192.168.1.22, thinking that would do the same thing as -b 192.168.1.22 did on the old stuff. Curiously, I also don't really see anything that looks like JBoss Web in the file. I was expecting to see the stuff that used to be in server.xml, and META-INF/*beans.xml file for configuring it, but I don't really see anything.
I'm not really sure what to look at next, so any pointers in the right direction is greatly appreciated.
Thanks.
Andy
15 years
Adding more trace level logging
by Scott Stark
With the problems with the debugger crashing the server vm, I'm finding
I need to add a lot of trace level statements to both the AS and
components to try to figure out why things don't work. What is the best
way to get these additions back into the AS codebase at least?
15 years
Re: [jboss-as7-dev] [JBoss JIRA] Created: (JBAS-9112) Create an "operation-header" section in operation requests
by Brian Stansberry
Heiko, Ike, Alexey (or others with thoughts):
In the operation request format there are a couple of extraneous bits
that have crept in that basically tell the server information about how
to execute the operation rather than the body of the operation itself.
Wanted to get your opinion on an idea that came up today (see JIRA
below) to segregate these from the rest of the operation.
Basically, instead of the current
{
"operation"=>"add",
"address"=>{"subsystem"=>"foo"},
"paramX"=>"A",
"paramY"=>true,
"rollback-on-runtime-failure"=>"false",
"rollout-plan"=>{.....}
}
It would be:
{
"operation"=>"add",
"address"=>{"subsystem"=>"foo"},
"paramX"=>"A",
"paramY"=>true,
"operation-headers"=>{
"rollback-on-runtime-failure"=>"false",
"rollout-plan"=>{.....}
}
}
Alexey, I first thought about the CLI just as I was about to send this.
This idea would make setting this kind of thing via the CLI harder for
users, which is a significant downside.
On 3/22/11 10:38 AM, Brian Stansberry (JIRA) wrote:
> Create an "operation-header" section in operation requests
> ----------------------------------------------------------
>
> Key: JBAS-9112
> URL: https://issues.jboss.org/browse/JBAS-9112
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public (Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.0.0.Beta2
>
>
> For the oddball stuff that goes along with some ops:
>
> "operation-headers"=>{"rollout-plan"=>{..},"rollback-on-runtime-failure"=>false, "ignore-restart-required"=>true,...}
>
> "operation" and "address" would not move -- too disruptive
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
15 years
Module classloader can't find JavaSE classes in AS7 testsuite?
by Jaikiran Pai
I'm trying to write a test in testsuite/smoke-tests. The test is pretty
simple and has a javax.naming.Context import in it. I keep running into
this CNFE every time I try running it:
17:12:22,623 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner]
(pool-31-thread-1) Error in test method: testLocalBindingsOnSLSB:
java.lang.NoClassDefFoundError: javax/naming/Context
at java.lang.Class.getDeclaredFields0(Native Method) [:1.6.0_21]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
[:1.6.0_21]
at java.lang.Class.getDeclaredFields(Class.java:1743) [:1.6.0_21]
at
org.jboss.as.arquillian.service.ArquillianService$TestClassLoaderImpl.isOSGiSubsystemRequired(ArquillianService.java:286)
at
org.jboss.as.arquillian.service.ArquillianService$TestClassLoaderImpl.loadTestClass(ArquillianService.java:268)
at
org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:140)
[arquillian-protocol-jmx-1.0.0.Alpha4.SP9.jar:1.0.0.Alpha4.SP9]
at
org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodEmbedded(JMXTestRunner.java:115)
[arquillian-protocol-jmx-1.0.0.Alpha4.SP9.jar:1.0.0.Alpha4.SP9]
at
org.jboss.as.arquillian.service.ArquillianService$1.runTestMethodEmbedded(ArquillianService.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[:1.6.0_21]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[:1.6.0_21]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[:1.6.0_21]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21]
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
[:1.6.0_21]
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
[:1.6.0_21]
at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
[:1.6.0_21]
at
com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
[:1.6.0_21]
at
com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
[:1.6.0_21]
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
[:1.6.0_21]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
[:1.6.0_21]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
[:1.6.0_21]
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
[:1.6.0_21]
at $Proxy39.runTestMethodEmbedded(Unknown Source) at
org.jboss.arquillian.protocol.jmx.JMXMethodExecutor$1.call(JMXMethodExecutor.java:102)
[arquillian-protocol-jmx-1.0.0.Alpha4.SP9.jar:1.0.0.Alpha4.SP9]
at
org.jboss.arquillian.protocol.jmx.JMXMethodExecutor$1.call(JMXMethodExecutor.java:98)
[arquillian-protocol-jmx-1.0.0.Alpha4.SP9.jar:1.0.0.Alpha4.SP9]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[:1.6.0_21]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_21]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: java.lang.ClassNotFoundException: javax.naming.Context from
[Module "deployment.dd-based-slsb.jar:main" from Service Module Loader]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184) [jboss-modules-1.0.0.Beta16.jar:1.0.0.Beta16]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357)
[jboss-modules-1.0.0.Beta16.jar:1.0.0.Beta16]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329)
[jboss-modules-1.0.0.Beta16.jar:1.0.0.Beta16]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306)
[jboss-modules-1.0.0.Beta16.jar:1.0.0.Beta16]
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100)
[jboss-modules-1.0.0.Beta16.jar:1.0.0.Beta16]
... 29 more
Apparently, the module classloader can't find the classes from the Java
SE runtime jar? By the way, is there a document around how AS7 testsuite
is integrated with Arquillian and jboss-modules and what are the step
required to get a test running (it's not straightforward, as I'm seeing
now)? I keep running into these CNFE/NCDFE issues everytime I write a
simple test.
-Jaikiran
15 years
Question about JBoss Logging
by Andrig Miller
I ask this on the forum, but haven't gotten a response, so I figured I would try here.
I have been porting an application up to AS 7. In doing that, I changed the logging I was doing in the application (mostly trace level), and I changed it to use JBoss Logging directly. When I deploy the application, it fails with a class not found exception, where it cannot find the Level class. So, my questions are.
Is JBoss Logging exposed as a public API through the module system? If not, was that intentional? If not, what is the recommended approach?
Andy
15 years
server-config, socket-binding-group reference?
by Heiko Braun
Why is the socket-binding-group not present in a server-config resource,
although it's in the schema?
[localhost:9999 /] /host=local/server-config=server-one:read-resource
{
"outcome" => "success",
"result" => {
"path" => undefined,
"system-property" => undefined,
"interface" => undefined,
"jvm" => {"default" => undefined},
"name" => "server-one",
"group" => "main-server-group",
"auto-start" => true
},
"compensating-operation" => undefined
}
Another thing I've noticed is that JVM reference:
It's a 'nameJvmType' schema type but appears as a Property in the DMR model.
IMO that's wrong.
Ike
15 years
I got closer to figuring out why epcpropagation didn't deploy in the as7 testsuite/integration...
by Scott Marlow
I want to port over more of the EJB3 JPA tests but want to get
epcpropagation to deploy correctly first.
The epcpropagation test is at
https://github.com/scottmarlow/jboss-as/tree/master/testsuite/integration...
Currently, when I try to run "mvn install" from testsuite/integration,
EPCPropagationTestCase starts to run but doesn't get through deployment
for some reason. I want to share some of what I am seeing, in case it
helps others when they hit similar problems.
1. I ran jconsole and used the MSC mbean to dump current service status
after hanging during the EPCPropagationTestCase. Output is here
http://pastie.org/1702369.
2. In the services dump, the following service is listed as a
dependency but never got started or deployed.
jboss.deployment.unit."EPCPropagationTestCaseArchive.jar".component.IntermediateStatefulBean.VIEW."org.jboss.as.testsuite.integration.jpa.epcpropagation.StatefulRemote
3. The following service depends on (2)
"jboss.naming.context.java.comp.EPCPropagationTestCaseArchive.EPCPropagationTestCaseArchive.InitEPCStatefulBean."env/org.jboss.as.testsuite.integration.jpa.epcpropagation.InitEPCStatefulBean/cmtBean"".
4. Since (2) is not being deployed, (3) will never be satisfied.
5. I enabled AS7 trace logging and looked for
"IntermediateStatefulBean" in server.log. Interesting occurrences are at:
http://pastie.org/1702410
I think there are two possible issues. Either we should of deployed
service (2) or service (3) shouldn't depend on (2). Either way, it
sounds like a deployment bug to me. I suppose it could also be a bug in
my testcase as well (operator error).
Scott
15 years
Full examples of json for talking to the JSON api?
by Heiko W.Rupp
Hi,
are there some full example like updating the port-offset in a socket-binding-group
available - including the JSON that is expected and the URL to throw it at?
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
15 years
