dev@glassfish.java.net

2-way bug bridge --- Re: AS EE 9.1 ea build 13

From: Eduardo Pelegri-Llopart <pelegri_at_sun.com>
Date: Mon, 21 Aug 2006 16:57:35 -0700

Yes, indeed!

We should be sure there is enough documentation and oppty for Q&A on it
when it goes live...

        - eduard/o

Sridatta Viswanath wrote:
> Deepa plans to have the 2-way bug bridge operational very soon -- matter
> of days! Go Deepa!
>
> -Sridatta
>
> Eduardo Pelegri-Llopart wrote:
>
>> I don't know. Sridatta would, though...
>>
>> - eduard/o
>>
>> Carla Mott wrote:
>>
>>> Given the bug id external users can view the bug. However,
>>> the 2-way bug bridge is supposed to handle this. Any idea when
>>> that will be operational?
>>>
>>> Carla
>>>
>>> Eduardo Pelegri-Llopart wrote:
>>>
>>>> We have to fix that. Those bugs need to be fully exposed to everybody.
>>>>
>>>> - eduard/o
>>>>
>>>> Lloyd L Chambers wrote:
>>>>
>>>>> Jan,
>>>>>
>>>>> (Not a criticism, it's just a bad setup with Glassfish IMO).
>>>>>
>>>>> It's not good referring to an internal bug system on a public alias...
>>>>>
>>>>> Lloyd
>>>>>
>>>>> On Aug 17, 2006, at 9:35 AM, Jan Luehe wrote:
>>>>>
>>>>>> Hi Jothir,
>>>>>>
>>>>>> jothir ganesan wrote On 08/17/06 05:17,:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I tried the following in a clean machine with no java processes
>>>>>>> running:
>>>>>>>
>>>>>>> - Installed the appserver
>>>>>>> - Started the domain
>>>>>>> - Created a node agent
>>>>>>> - Created a cluster and 3 instances for the cluster
>>>>>>> - Tried starting the nodeagent....
>>>>>>>
>>>>>>> When I tried listing the java processes,
>>>>>>>
>>>>>>> 1009 com.sun.enterprise.server.PELaunch
>>>>>>> 1056 sun.tools.jps.Jps
>>>>>>> 967 com.sun.enterprise.server.PELaunch
>>>>>>> 1010 com.sun.enterprise.server.PELaunch
>>>>>>> 991 com.sun.enterprise.ee.nodeagent.NodeAgentMain
>>>>>>> 1008 com.sun.enterprise.ee.tools.launcher.ProcessLauncher
>>>>>>> 1003 com.sun.enterprise.ee.tools.launcher.ProcessLauncher
>>>>>>> 1025 com.sun.messaging.jmq.jmsserver.Broker
>>>>>>> 1011 com.sun.enterprise.server.PELaunch
>>>>>>> 1047 com.sun.messaging.jmq.jmsserver.Broker
>>>>>>> 988 com.sun.enterprise.cli.framework.CLIMain
>>>>>>> 1005 com.sun.enterprise.ee.tools.launcher.ProcessLauncher
>>>>>>> 1036 com.sun.messaging.jmq.jmsserver.Broker
>>>>>>>
>>>>>>> this many processes were running. The machine is totally slow
>>>>>>> now. Could any one please clarify why so many processes are
>>>>>>> running and is it expected to work this way?
>>>>>>>
>>>>>>> Moreover, when I started the domain, I saw the following
>>>>>>> exception trace in the domain's server.log:
>>>>>>>
>>>>>>> [#|2006-08-17T17:23:49.169+0530|SEVERE|sun-appserver-ee9.1|
>>>>>>> org.apache.catalina.core.StandardContext|
>>>>>>> _ThreadID=10;_ThreadName=main;_RequestID=21217595-d807-45bc-aa96-
>>>>>>> ed7eadf04962;|PWC1315: Error reading listeners from TLD
>>>>>>> javax.servlet.ServletException: PWC3037: Exception processing
>>>>>>> TLD at resource path /WEB-INF/lib/cc.tld in context /asadmin
>>>>>>> at org.apache.catalina.startup.TldConfig.tldScanTld
>>>>>>> (TldConfig.java:724)
>>>>>>> at org.apache.catalina.startup.TldConfig.execute
>>>>>>> (TldConfig.java:440)
>>>>>>> at org.apache.catalina.core.StandardContext.start
>>>>>>> (StandardContext.java:4696)
>>>>>>> at
>>>>>>> com.sun.enterprise.web.WebModule.start(WebModule.java:292)
>>>>>>> at org.apache.catalina.core.ContainerBase.start
>>>>>>> (ContainerBase.java:1095)
>>>>>>> at org.apache.catalina.core.StandardHost.start
>>>>>>> (StandardHost.java:907)
>>>>>>> at org.apache.catalina.core.ContainerBase.start
>>>>>>> (ContainerBase.java:1095)
>>>>>>> at org.apache.catalina.core.StandardEngine.start
>>>>>>> (StandardEngine.java:520)
>>>>>>> at org.apache.catalina.startup.Embedded.start
>>>>>>> (Embedded.java:920)
>>>>>>> at com.sun.enterprise.web.WebContainer.start
>>>>>>> (WebContainer.java:811)
>>>>>>> at com.sun.enterprise.web.PEWebContainer.startInstance
>>>>>>> (PEWebContainer.java:733)
>>>>>>> at
>>>>>>> com.sun.enterprise.web.PEWebContainerLifecycle.onStartup
>>>>>>> (PEWebContainerLifecycle.java:72)
>>>>>>> at com.sun.enterprise.server.ApplicationServer.onStartup
>>>>>>> (ApplicationServer.java:326)
>>>>>>> at
>>>>>>> com.sun.enterprise.server.ondemand.OnDemandServer.onStartup
>>>>>>> (OnDemandServer.java:112)
>>>>>>> at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
>>>>>>> at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>> Method)
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke
>>>>>>> (NativeMethodAccessorImpl.java:39)
>>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke
>>>>>>> (DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>>>>> at
>>>>>>> com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
>>>>>>> Caused by: java.net.MalformedURLException
>>>>>>> at java.net.URL.<init>(URL.java:601)
>>>>>>> at java.net.URL.<init>(URL.java:464)
>>>>>>> at java.net.URL.<init>(URL.java:413)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> See http://bt2ws.central.sun.com/CrPrint?id=6453405 for the
>>>>>> cause of the java.net.MalformedURLException.
>>>>>>
>>>>>>
>>>>>> Jan
>>>>>>
>>>>>>
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrent
>>>>>>> Entity(XMLEntityManager.java:968)
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineD
>>>>>>> ocVersion(XMLVersionDetector.java:184)
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
>>>>>>> (XML11Configuration.java:798)
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
>>>>>>> (XML11Configuration.java:764)
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
>>>>>>> (XMLParser.java:148)
>>>>>>> at
>>>>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse
>>>>>>> (AbstractSAXParser.java:1242)
>>>>>>> at com.sun.org.apache.commons.digester.Digester.parse
>>>>>>> (Digester.java:1548)
>>>>>>> at org.apache.catalina.startup.TldConfig.tldScanStream
>>>>>>> (TldConfig.java:679)
>>>>>>> at org.apache.catalina.startup.TldConfig.tldScanTld
>>>>>>> (TldConfig.java:722)
>>>>>>> ... 20 more
>>>>>>> |#]
>>>>>>>
>>>>>>> Could anyone please clarify the above issues?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Jothir
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>