You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Siqi Du (JIRA)" <ji...@apache.org> on 2009/09/02 11:30:33 UTC

[jira] Created: (GERONIMO-4839) A non-existent EJB server also can run

A non-existent EJB server also can run
--------------------------------------

                 Key: GERONIMO-4839
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4839
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: monitoring
    Affects Versions: 2.2
            Reporter: Siqi Du
             Fix For: 2.2


1, Add an existent ejb server, and it works
2, Add an non-existent ejb server, and it also runs well.

I have investigated it and found that an issue(or a bug) of OpenEJB with the help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response.

But for the end user, it is really a bug of Geronimo,  I think it need to be work around anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (GERONIMO-4839) A non-existent EJB server also can run

Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siqi Du closed GERONIMO-4839.
-----------------------------


The bug in openejb has been fixed, close it.

> A non-existent EJB server also can run
> --------------------------------------
>
>                 Key: GERONIMO-4839
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4839
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 2.2
>            Reporter: Siqi Du
>             Fix For: 2.2
>
>         Attachments: screenshot-1.jpg
>
>
> 1, Add an existent ejb server, and it works
> 2, Add an non-existent ejb server, and it also runs well.
> I have investigated it and found that an issue(or a bug) of OpenEJB with the help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response.
> But for the end user, it is really a bug of Geronimo,  I think it need to be work around anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-4839) A non-existent EJB server also can run

Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753995#action_12753995 ] 

Siqi Du commented on GERONIMO-4839:
-----------------------------------

The bug in openejb has been fix in its trunk, and we still need to wait for the latest openejb build uploaded to maven repo .

> A non-existent EJB server also can run
> --------------------------------------
>
>                 Key: GERONIMO-4839
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4839
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 2.2
>            Reporter: Siqi Du
>             Fix For: 2.2
>
>         Attachments: screenshot-1.jpg
>
>
> 1, Add an existent ejb server, and it works
> 2, Add an non-existent ejb server, and it also runs well.
> I have investigated it and found that an issue(or a bug) of OpenEJB with the help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response.
> But for the end user, it is really a bug of Geronimo,  I think it need to be work around anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (GERONIMO-4839) A non-existent EJB server also can run

Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siqi Du resolved GERONIMO-4839.
-------------------------------

    Resolution: Fixed

> A non-existent EJB server also can run
> --------------------------------------
>
>                 Key: GERONIMO-4839
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4839
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 2.2
>            Reporter: Siqi Du
>             Fix For: 2.2
>
>         Attachments: screenshot-1.jpg
>
>
> 1, Add an existent ejb server, and it works
> 2, Add an non-existent ejb server, and it also runs well.
> I have investigated it and found that an issue(or a bug) of OpenEJB with the help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response.
> But for the end user, it is really a bug of Geronimo,  I think it need to be work around anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (GERONIMO-4839) A non-existent EJB server also can run

Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siqi Du updated GERONIMO-4839:
------------------------------

    Attachment: screenshot-1.jpg

> A non-existent EJB server also can run
> --------------------------------------
>
>                 Key: GERONIMO-4839
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4839
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 2.2
>            Reporter: Siqi Du
>             Fix For: 2.2
>
>         Attachments: screenshot-1.jpg
>
>
> 1, Add an existent ejb server, and it works
> 2, Add an non-existent ejb server, and it also runs well.
> I have investigated it and found that an issue(or a bug) of OpenEJB with the help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response.
> But for the end user, it is really a bug of Geronimo,  I think it need to be work around anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.