Default HTTPS port
by Rich Midwinter
All
I notice the default HTTPS socket binding in the AS7 console and the admin
guide is 8447. I'd have expected it to be 8443.
Presumably this isn't an oversight, but I was just wondering what the
rationale is?
Thanks
Rich
15 years, 1 month
Question about Async logging
by Andrig Miller
I have looked over the JBoss logging XSD, and believe I have configured asynchronous logging correctly, but I'm getting a parse error.
Here is my configuration:
<subsystem xmlns="urn:jboss:domain:logging:1.0">
<periodic-rotating-file-handler name="FILE" autoflush="true">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd"/>
</periodic-rotating-file-handler>
<async-handler name="ASYNC">
<level name="INFO"/>
<queue-length>1024</queue-length>
<overflow-action>block</overflow-action>
<subhandlers>FILE</subhandlers>
</async-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="ASYNC"/>
</handlers>
</root-logger>
</subsystem>
Here is the exception:
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[51,13]
Message: Missing required attribute(s): FILE_NAME
at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:115)
at org.jboss.as.logging.LoggingSubsystemParser.parseAsyncHandlerElement(LoggingSubsystemParser.java:259)
at org.jboss.as.logging.LoggingSubsystemParser.readElement(LoggingSubsystemParser.java:149)
at org.jboss.as.logging.LoggingSubsystemParser.readElement(LoggingSubsystemParser.java:84)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
at org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:309)
at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:163)
at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:87)
at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:75)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:105)
... 5 more
I far as I can see there is no FILE_NAME required attribute, and the line and column number it gives is the start of the async-handler tag in the configuration above.
Any ideas?
Thanks.
Andy
15 years, 1 month
Pointer to jboss logging schema?
by Andrig Miller
I'm trying to find the schema for jboss logging for AS 7, but cannot find it anywhere.
Can someone point me in the right direction? I was wanted to look it over to see all the options, and try out some things, like the async handler.
Andy
15 years, 1 month
Re: [jboss-as7-dev] [Resteasy-developers] NPE at org.jboss.resteasy.logging.Logger.classInClasspath(Logger.java:62)
by Bill Burke
Not sure how that NPE is possible. Thread.currentThread() or
Thread.currentThread().getContextClassLoader() has to be NULL. If AS7
is overriding ContextClassLoader to be NULL then thats pretty worrisome.
On 6/22/11 2:28 PM, Juergen Zimmermann wrote:
> JBoss 7 (Jenkins build 1253) meanwhile works regarding the
> NoMessageBodyWriterFoundFailure.
>
> However, when I want to also use Seam REST, I'm getting a NPE at
> org.jboss.resteasy.logging.Logger.classInClasspath(Logger.java:62). Please
> see the stacktrace:
>
> 20:20:06,541 INFO [org.jboss.weld] (MSC service thread 1-1) Processing CDI
> deployment: swe2.ear
> 20:20:06,566 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1)
> MSC00001: Failed to start service
> jboss.deployment.unit."swe2.ear".POST_MODULE:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."swe2.ear".POST_MODULE: Failed to process phase
> POST_MODULE of deployment "swe2.ear"
> at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUn
> itPhaseService.java:121)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerI
> mpl.java:1738)
> at
> org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControl
> lerImpl.java:2325)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
> va:886) [:1.6.0_26]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
> 08) [:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
> Caused by: java.lang.RuntimeException: Error instantiating class
> org.jboss.resteasy.cdi.ResteasyCdiExtension
> at
> org.jboss.weld.util.ServiceLoader.prepareInstance(ServiceLoader.java:282)
> at
> org.jboss.weld.util.ServiceLoader.loadService(ServiceLoader.java:238)
> at
> org.jboss.weld.util.ServiceLoader.loadServiceFile(ServiceLoader.java:194)
> at org.jboss.weld.util.ServiceLoader.reload(ServiceLoader.java:157)
> at
> org.jboss.weld.util.ServiceLoader.iterator(ServiceLoader.java:346)
> at
> org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadA
> ttachments(WeldPortableExtensionProcessor.java:84)
> at
> org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.deplo
> y(WeldPortableExtensionProcessor.java:78)
> at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUn
> itPhaseService.java:115)
> ... 5 more
> Caused by: java.lang.ExceptionInInitializerError
> at
> org.jboss.resteasy.cdi.ResteasyCdiExtension.<init>(ResteasyCdiExtension.java
> :44)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) [:1.6.0_26]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
> sorImpl.java:39) [:1.6.0_26]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
> torAccessorImpl.java:27) [:1.6.0_26]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> [:1.6.0_26]
> at
> org.jboss.weld.util.ServiceLoader.prepareInstance(ServiceLoader.java:273)
> ... 12 more
> Caused by: java.lang.NullPointerException
> at
> org.jboss.resteasy.logging.Logger.classInClasspath(Logger.java:62)
> at org.jboss.resteasy.logging.Logger.<clinit>(Logger.java:75)
> ... 18 more
>
>
>
>
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> _______________________________________________
> Resteasy-developers mailing list
> Resteasy-developers(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
15 years, 1 month
Deployment terms in CLI
by Heiko Braun
The deployment terms are really messed up in the CLI.
I.e. the command is named "deploy <foo.bar>", but at the same time an operation exists on the deployment to "deploy" (aka enable) it:
[domain@localhost:9999 /] deploy ~/Desktop/test-application.war --all-server-groups
[domain@localhost:9999 /] /server-group=main-server-group/deployment=test-application.war:deploy
I would suggest we align these terms with WIKI page:
http://community.jboss.org/wiki/AS7DeploymentTerms
This would mean to rename the command to "upload" and the operation to "enable".
Whatever we chose, we need to remove the ambiguity.
Ike
15 years, 1 month
Missing Documentation
by Heiko Braun
I finished the "Admin Guide" draft.
It still needs to be polished here and there, but what I am really missing is:
- Getting Started Guide
- Developer Guide
- High Availability Guide
Pete, Shelly, Paul, when can we expect the first content to be available here?
https://docs.jboss.org/author/display/AS7/Home
Ike
15 years, 1 month
Re: [jboss-as7-dev] [Resteasy-developers] NoMessageBodyWriterFoundFailure when migrating to JBoss 7
by Bill Burke
I haven't touched AS7 yet, somebody else did the integration. You're
gonna have to ask on the AS7 list
On 6/21/11 2:12 PM, Juergen Zimmermann wrote:
> I'm trying to migrate a part of an EAR to JBoss 7 (Jenkins build 1241). The
> EAR contains an EJB module with session beans, and some session beans are
> impl classes for interfaces with JAX-RS annotations (@Path, @GET, ...). The
> web module just consists of web.xml declaring some functionality for
> RESTEasy. I inserted into the META-INF/Manifest.MF file the following lines,
> but get a stacktrace (see below) when a GET request is submitted.
>
> Addition to the web module's Manifest.MF:
> Dependencies: org.jboss.resteasy.resteasy-jaxrs,
> org.jboss.resteasy.resteasy-jaxb-provider,
> org.jboss.resteasy.resteasy-jackson-provider,
> org.jboss.resteasy.async-http-servlet-30,
> org.jboss.resteasy.resteasy-cdi,
> org.jboss.resteasy.resteasy-multipart-provider
>
> Stacktrace for GET request:
> [org.jboss.resteasy.core.SynchronousDispatcher]
> (http-127.0.0.1-127.0.0.1-8080-2) Failed executing GET
> /kundenverwaltung/kunden/1:
> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find
> MessageBodyWriter for response object of type:
> de.swe1.kundenverwaltung.domain.Privatkunde of media type: application/xml
> at
> org.jboss.resteasy.core.ServerResponse.writeTo(ServerResponse.java:202)
> [file:C:%5CSoftware%5Cjboss-7.0.0.CR1-b1241%5Cmodules%5Corg%5Cjboss%5Crestea
> sy%5Cresteasy-jaxrs%5Cmain%5Cresteasy-jaxrs-2.1.0.GA.jar:]
> at
> org.jboss.resteasy.core.SynchronousDispatcher.writeJaxrsResponse(Synchronous
> Dispatcher.java:563)
> [file:C:%5CSoftware%5Cjboss-7.0.0.CR1-b1241%5Cmodules%5Corg%5Cjboss%5Crestea
> sy%5Cresteasy-jaxrs%5Cmain%5Cresteasy-jaxrs-2.1.0.GA.jar:]
> ...
>
> The message body writers for JAXB/XML are included in the
> resteasy-jaxb-provider module. Any hint is appreciated.
>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Resteasy-developers mailing list
> Resteasy-developers(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
15 years, 1 month
HornetQ docs
by Heiko Braun
Where can I find the mots recent hornetq docs?
Looking for 2.2.6.
Ike
15 years, 1 month
Logging codes for AS7
by Heiko Braun
Where can I found the list of logging codes?
Are they hidden in each project documentation, or is there a single resource
that I can reference from the Admin Guide?
Ike
15 years, 1 month
