jboss-admin : feature request
by Vimal Kansal
Hi,
It appears right now we don't have a cls/clear command - this will be a
good addition. Other capability will be to be able to pipe the output of
a command/operation to a file.
Thx
Vimal
12 years, 9 months
guava r06 memory leak
by Sebastian Otaegui
Hello all,
I tried to find in the code where you are using guava and could not find it
so I do not know if it is added as a module for a specific reason, it is
just a leftover or it is me that I just do not know how to grep code :)
I was reading the jenkins mailing list and apparently there is a memory leak
in guava r06 that was fixed in r09 (although the latest version is r10)
I thought you might want to take a look at that.
http://code.google.com/p/guava-libraries/issues/detail?id=573&can=1&q=mil...
Regards
--
Those who do not understand Unix are condemned to reinvent it, poorly.
Any sufficiently recent Microsoft OS contains an ad hoc,
informally-specified, bug-ridden, slow implementation of half of Unix.
12 years, 9 months
Quoted paths in Set-Cookie header
by Jim Crossley
I'm having a real dick of a time verifying that session replication
works in AS7. I think my problems may stem from cookies not being
passed correctly, because the Set-Cookie header includes Path="/"
instead of Path=/.
I'm testing with curl. I'm testing an app that works fine on AS6, which
returns a header like this:
Set-Cookie: JSESSIONID=0669E4BF117ED01784254238ED00E492; Path=/
When I deploy the app on AS7, I get this:
Set-Cookie: JSESSIONID=16S0e9hUZkQDpJCqxeBrBTLQ; Version=1; Path="/"
Which seems to prevent curl from passing the cookie back in subsequent
requests.
Interestingly, I can manually edit curl's cookie-store file to remove
the quotes, and subsequent requests work correctly.
Is this some sort of strict tomcat request handling behavior that I can
turn off? Anyone else seen this?
Thanks,
Jim
12 years, 9 months
Can't override the path "jboss.server.log.dir" in config file
by Vimal Kansal
Hi,
In the admin guide, it is mentioned under "Paths" section :
"
JBoss AS 7 automatically provides a number of standard paths without any
need for the user to configure them in a configuration file:
jboss.home - the root directory of the JBoss AS distribution
user.home - user's home directory
user.dir - user's current working directory
java.home - java installation directory
jboss.server.base.dir - root directory for an individual server
instance
jboss.server.data.dir - directory the server will use for
persistent data file storage
jboss.server.log.dir - directory the server will use for log file
storage
jboss.server.tmp.dir - directory the server will use for temporary
file storage
jboss.domain.servers.dir - directory under which a host controller
will create the working area for individual server instances (managed
domain mode only)
*Users can add their own paths or override all except the first 5 of the
above by adding a <path/> element to their configuration file.*
"
which means I should be able to override "jboss.server.log.dir" and when
I do that in "standalone_preview.xml" :
<paths>
<path name="jboss.server.log.dir" value="C:\\vkk\\as7log"/>
</paths>
I get the following error :
"
12:40:50,355 ERROR [stderr] at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:89)
12:40:50,356 ERROR [stderr] at java.lang.Thread.run(Thread.java:662)
12:40:50,357 ERROR [stderr] Caused by:
org.jboss.as.controller.persistence.ConfigurationPersistenceException:
Failed to parse configuration
12:40:50,357 ERROR [stderr] at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:115)
12:40:50,358 ERROR [stderr] at
org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:104)
12:40:50,359 ERROR [stderr] at
org.jboss.as.server.ServerService.boot(ServerService.java:193)
12:40:50,360 ERROR [stderr] at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83)
12:40:50,361 ERROR [stderr] ... 1 more
12:40:50,362 ERROR [stderr] Caused by:
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[55,3]
12:40:50,363 ERROR [stderr] *Message: jboss.server.log.dir is reserved*
12:40:50,364 ERROR [stderr] at
org.jboss.as.controller.parsing.CommonXml.parsePath(CommonXml.java:999)
12:40:50,365 ERROR [stderr] at
org.jboss.as.controller.parsing.CommonXml.parsePaths(CommonXml.java:370)
12:40:50,365 ERROR [stderr] at
org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:154)
12:40:50,366 ERROR [stderr] at
org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:91)
12:40:50,367 ERROR [stderr] at
org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:79)
12:40:50,367 ERROR [stderr] at
org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
12:40:50,368 ERROR [stderr] at
org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
12:40:50,369 ERROR [stderr] at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:107)
12:40:50,370 ERROR [stderr] ... 4 more
I was wondering, if the doc is wrong or I am doing something wrong.
Thx
Vimal
12 years, 9 months
Are jbowws-web.xml/jboss-app.xml/jboss.xml backward compatible?
by Vimal Kansal
Hi,
I tried deploying the richfaces demo war file (richfaces version 3.3.0
and JSF 1.2) and I get the following exception ?
"
21,610 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7)
MSC00001: Failed to start service
jboss.deployment.unit."richfaces-demo-3.3.3.Final-jee5.war".PARSE:
org.jboss.msc.service.Star
tion in service
jboss.deployment.unit."richfaces-demo-3.3.3.Final-jee5.war".PARSE:
Failed to process phase PARSE of deployment
"richfaces-demo-3.3.3.Final-jee5.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:*Failed
to parse
"/C:/Users/Vimal/content/richfaces-demo-3.3.3.Final-jee5.war/WEB-INF/jboss-web.xml"*
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[6,2]
e: *Unexpected element 'class-loading' encountered*
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 6 more
21,615 INFO [org.jboss.as.server.controller] (pool-2-thread-28)
Deployment of "richfaces-demo-3.3.3.Final-jee5.war" was rolled back with
failure message {"Failed services" => {"jboss.deployment
\"richfaces-demo-3.3.3.Final-jee5.war\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"richfaces-demo-3.3.3.Final-jee5.war\".PARSE:
Failed to process phase PA
deployment \"richfaces-demo-3.3.3.Final-jee5.war\""}}
"
Thx
Vimal
12 years, 9 months
DB2 datasources in AS7
by Joel Tosi
Morning list,
Has anyone encountered an issue with a DB2 datasource in CR1 or AS7
final? There appears to be a dependency problem and an issue with the
way datasources and drivers are defined in those versions (CR1 and
final) versus how it was accomplished in beta 3.
The current documentations says to deploy the jar as you would any
archive but then it appears as though the module architecture does not
recognize the driver as being deployed when the datasource association
to the driver is done. Does it expect the driver to be a module?
Any help around this would be greatly appreciated.
Thanks,
Tosi
12 years, 9 months
