Hi Naman,
Below ([1]) is the output. While it comes under 'Messages with no proper message
Id', the only messages without ids seem to be either parts of a multi-line
output or a java path.
FAILED message after your test is also confusing, because nothing actually fails.
thanks,
-marina
[1]
[echo] * Messages with no proper message Id:
[echo] /export/jdk1.6.0_07/bin/java
[echo]
[#|2010-06-28T15:51:50.824-0700|INFO|glassfish3.1|javax.enterprise.resource.jta.com.sun.enterprise.transaction|_ThreadID=14;_ThreadName=Thread-1;|DTX5019:
Using [com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate]
as the delegate|#]
[echo]
[#|2010-06-28T15:51:53.864-0700|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=14;_ThreadName=Thread-1;|core.start_container_done|#]
[echo]
[#|2010-06-28T15:52:31.083-0700|INFO|glassfish3.1|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=225;_ThreadName=Thread-1;|SEC1002:
Security Manager is OFF.|#]
[echo]
[#|2010-06-28T15:52:31.642-0700|INFO|glassfish3.1|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=225;_ThreadName=Thread-1;|SEC1143:
Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[echo]
[#|2010-06-28T15:54:43.265-0700|INFO|glassfish3.1|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=221;_ThreadName=Thread-1;|JTS5014:
Recoverable JTS instance, serverId = [3700]|#]
[echo]
[#|2010-06-28T15:55:23.961-0700|SEVERE|glassfish3.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=222;_ThreadName=Thread-1;|DPL8007:
Invalid Deployment Descriptors element mlns value
http://java.sun.com/xml/ns/j2ee|#]
[echo]
[#|2010-06-28T15:55:34.512-0700|INFO|glassfish3.1|com.sun.xml.ws.servlet.http|_ThreadID=26;_ThreadName=Thread-1;|WSSERVLET14:
JAX-WS servlet initializing|#]
[echo]
[#|2010-06-28T15:55:55.981-0700|SEVERE|glassfish3.1|null|_ThreadID=34;_ThreadName=Thread-1;|cannot
load libbtrace.so, will miss DTrace probes from BTrace|#]
[echo] class com.sun.jersey.multipart.impl.FormDataMultiPartDispatchProvider
[echo] class com.sun.jersey.multipart.impl.MultiPartConfigProvider
[echo] class com.sun.jersey.multipart.impl.MultiPartReader
[echo] class com.sun.jersey.multipart.impl.MultiPartWriter|#]
[echo] class com.sun.jersey.multipart.impl.FormDataMultiPartDispatchProvider
[echo] class com.sun.jersey.multipart.impl.MultiPartConfigProvider
[echo] class com.sun.jersey.multipart.impl.MultiPartReader
[echo] class com.sun.jersey.multipart.impl.MultiPartWriter|#]
[echo]
[#|2010-06-28T15:57:58.627-0700|INFO|glassfish3.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=29;_ThreadName=Thread-1;|MQJMSRA_RA1101:
SJSMQ JMS Resource Adapter starting: DIRECT|#]
[echo]
[#|2010-06-28T15:58:03.021-0700|INFO|glassfish3.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=29;_ThreadName=Thread-1;|MQJMSRA_RA1101:
SJSMQ JMSRA Started:DIRECT|#]
[echo]
[#|2010-06-28T15:59:06.473-0700|INFO|glassfish3.1|com.sun.xml.ws.servlet.http|_ThreadID=27;_ThreadName=Thread-1;|WSSERVLET15:
JAX-WS servlet destroyed|#]
[echo]
[#|2010-06-28T15:59:10.208-0700|INFO|glassfish3.1|null|_ThreadID=24;_ThreadName=Thread-1;|ERROR:
Error writing persistent state to bundle archive.
(java.io.InterruptedIOException)|#]
[echo]
[#|2010-06-28T15:59:10.209-0700|SEVERE|glassfish3.1|null|_ThreadID=24;_ThreadName=Thread-1;|java.io.InterruptedIOException|#]
[echo] /export/jdk1.6.0_07/bin/java
[echo] Jun 28, 2010 3:59:10 PM
com.sun.enterprise.admin.launcher.GFLauncherLogger severe
[echo] SEVERE: The configured OSGi Telnet port (6666) is already in use by
another process. The OSGi Telnet Service will not be available but GlassFish
won't be affected otherwise.
[echo] Jun 28, 2010 3:59:24 PM null
[echo]
[#|2010-06-28T15:59:25.619-0700|INFO|glassfish3.1|javax.enterprise.resource.jta.com.sun.enterprise.transaction|_ThreadID=14;_ThreadName=Thread-1;|DTX5019:
Using [com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate]
as the delegate|#]
[echo]
[#|2010-06-28T15:59:25.702-0700|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|cannot
load libbtrace.so, will miss DTrace probes from BTrace|#]
[echo]
[#|2010-06-28T15:59:29.474-0700|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=14;_ThreadName=Thread-1;|core.start_container_done|#]
[echo]
[echo]
Naman Mehta wrote:
>
> hi marina,
>
> Updated the exception list with proper details. Output should not be
> bigger now. If you get bigger list please send me the QL output log.
>
> Regards,
> Naman
>
> On Sunday 27 June 2010 03:18 AM, Marina Vatkina wrote:
>
>> Naman,
>>
>> Can you have a human-readable output from this test? The output is so
>> long, you can't spot anything there...
>>
>> thanks,
>> -marina
>>
>> Naman Mehta wrote:
>>
>>> On Saturday 26 June 2010 02:11 AM, Chris Kasso wrote:
>>>
>>>>
>>>>
>>>> Naman Mehta wrote:
>>>>
>>>>>
>>>>> hi tom,
>>>>>
>>>>> Right now, it won't fail QL otherwise hudson will remain RED and
>>>>> due to this RE can not promote a build and SQE can not certify a
>>>>> build.
>>>>>
>>>>> My plan is to monitor this and raised the bug for respective module
>>>>> with P2.
>>>>
>>>>
>>>> A P2 seems a bit high for some of the issues this test may find. A
>>>> P2 suggests the fix should be in by the next milestone. For
>>>> example a misspelling of a log message while easy to fix is not a P2
>>>> issue. I think most of the issues this test would find should be
>>>> P3's some maybe P4's.
>>>>
>>>> Can you also choose a consistent keyword to be put in the whiteboard
>>>> field to make it easy to track these logging issues in issuetracker?
>>>
>>>
>>> Make it as P2 to make sure developer can fix immediately and these
>>> are the issues to be fixed easily. We need to close all log message
>>> issues before MS3 if possible so we don't have much left after MS3. I
>>> will use proper keyword as subject line(starting with Log: ) to
>>> differentiate with other bugs.
>>>
>>> Regards,
>>> Naman
>>>
>>>>
>>>> thanks,
>>>> Chris
>>>>
>>>>>
>>>>> Regards,
>>>>> Naman
>>>>>
>>>>> On Friday 25 June 2010 07:33 PM, Tom Mueller wrote:
>>>>>
>>>>>> Naman,
>>>>>>
>>>>>> This sounds like a very nice tool. I would suggest that if any
>>>>>> problem found by this tool would be considered a P3 or higher
>>>>>> defect, then we should have failure of the tool cause failure of
>>>>>> the QL tests. Otherwise, the failure output will be ignored until
>>>>>> much later in the project when the fix will be more expensive to
>>>>>> make.
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>>
>>>>>> On 6/25/2010 12:33 AM, Naman Mehta wrote:
>>>>>>
>>>>>>>
>>>>>>> hi all,
>>>>>>>
>>>>>>> I am planning to send same email. How to use this and How to
>>>>>>> check your error?
>>>>>>>
>>>>>>> Right now it's giving error for all messages(from server.log
>>>>>>> file) not specific to your module.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Naman
>>>>>>>
>>>>>>> On Friday 25 June 2010 05:22 AM, Ming Zhang wrote:
>>>>>>>
>>>>>>>> Naman integrated the check-logged-message target to QL yesterday.
>>>>>>>>
>>>>>>>> Naman, can you add descriptions to section I of
>>>>>>>> quicklook/QuickLook_Test_Instructions.html for how user should
>>>>>>>> use/interpreate this target?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Ming
>>>>>>>>
>>>>>>>> On 6/24/2010 3:32 PM, Jane Young wrote:
>>>>>>>>
>>>>>>>>> Okay, I see the check-logged-message target:
>>>>>>>>>
>>>>>>>>> check-logged-messages:
>>>>>>>>> [echo] Checking messages in:
>>>>>>>>> [echo]
>>>>>>>>> /BUILD_AREA/workspace/gf-trunk-build-continuous/gfv3-gp/glassfishv3/glassfish/domains/domain1/logs/server.log
>>>>>>>>>
>>>>>>>>> [echo] [copy] Copying 1 file to
>>>>>>>>> /export/home1/java_re/BUILD_AREA/workspace/gf-trunk-build-continuous/v3/tests/test-output
>>>>>>>>>
>>>>>>>>> [echo]
>>>>>>>>> [echo] * Message keys logged instead of message:
>>>>>>>>> [echo] (none)
>>>>>>>>> [echo]
>>>>>>>>>
>>>>>>>>> Ming, can you answer Marina's question.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Jane
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Marina Vatkina wrote:
>>>>>>>>>
>>>>>>>>>> I'm asking what the check-logged-messages test does and how to
>>>>>>>>>> decipher its output?
>>>>>>>>>>
>>>>>>>>>> thanks,
>>>>>>>>>> -marina
>>>>>>>>>>
>>>>>>>>>> Jane Young wrote:
>>>>>>>>>>
>>>>>>>>>>> I'm not sure what you're asking. But you can check if QL
>>>>>>>>>>> tests are passing on Hudson:
>>>>>>>>>>> http://hudson.glassfish.org/job/gf-trunk-build-continuous/
>>>>>>>>>>> If Hudson tests are passing and your local QL tests are
>>>>>>>>>>> failing then it may be related to your changes.
>>>>>>>>>>>
>>>>>>>>>>> Marina Vatkina wrote:
>>>>>>>>>>>
>>>>>>>>>>>> What does its long output mean and how can I check if I
>>>>>>>>>>>> broke anything?
>>>>>>>>>>>>
>>>>>>>>>>>> thanks,
>>>>>>>>>>>> -marina
>>>>>>>>>>>>
>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> dev-help_at_glassfish.dev.java.net
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> quality-help_at_glassfish.dev.java.net
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>