July 2011 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Assigned: (EMBJOPR-160) Expand navigation tree to the newly created resource's node

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-160?page=com.atlassian.jira.plugi... ] Ondrej Zizka reassigned EMBJOPR-160: ------------------------------------ Assignee: Charles Crouch Will this be implemented? > Expand navigation tree to the newly created resource's node > ----------------------------------------------------------- > > Key: EMBJOPR-160 > URL: https://issues.jboss.org/browse/EMBJOPR-160 > Project: Embedded Jopr > Issue Type: Enhancement > Environment: EmbJopr r325 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > After creating a JMS Topic, the Topic nav tree node remains collapsed. Would be better to have it expanded. > I haven't tried with other resources, but assume it's general behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-190) Make error messages formatted

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-190?page=com.atlassian.jira.plugi... ] Ondrej Zizka updated EMBJOPR-190: --------------------------------- Priority: Major (was: Minor) I assume parsing messages from AS exception is not a nice way to get some information out of it... Perhaps there could be some other way to get an object or XML snippet with the error info and render it. But that would probably need too substantial effort in AS 5 plugin. > Make error messages formatted > ----------------------------- > > Key: EMBJOPR-190 > URL: https://issues.jboss.org/browse/EMBJOPR-190 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.2 > Environment: r500 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Attachments: EMBJOPR-190b.png, Obrazovka-JBoss AS Administration Console - Mozilla Firefox.png > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > Currently, error messages are displayed in a simple div using red bold Verdana. > This is kind of unreadable in situations when some operation causes an exception with a long message - see attached screenshot. > What about making this a bit formatted, e.g. divide it to logical parts - if it's possible to do it in some general way. In the case depicted in the screenshot, it would be something like the following: > <div> > Failed to create Resource ejbredeploy-bad.jar - cause: > <div>java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: ... </div> > <div>Error vfszip:/home/brq/ozizka/JoprEmbedded/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/ejbredeploy-bad.jar/</div> > <div>org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/brq/ozizka ...</div> > ... > </div> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (EMBJOPR-190) Make error messages formatted

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-190?page=com.atlassian.jira.plugi... ] Ondrej Zizka reassigned EMBJOPR-190: ------------------------------------ Assignee: Charles Crouch > Make error messages formatted > ----------------------------- > > Key: EMBJOPR-190 > URL: https://issues.jboss.org/browse/EMBJOPR-190 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.2 > Environment: r500 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > Attachments: EMBJOPR-190b.png, Obrazovka-JBoss AS Administration Console - Mozilla Firefox.png > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > Currently, error messages are displayed in a simple div using red bold Verdana. > This is kind of unreadable in situations when some operation causes an exception with a long message - see attached screenshot. > What about making this a bit formatted, e.g. divide it to logical parts - if it's possible to do it in some general way. In the case depicted in the screenshot, it would be something like the following: > <div> > Failed to create Resource ejbredeploy-bad.jar - cause: > <div>java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: ... </div> > <div>Error vfszip:/home/brq/ozizka/JoprEmbedded/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/ejbredeploy-bad.jar/</div> > <div>org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/brq/ozizka ...</div> > ... > </div> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-190) Make error messages formatted

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-190?page=com.atlassian.jira.plugi... ] Ondrej Zizka commented on EMBJOPR-190: -------------------------------------- Stacktraces still dumped for most resources. Will this be fixed? > Make error messages formatted > ----------------------------- > > Key: EMBJOPR-190 > URL: https://issues.jboss.org/browse/EMBJOPR-190 > Project: Embedded Jopr > Issue Type: Feature Request > Affects Versions: 1.2 > Environment: r500 > Reporter: Ondrej Zizka > Priority: Minor > Attachments: EMBJOPR-190b.png, Obrazovka-JBoss AS Administration Console - Mozilla Firefox.png > > Original Estimate: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > Currently, error messages are displayed in a simple div using red bold Verdana. > This is kind of unreadable in situations when some operation causes an exception with a long message - see attached screenshot. > What about making this a bit formatted, e.g. divide it to logical parts - if it's possible to do it in some general way. In the case depicted in the screenshot, it would be something like the following: > <div> > Failed to create Resource ejbredeploy-bad.jar - cause: > <div>java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: ... </div> > <div>Error vfszip:/home/brq/ozizka/JoprEmbedded/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/ejbredeploy-bad.jar/</div> > <div>org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/brq/ozizka ...</div> > ... > </div> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-176) Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-176?page=com.atlassian.jira.plugi... ] Ondrej Zizka commented on EMBJOPR-176: -------------------------------------- So, what happened in the end? Is it now part of some EmbJopr release? Or what is the plan? > Call to org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource() timed out > -------------------------------------------------------------------------------------- > > Key: EMBJOPR-176 > URL: https://issues.jboss.org/browse/EMBJOPR-176 > Project: Embedded Jopr > Issue Type: Bug > Environment: EmbJopr testsuite - testEarDeploymentRepeated() > Reporter: Ondrej Zizka > Assignee: Ian Springer > > After deploying and undeploying the same EAR for several times (around 60), the call to testEarDeploymentRepeated() times out. > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:595) > Failed to create Resource eardeployment.ear - cause: org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource()] with args [[CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Enterprise Application (EAR), plugin=JBossAS5]], ResourceKey=[null]]] timed out. Invocation thread will be interrupted > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:437) > at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:406) > at $Proxy264.createResource(Unknown Source) > at org.rhq.core.pc.inventory.CreateResourceRunner.call(CreateResourceRunner.java:113) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-168) Uploading a large file causes OOME

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-168?page=com.atlassian.jira.plugi... ] Ondrej Zizka updated EMBJOPR-168: --------------------------------- Priority: Critical (was: Minor) > Uploading a large file causes OOME > ---------------------------------- > > Key: EMBJOPR-168 > URL: https://issues.jboss.org/browse/EMBJOPR-168 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.2 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Critical > > Uploading a large file causes OOME. > There should be some upper limit, or seam should not keep whole body of the upload request in the memory. > Reproduce steps: > Try to deploy some large file ( > 250 MB). > Fails with this stacktrace: > java.lang.OutOfMemoryError: Java heap space > java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) > org.jboss.seam.web.MultipartRequestImpl$FileParam.appendData(MultipartRequestImpl.java:181) > org.jboss.seam.web.MultipartRequestImpl.parseRequest(MultipartRequestImpl.java:408) > org.jboss.seam.web.MultipartRequestImpl.getParameterNames(MultipartRequestImpl.java:520) > org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:84) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) > org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) > org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) > org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) > org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:94) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-168) Uploading a large file causes OOME

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-168?page=com.atlassian.jira.plugi... ] Ondrej Zizka commented on EMBJOPR-168: -------------------------------------- Will this be fixed? > Uploading a large file causes OOME > ---------------------------------- > > Key: EMBJOPR-168 > URL: https://issues.jboss.org/browse/EMBJOPR-168 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.2 > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Minor > > Uploading a large file causes OOME. > There should be some upper limit, or seam should not keep whole body of the upload request in the memory. > Reproduce steps: > Try to deploy some large file ( > 250 MB). > Fails with this stacktrace: > java.lang.OutOfMemoryError: Java heap space > java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) > org.jboss.seam.web.MultipartRequestImpl$FileParam.appendData(MultipartRequestImpl.java:181) > org.jboss.seam.web.MultipartRequestImpl.parseRequest(MultipartRequestImpl.java:408) > org.jboss.seam.web.MultipartRequestImpl.getParameterNames(MultipartRequestImpl.java:520) > org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:84) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) > org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) > org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) > org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) > org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:94) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (EMBJOPR-164) Pagination in ops history table slightly distorted

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-164?page=com.atlassian.jira.plugi... ] Ondrej Zizka commented on EMBJOPR-164: -------------------------------------- Will this be fixed? > Pagination in ops history table slightly distorted > -------------------------------------------------- > > Key: EMBJOPR-164 > URL: https://issues.jboss.org/browse/EMBJOPR-164 > Project: Embedded Jopr > Issue Type: Bug > Environment: Embedded Jopr Core 1.2.0-SNAPSHOT (r329) > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Trivial > Attachments: Obrazovka-Embedded Jopr Core - Mozilla Firefox-1.png > > > Go to web apps, restart some war 11 times. See the attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (EMBJOPR-164) Pagination in ops history table slightly distorted

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-164?page=com.atlassian.jira.plugi... ] Ondrej Zizka reassigned EMBJOPR-164: ------------------------------------ Assignee: Charles Crouch > Pagination in ops history table slightly distorted > -------------------------------------------------- > > Key: EMBJOPR-164 > URL: https://issues.jboss.org/browse/EMBJOPR-164 > Project: Embedded Jopr > Issue Type: Bug > Environment: Embedded Jopr Core 1.2.0-SNAPSHOT (r329) > Reporter: Ondrej Zizka > Assignee: Charles Crouch > Priority: Trivial > Attachments: Obrazovka-Embedded Jopr Core - Mozilla Firefox-1.png > > > Go to web apps, restart some war 11 times. See the attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-160) Expand navigation tree to the newly created resource's node

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-160?page=com.atlassian.jira.plugi... ] Ondrej Zizka updated EMBJOPR-160: --------------------------------- Issue Type: Enhancement (was: Bug) > Expand navigation tree to the newly created resource's node > ----------------------------------------------------------- > > Key: EMBJOPR-160 > URL: https://issues.jboss.org/browse/EMBJOPR-160 > Project: Embedded Jopr > Issue Type: Enhancement > Environment: EmbJopr r325 > Reporter: Ondrej Zizka > Priority: Minor > > After creating a JMS Topic, the Topic nav tree node remains collapsed. Would be better to have it expanded. > I haven't tried with other resources, but assume it's general behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues July 2011