Yes Kedar,
I am stuck with this issue for 3 builds starting from build 16. It is
reproducible on Linux too. Please see bug#6467623.
Could you please explain what the EE QL is?
Thanks
Jothir
Kedar Mhaswade wrote:
> Also, can you try the same thing on an older build? (b16, b17 for
> instance)?
>
> Thanks,
> Kedar
>
> Kedar Mhaswade wrote:
>
>> Hi Jothir,
>>
>> I am seeing these errors while running the EE QL on Solaris.
>> Let us investigate ...
>> The tinderbox appears to be all green, however.
>>
>> Regards,
>> Kedar
>>
>> jothir ganesan wrote:
>>
>>> Hi
>>>
>>> Could anyone please let me know the possible reasons for "EEADM0068:
>>> Instance instance xxx is not reachable" ? The exception shows up
>>> when trying to deploy an app on the cluster and the app fails to get
>>> deployed...
>>>
>>> I have the following setup:
>>>
>>> 3 nodeagents on 3 different machines with each nodeagent having one
>>> instance.
>>> Domain is started and the cluster,created on DAS, with the three
>>> instances - running
>>> Nodeagents- running
>>>
>>> Other configuration did:
>>> - hadb nodes running and ha-cluster is configured.
>>> - Access log buffer size ->
>>> cluster1-config.http-service.virtual-server.server.property.accessLogBufferSize
>>> set to 10 for cluster config
>>> - cluster1-config.http-service.keep-alive.timeout-in-seconds set to 0.
>>> - Some jdbc resources and connection pools created.
>>>
>>>
>>> I have my nodeagents and instances up and running.
>>> Command start-cluster executed successfully.
>>> bash-3.00# asadmin list-instances --passwordfile passwordfile
>>> instance1 running
>>> instance2 running
>>> instance3 running
>>> Command list-instances executed successfully.
>>> bash-3.00# /space/91/appserver/bin/asadmin deploy --host localhost
>>> --port 4848 --user admin --passwordfile passwordfile --target
>>> cluster1
>>> /space/91/sift/agent/file-repository/70/Apps/SampleApplications/Clusterjsp1/clu
>>> sterjsp1.war
>>> Command deploy executed successfully.
>>> bash-3.00# asadmin list-node-agents --passwordfile passwordfile
>>> sqe-agent1 running
>>> sqe-agent2 running
>>> sqe-agent3 running
>>> Command list-node-agents executed successfully.
>>>
>>> But still when I try to deploy the app, I could see :
>>> [#|2006-09-26T16:03:20.722+0530|WARNING|sun-appserver-ee9.1|javax.ee.enterprise
>>> .system.tools.admin|_ThreadID=198;_ThreadName=event-handler-0;instance1;_Request
>>> ID=4c5551da-d066-451e-a7a9-ee36c5a8ab47;|EEADM0068: Instance
>>> instance1 is not reachable.|#]
>>>
>>> [#|2006-09-26T16:03:20.739+0530|WARNING|sun-appserver-ee9.1|javax.ee.enterprise
>>> .system.tools.admin|_ThreadID=199;_ThreadName=event-handler-1;instance2;_Request
>>> ID=3c7c1df3-a47f-44a9-a418-e506bab400bf;|EEADM0068: Instance
>>> instance2 is not reachable.|#]
>>>
>>> [#|2006-09-26T16:03:20.759+0530|WARNING|sun-appserver-ee9.1|javax.ee.enterprise
>>> .system.tools.admin|_ThreadID=200;_ThreadName=event-handler-2;instance3;_Request
>>> ID=da9f94fd-c35e-417d-ba3a-41c0cecc91c5;|EEADM0068: Instance
>>> instance3 is not reachable.|#]
>>>
>>> What else do I need to check?
>>>
>>> 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
>