[JBoss JIRA] Resolved: (JBAS-3150) Cipher attribute in the SSL Connector is ignored
by Anil Saldhana (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3150?page=all ]
Anil Saldhana resolved JBAS-3150.
---------------------------------
Resolution: Rejected
I reject this as a bug for the following reason.
When the user configures a comma-separated list of ciphers, then there are two criteria that are applied to figure out the final cipher suite:
Requested Cipher Suite and the default cipher suite (provided by the JDK SSLSocketFactory)
http://java.sun.com/j2se/1.4.2/docs/api/javax/net/ssl/SSLSocketFactory.html
So basically, if the user configures: ciphers = "TEST_DUMMY"
then the request cipher suite is "TEST_DUMMY" where as the default cipher suite can be:
-------------------------------------------------------------------------------------------------------------------------------
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[0]=SSL_RSA_WITH_RC4_128_MD5
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[1]=SSL_RSA_WITH_RC4_128_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[2]=TLS_RSA_WITH_AES_128_CBC_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[3]=TLS_DHE_RSA_WITH_AES_128_CBC_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[4]=TLS_DHE_DSS_WITH_AES_128_CBC_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[5]=SSL_RSA_WITH_3DES_EDE_CBC_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[6]=SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
2006-09-18 12:05:21,343 ERROR [STDERR] Supported Cipher:[7]=SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[8]=SSL_RSA_WITH_DES_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[9]=SSL_DHE_RSA_WITH_DES_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[10]=SSL_DHE_DSS_WITH_DES_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[11]=SSL_RSA_EXPORT_WITH_RC4_40_MD5
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[12]=SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[13]=SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[14]=SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[15]=TLS_RSA_WITH_AES_256_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[16]=TLS_DHE_RSA_WITH_AES_256_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[17]=TLS_DHE_DSS_WITH_AES_256_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[18]=SSL_RSA_WITH_NULL_MD5
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[19]=SSL_RSA_WITH_NULL_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[20]=SSL_DH_anon_WITH_RC4_128_MD5
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[21]=TLS_DH_anon_WITH_AES_128_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[22]=TLS_DH_anon_WITH_AES_256_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[23]=SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[24]=SSL_DH_anon_WITH_DES_CBC_SHA
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[25]=SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
2006-09-18 12:05:21,359 ERROR [STDERR] Supported Cipher:[26]=SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
================================================================================================
Since the request cipher does not exist in the default cipher, the default cipher list applies.
Now, if I configure ciphers = "TEST_DUMMY,SSL_RSA_WITH_3DES_EDE_CBC_SHA"
then the logic would enable such that the final cipher will be restricted to "SSL_RSA_WITH_3DES_EDE_CBC_SHA"
=============================================================
ERROR [STDERR] Cipher:[0]=SSL_RSA_WITH_3DES_EDE_CBC_SHA
=============================================================
===============================================
protected String[] getEnabledCiphers(String arg0, String[] arg1)
{
String[] baseCiphers = super.getEnabledCiphers(arg0, arg1);
//Print them out
int len = baseCiphers != null ? baseCiphers.length: 0;
for(int i = 0; i < len; i++)
{
System.err.println("Cipher:["+i+"]=" + baseCiphers[i]);
}
return baseCiphers;
}
================================================
So the behavior is consistent with what is expected. If the cipher suite
provided does not contain any of the default ciphers supported by the JDK,
then the default ciphers apply.
So in theory, you should have atleast one cipher that is supported by the JDK in your
cipher restriction.
> Cipher attribute in the SSL Connector is ignored
> ------------------------------------------------
>
> Key: JBAS-3150
> URL: http://jira.jboss.com/jira/browse/JBAS-3150
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service, Security
> Affects Versions: JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP1
> Reporter: Anil Saldhana
> Assigned To: Anil Saldhana
> Fix For: JBossAS-4.0.5.GA
>
>
> Please refer to the forum thread for more information.
> Please investigate this issue.
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-2299) OutOfMemory error when repetatively deploying and undeploying with 10 minute interval
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2299?page=all ]
Clebert Suconic updated JBAS-2299:
----------------------------------
Fix Version/s: JBossAS-4.0.5.GA
(was: JBossAS-4.0.6.CR1)
> OutOfMemory error when repetatively deploying and undeploying with 10 minute interval
> -------------------------------------------------------------------------------------
>
> Key: JBAS-2299
> URL: http://jira.jboss.com/jira/browse/JBAS-2299
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Deployment services
> Affects Versions: JBossAS-4.0.3RC2
> Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07
> Reporter: Amar Syed
> Assigned To: Clebert Suconic
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: Data.txt, SampleApp.ear
>
>
> Using a manual copy and delete mechanism with the server\default\deploy folder the sample ear (attached) caused an outofmemory error eventually after 90 repetitions.
> The min and max heap settings were configured as : -Xms128m -Xmx512m
> The time delay after dropping/deploying the ear at each repetition was set to 10 minutes after which the ear is deleted/undeployed followed by a 10 second sleep till the next deploy cycle.
> I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is supposed to have fixed this issue.
> The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows:
> 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null
> 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50, cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0}
> 2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw error
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] StandardWrapper.Throwable
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null
> The following two jars were added to the server\default\lib folder.
> commons-validator.jar --- version 1.1.3
> struts.jar ---- version 1.2.4
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBPM-587) GPD crashes if xmlbuddy plugin is installed
by James Callaghan (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-587?page=comments#action_12343481 ]
James Callaghan commented on JBPM-587:
--------------------------------------
I tried to disable the JBoss IDE features and plugins but the GDP still crashed when you opened it. I re-installed eclipse from scratch and added the jBPM plugins and features manually. After restarting Eclipse, jBPM worked fine. I suppose I'll just have to start and stop JBoss from a command prompt :(
> GPD crashes if xmlbuddy plugin is installed
> -------------------------------------------
>
> Key: JBPM-587
> URL: http://jira.jboss.com/jira/browse/JBPM-587
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Graphical Process Designer
> Affects Versions: jBPM GPD 3.0.8
> Environment: Gentoo Linux / Eclipse 3.1.2
> Reporter: Matthias Germann
> Assigned To: Tom Baeyens
>
> If the Graphical Process Designer plugin and the XML Buddy Plugin are installed in the same eclipse installation, the GPD crases when opening a process definition file. The problem can be reproduced by unzipping the XML Buddy Free Edition ZIP File into the plugins directory of a eclipse installation with GPD installed.
> The GPD reports the following error when opening a jBPM process definition File:
> Unable to create this part due to an internal error. Reason for the failure: An unexpected exception was thrown.
> Detail:
> java.lang.NullPointerException
> at org.jbpm.ui.editor.DesignerContentProvider.addProcessDiagramDimension(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerGraphicalEditorPage.initInput(Unknown Source)
> at org.jbpm.ui.editor.DesignerGraphicalEditorPage.init(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:152)
> at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source)
> at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:241)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552)
> at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:223)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2362)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295)
> at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:279)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:271)
> at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:178)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1021)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2867)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2572)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
> 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 org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> at org.eclipse.core.launcher.Main.run(Main.java:973)
> at org.eclipse.core.launcher.Main.main(Main.java:948)
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-2299) OutOfMemory error when repetatively deploying and undeploying with 10 minute interval
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2299?page=all ]
Clebert Suconic updated JBAS-2299:
----------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
> OutOfMemory error when repetatively deploying and undeploying with 10 minute interval
> -------------------------------------------------------------------------------------
>
> Key: JBAS-2299
> URL: http://jira.jboss.com/jira/browse/JBAS-2299
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Deployment services
> Affects Versions: JBossAS-4.0.3RC2
> Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07
> Reporter: Amar Syed
> Assigned To: Clebert Suconic
> Fix For: JBossAS-4.0.6.CR1
>
> Attachments: Data.txt, SampleApp.ear
>
>
> Using a manual copy and delete mechanism with the server\default\deploy folder the sample ear (attached) caused an outofmemory error eventually after 90 repetitions.
> The min and max heap settings were configured as : -Xms128m -Xmx512m
> The time delay after dropping/deploying the ear at each repetition was set to 10 minutes after which the ear is deleted/undeployed followed by a 10 second sleep till the next deploy cycle.
> I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is supposed to have fixed this issue.
> The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows:
> 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null
> 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50, cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0}
> 2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw error
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] StandardWrapper.Throwable
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception
> java.lang.OutOfMemoryError
> 2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null
> The following two jars were added to the server\default\lib folder.
> commons-validator.jar --- version 1.1.3
> struts.jar ---- version 1.2.4
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-1939) MBean getAttribute() launch NotSerializableException when invoked from a remote client
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1939?page=all ]
Clebert Suconic updated JBAS-1939:
----------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
> MBean getAttribute() launch NotSerializableException when invoked from a remote client
> --------------------------------------------------------------------------------------
>
> Key: JBAS-1939
> URL: http://jira.jboss.com/jira/browse/JBAS-1939
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.2 Final
> Environment: jmx, twiddle
> Reporter: Fabiano C. de Oliveira
> Assigned To: Clebert Suconic
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> when executing twiddle to get attribute from some MBeans a NotSerializableException java.io.NotSerializableException is launched.
> To reproduce this just type:
> D:\jboss-4.0.2\bin>twiddle.bat get "jboss.web:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,name=//localhost/" logger
> How can this can be fixed ? Ignoring the Non serializable attributes, returning null to Nonserializable attributes, become invisible all non-serializable attribute ?
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-1082) jdbc.WrapperDataSource.getConnection is slow
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1082?page=all ]
Clebert Suconic updated JBAS-1082:
----------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
> jdbc.WrapperDataSource.getConnection is slow
> --------------------------------------------
>
> Key: JBAS-1082
> URL: http://jira.jboss.com/jira/browse/JBAS-1082
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-3.2.6 Final
> Reporter: Elias Ross
> Assigned To: Clebert Suconic
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> SourceForge Submitter: genman .
> I've been profiling JMS code. When a JMS message is
> added to the server, the persistence manager locates an
> appropriate DataSource.
> Out of the time spent in
> org.jboss.mq.Connection.sendToServer, about 28% of the
> time is getting the database connection through
> jdbc.WrapperDataSource.getConnection to do its work.
> This is after the pool has been initialized, etc. (40%
> is actual persistence, though most of it is the message
> serialization.)
> I suspect a lot of the work is calculating a hashCode
> on the javax.security.auth.Subject. SubjectCriKey and
> SubjectKey should have this value cached. Ideally,
> when one is accessing the local DB, none of this auth
> stuff should have to take place. Looking at the source
> for Subject.java, the hash code is not kept.
> BaseConnectionManager2.allocateConnection %CPU=27.949
> %Time=27.963 calls=411
> Allocations I've seen:
> JBossManagedConnectionPool$SubjectActions
> is created 3284 times (for 411 getConnection calls)
> java.util.Properties (1642 times)
> (Disclaimer: This was done through JBoss profiler,
> which may or may not create real numbers. It does
> look, though, that CX is pretty slow for some operations.)
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBPM-587) GPD crashes if xmlbuddy plugin is installed
by James Callaghan (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-587?page=comments#action_12343480 ]
James Callaghan commented on JBPM-587:
--------------------------------------
I don't have XML buddy either and the GDP is unusable. It just crashes as soon as I open a process. I do however have JBoss IDE 1.5.0 so that seems to be something I have in common with Carmine.
> GPD crashes if xmlbuddy plugin is installed
> -------------------------------------------
>
> Key: JBPM-587
> URL: http://jira.jboss.com/jira/browse/JBPM-587
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Graphical Process Designer
> Affects Versions: jBPM GPD 3.0.8
> Environment: Gentoo Linux / Eclipse 3.1.2
> Reporter: Matthias Germann
> Assigned To: Tom Baeyens
>
> If the Graphical Process Designer plugin and the XML Buddy Plugin are installed in the same eclipse installation, the GPD crases when opening a process definition file. The problem can be reproduced by unzipping the XML Buddy Free Edition ZIP File into the plugins directory of a eclipse installation with GPD installed.
> The GPD reports the following error when opening a jBPM process definition File:
> Unable to create this part due to an internal error. Reason for the failure: An unexpected exception was thrown.
> Detail:
> java.lang.NullPointerException
> at org.jbpm.ui.editor.DesignerContentProvider.addProcessDiagramDimension(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.editor.DesignerGraphicalEditorPage.initInput(Unknown Source)
> at org.jbpm.ui.editor.DesignerGraphicalEditorPage.init(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:152)
> at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source)
> at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:241)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552)
> at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:223)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2362)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295)
> at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:279)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:271)
> at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:178)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1021)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2867)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2572)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
> 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 org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> at org.eclipse.core.launcher.Main.run(Main.java:973)
> at org.eclipse.core.launcher.Main.main(Main.java:948)
--
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
19 years, 10 months