 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] Created: (JBIDE-2173) Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
                                
                                
                                
                                    
                                        by Vitali Yemialyanchyk (JIRA)
                                    
                                
                                
                                        Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
----------------------------------------------------------------------------------------------------------
                 Key: JBIDE-2173
                 URL: http://jira.jboss.com/jira/browse/JBIDE-2173
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: Hibernate
            Reporter: Vitali Yemialyanchyk
         Assigned To: Vitali Yemialyanchyk
            Priority: Minor
For test purposes I create org.hibernate.eclipse.console.test -> org.hibernate.eclipse.console.db.test.BigDBCreateTest - the main goal of this class is creation test database with specified number of related tables. Then with help of BigDBCreateTest I create a big enough databases with different number of tables in it. And then I try to test hibernate plugins performance. I create a configuration for my test db.
In Hibernate Console I try to expand tree. Here is a time:
200 tables in db - takes 40 seconds;
300 tables in db - takes 2 minutes 45 seconds;
500 tables in db - too long I do not get results.
Remark: I use MySQL as test db. 3000 tables - too much for MySQL. Also - it is intresting - when I create such big db - I try to expand Hibernate Console tree - I get MySQL exception - but in this case Hibernate Console display all items quickly!
JBIDE-2162 is related;
JBIDE-2163 & JBIDE-2164 are related by implication - till the moment when I have fixed its in my test environment - I can't see performance problems.
-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
        
                                
                         
                        
                                
                                13 years, 1 month
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] Created: (JBIDE-7271) Ensure Tools work with out-of-the-box platforms
                                
                                
                                
                                    
                                        by Rob Stryker (JIRA)
                                    
                                
                                
                                        Ensure Tools work with out-of-the-box platforms
-----------------------------------------------
                 Key: JBIDE-7271
                 URL: https://jira.jboss.org/browse/JBIDE-7271
             Project: Tools (JBoss Tools)
          Issue Type: Task
          Components: JBossAS
    Affects Versions: 3.2.0.M2
            Reporter: Rob Stryker
            Assignee: Rob Stryker
             Fix For: 3.2.0.CR1
I've recently started re-testing with out-of-the box platforms (EPP, EAP, SOA-P), fresh unzipped installations, and I'm realizing most of them do not have JMX enabled. This is a problem for our tools. It means things like putting the our deployments into a metadata location rather than config/deploy cannot work, because we cannot tell the Deployment Scanner (via JMX) that thats where our deployments are. Also, without JMX enabled, I've noticed my shutdown scripts fail. 
Originally I thought this was just a toolset issue, but when I started using the command line to see if there was some problem in the tools or not, I started realizing, I have absolutely *NO* idea how to properly shut down these platform servers without modifying property files. IS there a way? Or are all new users of EAP / EPP / SOA-P expected to go expose their jmx console in order to use the ./shutdown.sh script? 
For EAP and EPP, I am only able to properly shut down the server if I modify the default/conf/props/jmx-console-users.properties file. Is this correct? There is no way to shut down the server from the command line without exposing a user via JMX? 
When trying SOA-P 5.1, I notice the same behaviour. The shutdown script does not work at all without JMX exposed, *AND*, in this case, the "soa-users.properties" file is the one containing the usernames and passwords admin=admin. 
A summary, In order to enable *command line* shutdowns (and thus tooling shutdowns), it seems I must modify a properties file (who's name changes between platforms??) to expose the jmx console. 
So again, I ask, am I doing this right? This is all command-line. The next problem is, assuming all my assumptions are correct, what should our tools do to help users with a fresh *manually downloaded* EAP / EPP / SOA-P installations do to get set up? (As far as I know, JBDS bundles customize the configuration slightly). Should we offer to expose their consoles FOR them by changing this properties file? Or should we simply deploy all objects in server/{config}/deploy instead of in workspace.metadata.folder and use jmx to add that folder to the deployment scanner? 
-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
        
                                
                         
                        
                                
                                13 years, 1 month
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] Created: (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
                                
                                
                                
                                    
                                        by Rob Stryker (JIRA)
                                    
                                
                                
                                        Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
-------------------------------------------------------------------------------------------------
                 Key: JBIDE-7379
                 URL: https://jira.jboss.org/browse/JBIDE-7379
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: JBossAS
    Affects Versions: 3.2.0.Beta1
            Reporter: Rob Stryker
            Assignee: Rob Stryker
             Fix For: 3.2.0.Beta2, 3.2.0.CR1
Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args. 
Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for. 
This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin. 
It currently seems to be saving only servers and not the runtimes. 
-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
        
                                
                         
                        
                                
                                13 years, 1 month
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] Created: (JBDS-1229) ESB binary export from JBDS doesn't include source
                                
                                
                                
                                    
                                        by Stelios Koussouris (JIRA)
                                    
                                
                                
                                        ESB binary export from JBDS doesn't include source
--------------------------------------------------
                 Key: JBDS-1229
                 URL: https://jira.jboss.org/browse/JBDS-1229
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Feature Request
          Components: libmanagement
    Affects Versions: 3.0.0.GA
            Reporter: Stelios Koussouris
Trying to export ESB binary along with the source code of
a) the esb actions
b) the referenced jars
The result of setting the references to other projects/jars via 
ESB Project --> Properties --> Module Assembly and then
ESB Project --> Export --> ESB --> clicking the  "export source files"
the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects.
-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
        
                                
                         
                        
                                
                                13 years, 1 month
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] Created: (JBIDE-473) JBoss AS ignores context root property of dynamic web project
                                
                                
                                
                                    
                                        by Viacheslav Kabanovich (JIRA)
                                    
                                
                                
                                        JBoss AS ignores context root property of dynamic web project
-------------------------------------------------------------
                 Key: JBIDE-473
                 URL: http://jira.jboss.com/jira/browse/JBIDE-473
             Project: JBoss Tools
          Issue Type: Feature Request
            Reporter: Viacheslav Kabanovich
Open editor for Tomcat Server (double click Tomcat node in Servers view). The editor has two tabs - Overview and Modules. In Modules tab, it is possible to select a registered web project and call dialog for changing path (context root) property by Edit button. Then, for example, if project's name is MyProject but path is set to /OurProject, in order to access the application running on Tomcat server one has to type in browser an address like http://localhost:8080/OurProject rather than http://localhost:8080/MyProject.
Red Hat studio defines menu action 'Register Web Context in Server', which invokes dialog that allows to set context root property. That works fine with Tomcat server, but fails with JBoss AS, because it seems that its implementation ignores this property of web project when deploying it. Hence, the request is to develop this functionality of JBoss AS to the level of Tomcat server.
Context root property is accessible through class org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities with methods
public static void setServerContextRoot(IProject project, String contextRoot)
public static String getServerContextRoot(IProject project)
-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
        
                                
                         
                        
                                
                                13 years, 1 month