FINE logging from sun
by Brian Stansberry
Without objection I'm going to change jboss-log4j.xml to limit to INFO
logging from the following categories:
sun
com.sun
javax.xml.bind
All three are extremely verbose at FINE level. They treat FINE the way
we would treat log4j TRACE. But our logging impl maps FINE to DEBUG, so
when we have DEBUG logging enabled, these categories flood the logs.
Been looking at a lot of server.log files chasing testsuite issues and
this noise is driving me nuts. :)
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
16 years, 11 months
Issue in JMS queue consumption using receiveNoWait method
by Ansari
Hi all,
We are looking for a standalone program to read the messages from a JMS
queue configured.
This message reading should be synchronous. It should read and process all
the available messages in the queue. All processed valid messages should be
removed from the queue and rest of the messages (invalid/improper should
remain in the queue itself).
We wrote a client program to do the same (attach our piece of code). We used
receiveNoWait function available over message consumer class. Even though
messages are there in the queue (which we confirmed by writing a sample
program by creating the message browser), recieveNoWait method returns null.
(We tried by running the sample program even after some 30 minutes and one
hour)
Actually there are two parts in our query
1) receiveNoWait function available over message consumer class is not
returning the messages available in queue, it’s always returning null. (Even
though messages present in the queue, which we confirmed by writing a
message browser). We are concerned about this issue very much
2) After processing each and every message, only valid messages should get
removed from the queue. In your response you have mentioned that message can
be put into some other queue if it’s invalid. But our requirement is that
the invalid messages should remain over there in the queue itself. Only
valid messages should be removed from the queue. This can be achieved by
creating a transacted session of message consumer for reading each and every
message. If it’s a valid message, the session will be committed and the
message will be removed from the queue, else it remains in the queue itself.
We tested this with other AppServers and it works fine.
Uploaded test program for reference
Our main concern is with the 1st part of our query. Expecting your guidance
for the same
Can you please help on this?
http://www.nabble.com/file/p23175484/TestMessageConsumer.java
TestMessageConsumer.java
--
View this message in context: http://www.nabble.com/Issue-in-JMS-queue-consumption-using-receiveNoWait-...
Sent from the JBoss - Dev mailing list archive at Nabble.com.
16 years, 11 months
Problem detecting modified deployments
by Brian Stansberry
This would be a "Design of POJO Server" thread but forums are down so am
using this broad distribution list. Those not interested in the
technical details of detecting modified deployments can ignore. :)
I'm looking for some input from the VFS and ProfileService folks.
I'm having an issue where the ClusteredDeploymentRepository is failing
to detect modified deployments. Issue leads to a failure in a newly
added test[1]. What the test does is make some changes in the contents
of the farm/ dir, gives time for the HDScanner to run, and then verifies
that the updated content is deployed in all nodes in the cluster.
Everything works fine for content additions and removals, but modifying
an existing file doesn't work.
Problem is in the ClusteredDeploymentRepository.createModificationInfo()
method, which basically duplicates the logic in
HotDeploymentRepository.getModifiedDeployments(). Loops through the
VirtualFiles representing the root of known deployments, checking if
they are removed, and if not, asking the StructureModificationChecker if
they are modified:
// Check for modification
else if (hasDeploymentContentFlags(pathName,
DeploymentContentFlags.MODIFIED)
|| getChecker().hasStructureBeenModified(root))
{
long rootLastModified = root.getLastModified();
...
// Create the modification info
ModificationInfo info = new ModificationInfo(ctx, rootLastModified,
ModifyStatus.MODIFIED);
modified.add(info);
}
Problem occurs in
AbstractStructureModificationChecker.hasStructureBeenModified(VirtualFile):
if (root == null)
throw new IllegalArgumentException("Null root");
// skip vfs deployment context lookup if archive or file
if (root.isArchive() || root.isLeaf())
return root.hasBeenModified(); // !!! RETURNS FALSE
The problem is root.hasBeenModified() returns false. I don't think
VirtualFile.hasBeenModified() is a safe way to check for modification,
since following a modification, it will return true once and only once.
So whatever code asks first gets "true", later code will get "false".
AFAICT, this is the reason AbstractStructureModificationChecker has a
StructureCache injected -- the cache stores modification timestamps to
avoid this problem.
Shouldn't the timestamps for archives/leaf deployments be stored in the
StructureCache as well? And then check for modification using the
StructureCache's data, same as we do for, e.g. a WEB-INF/web.xml?
FYI, the reason that in this case root.hasBeenModified() returns false
is earlier in the HDScanner run ClusteredDeploymentRepository has
scanned the repository content looking for changes so it can replicate
modified files around the cluster. That scan results in a call to
VirtualFile.getChildren() which ends up calling
AbstractVirtualFileHandler()hasBeenModified().
A final twist:
While experimenting with this manually, I found that the first time I
modify the file, the above problem occurs. But then if I modify the file
again, it gets picked up as modified and redeployed. And thereafter,
every time I modify it, it gets redeployed. Only fails the first time.
I've been poking around a long time and have no explanation for why this is.
[1]
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-test...
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
16 years, 11 months
Should JBAS5.x honor context path in context.xml?
by Anil Saldhana
https://jira.jboss.org/jira/browse/JBAS-6811 has a web application
attached (lambda.war). It has a WEB-INF/context.xml with the following
setting:
=======
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/probe" privileged="true">
</Context>
================
The expectation is that the context path is set to "/path"
But the log shows:
=================================
20:00:49,297 INFO [TomcatDeployment] deploy,
ctxPath=/jmx-console
20:00:49,399 INFO [TomcatDeployment] deploy, ctxPath=/lambda
=====================================
I think this is a bug.
16 years, 11 months
"problems downloading files from solaris"
by Jane Doe
I am having trouble with Flash files sometimes not completely downloading. The mime type is set correctly. I also have download issues with zip files. I am not sure what to check to troubleshoot this issue. Any guidance would be appreciated.
Thanks in advance.
span.widgetWrapper { font-size:1em; color:#B11196; text-decoration:underline; } a.widgetLink { color:#000000; text-decoration:none; } span.widgetInLink:hover { background-color:#B11196; }
16 years, 11 months
Branch_5_x build broken
by Paul Ferraro
... due to a recent upgrade of jboss-metadata to 1.0.0.CR18. The new
version exists in the maven repository, but the updated
maven-metadata.xml was not checked in.
16 years, 11 months
Maven Repo is not synching
by Jason T. Greene
FYI,
There is some kind of outage prevent the maven repo from syncing. So
unfortunately component updates will have to wait. IT tells me they are
working hard on it.
--
Jason T. Greene
JBoss, a division of Red Hat
16 years, 11 months
